openssh bugs - Dec 2005 - [Bug 1137] ssh does not always return code 255 when in error

http://bugzilla.mindrot.org/show_bug.cgi?id=1137

           Summary: ssh does not always return code 255 when in error
           Product: Portable OpenSSH
           Version: 4.2p1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ssh
        AssignedTo: bitbucket at mindrot.org
        ReportedBy: ombugr at mayoxide.com


The ssh client does not always return exit code 255 when it a client error
occurs, as it is documented in the man page. For example, a refused or timed
out connection returns exit code 1, while a unknown hostname returns 255. This
makes automating tasks using ssh tricky, as I can't be sure if the exit code
comes from the remote command or the client when there is a connection problem.

About 6 months ago, someone posted a report on the mailing list detailing the
exact same problem, see: 
http://marc.theaimsgroup.com/?l=openssh-unix-dev&m=111754196015597&w=2

I wondered if it could be possible to correct this in the client in the future.
If the behaviour is normal, then the man page should then be updated, as
currently this is ambiguous.

Thanks




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=1137





------- Comment #1 from dtucker at zip.com.au  2005-12-20 11:30 -------
Created an attachment (id=1048)
 --> (http://bugzilla.mindrot.org/attachment.cgi?id=1048&action=view)
exit(255) for ssh internal errors

Fair enough.  I think this patch gets the appropriate ones.




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=1137


dtucker at zip.com.au changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
OtherBugsDependingO|                            |1047
              nThis|                            |
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Comment #2 from dtucker at zip.com.au  2005-12-20 16:20 -------
The patch has been applied.  It will be in tomorrow's snapshot and the 4.3
release.

Thanks for the report.




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.