Re: [Announce] A New Future for GnuPG

2022-01-03 Thread Michael Uplawski
Am Tue, Jan 04, 2022 at 04:02:21PM +1100 schrieb raf via Gnupg-users: > > Hello and a Happy Gnu Year! This makes me count the years. Should I really start? I had “used” PGP before I had an Internet-connection and longer even before I had changed careers to become a “software-developer” (of a kind

Re: [Announce] A New Future for GnuPG

2022-01-03 Thread raf via Gnupg-users
On Mon, Jan 03, 2022 at 08:19:26AM +0100, Werner Koch via Gnupg-users wrote: > Hello and a Happy Gnu Year! Happy Gnu Year indeed! Congratulations on the marvellous news, and many thanks for all that you do. cheers, raf ___ Gnupg-users mailing list

Re: [Announce] A New Future for GnuPG

2022-01-03 Thread Rainer Fiebig via Gnupg-users
Great! This sounds like a success story that has only just begun. The right solution at the right time! The market for secure communication is huge and IMO still in its infancy. And for a small fish in a big pond there's lots of room to grow. ;) Congratulations! And good luck to you and GnuPG.com

Re: [Announce] A New Future for GnuPG

2022-01-03 Thread Steffen Nurpmeso
Robert J. Hansen wrote in : |Werner, this is amazing news. Thank you for sharing it! | |For the list: as you may remember, each Christmas I run a fundraiser for |GnuPG. You pledge $X and I match it, that sort of thing. I didn't do |one this year because Werner contacted me earlier asking

Re: Levels of validation

2022-01-03 Thread Christoph Klassen via Gnupg-users
On Sun, 02 Jan 2022 19:45:27 +0100 Ingo Klöcker wrote: > With regard to the validity of the two keys A and B the result of the > last two cases are the same. But the semantics of key signatures and > owner trust are completely different. Sorry, I didn't say clear enough what I meant. For me pe

Re: [Announce] A New Future for GnuPG

2022-01-03 Thread Robert J. Hansen via Gnupg-users
I did spend about six months doing a clean-room implementation of RFC2440 in PHP3.  It was a vile experience and one I don't recommend. I am simultaneously shocked, impressed, and disgusted. ;-) I rarely talk about that job because it's sort of like saying you made a healthy and tasty meal ou

Re: Gpg4win LetsEncrypt issue

2022-01-03 Thread Andrew Gallagher via Gnupg-users
On Fri, 2021-12-31 at 23:23 +0200, Alex Nadtoka wrote: > Ok, thanks. Where on the client end i can remove it? This blog appears to do it correctly (to the best of my knowledge) and as its worked example uses the very same CA certificate that we have just been discussing:   https://www.thesslstore

Re: [Announce] A New Future for GnuPG

2022-01-03 Thread Andrew Gallagher via Gnupg-users
On Mon, 2022-01-03 at 11:31 -0500, Robert J. Hansen via Gnupg-users wrote: > Werner, this is amazing news. Thank you for sharing it! Indeed, many congratulations! > I did spend about six months doing a clean-room implementation of > RFC2440 in PHP3.  It was a vile experience and one I don't rec

Re: [Announce] A New Future for GnuPG

2022-01-03 Thread Robert J. Hansen via Gnupg-users
Werner, this is amazing news. Thank you for sharing it! For the list: as you may remember, each Christmas I run a fundraiser for GnuPG. You pledge $X and I match it, that sort of thing. I didn't do one this year because Werner contacted me earlier asking me not to, saying he would soon have

Re: [Announce] A New Future for GnuPG

2022-01-03 Thread Werner Koch via Gnupg-users
Hi! small but important correction: > Chiasmus: the proprietary GreenBone software from /cryptovision GmbH/ Of course I meant GreenShield and not Greenbone. The latter is a company which provides free software network security scanners. See https://www.greenbone.net/en/ Shalom-Salam, W