| Summary: | Misleading error message in ssh-keygen | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | jchadima | ||||||
| Component: | ssh-keygen | Assignee: | Assigned to nobody <unassigned-bugs> | ||||||
| Status: | CLOSED FIXED | ||||||||
| Severity: | minor | CC: | djm, jchadima | ||||||
| Priority: | P2 | ||||||||
| Version: | 5.4p1 | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Attachments: |
|
||||||||
|
Description
jchadima
2010-03-24 22:04:20 AEDT
Created attachment 1818 [details]
patch solving the problem
Is the error message that you are talking about "Could not create directory '/home/djm/.ssh'"? That doesn't seem misleading to me. In the case when the directory exists it's misleading. One user contact me me asking why it prints "Could not create directory '/home/luser/.ssh'" when I have one? The stat() result EPERM means that user have insufficient permissions to existing file, respectively to the directory containing the file. Created attachment 1842 [details]
keygen-report-stat-errors.diff
tweaked patch
patch applied. Will be in OpenSSH-5.6p1 Move resolved bugs to CLOSED after 5.7 release |