#169: segmentation fault in pubkey authentication
-+--
Reporter: suyogjadhav | Owner:
Type: defect | Status: new
Priority: high | Milestone:
Component: API |
#169: segmentation fault in pubkey authentication
--+-
Reporter: suyogjadhav | Owner:
Type: defect | Status: closed
Priority: high | Milestone: 1.2.5
Component: API
#169: segmentation fault in pubkey authentication
--+-
Reporter: suyogjadhav | Owner:
Type: defect | Status: closed
Priority: high | Milestone: 1.2.5
Component: API
On Mon, 29 Mar 2010, libssh2 Trac wrote:
Comment(by alamaison):
I've got to say I would find it very strange to revert a fix that makes
using our library ''safer''. Ideally, it should never be possible to crash
no matter what inputs a component receives.
-1 for reverting.
I don't quite
On Mon, 29 Mar 2010, Daniel Stenberg wrote:
I don't quite understand that resistance either. As I said
before: this function is not documented clearly to *not*
accept a NULL for a blank passphrase even though it isn't
documented to accept it either. Given that small uncertainty
in API
#169: segmentation fault in pubkey authentication
--+-
Reporter: suyogjadhav | Owner:
Type: defect | Status: closed
Priority: high | Milestone: 1.2.5
Component: API
