Bug 2508 - Wanting OpenSSL error messages in ssherr() for SSH_ERR_LIBCRYPTO_ERROR
Summary: Wanting OpenSSL error messages in ssherr() for SSH_ERR_LIBCRYPTO_ERROR
Status: NEW
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: Miscellaneous (show other bugs)
Version: 7.1p1
Hardware: SPARC Solaris
: P5 enhancement
Assignee: Assigned to nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-27 02:24 AEDT by Tomas Kuthan
Modified: 2015-11-27 02:32 AEDT (History)
0 users

See Also:

Attachments
Simple and thread-unsafe patch to add OpenSSL error strings to ssherr() (703 bytes, patch)
2015-11-27 02:32 AEDT, Tomas Kuthan 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Kuthan 2015-11-27 02:24:55 AEDT 
After code refactoring for library-like interfaces,OpenSSL error string were replaced by generic and vague "error in libcrypto" message.

This enhancement asks for returning OpenSSL error strings for SSH_ERR_LIBCRYPTO_ERROR errors.
Comment 1 Tomas Kuthan 2015-11-27 02:32:26 AEDT 
Created attachment 2759 [details]
Simple and thread-unsafe patch to add OpenSSL error strings to ssherr()

For use in single-threaded OpenSSH binaries this patch based on static error buffer for OpenSSL error strings should be sufficient.

For library API this would hardly be suitable.
Providing contextual error messages would probably require a more robust and flexible error message framework.