• 0 Posts
  • 209 Comments
Joined 1 year ago
cake
Cake day: August 18th, 2023

help-circle
  • NaN@lemmy.sdf.orgtoLinux@lemmy.mlVPS encryption
    link
    fedilink
    English
    arrow-up
    16
    ·
    1 day ago

    Encrypt them before they’re ever put there. One example I can think of is in resilio sync, which has the option for sharing a folder to an encrypted peer. Other peers encrypt it before sending anything, that peer doesn’t have the decryption keys at all.




  • They are logged, but swatting people get around it. They are suspicious “looking” calls, but so are bomb threats.

    Swatting is pretty much always a blocked number to a non-emergency line. If they are traced it is typically one of those free online voip services. It takes work and access to really get from A to B, which is why it only happens when there are awful results.

    In the US at least, 911 gets special access and calling it will always get you to your local dispatch (unless you have voip with the wrong account address). Non-emergency is just a normal phone number. If someone wants to call from out of the area or hide their number, non-emergency is how they have to do it. This is suspicious because in a real situation like “I just shot my dad” or whatever they say, nobody is taking time to look up non-emergency.




  • It’s probably something most people could learn a bit more about. On Red Hat or Fedora you don’t have to get too far out of vanilla before SELinux starts breaking things (oh, you wanted your custom systemd service to run that binary from that directory? Tough! Figure it out!), in comparison AppArmor on Ubuntu and Debian seems to get in the way a lot less. I’m not sure if that’s due to how it functions as a product or upfront work to configure it to be less intrusive.





  • One thing the article doesn’t make very clear is that for 2FA the PIN requirement comes from the site itself. If the site requires User Verification, the PIN is required. If not, it is not prompted even if set and this attack is possible. The response to the site just says they knew it.

    It is different for Passkeys. They are stored on the device and physically locked behind the PIN, but this is just an attack on 2FA where the username and password are known. (In depth it’s more than that, but for most people walking around with a Yubikey…)

    It also seems limited in scope to the targeted site and not that everything else protected by that specific Yubikey. That limits how useful this is in general, which is another reason it is sort of nation-state level or an extremely targeted attack. It’s not something your local law enforcement are going to use.

    I think the YubiHSM is a much more appealing target, but that isn’t so much a consumer device and has its own authentication methods.


  • The bot demonstrated very well what this article is about. I don’t know the internals, but I also can’t image the bot was using the best and most expensive ways of doing analysis.

    It was pretty bad at “getting the point” even when it was obvious, a better system should be able to do so. Sometimes the point is more difficult to discern and there has to be some judgement, you can see this in comments sometimes where people discuss what “the point” was and not just the data. I imagine an AI would have some difficulty determining what is worth summarizing in these situations especially.







  • Somewhat. One, a system can be bootable without the entries because they are just pointers to the actual bootloader, so even if windows does the stupid and deletes them it isn’t the end of the world. It does depend on your specific firmware though.

    Also two, you can write them again with a single line in efibootmgr, they’re just saying “if I click Fedora load the shim from the EFI system partition on disk 1”.

    This is very different than the old world where windows would delete your bootloader entirely and the MBR couldn’t be easily explored. They live in the efi system partition instead - or at least the shim does- and typically every OS leaves the other ones alone (even Windows, except in this case, although it didn’t touch the shim itself).

    The initial comment was about the bootloader and really only applies to MBR partitions.



  • NaN@lemmy.sdf.orgtoLinux@lemmy.ml33 years ago...
    link
    fedilink
    English
    arrow-up
    4
    ·
    21 days ago

    XNU is the kernel in Darwin, XNU is an Apple product derived from BSD and Mach. Darwin has a lot of FreeBSD in it.

    Apple shares that code though. It’s on GitHub. There used to be Darwin distributions.

    Your Android example doesn’t make very much sense either. The largest Android issues are typically hardware lockdown. Nothing about the GPL prevents someone building an ad platform that spies on you, it just makes them share the source code for it. Google’s licensing choices means they don’t share the source code for the Google pieces they put on top of AOSP, the entire project means people can build the alternatives though.

    The lawsuits were about AT&Ts proprietary license. BSD and similar licenses are not that.