• 5 Posts
  • 118 Comments
Joined 1 year ago
cake
Cake day: July 25th, 2023

help-circle









  • Almost all oft their breaking changes over the last few months were about their docker-compose setup and the simplification of the same. They’ve startend out with multiple purpose-specific (micro) containers, which turned out as a Bad design decision. These changes require manual intervention but seem to be mostly finished, so I don’t expect these to be many breaking changes in the forsseeable future.

    The better you plan ahead, the fewer breaking changes you have to impose on your users.

    I agree. From what I’ve read, they now have (published) plans for what’s ahead.


  • desec.io can be used with any domain registrar and has an API with support for various ddns clients (ddclient, lego).

    deSEC is a free DNS hosting service, designed with security in mind.

    Running on open-source software and supported by SSE, deSEC is free for everyone to use.

    Edit: To clarify, desec.io does not sell/rent domains. Desec has to be set as the authoritative nameserver on the registrar, then desec can manage domain records instead of the registrar (which usually also provides their own domain hosting for “free” by default).






  • I prefer swap files over swap partitions, because it makes it my partition layout simpler to manage.

    If your using a swap partition, make sure it’s located on an encrypted partition, else it exposes data stored in RAM (encryption keys etc). With SSD’s it’s difficult to make sure this data is actually deleted, even after overwriting.

    My preferred setup for a long time was LUKS with btrfs on top. Then subvolumes for /, /home and the swap file (+ /var/cache, /var/log etc.). This gives me peace of mind nothing is unencrypted except /boot.

    Nowadays I simply use zram, which allows for a small part of RAM to be compressed for swap. It’s great, simple to setup and performs well. Imo it should be default for all desktops.



  • Online transactions require a second factor which displays the actual amount to be transferred. This works by either an app which receives the transaction data (recipient, how much) over the network, or a device which takes the bank card and is used to scan something similar to a qr code. The device then displays the transaction data.

    This makes sure a fraudulent site can’t easily change the amount or the recipient of a transaction, even if they somehow made an identical website (or close enough).

    For remote transactions (e.g. online payments), the security requirements go even further, requiring a dynamic link to the amount of the transaction and the account of the payee, to further protect the user by minimising the risks in case of mistakes or fraudulent attacks.

    https://www.ecb.europa.eu/press/intro/mip-online/2018/html/1803_revisedpsd.en.html

    It’s not perfect, especially with people using a banking app and the second factor app on the same device for convenience sake.


  • That’s a bummer. Seems like Google Pixel and Fairphone are the only ones left. I don’t even know why manufacturers wouldn’t allow for relocking or even unlocking of their phones. I can’t imagine they make much money with user data and the phone is already paid for. Warranty claims shouldn’t be much of an issue either, as modifications can be easily detected and it’s likely not a relevant amount of people anyway.


  • The banking apps I’ve tried don’t require SafetyNet, instead they use Android AOSP’s basicIntegrity. The latter doesn’t require certification by Google, but also checks whether the device is rooted and the bootloader is locked.

    This means custom ROM’s on most devices won’t pass basicIntegrity, as only Google Pixel, OnePlus and Fairphone allow for relocking the bootloader.