Skip to content

Behave more sensibly in case of libgcrypt errors #52

@redlizard

Description

@redlizard

Currently, almost any unexpected result by a libgcrypt call will result in a CryptoException that isn't handled anywhere, leading to an exit(). This is a rare occurrence, but still a bad thing when it does happen. This error handling should be improved.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions