Nickolay Olshevsky

Results 208 comments of Nickolay Olshevsky

@dkg sorry, somehow missed to reply here in time. Finally this settled up in a head (mostly due to the security concerns), and we decided to change to the behaviour...

Note sure whether this applies to the issue, but may be useful: https://redhat-scholars.github.io/openshift-starter-guides/rhs-openshift-starter-guides/4.7/nationalparks-java-codechanges-github-actions.html

@p-barabas I'm not familiar with Swift yet, but it seems you may use library directly with rnp.h header and compiled dylib: https://developer.apple.com/documentation/swift/imported_c_and_objective-c_apis/using_imported_c_functions_in_swift As a guide to calls you need to...

@andrey-utkin these CI failures are related to changes in GHA/used OS images/whatever else. Those are merged into master already so you just would need to cherry-pick those as well.

Hm, this would require adding new function as this doesn't have any state parameters. It's signature could be like `rnp_result_t rnp_decrypt_ex(rnp_ffi_t ffi, rnp_input_t input, rnp_output_t output, rnp_op_verify_t *op)`, allowing to...

Sorry, somehow missed to reply. It would be a bit overhead for the FFI - as we cannot have structs, we'll need to return some opaque object and have functions...

@antonsviridenko Instead of making such function for each hash/symmetric algo/curve/whatever else we could use single and extensible one, as it is done in `rnp_supports_feature`/`rnp_supported_features`. For instance, later on we may...

> Ok, what other algorithms can be added as weak now? Or keep only hash for now? Let's mark IDEA and 3DES as weak for now. @ronaldtse Does this sound...

> @ni4 for example users can already use --force flag for some other purpose, like overwriting destination file and weak algorithms can be unintentionally enabled this way, so I think...