search for: opengpg

The upstream provider decided to remove OpenGPG support in its thunderbird-78 packages, see https://bugzilla.redhat.com/show_bug.cgi?id=1886962 https://bugzilla.redhat.com/show_bug.cgi?id=1886958 https://bugzilla.redhat.com/show_bug.cgi?id=1837512 recommending to either use Mozilla binaries, use Flatpak or switch to Evolution Is there any pla...

...s inside ssh-agent are now using a refcount to share the private parts between "Identities". The reason for this change was that the PKCS#11 code might have redirected ("wrap") the RSA functions to a hardware token. We don't want to mess with those internals. Tested with an OpenGPG card. Patch developed against 6.9p and applies to original 6.9, too. Please CC: comments. Signed-off-by: Thomas Jarosch <thomas.jarosch at intra2net.com> diff -u -r -p openssh-6.9p1/ssh-add.1 openssh.cert_shadow/ssh-add.1 --- openssh-6.9p1/ssh-add.1 2015-07-01 04:35:31.000000000 +0200 +++...

...----------------------------------------- The new commands 'samba-tool user getpassword' and 'samba-tool user syncpasswords' provide access and syncing of various password fields. If compiled with GPGME support (--with-gpgme) it's possible to store cleartext passwords in a PGP/OpenGPG encrypted form by configuring the new "password hash gpg key ids" option. This requires gpgme devel and python packages to be installed (e.g. libgpgme11-dev and python-gpgme on debian/ubuntu). Python crypto requirements -------------------------- Some samba-tool subcommands require pyth...

...----------------------------------------- The new commands 'samba-tool user getpassword' and 'samba-tool user syncpasswords' provide access and syncing of various password fields. If compiled with GPGME support (--with-gpgme) it's possible to store cleartext passwords in a PGP/OpenGPG encrypted form by configuring the new "password hash gpg key ids" option. This requires gpgme devel and python packages to be installed (e.g. libgpgme11-dev and python-gpgme on debian/ubuntu). Python crypto requirements -------------------------- Some samba-tool subcommands require pyth...

...----------------------------------------- The new commands 'samba-tool user getpassword' and 'samba-tool user syncpasswords' provide access and syncing of various password fields. If compiled with GPGME support (--with-gpgme) it's possible to store cleartext passwords in a PGP/OpenGPG encrypted form by configuring the new "password hash gpg key ids" option. This requires gpgme devel and python packages to be installed (e.g. libgpgme11-dev and python-gpgme on Debian/Ubuntu). Python crypto requirements -------------------------- Some 'samba-tool' subcommands re...

...----------------------------------------- The new commands 'samba-tool user getpassword' and 'samba-tool user syncpasswords' provide access and syncing of various password fields. If compiled with GPGME support (--with-gpgme) it's possible to store cleartext passwords in a PGP/OpenGPG encrypted form by configuring the new "password hash gpg key ids" option. This requires gpgme devel and python packages to be installed (e.g. libgpgme11-dev and python-gpgme on Debian/Ubuntu). Python crypto requirements -------------------------- Some 'samba-tool' subcommands re...

...----------------------------------------- The new commands 'samba-tool user getpassword' and 'samba-tool user syncpasswords' provide access and syncing of various password fields. If compiled with GPGME support (--with-gpgme) it's possible to store cleartext passwords in a PGP/OpenGPG encrypted form by configuring the new "password hash gpg key ids" option. This requires gpgme devel and python packages to be installed (e.g. libgpgme11-dev and python-gpgme on Debian/Ubuntu). Python crypto requirements -------------------------- Some 'samba-tool' subcommands re...

...----------------------------------------- The new commands 'samba-tool user getpassword' and 'samba-tool user syncpasswords' provide access and syncing of various password fields. If compiled with GPGME support (--with-gpgme) it's possible to store cleartext passwords in a PGP/OpenGPG encrypted form by configuring the new "password hash gpg key ids" option. This requires gpgme devel and python packages to be installed (e.g. libgpgme11-dev and python-gpgme on Debian/Ubuntu). Python crypto requirements -------------------------- Some 'samba-tool' subcommands re...

...----------------------------------------- The new commands 'samba-tool user getpassword' and 'samba-tool user syncpasswords' provide access and syncing of various password fields. If compiled with GPGME support (--with-gpgme) it's possible to store cleartext passwords in a PGP/OpenGPG encrypted form by configuring the new "password hash gpg key ids" option. This requires gpgme devel and python packages to be installed (e.g. libgpgme11-dev and python-gpgme on Debian/Ubuntu). Python crypto requirements -------------------------- Some 'samba-tool' subcommands re...

...----------------------------------------- The new commands 'samba-tool user getpassword' and 'samba-tool user syncpasswords' provide access and syncing of various password fields. If compiled with GPGME support (--with-gpgme) it's possible to store cleartext passwords in a PGP/OpenGPG encrypted form by configuring the new "password hash gpg key ids" option. This requires gpgme devel and python packages to be installed (e.g. libgpgme11-dev and python-gpgme on Debian/Ubuntu). Python crypto requirements -------------------------- Some 'samba-tool' subcommands re...

...-------- > > The new commands 'samba-tool user getpassword' > and 'samba-tool user syncpasswords' provide > access and syncing of various password fields. > > If compiled with GPGME support (--with-gpgme) it's > possible to store cleartext passwords in a PGP/OpenGPG > encrypted form by configuring the new "password hash gpg key ids" > option. This requires gpgme devel and python packages to be installed > (e.g. libgpgme11-dev and python-gpgme on Debian/Ubuntu). > > Python crypto requirements > -------------------------- > > So...

...s inside ssh-agent are now using a refcount to share the private parts between "Identities". The reason for this change was that the PKCS#11 code might have redirected ("wrap") the RSA functions to a hardware token. We don't want to mess with those internals. Tested with an OpenGPG card. Patch developed against 6.9p and applies to original 6.9, too. Original patch from openssh-unixdev has been split into three smaller patches for easier review. It has also been updated for version 7.1p1. (KEY_RSA_CERT_V00 / KEY_DSA_CERT_V00 was removed). Original submission: https://marc.in...