Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)LE
Posts
15
Comments
2,750
Joined
2 yr. ago

  • Once a browser has seen an HSTS flag it will never attempt a non-TLS connection to that site (unless it successfully makes a TLS connection and the flag is gone).

    This error is caused by a bad certificate. It can show up if your certificate expired, for instance. It's confusing that the HSTS error takes precedence, I think the bad certificate should take precedence but there you have it.

    My money is on the hospital trying to use TLS stripping.

  • Personally I would take this opportunity to segregate /home and / on two distinct SSDs. You can upgrade them separately in the future, optimize each of them for different purposes, you can fuff around with system partitions and trying new distros and whatnot without touching home etc.

    There's nothing outstanding to gain from RAID0 if you don't need the increase in speed. You could make an argument for RAID1 but unless you actually need 100% availability, again, not worth the complications. Take frequent backups (preferably incremental) and that's it.

  • Firefox Sync was purposefully built too, they didn't wake up one day to find it on the porch in a basket.

    It syncs passwords, works on desktop and mobile and can do some other cool stuff — syncs tabs and bookmarks, alerts you to password breaches, send tabs from one device to another, lets you export your passwords etc. It's a good password manager.

  • There are alternatives if you want to host your calendar and contacts and sync them securely. You could use Radicale and put a reverse proxy in front of it (Nginx Proxy Manager makes it easy to set up and easy to get and renew certificates).

  • Unfortunately it's full of specialist subs and useful walkthroughs, tutorials, answers and so on. It's impossible to replicate the work of so many years.

    Not only do we need Reddit, we need to get a hold of post archives (as recent as possible until they limited the API) and make them searchable offline.

  • If you're in the US (or Japan, they also restrict some models there) you can visit the unlock pages (select a model from the list on the page I linked) and see what they say. Maybe they don't restrict all models, or maybe they don't restrict older/cheaper models. I'm not in the US so I never get to see the message directly, I've only seen in other people's screenshots.

    Also I'm not 100% if they give you the message if they see you have an American IP, or wait until you enter the IMEI to slap you down.

  • Just to be clear, I'm talking about bootloader unlock (so you can root it and install custom ROMs) not carrier unlock. Normally Sony offer bootloader unlock codes on their website, but not for US models.

    Carrier (network) lock and unlock is done by the carriers, manufacturer doesn't care.

  • Normally I wouldn't worry about it, Samsung just apes everything Google does. It's part of their tug of war, basically Samsung is saying "if you ever pull a Huawei on me and disable every Google feature I'll still have a copy of everything".

    Then again the US market is wierd so I don't know. You can unlock Sony bootloaders everywhere else without a hitch but they cut a deal with US carriers so they won't give unlock codes to US models. If Sony did deals like that so can Samsung.

  • Same here. iOS is so severely limited compared to Android it would be unusable to me as an phone.

    As a tablet I use it 99% for streaming apps (music and series) that I put on while cooking or doing chores, 1% as a backup device for things like access to my bank app.

  • Similarly, a flower pot falling on your head is not a hypothetical, it just hasn't happened to you.

    But does it mean you should wear a helmet every time you go outside?

    To begin with, the probability of keylogging being used in an attack against you is abysmal. Not because it can't be done, but because it's a complicated, inefficient attack, and if the attacker can run code on your machine there are much better ones.

    Secondly, keylogging is still possible on Wayland, if the malicious code can attach to the relevant processes. Such as a vulnerability in your browser, which also happens to be a place where you type passwords and CC numbers a lot.

    Third, as Wayland evolves it will have to develop better IPC features. You can't have a functional desktop with zero communication. And we'll be back to square one.

    Fourth, desktop communication is not even that sensitive. 99% of it is stuff like "window id 0x09123 was maximized".

    Last but not least, if keylogging were a real issue, don't you think it would have been addressed in the 40 years that X11 and Xorg have been around? It's fascinating how some people think that Wayland was the first to discover this previously completely unknown threat that threatens to doom us all.