This is the mail archive of the
mailing list for the Cygwin project.
RE: ssh Authentication--RSA/Password
- To: "Corinna Vinschen" <cygwin at cygwin dot com>
- Subject: RE: ssh Authentication--RSA/Password
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- Date: Tue, 3 Apr 2001 09:31:14 +1000
- Thread-Index: AcC7U9w2ZRxeNg5XTWu42ljz1mBwwwAeNB4g
- Thread-Topic: ssh Authentication--RSA/Password
> -----Original Message-----
> From: Corinna Vinschen [mailto:firstname.lastname@example.org]
> Sent: Monday, April 02, 2001 7:10 PM
> To: cygwin
> Subject: Re: ssh Authentication--RSA/Password
> > What about a community sponsored effort - ie via one of the
> "open source
> > markets". I'm just thinking there are enough folk here who are
> > interested in this, may be we could collectively fund it?
> I'm not sure if that would work.
Any particular reason it would fail? $$$ needed? Contractual issues?
> > > BTW, using that method for logon introduces another
> problem. Since the
> > > user never typed her password the created user token has no
> > credentials
> > > to open network connections. This requires the user to call
> > > `net use ...' for each network resource and each call requires a
> > > password!
> > Could they use ssh to authenticate to other NT machines
> with the ssh LSA
> > extension installed?
> Each target system would need the module.
I was thinking about this. It seems to me that if an ssh LSA module is
developed, it should be able to implement setuid() for non-ssh programs
with trivial modifications. Does that sound feasible?
If so, that's something that would be really useful to me. (meaning I'll
put some money where my fingers are).
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple