Feature Request: Release package signing

[g4jc]

Hello, There is currently no way to verify the complete integrity of releases. Please consider signing your releases so that package maintainers can verify the sources prior to packaging.

See here for how-to and complete details: https://wiki.debian.org/Creating%20signed%20GitHub%20releases

Thank you

[Anabel-Dev]

Hello, Currently we are trying to encrypt a folder using ecryptfs via pkcs11-helper(a public key stored in ATECC608A). We able to communicate with the cryptochip through pkcs11(using p11tool). While running the ecryptfs-manager we didn't get any PKCS#11 serialized object id just it returns to the main menu ad depicted below:

$ ecryptfs-manager

eCryptfs key management menu

1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

Make selection: 2

Select key type to use for newly created files: 1) pkcs11-helper 2) passphrase 3) openssl Selection: 1

Returning to main menu

eCryptfs key management menu

1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

Make selection: 4

We configured the ~/.ecryptfsrc.pkcs11 file as pkcs11-log-level=5 pkcs11-provider,name=cryptoauthlib,library=/usr/lib/libcryptoauth.so

can anyone please explain or share your comments what we are doing wrong?

[alonbl]

On Thu, 27 Feb 2020 at 14:01 Anabel-Dev notifications@github.com wrote:

Hello, Currently we are trying to encrypt a folder using

Please communicate via opensc mailing list or create a new issue, do not hijack issues.

[alonbl]

I can't download OpenVPN through the command (brew install OpenVPN), because there is no 1.28.0 file in bz2 format

Please do not hijack issues, open new ones. Thanks for noticing fixed.