The March release for #GnuPG in the PQC public testing release series is here: v2.5.5 only has a few fixes, but those seem important ... removing potential "hangs" 🧐 on windows and elsewhere.
https://dev.gnupg.org/T7530
https://lists.gnupg.org/pipermail/gnupg-announce/2025q1/000491.html
#GnuPG 2.4.6 is available. Accumulated fixes and small improvements over the last 7 months. There is even a new tool `gpg-mail-tube` to encrypt an email automatically in a pipe. Give it a try, especially if you use hardware tokens.
https://lists.gnupg.org/pipermail/gnupg-announce/2024q4/000486.html
Want an #EmailRenaissance! As there are so many structural advantages to email, by being able to communicate to people outside of your organisation, adding #endtoendsecurity, and having your own software decide what to display how and when. Using email in an advanced way is control taken back from big IT companies. And this also explains partly why many fully email clients appear to be old these days: There is not much money to be made from them ... they don't sell your data or attention. 🤔 💌 📬
With Univention another company support WKD (for distributing public OpenPGP keys for #GnuPG ans other implementations) Cool! https://lists.gnupg.org/pipermail/gnupg-users/2023-February/066442.html #EndtoEndSecurity
RT @gpg4win@twitter.com
Upgrade #Gpg4win to 4.0.4 (including #GnuPG 2.3.8), fixing critical defect (CVE-2022-3515)! It is important, as there can be attacks from remote to gain control of your computer. See https://lists.wald.intevation.org/pipermail/gpg4win-announce/2022/000098.html Advisory: https://www.gnupg.org/blog/20221017-pepe-left-the-ksba.html #Security #OpenPGP #EndtoEndSecurity.
Upgrade #Gpg4win (contains #GnuPG) to version 4.0.4 for fixing a critical defect (CVE-2022-3515)! It is important that you do, as there can be attacks from remote to gain control of your computer. See https://lists.wald.intevation.org/pipermail/gpg4win-announce/2022/000098.html Technical Advisory: https://www.gnupg.org/blog/20221017-pepe-left-the-ksba.html #Security #FreeSoftware #OpenPGP #EndtoEndSecurity.
#GnuPG v2.2.26 improves support for auto-locating pubkeys on
LDAP and Active Directory keyservers and helps other enterprise use cases e.g. with global config file support.
https://lists.gnupg.org/pipermail/gnupg-announce/2020q4/000451.html #EndtoEndSecurity #FreeSoftware
#GnuPG 2.2.25 fixes minor regression over last week's 2.2.24 for hardware tokens https://dev.gnupg.org/T5140 #FreeSoftware #EndToEndSecurity (As users often only start testing when there is a real release, doing more releases is a good thing, even if you get more regressions, as there is more stability and more functionality over time on the average. :) #SoftwareEngineeringExplanationOfTheDay )
#GnuPG version 2.2.22 is available and moves the default OpenPGP algorithm to rsa3072. :) See some of the old discussions listed at https://wiki.gnupg.org/LargeKeys why this is not an easy topic.
https://lists.gnupg.org/pipermail/gnupg-announce/2020q3/000447.html #FreeSoftware #EndtoEndSecurity #OpenPGP
#Gpg4win version 3.1.12 got released on the 24th of July. One security issue fixed. A number of improvements to the Outlook-Add-in, the next version of the stable GnuPG crypto backend and a bit to better the expert tool Kleopatra. https://www.gpg4win.de/change-history.html #FreeSoftware #EndtoEndSecurity
#Gpg4win version 3.1.11 can be downloaded. Recommended for user of the Outlook Add-in GpgOL, because of a handful of improvements. A must-have for people handling many public keys is the new tagging feature (as part of a pubkey "certification"). It helps grouping and sorting many pubkeys. Also has the current #GnuPG version (2.2.19) and its improvements. #FreeSoftware #EndtoEndSecurity
#GnuPG v2.2.19 fixes a small regression over 2.2.18. Still two small real world uses case solutions sneaked in. They show why it is a lot of work to create a crypto solution that works well in the wild: You need to fully understand first how other people run their software. https://dev.gnupg.org/T4768 https://lists.gnupg.org/pipermail/gnupg-announce/2019q4/000443.html #EndtoEndSecurity #FreeSoftware
#GnuPG: with just released v2.2.18 there is a steady flow of small improvements, e.g. in the area of hardware token support, CMS (for S/MIME), diagnostics, how pubkeys are stored and more, see details at https://lists.gnupg.org/pipermail/gnupg-announce/2019q4/000442.html #EndtoEndSecurity #FreeSoftware
How to detect 'spoofed' email signatures https://www.gpg4win.org/statement-spoofing.html : Stay updated. Be adequately cautious. As developer: Use GPGME (the official API). Avoid HTML by default. Employ WKD. #EndtoEndSecurity #OpenPGP #GnuPG #CMS #Gpg4win
#GnuPG 2.2.14 is available. Improves Cryptographic Message Syntax (aka CMS, needed for S/MIME) handling. Minor improvement for crypto tokens and compatibility. https://lists.gnupg.org/pipermail/gnupg-announce/2019q1/000435.html
#GnuPG #EndtoEndSecurity #FreeSoftware
GnuPG v2.2.13 was released. Small steps that show work is ongoing for crypto tokens like smart cards and usb based tokens. It is usually a good sign if releases come in regular intervals and they fix small defects, as it means that there are no major large defects known. >:)
https://lists.gnupg.org/pipermail/gnupg-announce/2019q1/000434.html #GnuPG #EndtoEndSecurity #FreeSoftware
GnuPG 2.2.11 has landed. If you look at the changes (https://dev.gnupg.org/T4233) there are many little things, common with a maintenance release , but you can also see that distributing pubkeys with https://wiki.gnupg.org/WKD is getting more important, just as preparations for implementing something like https://wiki.gnupg.org/AutomatedEncryption in mail clients. #FreeSoftware #EndtoEndSecurity (And it is good to see regular releases of GnuPG! :))
