TPM is not only used by the system encryption. But no i do not use it for it. Not because of privacy, cause of security reasons.
TPM is not only used by the system encryption. But no i do not use it for it. Not because of privacy, cause of security reasons.
As for a backup, I figured I would have to raid it.
RAID is not a backup. Never ever consider having the data on a RAID to be backed up.
Basically, when you do not run server side transcoding and instead rely on client side support you will run from time to time into issues. Jellyfin does not have the ppl to get every client to work with all the different formats on every hardware.
1080 h264/h265 does not say much about the media format. Those codec differentiate in things like Chroma (4:2:0; 4:4:4, etc) or in color depth like 8 or 10 bit. So not every h264 media file does run on the same hardware. Audio codecs are even more complicated.
I think since i setup my hardware transcoding I ran into a not playable file once. But depending on the hardware it can be worse. On android TV you may have to play around with the settings.
I understand that this can be a deal breaker for some ppl.
Yes you have. Please explain to me the additional context. I seem to not grasp it.
What else are they doing then asking? Doing some marketing around it? If you get pressured by that you should not lead a company.
If you don’t want a permissive license don’t license your software that way, your motivation clearly doesn’t align with these licenses anyway.
Why does asking for money not align with the licenses?
Any software potentially has security issues. The matter is how they deal with it.
You still need to store those secrets. You would probably refer to a keychain but in the end it is still a password/secret manager.
And the current implementation is not really better, services like paypal still do not allow you to use a passkey on the desktop.
That is why you use an open source manager. KeePassXC for example is not owned by a for-profit company.
Losing the container due to corruption disk failure etc can be easily managed with backups.
Losing the password. Yes this is a real valid scenario. I personally have no problem with that i manage fine for years without having to write it out on paper to backup it. A solution would be to actually write that password out somewhere and hide it/ put it into a safe. An attack then needs to attack both, depending if you use disk encryption it is easy to get access to the password safe or not. There are other things to consider, like you could try to hide it in a very long string of characters like 20 pages of random characters, even if you forget it you will be able to find it cause it is very likely that you remember a few characters.
I know a lot of services that log you out regularly. Or need a password when you change settings or whatever.
Well yea people with the “I don’t care. I just press the button and it always works” model do exist.
WTF no. Password managers are reasonable secure. That is no i don’t care behavior.
And when you are worried about password managers you should not use cookies. Stealing a cookie is much more simple than stealing and encrypting your password safe.
Differences in the thread model. And of course convince. How to you backup your paper regulary? How do you transfer it? What if you need to access a pasdword when you are not home?
Most ppl will just reuse or use very weak passwords when they have to write every password they have to enter.
Best we have and probably will ever have on the current web. Not sure what the problem is with password managers?
I am talking about the fork. It is operated by someone else.
The syncthing fork on f-droid is still an option. An issue has been opened on the github repo. Lets see what will happen with the fork
No Web Screenshots are included.
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.
Wasn’t the CVE fixed in a reasonable time frame? I seriously doubt that the maintainers would have ignored it if it wouldn’t have been discussed so publicly.
AFAIK, to exploit it, you need network access to CUPS then add the printer and then the client needs to add/select a new printer on the client device and actively print something.
If CUPS is reachable from the internet, then the system/network is misconfigured anyway, no excuse for ignoring the issue but those systems have other sever issues anyway.