Aaanyways, I do have one fairly serious problem (despite the severity of this bug report ;). The files in ~/.lsh/authorized_keys_sha1/ aren't human-readable, and lsh-authorize doesn't store key comments anywhere else. This might actually be a security concern; if I can't figure out which key to delete now that a host I connect from is decommissioned, I'll leave it there.
Hrrm, if you at least know your key, you can try something like this to find out which key file authorizes it.
--CUT-- #! /bin/sh
usage () { echo Usage: $0 }
while [ $# != 0 ]; do case $1 in -help | --help | --hel | --he) usage exit 0 ;; --*) echo Unknown option $1 usage exit 1 ;; *) break ;; esac
options="$options $1" shift done
if [ $# != 0 ] ; then usage exit 0 fi
: ${SEXP_CONV:=sexp-conv} : ${LSH_EXPORT_KEY:=lsh-export-key}
if type "$SEXP_CONV" >/dev/null 2>&1 ; then : ; else echo "Can't find the sexp-conv program" exit 1 fi
if type "$LSH_EXPORT_KEY" >/dev/null 2>&1 ; then : ; else echo "Can't find the lsh-export-key program" exit 1 fi
if [ -d $HOME/.lsh/authorized_keys_sha1 ] ; then echo "Authorized keys:" for key in $HOME/.lsh/authorized_keys_sha1/*; do echo echo Key file $key echo echo lsh format "$SEXP_CONV" -i canonical -f transport < $key echo echo "OpenSSH format (base64-encoded, ignore linebreaks and spaces)" echo "$LSH_EXPORT_KEY" -i canonical < $key echo done else echo "No authorized keys" fi --CUT--
So, I guess this feature request is just for (yet another) lsh- util that'll read the comment stored in the non-human-readable file. Dunno if one's stored right now, but it's probably worth doing ;)
The above utility should help you a little bit, although it is probably a good idea to allow lsh-authorize to take a comment and store it when you authorize a key.
/Pontus