Remotely Unlock Fully Encrypted Debian Squeeze

Discussion in 'HOWTO-Related Questions' started by slothrop, Apr 21, 2012.

  1. slothrop

    slothrop New Member

    I followed the tutorial[1], but when I try and ssh to my server, I get a "Connection Refused" error.

    I have tried changing the port in /etc/defaults/dropbear and allowing that port in ufw (22 is disabled). But nmap shows that at boot the new port is closed. In fact, all ports seem closed.

    How can I make sure that a port is open so I can unlock the LUKS container?


    1. http://www.howtoforge.com/remotely-unlock-fully-encrypted-debian-squeeze
     
    Last edited: Apr 21, 2012
  2. sjau

    sjau Local Meanie

    you use debian squeeze?
     
  3. slothrop

    slothrop New Member

    Yes. x86_64:
    Code:
    Distributor ID: Debian
    Description:    Debian GNU/Linux 6.0.3 (squeeze)
    Release:        6.0.3
    Codename:       squeeze
    
     
  4. sjau

    sjau Local Meanie

    once the initrd is booted, can you actually ping the server?
     
  5. slothrop

    slothrop New Member

    Yes: I can ping the server, but nmap shows all the ports as closed.
     
  6. sjau

    sjau Local Meanie

    when you can ping it, it means the networking is up so the altered initrd works.... as for the port, no idea...

    Setup an encrypted Squeeze in a vm, run the script and try if you can remotely unlock it - well, you can.... so you have something configured somewhere that prevents that. I can't help you with that.
     
: debian, dropbear, luks, ssh

Share This Page