Skip to content

NetSSL_Win: bad error handling when decodeMessage() fails #3465

@obiltschnig

Description

@obiltschnig

See my-devices/sdk@5127d47

Throwing an exception in decodeBufferFull() leaves the internal state of the SecureSocketImpl unchanged. A follow up call to receiveBytes() will do the same again, leading to a potential endless loop. Instead, simply return the error code and let receiveBytes() deal with it.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions