OpenKeychain VS Byte Buddy

In addition to my PC set up I am also using the Android Password Store in combination with OpenKeyChain. Everything works fine except that decrypting any password simply works without requiring my PIN. I've tried both USB C connection and NFC and neither interface requires the PIN.

OpenKeychain is an Android app for doing some basic GPG related work. It can verify signatures (hidden in the "encrypt/decrypt" menu)

Also it integrates i.e. with K-9 mail to sign and verify.

https://github.com/open-keychain/open-keychain

I don't know what features you are looking for in encryption software but OpenKeychain is foss, audited and works just fine if you just want basic encryption/decryption/signing.

OpenKeychain: Easy PGP (version 5.8.0): Encrypt your Files and Communications. Compatible with the OpenPGP Standard.

I use mailbox.org with the encrypted inbox, Mozilla Thunderbird on desktop, and FairEmail + OpenKeychain on Android. I think StartMail is the only other one of those four options that supports standard IMAP and SMTP.

On Android OpenKeychain, TermBot, and K-9 Mail, are awesome.

I would try openpgp, you can use https://www.gpg4win.org/ on windows and https://github.com/open-keychain/open-keychain (not actively developed, if someone knows a good alternative please comment) for android.

Openkeychain is a good gnupg encryption tool for Android. https://www.openkeychain.org/. It mostly is for using gnupg for email encryption, but you can also use it for file encryption too.

As seen above, the API exposes the user to low-level bytecode manipulation via byte arrays. It would be unwieldy to do it directly. Hence, real-life projects rely on bytecode manipulation libraries. ASM has been the traditional library for this, but it seems that Byte Buddy has superseded it. Note that Byte Buddy uses ASM but provides a higher-level abstraction.

Just a drive-by comment: ByteBuddy is worth a look https://bytebuddy.net/. It is built on top of ASM.

> can you show an example of how you'd parse, say, a .java.in

The canonical way to do such a thing is through the java annotation processing api [1] and using a tool like java poet [2]. Before you did that, you'd probably decide if you wanted to instead use bytecode generation with a library like bytebuddy [3]

But, assuming for some reason, you wanted to torture yourself and actually consume a java.in file and apply a regex, then you'd probably pull out the "maven-replacer-plugin" [4] and configure that for the task at hand. (or use your favorite templating language plugin. There's a million of them).

Though, to be fair, this really isn't something that comes up in regular java programming due to the nature of the ecosystem. Anything you'd want to codegen likely already has a library and anything you didn't would receive (legitimate) push back.

[1] https://www.baeldung.com/java-annotation-processing-builder

[2] https://github.com/square/javapoet

[3] https://bytebuddy.net/

[4] https://github.com/beiliubei/maven-replacer-plugin

Have a look at byte buddy.

If you've ever used libraries like https://github.com/JakeWharton/hugo or https://hibernate.org/ (if you've ever done some backend development) and wondered how do they seem to add some code/logic into your app just by adding some annotation to some method, or if you ever wondered how mocking frameworks like Mockito can change a class behavior for example, then most likely you're interested in a programming technique that allows to modify existing code, usually known as Aspect oriented programming (also known in Java as Bytecode instrumentation) which, even though it might sound intimidating at first, some really cool tools such as Byte Buddy or AspectJ make it quite easy to accomplish.