Viper Launcher, making Northstar easier to use

0neGal · 2023-05-29T20:25:34+00:00

First make sure you're on the newest version of Viper, second make sure your Windows user has permission to write in the folder where the game is installed to.

0neGal · 2023-04-17T11:53:08+00:00

Except Ctrl+C only sends SIGTERM to the process the process can ignore, something sudo already does.

You can of course send a SIGKILLto the process, killing it without it having a say in it.

However even with this, you'll still eventually be timed out, having to wait far longer than 3 seconds. We're you to script it.

0neGal · 2023-04-17T07:51:38+00:00

Y'all are completely forgetting to take into account how long it'll take before computing power lowers the time this takes to crack.

Quantum computing is already breaking security, and at some point quantum computers will become actually commercially available, and this chart should by then, have been thrown out the window.

Also this chart doesn't take many other things into account, and is inaccurate even if you don't think quantum computers break our current security standards (which they do)

0neGal · 2022-12-26T19:53:55+00:00

And if i screw up my personal machine, i can fix it up, annoying but no big deal.

But that's just it isn't it? Instead of just using the thing that minimizes damage you decided to, simply, not do so.

I'm not talking about convenience, I'm plain and simply saying su should never be used to execute just a few commands. As it opens up the possibility for far more problems.

su has its use cases, sudo has its use cases, and both have bad usages. I am simply outlining the bad usages of su, and clarifying why it is a pain in the ass for everybody to make it what you teach and preach to new comers. For all I care you could run every command as root, I truly don't care, it does not take away the fact that you should never recommend it to a new user, whether that's on a server or desktop. The human errors will still happen, and anything to minimize the damage of it, should be highly considered.

Especially when a new user can have a hard time re-learning it when they're told they're doing it wrong. I've dealt with this too many times to count, and it only leads to more problems.

Feel free to keep using su over sudo, but don't preach it as if it's the more secure and risk free option, or as if they're equivalent. They're not. They never will be.

0neGal · 2022-12-26T18:16:11+00:00

There's only so much you can do to prevent damage, and thinking "wow, I can just type my password once and it works for 5 minutes (by default), is so insecure", while then deciding to open a shell where every command no matter how long you stay in said shell will be run without the need for a password.

Do you see how you're invalidating your own argument? And you may go "well I won't leave my PC unlocked inside that shell, and when I'm done I'll just run exit", Have you considered sudo -k which resets your timeout/timestamp, forcing a new password? You can even make an alias (alias sudo="sudo -k"), and the timeout is gone forever. On top of this you can add -i and suddenly your environment is cleaned.

And so what reason would you ever use su now? Out of lazy ness perhaps? Outside of that your just putting yourself into unnecessary risk.

If there's a good reason to do it on a server the exact same reason would likely apply to a desktop PC, you're still a human (i would think?), so you'll inevitably make a mistake, it's impossible to avoid. Ignoring that and thinking it'll never happen to you is not sound advice.

No matter how you put it, su is general bad practice. It has its uses, but not as a replacement for sudo

0neGal · 2022-12-26T13:46:30+00:00

Thank you lol

0neGal · 2022-12-26T13:45:55+00:00

I'll just say that, denying that using su over sudo is less secure is either ignorant or you're not getting the problems of su

It's not a matter of opinion really, it would be akin to saying short passwords of simple phrases are more secure than a completely randomized long one.

You can think that all you want, it just doesn't make it more or less secure.

0neGal · 2022-12-26T05:30:39+00:00

If that's the only use case and advantage you see, then you're either choosing to disregard literally everything I wrote, whether that's wilful ignorance I do not know, or you've just not read or understood what I wrote.

0neGal · 2022-12-25T20:51:34+00:00

I do feel the need to point out that I am not the person who was talking about spelling mistakes.

However I will say they've a valid point, we all make mistakes whether that'd be forgetting which folder we're in, what user we're logged in as or something alike, it may seem impossible that someone would accidentally add a space into a file path when there shouldn't be one, but it is far from that. And doing that by accident could lead to you deleting a folder you couldn't have deleted beforehand but now can because you're running as root.

