The following change is part of the update from 0.1 to 0.2:
--ssh-key Add the given ssh public key file (absolute path)
- to root's authorized keys and install openssh-server
+ to user's authorized keys and install openssh-server (WARNING: this has strong security implications)
...
fi
# we have a key, add it
chroot root apt-get install --force-yes -y openssh-server
- mkdir root/root/.ssh
- cp "$SSHKEY" root/root/.ssh/authorized_keys
+ mkdir root/home/$VMUSER/.ssh
+ cp "$SSHKEY" root/home/$VMUSER/.ssh/authorized_keys
+ chroot root chown -R $VMUSER:$VMUSER /home/$VMUSER/.ssh
+}
+
I don't think it is part of this bugfix in particular, but this breaks the behavior between the version of ubuntu-vm-builder in hardy and the behavior of the version in hardy-proposed and is IMHO unsuitable for a SRU.
I also couldn't find a entry in the changelog of 0.1 to 0.2 that indicates this change. The upload breaks ssh login for me.
The following change is part of the update from 0.1 to 0.2:
--ssh-key Add the given ssh public key file (absolute path)
( WARNING: this has strong security implications) .ssh/authorized _keys $VMUSER/ .ssh $VMUSER/ .ssh/authorized _keys
- to root's authorized keys and install openssh-server
+ to user's authorized keys and install openssh-server
...
fi
# we have a key, add it
chroot root apt-get install --force-yes -y openssh-server
- mkdir root/root/.ssh
- cp "$SSHKEY" root/root/
+ mkdir root/home/
+ cp "$SSHKEY" root/home/
+ chroot root chown -R $VMUSER:$VMUSER /home/$VMUSER/.ssh
+}
+
I don't think it is part of this bugfix in particular, but this breaks the behavior between the version of ubuntu-vm-builder in hardy and the behavior of the version in hardy-proposed and is IMHO unsuitable for a SRU.
I also couldn't find a entry in the changelog of 0.1 to 0.2 that indicates this change. The upload breaks ssh login for me.
Thanks,
Michael