Either you are heavily misinformed about how difficult arch is, or you lack any confidence in your ‘Linux skill’.
Choose the system you want to achieve, follow the wiki and choose the software you want to use using it and you are good to go, it really is not that hard. You can always use archinstall.
So I’d like to split my passwords file into multiple “files”, where the unimportant logins are permanently unlocked for convenience, while the more sensitive login credentials remain encrypted until I actually need them.
And how should that protect you against an attack that has compromised your system? If the system is compromised, then an additional lock does not hinder the attacker to wait until you open it.
The tweet he commented on was indeed a nice idea, but a CEO should have more foresight that the things Trump stated in it would not be true. When you look at it now, it looks like it was more or less a threat that led to a closer relationship between “tech bros” and the current administration instead of the “take down” of them.
This is correct, i missed that part. pfSense is mentioned 259 vs. OPNsense 3 times. But only the “not nice part” is mentioned and not the hostility towards FOSS. Here are some examples https://github.com/rapi3/pfsense-is-closed-source
I have not vetted every single claim but just alone that fact that they have this closed source model is enough for not using it. OPNsense is to my knowledge fully open source.
OpenVPN is still a solid option and widely used today.
Absolutely, but Wireguard is simpler to setup and comes by default and by design with a more secure default config.
Now look at all those options you need to tune on OpenVPN.
even though the company behind it isnt perfect.
But then why recommending pfSense? OPNsense is the same with a much more FOSS friendly company behind it. Yes pfSense is at the moment ok but no reason to use it over OPNsense imho.
People should still be able to use whatever software they like without being juged by it.
Yes. And i never judged anyone running thr software, only ppl who recommend it.
Its better for people to at least start with something, rather than nothing
I am not sure about it. Personally, when i get into a new topic i like to have comparisons. They show me what is actually relevant and what i should look out for. But maybe it is just me.
I said multiple times “recommend” here, but that is actually my main problem, i would be much more ok when he simply said there is x and y also available but i use z because of 123…
This guide is heavily opinionated and simply outdated. 2 examples:
And that are only 2 points i discovered while scrolling through. Louis is a great guy but as it looks like he should leave that topic to other people.
That was a rhetorical question towards the commenter since the discussion point was not understood.
The thing is, that you only have to share public keys and never private ones. So you can only phish public keys…
How would you sync or transfer a passkey across devices without transferring the private key?
Why do you think SSH-Keys are safe against phishing? I mean it is unlikely, that someone will just send the key per mail or upload it somewhere since most ppl using SSH-Keys are more knowledgeable.
When you now get an easy one click solution to transfer Passkeys from one Cloud provider to another it will get easier to trick a user to do that. Scenario: You get a mail from Microsoft that there is a thread and that you need to transfer your keys to their cloud.
With the ability to transfer passkeys, the attack vector phishing does not sound that far fetched. Tho i have not looked into the transfer process.
We will see i guess.
You generate a second one on the other device.
Not everyone throws their E-Mail at every Text field they see.
They moved to wayland 2 years ago. https://tails.net/news/test_5.8-beta1/#index2h1
The thing is, those poor design decisions have nothing to do with those features, i claim that every feature could be implemented without “holding the compose files hostage”.
Btw. dockge does support connecting to another docker dockge instance.
No, that would make no sense and is obviously not what i meant.
But you could separate the arr stack from things like pihole with a vm. For example you could pin one thread to that VM so you will not bottleneck your DNS when you are doing heavy loads on the rest of the system. This is just one example what can be done.
Just because you do not see a benefit, does not mean there is none.
Also, VMs are not “heavy” thanks to virtualization technology built into modern hardware, VMs are quite light on the system. Yes they still have overhead but its not like you are giving up big percentages of your potential performance, depending on the setup.
You talk like there is not in between containers and VMs. You can use both.
What exactly are you referring to? ZIL? ARC? L2ARC? And what docs? Have not found that call out in the official docs.
I use a consumer SSD for caching on ZFS now for over 2 years and do not have any issues with it. I have a 54 TB pool with tons of reads and writes and no issue with it.
smart reports 14% used.
You recall wrong. ECC is recommended for any server system but not necessary.
On most systems copy pasting is heavily insecure since a lot of processes have access to the clipboard. autotype and thinga like browser extensions are considered more secure.