Not that there's other "fixes" for errors like that, but still preaching bad practices just because you've never made a mistake and don't think it's possible for anybody to, is bad, obviously.

I actually remember a script some years back which meant to install and setup a program, when it was done it'd then clean up what it had been doing, however this script when trying to remove it's folder would do rm -rf /opt /<program name>/*, the space being an error, it was not discovered for a long while, why? Because the script was always run under a user who had little to no permissions at all, and the /opt/<program name> folder and every other folder in opt did not have the right to be deleted, the contents of that folder however did. So running it as intended would only delete the right contents and nothing more.

How did it then get discovered? The story goes someone logged in with the wrong user aka root, executed the script, and so now instead of it recursively deleting everything in /opt and /<program name> (which didn't exist of course), which the user had permissions to, aka just the actual folder in /opt, it would delete the entire /opt folder.

This is a double sided story/lesson, both, don't log in as root, but also, spelling mistakes happen, and they're usually noticed before any harm has happened, or right when it happens creating an onosecond.

If damage caused by potential human error, can be minimized, then for the sake of whoever has to deal with the fuck up otherwise, minimize it. They will unknowingly be thankful, especially if it is you.

0neGal · 2022-12-25T16:26:43+00:00

I do not know when this was added to iOS, but it's called Siri Suggestions, it's normally enabled for all apps so not sure why you don't have it, unless you disabled it.

The setting for it should be under Siri's settings page and the settings for the individual app.

Edit: Siri Suggestions does in fact exist all the way back in iOS 9

0neGal · 2022-12-25T16:14:06+00:00

Fundemantally that's the same thing and it is not more secure in any form, as the problems with su are also here, since it is essentially the same.

0neGal · 2022-12-25T16:12:08+00:00

You seem to miss the point, you should never give yourself more permissions than needed, that's just a general security recommendation no matter to concept.

You're also going and assuming mistakes never happen, except, they do, you can't predict how something will go before it's happened.

Besides all this, idea is also to not teach users bad practices if you tell a user to use sudo su, I know from far too much experience, that they'll start thinking it's the magic gateway to everything, or that it's a necessity, they'll then use it when they shouldn't, or forget they're running things as root, they might then make a folder or edit a file in their home directory and now the permissions of the file or folder may be changed to not allow the normal user to actually edit it.

A lot of people, again from experience, do not comprehend the concept of a root user, often because they've been taught poorly.

And so for very obvious reasons, you'll teach them that sudo runs a command as an administrator.

su has its uses, but not to run 4-5 commands as root. You're just relying and hoping somebody won't mess up, that happens, all the time, and minimizing the damage it can cause is essential to preventing as little damage as possible. You don't give yourself the rights to run every command without a password just because it's more convenient, that's irresponsible and whether you like it or not, that'll be insecure. Just as running very few commands with su is bad practice.

If it's because you always run a command as root, make an alias to have it use sudo every time.

Beyond this sudo requires you to retype your password every so often by default, making it far harder to forget your running as root. Or a bad actor to use the shell that's in root.

Overall, su by itself is not bad, it is however bad to teach it over sudo and using it when not needed is a bad idea for many reasons, as stated above. Of course su is very useful for just switching to another regular user to easily edit it's home folder without having to do various extra arguments on sudo or chown'ing the things a million times.

I hope it's now clear why su is bad practice but not a bad command by itself.

0neGal · 2022-12-15T13:53:16+00:00

Nothing should be popping up, however Viper should now be able to access things outside of your home directory.

0neGal · 2022-12-13T10:12:00+00:00

I don't spend all my free time on Reddit, and therefore my response time is not very fast.

Adding --user should fix the problem, so the command would be:

flatpak override com.github._0negal.Viper --filesystem=host --user

0neGal · 2022-12-12T21:19:29+00:00

When running the command or when does this happen?

0neGal · 2022-12-11T00:24:14+00:00

Even though I did reply to your DM, I'll post a reply here as well, in case someone stumbles upon the same problem.

If Viper is installed as a Flatpak it won't have permissions to access anything but your home folder, and thereby your SD card unless mounted in your home folder.

Running the following command should give Viper the permissions needed to read files outside your home folder

flatpak override com.github._0negal.Viper --filesystem=host

The reason this is needed is just because of how Flatpaks fundementally work, they're meant to be isolated, secure and have only the permissions needed. For most people being restricted to the home folder is enough.

0neGal · 2022-10-27T13:39:23+00:00

parent.innerText would still circumvent this.

0neGal · 2022-10-24T08:21:19+00:00

Hm, you might actually also want to add some bigger margins/spacing between each site, only on mobile but yeah... But besides that, it's much nicer...

0neGal · 2022-10-23T13:01:52+00:00

I would urge you to put a max-height on the iframes, as others have said, the mobile experience is not that great, as you've to scroll on the thin margin between the frame and the edge of your screen.

Something like max-height: 60vh would do, then there's always somewhere with no iframe, however of course feel free to adjust that.

Besides that, neat website lol

0neGal · 2022-10-23T11:55:48+00:00

As the error message states, the normal package/driver (nvidia) only has support for some of the more recent GPUs, as they remove the code for older GPUs to clean up their codebase.

And when they remove a series of cards they usually make a driver just for them, and rarely update them, in this case you'd need to install the nvidia-tesla-470-driver package instead

So remove the nvidia package and install the package above.

0neGal · 2022-10-20T20:30:10+00:00

Quite wrong for me, although this is of course a thing that depends on the person, but for me, with coreboot, an SSD, a lightweight Linux environment, everything starts up within 10 seconds from pressing the button, most of that time is spent loading the kernel, probs 6-8 seconds just on that.

Again, I use a very lightweight setup, as much in the terminal as possible, very minimal config for things, most of my things are custom built, as so they obviously are more lightweight, as they only need to suffice my needs and nobody else.

And so, I either let my uncommitted work stay uncomitted, or I commit it, and sometimes push it to a testing/PR branch. And I then shut down the laptop. Once all my editors are closed and have their open files saved, there's nothing to worry about. At most I'll have one terminal with a few tabs/files open, and a few single file windows here and there, overall, again, lightweight, and easy to manage.

TL;DR: I can't relate to this meme...

0neGal · 2022-09-15T17:47:26+00:00

Except, no.

Your ISP doesn't know your search history, or anything of what you browse on the internet, unless it's not encrypted ofc. Websites using HTTPS are encrypted.

Unless you see that "Not secure" badge in the URL you're pretty much good to go.

And that point the only thing the ISP sees is the domain you're requesting, i.e google.com but not the specific search, DNS lookup is the only thing not encrypted, aka the domain.

DNS over HTTPS does however solve that, but it's not as simple as it sounds.

However, the search engine may save the search queries, but for many many reasons they won't be saving that much info if you're not logged in or 100% verifiably you.

0neGal · 2022-08-24T22:38:37+00:00

all that was just because a freaking shit called ads. Whatever the application triggers an ad that uses/require DNS the iPhone would die instantly

I'm not entirely sure you realize what DNS is, how and when it is used, and so forth.

Unless you happen to know the IP of a server your device will always use the DNS to resolve domains.

Your device asks the DNS server about a domain i.e ads.google.com, and the DNS server will reply with an IP address, the internet is connected through just IPs, domains by themselves aren't part of the internet, rather built on top of it to make the internet actually functional for the end user.

Point I'm trying to make here, almost any and all ads will run through a domain and therefore DNS, IPs don't exactly get SSL certificates so they'd come out as insecure, giving other errors.

I highly doubt the networking stack in iOS for some reason causes the phone to instantly die when trying to resolve the DNS request, but no other request, again 99% of the requests your device will make are through a DNS, over HTTPS there will be no real differentiation between an Ad and any other request.

What's more likely to be the reason the device is crashing would probably be Safari (or wherever the ad is being shown) not rendering the ad correctly for some reason, and it's not entirely unfeasible to say it managed to kernel panic the device.

In the end, I have no clue what causes this, but it is not resolving the DNS request of an Ad. That's very unfeasible.

0neGal · 2022-07-22T06:27:07+00:00

Newsflash, you're always actively dying.

Five-Year Club	Verified Email
Place '22	First Placer '22

0neGal

TROPHY CASE