also sprach Colin Watson <cjwatson@debian.org> [2003.03.11.0109 +0100]: > Oh, I see. Then you should use a forced command in > ~/.ssh/authorized_keys, establishing the security context on the server > side. For example, my dynamic DNS is set up using a passphraseless key > and this line in the authorized_keys file on the server side: > > command="userv dyndns dyndns dynamic.greenend.org.uk riva",no-pty,no-port-forwarding 1024 35 ... right, but then i'd have to manage this file, which is everything but nice. i am trying to solve exactly this problem though. how nice would it be if sshd spawned a shell and gave it something like $SSH_DSA_KEYID for its environment. > > does anyone here have a connection into the OpenSSH team and could > > forward a feature request? i'd prefer not to enlist with the mailing > > list... > > There are a lot of bugs against ssh in the Debian BTS, but I do forward > bugs filed there to upstream as I get time. ok. i'll file a wishlist. -- Please do not CC me when replying to lists; I read them! .''`. martin f. krafft <madduck@debian.org> : :' : proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system NOTE: The pgp.net keyservers and their mirrors are broken! Get my key here: http://people.debian.org/~madduck/gpg/330c4a75.asc
Attachment:
pgpKb41fjktcO.pgp
Description: PGP signature