Re: Description for sshproxy
- To: debian-l10n-english@lists.debian.org
- Subject: Re: Description for sshproxy
- From: MJ Ray <mjr@phonecoop.coop>
- Date: Wed, 02 Jan 2008 11:06:54 +0000
- Message-id: <[🔎] 477b704e.sccTADdpzzBX85Va%mjr@phonecoop.coop>
- In-reply-to: <m37iiwhx7f.fsf@neo.luffy.cx>
- References: <962be12d594dbc4bf2fba5d03a676c45@imap.luffy.cx> <20071229210517.GA13310@xibalba.demon.co.uk> <m3tzm0ij0w.fsf@neo.luffy.cx> <4777a388.ZrcWJjFgHFpqqdf6%mjr@phonecoop.coop> <20071230152617.GA21790@xibalba.demon.co.uk> <m37iiwhx7f.fsf@neo.luffy.cx>
Vincent Bernat <bernat@luffy.cx> wrote:
> 16:26, Justin B Rye <jbr@edlug.org.uk> disait:
> > This SSH proxy allows users to connect without having passwords or keys
> > for the remote site. First they connect to the proxy using their own
> > credentials, and then the proxy initiates the connection to the remote
> > site using, for example, the root password. Access Control Lists are
> > used to check that a user is authorized to connect to a given remote
> > site.
>
> > (I've shifted the "first" and capitalised the expansion for ACLs.)
>
> I adopt this proposition. Any other comment?
Fine by me.
Thanks,
--
MJR/slef
My Opinion Only: see http://people.debian.org/~mjr/
Please follow http://www.uk.debian.org/MailingLists/#codeofconduct
Reply to: