| Summary: | make ssh default identity configuration more user-friendly in cygwin | ||
|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Ralf Hauser <hauser> |
| Component: | ssh | Assignee: | OpenSSH Bugzilla mailing list <openssh-bugs> |
| Status: | CLOSED INVALID | ||
| Severity: | enhancement | CC: | vinschen |
| Priority: | P2 | ||
| Version: | -current | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://www.openbsd.org/cgi-bin/man.cgi?query=ssh | ||
|
Description
Ralf Hauser
2003-02-19 09:19:42 AEDT
Apparently you didn't read /usr/doc/Cygwin/openssh-3.5p1.README. Run ssh-host-config to create the host configuration files and keys and run ssh-user-config to create your personal keys in ~/.ssh. O.K, I did it: <<rhauser@PC:~/<2>Man/cat1> ssh-user-config Configuration finished. Have fun!>> I thought I would now be asked something (why would I be able to specify a "-y" or "-n" option otherwise anyway? Conclusion, it still doesn't give a clue from which directory it did what... ====> Suggestion: add a "-v" option that tells in an end-user-intelligible way what happens. (sure, there is the "-d" option that eventually utters "+ [ ! -f /rsync/.ssh/identity ]" - but this appears to be development-team-internal...) P.S.: Especially when clicking on wincvs, it is not that obvious to find out why this happens ... see https://sourceforge.net/tracker/?func=detail&aid=689081&group_id=10072&atid=110072 As I told you on the cygwin ML, check your home dir in /etc/passwd. Your description points to /rsync being set as your home dir in /etc/passwd. If you'd look into the ssh-user-config script you'd find that it uses your home dir from /etc/passwd same as ssh does. It does especially *NOT* use the value of $HOME, same as ssh. Thx for the additional explanation. I change the title and now classify it as an enhancement request for an intelligible "-v". If this ssh-user-config business really only applies to cygwin, I would appreciate a pointer to a bug-tracking system of them in order to close it here and open it there. Cygwin reports via http://cygwin.com/bugs.html, not here. |