On Tue, Mar 11, 2003 at 02:58:14AM +0100, martin f krafft wrote: > also sprach Colin Watson <[EMAIL PROTECTED]> [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.
Don't understand. It's easy. What are you actually trying to *do*? > 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. Hm, environment variable cruft ... Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
