home.social

#cryptsetup — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #cryptsetup, aggregated by home.social.

  1. Bonus: I can wake up the desktop through Home Assistant.

    And with VPN through Wireguard I then have access to my desktop system, its files and services that I need in rare cases.

    I used this article
    cyberciti.biz/security/how-to- from [email protected] . Thank you.

    2/2

    #homeassistant #cryptsetup #dropbear #ubuntu

  2. Bonus: I can wake up the desktop through Home Assistant.

    And with VPN through Wireguard I then have access to my desktop system, its files and services that I need in rare cases.

    I used this article
    cyberciti.biz/security/how-to- from [email protected] . Thank you.

    2/n

    #homeassistant #cryptsetup #dropbear #ubuntu

  3. Bonus: I can wake up the desktop through Home Assistant.

    And with VPN through Wireguard I then have access to my desktop system, its files and services that I need in rare cases.

    I used this article
    cyberciti.biz/security/how-to- from [email protected] . Thank you.

    2/2

    #homeassistant #cryptsetup #dropbear #ubuntu

  4. Bonus: I can wake up the desktop through Home Assistant.

    And with VPN through Wireguard I then have access to my desktop system, its files and services that I need in rare cases.

    I used this article
    cyberciti.biz/security/how-to- from [email protected] . Thank you.

    2/n

    #homeassistant #cryptsetup #dropbear #ubuntu

  5. Bonus: I can wake up the desktop through Home Assistant.

    And with VPN through Wireguard I then have access to my desktop system, its files and services that I need in rare cases.

    I used this article
    cyberciti.biz/security/how-to- from [email protected] . Thank you.

    2/2

    #homeassistant #cryptsetup #dropbear #ubuntu

  6. Today's desktop computer challenge: For the case I need access to my home desktop from remote, I trigger boot through wake on LAN and then remotely unlock the encrypted hard disks through SSH.

    The challenge: Two encrypted hard disks. Solution: For the second hard drive add a key file located on the first hard disk as additional slot through cryptsetup, update the configuration in `/etc/crypttab`. Done.

    1/2

    #ubuntu #dropbear #cryptsetup #wol

  7. Today's desktop computer challenge: For the case I need access to my home desktop from remote, I trigger boot through wake on LAN and then remotely unlock the encrypted hard disks through SSH.

    The challenge: Two encrypted hard disks. Solution: For the second hard drive add a key file located on the first hard disk as additional slot through cryptsetup, update the configuration in `/etc/crypttab`. Done.

    1/n

    #ubuntu #dropbear #cryptsetup #wol

  8. Today's desktop computer challenge: For the case I need access to my home desktop from remote, I trigger boot through wake on LAN and then remotely unlock the encrypted hard disks through SSH.

    The challenge: Two encrypted hard disks. Solution: For the second hard drive add a key file located on the first hard disk as additional slot through cryptsetup, update the configuration in `/etc/crypttab`. Done.

    1/2

    #ubuntu #dropbear #cryptsetup #wol

  9. Today's desktop computer challenge: For the case I need access to my home desktop from remote, I trigger boot through wake on LAN and then remotely unlock the encrypted hard disks through SSH.

    The challenge: Two encrypted hard disks. Solution: For the second hard drive add a key file located on the first hard disk as additional slot through cryptsetup, update the configuration in `/etc/crypttab`. Done.

    1/n

    #ubuntu #dropbear #cryptsetup #wol

  10. Today's desktop computer challenge: For the case I need access to my home desktop from remote, I trigger boot through wake on LAN and then remotely unlock the encrypted hard disks through SSH.

    The challenge: Two encrypted hard disks. Solution: For the second hard drive add a key file located on the first hard disk as additional slot through cryptsetup, update the configuration in `/etc/crypttab`. Done.

    1/2

    #ubuntu #dropbear #cryptsetup #wol

  11. LUKS/Fedora question: Does anybody know if there is a way to increase the number of passphrase attempts to unlock the encrypted partition at boot before cryptsetup failure ?

    #Linux #Fedora #LUKS #CryptSetup #GNOME

  12. LUKS/Fedora question: Does anybody know if there is a way to increase the number of passphrase attempts to unlock the encrypted partition at boot before cryptsetup failure ?

    #Linux #Fedora #LUKS #CryptSetup #GNOME

  13. LUKS/Fedora question: Does anybody know if there is a way to increase the number of passphrase attempts to unlock the encrypted partition at boot before cryptsetup failure ?

    #Linux #Fedora #LUKS #CryptSetup #GNOME

  14. My experience with #FlashDrives recently has been mixed. I have no problem in encrypting them with #LUKS, using #cryptsetup or with formatting a partition with #Btrfs, for instance, using #gparted and doing other tinkering with #Gnome #disks. But the problem has been with the actual drives themselves. The cheaper ones seem to have quite a few bad sectors, etc. and so they’re not really reliable for medium term storage.

    1/2

    #Hardware #StorageDevices #Unix #GNU #Linux #Fedora

  15. My experience with #FlashDrives recently has been mixed. I have no problem in encrypting them with #LUKS, using #cryptsetup or with formatting a partition with #Btrfs, for instance, using #gparted and doing other tinkering with #Gnome #disks. But the problem has been with the actual drives themselves. The cheaper ones seem to have quite a few bad sectors, etc. and so they’re not really reliable for medium term storage.

    1/2

    #Hardware #StorageDevices #Unix #GNU #Linux #Fedora

  16. My experience with #FlashDrives recently has been mixed. I have no problem in encrypting them with #LUKS, using #cryptsetup or with formatting a partition with #Btrfs, for instance, using #gparted and doing other tinkering with #Gnome #disks. But the problem has been with the actual drives themselves. The cheaper ones seem to have quite a few bad sectors, etc. and so they’re not really reliable for medium term storage.

    1/2

    #Hardware #StorageDevices #Unix #GNU #Linux #Fedora

  17. My experience with #FlashDrives recently has been mixed. I have no problem in encrypting them with #LUKS, using #cryptsetup or with formatting a partition with #Btrfs, for instance, using #gparted and doing other tinkering with #Gnome #disks. But the problem has been with the actual drives themselves. The cheaper ones seem to have quite a few bad sectors, etc. and so they’re not really reliable for medium term storage.

    1/2

    #Hardware #StorageDevices #Unix #GNU #Linux #Fedora

  18. My experience with #FlashDrives recently has been mixed. I have no problem in encrypting them with #LUKS, using #cryptsetup or with formatting a partition with #Btrfs, for instance, using #gparted and doing other tinkering with #Gnome #disks. But the problem has been with the actual drives themselves. The cheaper ones seem to have quite a few bad sectors, etc. and so they’re not really reliable for medium term storage.

    1/2

    #Hardware #StorageDevices #Unix #GNU #Linux #Fedora

  19. In case someone else is wondering why linux luks hard disk encryption is usually within a lvm container: that way you only need one password to unlock multiple partitions.

    (found out the hard way)

    #linux #cryptsetup #harddisk #encryption

  20. In case someone else is wondering why linux luks hard disk encryption is usually within a lvm container: that way you only need one password to unlock multiple partitions.

    (found out the hard way)

    #linux #cryptsetup #harddisk #encryption

  21. In case someone else is wondering why linux luks hard disk encryption is usually within a lvm container: that way you only need one password to unlock multiple partitions.

    (found out the hard way)

    #linux #cryptsetup #harddisk #encryption

  22. In case someone else is wondering why linux luks hard disk encryption is usually within a lvm container: that way you only need one password to unlock multiple partitions.

    (found out the hard way)

    #linux #cryptsetup #harddisk #encryption

  23. In case someone else is wondering why linux luks hard disk encryption is usually within a lvm container: that way you only need one password to unlock multiple partitions.

    (found out the hard way)

    #linux #cryptsetup #harddisk #encryption

  24. So today I tired #mkfs.btrfs and this works. I was using #gparted, which can’t create #encrypted file systems and so I created a blank (cleared) one, used #cryptsetup to create the #encryption on the device, and then created the brtrfs file system.

    #GNU #FreeSoftware

  25. So today I tired #mkfs.btrfs and this works. I was using #gparted, which can’t create #encrypted file systems and so I created a blank (cleared) one, used #cryptsetup to create the #encryption on the device, and then created the brtrfs file system.

    #GNU #FreeSoftware

  26. So today I tired #mkfs.btrfs and this works. I was using #gparted, which can’t create #encrypted file systems and so I created a blank (cleared) one, used #cryptsetup to create the #encryption on the device, and then created the brtrfs file system.

    #GNU #FreeSoftware

  27. So today I tired #mkfs.btrfs and this works. I was using #gparted, which can’t create #encrypted file systems and so I created a blank (cleared) one, used #cryptsetup to create the #encryption on the device, and then created the brtrfs file system.

    #GNU #FreeSoftware

  28. So today I tired #mkfs.btrfs and this works. I was using #gparted, which can’t create #encrypted file systems and so I created a blank (cleared) one, used #cryptsetup to create the #encryption on the device, and then created the brtrfs file system.

    #GNU #FreeSoftware

  29. Does someone have a working #nixos setup where they decrypt their drive via #cryptsetup that they access remotely via #tailscale?

    That's what I am building for my new working machine.

    Also WakeOnLan (via local network though).

    :boost_ok: #followerpower

  30. Does someone have a working #nixos setup where they decrypt their drive via #cryptsetup that they access remotely via #tailscale?

    That's what I am building for my new working machine.

    Also WakeOnLan (via local network though).

    :boost_ok: #followerpower

  31. Does someone have a working #nixos setup where they decrypt their drive via #cryptsetup that they access remotely via #tailscale?

    That's what I am building for my new working machine.

    Also WakeOnLan (via local network though).

    :boost_ok: #followerpower

  32. Does someone have a working #nixos setup where they decrypt their drive via #cryptsetup that they access remotely via #tailscale?

    That's what I am building for my new working machine.

    Also WakeOnLan (via local network though).

    :boost_ok: #followerpower

  33. Does someone have a working #nixos setup where they decrypt their drive via #cryptsetup that they access remotely via #tailscale?

    That's what I am building for my new working machine.

    Also WakeOnLan (via local network though).

    :boost_ok: #followerpower

  34. Does someone have a working #nixos setup where they decrypt their drive via #cryptsetup that they access remotely via #tailscale?

    That's what I am building for my new working machine.

    Also WakeOnLan (via local network though).

    :boost_ok: #followerpower

  35. Does someone have a working #nixos setup where they decrypt their drive via #cryptsetup that they access remotely via #tailscale?

    That's what I am building for my new working machine.

    Also WakeOnLan (via local network though).

    :boost_ok: #followerpower

  36. Does someone have a working #nixos setup where they decrypt their drive via #cryptsetup that they access remotely via #tailscale?

    That's what I am building for my new working machine.

    Also WakeOnLan (via local network though).

    :boost_ok: #followerpower

  37. Does someone have a working #nixos setup where they decrypt their drive via #cryptsetup that they access remotely via #tailscale?

    That's what I am building for my new working machine.

    Also WakeOnLan (via local network though).

    :boost_ok: #followerpower

  38. Does someone have a working #nixos setup where they decrypt their drive via #cryptsetup that they access remotely via #tailscale?

    That's what I am building for my new working machine.

    Also WakeOnLan (via local network though).

    :boost_ok: #followerpower

  39. USBのケースに2.5インチHDDを?

    ?れて初期化しました.

    LUKSで暗号化のためにCryptsetupを,透過圧縮,重複排除も使いたいということでBtrFSを利用しました.

    […]

    https://matoken.org/blog/2024/11/12/initialize-usb-hdd-with-luks-btrfs/

  40. Восстановление данных с зашифрованного Linux тома с помощью cryptsetup

    В этой статье мы разберем восстановление данных с зашифрованного с помощью LUKS тома NAS. Внимание : в самом худшем случае для восстановления данных этим способом потребуется свободное место равное двум объемам зашифрованного раздела. Например, если у вас есть зашифрованный раздел на 1 ТБ, то необходимо иметь 2 ТБ свободного места. В лучшем случае (незначительные повреждения) понадобится один объем свободного дискового пространства. Также обращаем внимание, что вам НУЖНО ЗНАТЬ пароль, который использовался для шифрования тома Для примера мы будем использовать диск от QNAP с зашифрованном разделом. 1. Подключаем диск от QNAP к компьютеру с помощью USB или SATA. После чего нужно любым доступным способом создать образ зашифрованного раздела. Для примера мы будем использовать программу Vолга. Выбираем раздел QNAP и начинаем создание образа. Мы советуем сохранить образ в формате .img (посекторный RAW образ) на любой внешний диск.

    habr.com/ru/articles/855290/

    #Шифрование #luks #cryptsetup #зашифрованный_раздел #восстановление_данных #расшифровка_данных