Clarify the padding and fix some missing frees for openssl objects

[timlegge]

Closed #65

[guest20]

Are there other choices for padding?

It looks like there are only 2 types of padding available and they each have only one use case - would it be useful to recommend that the consumer of the library not request a specific posting themselves?

[timlegge]

Are there other choices for padding?

It looks like there are only 2 types of padding available and they each have only one use case - would it be useful to recommend that the consumer of the library not request a specific posting themselves?

There are effectively four types available: Older openssl versions also support the first three and are unaffected by there changes.

With openssl 3.0+

• use_no_padding
• use_pkcs1_oaep_padding (only encryption/decryption)
• use_pkcs1_pss_padding (only signing/verifying)

With openssl < 3.0

• use_sslv23_padding

Disabled:

• use_pkcs1_padding

However, you are probably correct recommending not setting one is likely best. As I think of it, we could probably add a:

set_signature_padding(type), set_encryption_padding(type)
It might make it easier to deal with in the future.

[timlegge]

Are there other choices for padding?
It looks like there are only 2 types of padding available and they each have only one use case - would it be useful to recommend that the consumer of the library not request a specific posting themselves?

There are effectively four types available: Older openssl versions also support the first three and are unaffected by these changes.

With openssl 3.0+

• use_no_padding
• use_pkcs1_oaep_padding (only encryption/decryption)
• use_pkcs1_pss_padding (only signing/verifying)

With openssl < 3.0

• use_sslv23_padding

Disabled:

• use_pkcs1_padding

However, you are probably correct recommending not setting one is likely best. As I think of it, we could probably add a:

set_signature_padding(type), set_encryption_padding(type) It might make it easier to deal with in the future.