From omerusta at gmail.com Mon Apr 1 06:11:17 2024 From: omerusta at gmail.com (=?UTF-8?B?w5ZtZXIgRmFkxLFsIFVTVEE=?=) Date: Mon, 1 Apr 2024 07:11:17 +0300 Subject: Git server have some problems Message-ID: Hello sorry for disturbing and I'm not sure if this is the correct place to send this mail or not. Currently i'm having issues to fetch gnupg's git servers and getting 500 time to time. And the logs from my side is not have enough information that i can provide but still here: GIT_CURL_VERBOSE=1 git clone https://dev.gnupg.org/source/gpgme.git Cloning into 'gpgme'... 06:58:07.943974 http.c:843 == Info: Couldn't find host dev.gnupg.org in the .netrc file; using defaults 06:58:07.947668 http.c:843 == Info: Host dev.gnupg.org:443 was resolved. 06:58:07.947678 http.c:843 == Info: IPv6: 2a01:4f8:160:1386::54 06:58:07.947681 http.c:843 == Info: IPv4: 176.9.139.178 06:58:07.947694 http.c:843 == Info: Trying 176.9.139.178:443 ... 06:58:07.993057 http.c:843 == Info: Connected to dev.gnupg.org (176.9.139.178) port 443 06:58:07.994486 http.c:843 == Info: ALPN: curl offers h2,http/1.1 06:58:07.994693 http.c:843 == Info: TLSv1.3 (OUT), TLS handshake, Client hello (1): 06:58:08.002105 http.c:843 == Info: CAfile: /etc/ssl/certs/ca-certificates.crt 06:58:08.002112 http.c:843 == Info: CApath: none 06:58:11.359850 http.c:843 == Info: TLSv1.3 (IN), TLS handshake, Server hello (2): 06:58:11.359926 http.c:843 == Info: TLSv1.2 (IN), TLS handshake, Certificate (11): 06:58:11.360370 http.c:843 == Info: TLSv1.2 (IN), TLS handshake, Server key exchange (12): 06:58:11.361033 http.c:843 == Info: TLSv1.2 (IN), TLS handshake, Server finished (14): 06:58:11.361196 http.c:843 == Info: TLSv1.2 (OUT), TLS handshake, Client key exchange (16): 06:58:11.361325 http.c:843 == Info: TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): 06:58:11.361452 http.c:843 == Info: TLSv1.2 (OUT), TLS handshake, Finished (20): 06:58:11.406963 http.c:843 == Info: TLSv1.2 (IN), TLS handshake, Finished (20): 06:58:11.407032 http.c:843 == Info: SSL connection using TLSv1.2 / ECDHE-ECDSA-AES256-GCM-SHA384 / x25519 / id-ecPublicKey 06:58:11.407037 http.c:843 == Info: ALPN: server accepted http/1.1 06:58:11.407042 http.c:843 == Info: Server certificate: 06:58:11.407049 http.c:843 == Info: subject: CN=dev.gnupg.org 06:58:11.407067 http.c:843 == Info: start date: Mar 30 02:19:10 2024 GMT 06:58:11.407071 http.c:843 == Info: expire date: Jun 28 02:19:09 2024 GMT 06:58:11.407098 http.c:843 == Info: subjectAltName: host " dev.gnupg.org" matched cert's "dev.gnupg.org" 06:58:11.407106 http.c:843 == Info: issuer: C=US; O=Let's Encrypt; CN=R3 06:58:11.407110 http.c:843 == Info: SSL certificate verify ok. 06:58:11.407118 http.c:843 == Info: Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using sha256WithRSAEncryption 06:58:11.407123 http.c:843 == Info: Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption 06:58:11.407140 http.c:843 == Info: Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption 06:58:11.407144 http.c:843 == Info: using HTTP/1.x 06:58:11.407229 http.c:790 => Send header, 0000000244 bytes (0x000000f4) 06:58:11.407236 http.c:802 => Send header: GET /source/gpgme.git/info/refs?service=git-upload-pack HTTP/1.1 06:58:11.407257 http.c:802 => Send header: Host: dev.gnupg.org 06:58:11.407259 http.c:802 => Send header: User-Agent: git/2.44.0 06:58:11.407262 http.c:802 => Send header: Accept: */* 06:58:11.407265 http.c:802 => Send header: Accept-Encoding: deflate, gzip, br, zstd 06:58:11.407269 http.c:802 => Send header: Accept-Language: en-US, *;q=0.9 06:58:11.407272 http.c:802 => Send header: Pragma: no-cache 06:58:11.407275 http.c:802 => Send header: Git-Protocol: version=2 06:58:11.407278 http.c:802 => Send header: 06:58:11.407284 http.c:843 == Info: Request completely sent off 06:58:11.560463 http.c:790 <= Recv header, 0000000017 bytes (0x00000011) 06:58:11.560478 http.c:802 <= Recv header: HTTP/1.1 200 OK 06:58:11.560503 http.c:790 <= Recv header, 0000000037 bytes (0x00000025) 06:58:11.560505 http.c:802 <= Recv header: Date: Mon, 01 Apr 2024 03:58:11 GMT 06:58:11.560509 http.c:790 <= Recv header, 0000000032 bytes (0x00000020) 06:58:11.560531 http.c:802 <= Recv header: Server: Apache/2.4.54 (Debian) 06:58:11.560534 http.c:790 <= Recv header, 0000000023 bytes (0x00000017) 06:58:11.560536 http.c:802 <= Recv header: X-Frame-Options: Deny 06:58:11.560541 http.c:790 <= Recv header, 0000000045 bytes (0x0000002d) 06:58:11.560544 http.c:802 <= Recv header: Strict-Transport-Security: max-age=31536000 06:58:11.560548 http.c:790 <= Recv header, 0000000306 bytes (0x00000132) 06:58:11.560552 http.c:802 <= Recv header: Content-Security-Policy: default-src https://files.gnupg.net; img-src https://files.gnupg.net data:; style-src https://files.gnupg.net 'unsafe-inline'; script-src https://files.gnupg.net; connect-src 'self'; frame-src 'self'; frame-ancestors 'none'; object-src 'none'; form-action 'self'; base-uri 'none' 06:58:11.560557 http.c:790 <= Recv header, 0000000030 bytes (0x0000001e) 06:58:11.560559 http.c:802 <= Recv header: Referrer-Policy: no-referrer 06:58:11.560576 http.c:790 <= Recv header, 0000000040 bytes (0x00000028) 06:58:11.560579 http.c:802 <= Recv header: Expires: Fri, 01 Jan 1980 00:00:00 GMT 06:58:11.560582 http.c:790 <= Recv header, 0000000018 bytes (0x00000012) 06:58:11.560603 http.c:802 <= Recv header: Pragma: no-cache 06:58:11.560606 http.c:790 <= Recv header, 0000000053 bytes (0x00000035) 06:58:11.560609 http.c:802 <= Recv header: Cache-Control: no-cache, max-age=0, must-revalidate 06:58:11.560620 http.c:790 <= Recv header, 0000000024 bytes (0x00000018) 06:58:11.560623 http.c:802 <= Recv header: Content-Encoding: gzip 06:58:11.560626 http.c:790 <= Recv header, 0000000023 bytes (0x00000017) 06:58:11.560628 http.c:802 <= Recv header: Vary: Accept-Encoding 06:58:11.560631 http.c:790 <= Recv header, 0000000022 bytes (0x00000016) 06:58:11.560634 http.c:802 <= Recv header: Content-Length: 6939 06:58:11.560637 http.c:790 <= Recv header, 0000000059 bytes (0x0000003b) 06:58:11.560639 http.c:802 <= Recv header: Content-Type: application/x-git-upload-pack-advertisement 06:58:11.560655 http.c:790 <= Recv header, 0000000002 bytes (0x00000002) 06:58:11.560657 http.c:802 <= Recv header: 06:58:11.560815 http.c:843 == Info: Connection #0 to host dev.gnupg.org left intact 06:58:11.567707 http.c:843 == Info: Couldn't find host dev.gnupg.org in the .netrc file; using defaults 06:58:11.567742 http.c:843 == Info: Found bundle for host: 0x5f45ca40b310 [serially] 06:58:11.567747 http.c:843 == Info: Can not multiplex, even if we wanted to 06:58:11.567771 http.c:843 == Info: Re-using existing connection with host dev.gnupg.org 06:58:11.567895 http.c:790 => Send header, 0000000316 bytes (0x0000013c) 06:58:11.567902 http.c:802 => Send header: POST /source/gpgme.git/git-upload-pack HTTP/1.1 06:58:11.567923 http.c:802 => Send header: Host: dev.gnupg.org 06:58:11.567925 http.c:802 => Send header: User-Agent: git/2.44.0 06:58:11.567928 http.c:802 => Send header: Accept-Encoding: deflate, gzip, br, zstd 06:58:11.567931 http.c:802 => Send header: Content-Type: application/x-git-upload-pack-request 06:58:11.567952 http.c:802 => Send header: Accept: application/x-git-upload-pack-result 06:58:11.567955 http.c:802 => Send header: Accept-Language: en-US, *;q=0.9 06:58:11.567958 http.c:802 => Send header: Content-Encoding: gzip 06:58:11.567960 http.c:802 => Send header: Content-Length: 3495 06:58:11.567963 http.c:802 => Send header: 06:58:11.567967 http.c:843 == Info: upload completely sent off: 3495 bytes 06:58:14.636882 http.c:843 == Info: HTTP 1.0, assume close after body 06:58:14.636912 http.c:790 <= Recv header, 0000000036 bytes (0x00000024) 06:58:14.636918 http.c:802 <= Recv header: HTTP/1.0 500 Internal Server Error 06:58:14.636947 http.c:790 <= Recv header, 0000000037 bytes (0x00000025) 06:58:14.636969 http.c:802 <= Recv header: Date: Mon, 01 Apr 2024 03:58:11 GMT 06:58:14.636976 http.c:790 <= Recv header, 0000000032 bytes (0x00000020) 06:58:14.636979 http.c:802 <= Recv header: Server: Apache/2.4.54 (Debian) 06:58:14.636982 http.c:790 <= Recv header, 0000000023 bytes (0x00000017) 06:58:14.636985 http.c:802 <= Recv header: X-Frame-Options: Deny 06:58:14.636989 http.c:790 <= Recv header, 0000000306 bytes (0x00000132) 06:58:14.636993 http.c:802 <= Recv header: Content-Security-Policy: default-src https://files.gnupg.net; img-src https://files.gnupg.net data:; style-src https://files.gnupg.net 'unsafe-inline'; script-src https://files.gnupg.net; connect-src 'self'; frame-src 'self'; frame-ancestors 'none'; object-src 'none'; form-action 'self'; base-uri 'none' 06:58:14.636997 http.c:790 <= Recv header, 0000000030 bytes (0x0000001e) 06:58:14.637000 http.c:802 <= Recv header: Referrer-Policy: no-referrer 06:58:14.637003 http.c:790 <= Recv header, 0000000025 bytes (0x00000019) 06:58:14.637006 http.c:802 <= Recv header: Cache-Control: no-store 06:58:14.637009 http.c:790 <= Recv header, 0000000040 bytes (0x00000028) 06:58:14.637012 http.c:802 <= Recv header: Expires: Sat, 01 Jan 2000 00:00:00 GMT 06:58:14.637015 http.c:790 <= Recv header, 0000000033 bytes (0x00000021) 06:58:14.637018 http.c:802 <= Recv header: X-Content-Type-Options: nosniff 06:58:14.637028 http.c:790 <= Recv header, 0000000024 bytes (0x00000018) 06:58:14.637031 http.c:802 <= Recv header: Content-Encoding: gzip 06:58:14.637034 http.c:790 <= Recv header, 0000000023 bytes (0x00000017) 06:58:14.637037 http.c:802 <= Recv header: Vary: Accept-Encoding 06:58:14.637040 http.c:790 <= Recv header, 0000000045 bytes (0x0000002d) 06:58:14.637043 http.c:802 <= Recv header: Strict-Transport-Security: max-age=31536000 06:58:14.637049 http.c:790 <= Recv header, 0000000022 bytes (0x00000016) 06:58:14.637052 http.c:802 <= Recv header: Content-Length: 1185 06:58:14.637056 http.c:790 <= Recv header, 0000000019 bytes (0x00000013) 06:58:14.637059 http.c:802 <= Recv header: Connection: close 06:58:14.637062 http.c:790 <= Recv header, 0000000040 bytes (0x00000028) 06:58:14.637065 http.c:802 <= Recv header: Content-Type: text/html; charset=UTF-8 06:58:14.637068 http.c:790 <= Recv header, 0000000002 bytes (0x00000002) 06:58:14.637071 http.c:802 <= Recv header: 06:58:14.637122 http.c:843 == Info: Closing connection 06:58:14.637138 http.c:843 == Info: TLSv1.2 (IN), TLS alert, close notify (256): error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500 fatal: the remote end hung up unexpectedly ?mer Fad?l Usta -------------- next part -------------- An HTML attachment was scrubbed... URL: From omerusta at gmail.com Mon Apr 1 07:46:57 2024 From: omerusta at gmail.com (=?UTF-8?B?w5ZtZXIgRmFkxLFsIFVTVEE=?=) Date: Mon, 1 Apr 2024 08:46:57 +0300 Subject: Git server have some problems In-Reply-To: References: Message-ID: After a little investigation i have found that git servers actually working but there are problems on https part because i can clone with git://git.gnupg.org/gpgme.git but couldnt via https://dev.gnupg.org/source/gpgme.git ?mer Fad?l USTA , 1 Nis 2024 Pzt, 07:11 tarihinde ?unu yazd?: > Hello sorry for disturbing and I'm not sure if this is the correct place > to send this mail or not. > Currently i'm having issues to fetch gnupg's git servers and getting 500 > time to time. > > And the logs from my side is not have enough information that i can > provide but still here: > > > GIT_CURL_VERBOSE=1 git clone https://dev.gnupg.org/source/gpgme.git > Cloning into 'gpgme'... > 06:58:07.943974 http.c:843 == Info: Couldn't find host > dev.gnupg.org in the .netrc file; using defaults > 06:58:07.947668 http.c:843 == Info: Host dev.gnupg.org:443 > was resolved. > 06:58:07.947678 http.c:843 == Info: IPv6: > 2a01:4f8:160:1386::54 > 06:58:07.947681 http.c:843 == Info: IPv4: 176.9.139.178 > 06:58:07.947694 http.c:843 == Info: Trying 176.9.139.178:443 > ... > 06:58:07.993057 http.c:843 == Info: Connected to > dev.gnupg.org (176.9.139.178) port 443 > 06:58:07.994486 http.c:843 == Info: ALPN: curl offers > h2,http/1.1 > 06:58:07.994693 http.c:843 == Info: TLSv1.3 (OUT), TLS > handshake, Client hello (1): > 06:58:08.002105 http.c:843 == Info: CAfile: > /etc/ssl/certs/ca-certificates.crt > 06:58:08.002112 http.c:843 == Info: CApath: none > 06:58:11.359850 http.c:843 == Info: TLSv1.3 (IN), TLS > handshake, Server hello (2): > 06:58:11.359926 http.c:843 == Info: TLSv1.2 (IN), TLS > handshake, Certificate (11): > 06:58:11.360370 http.c:843 == Info: TLSv1.2 (IN), TLS > handshake, Server key exchange (12): > 06:58:11.361033 http.c:843 == Info: TLSv1.2 (IN), TLS > handshake, Server finished (14): > 06:58:11.361196 http.c:843 == Info: TLSv1.2 (OUT), TLS > handshake, Client key exchange (16): > 06:58:11.361325 http.c:843 == Info: TLSv1.2 (OUT), TLS change > cipher, Change cipher spec (1): > 06:58:11.361452 http.c:843 == Info: TLSv1.2 (OUT), TLS > handshake, Finished (20): > 06:58:11.406963 http.c:843 == Info: TLSv1.2 (IN), TLS > handshake, Finished (20): > 06:58:11.407032 http.c:843 == Info: SSL connection using > TLSv1.2 / ECDHE-ECDSA-AES256-GCM-SHA384 / x25519 / id-ecPublicKey > 06:58:11.407037 http.c:843 == Info: ALPN: server accepted > http/1.1 > 06:58:11.407042 http.c:843 == Info: Server certificate: > 06:58:11.407049 http.c:843 == Info: subject: CN= > dev.gnupg.org > 06:58:11.407067 http.c:843 == Info: start date: Mar 30 > 02:19:10 2024 GMT > 06:58:11.407071 http.c:843 == Info: expire date: Jun 28 > 02:19:09 2024 GMT > 06:58:11.407098 http.c:843 == Info: subjectAltName: host " > dev.gnupg.org" matched cert's "dev.gnupg.org" > 06:58:11.407106 http.c:843 == Info: issuer: C=US; O=Let's > Encrypt; CN=R3 > 06:58:11.407110 http.c:843 == Info: SSL certificate verify > ok. > 06:58:11.407118 http.c:843 == Info: Certificate level 0: > Public key type EC/secp384r1 (384/192 Bits/secBits), signed using > sha256WithRSAEncryption > 06:58:11.407123 http.c:843 == Info: Certificate level 1: > Public key type RSA (2048/112 Bits/secBits), signed using > sha256WithRSAEncryption > 06:58:11.407140 http.c:843 == Info: Certificate level 2: > Public key type RSA (4096/152 Bits/secBits), signed using > sha256WithRSAEncryption > 06:58:11.407144 http.c:843 == Info: using HTTP/1.x > 06:58:11.407229 http.c:790 => Send header, 0000000244 bytes > (0x000000f4) > 06:58:11.407236 http.c:802 => Send header: GET > /source/gpgme.git/info/refs?service=git-upload-pack HTTP/1.1 > 06:58:11.407257 http.c:802 => Send header: Host: > dev.gnupg.org > 06:58:11.407259 http.c:802 => Send header: User-Agent: > git/2.44.0 > 06:58:11.407262 http.c:802 => Send header: Accept: */* > 06:58:11.407265 http.c:802 => Send header: Accept-Encoding: > deflate, gzip, br, zstd > 06:58:11.407269 http.c:802 => Send header: Accept-Language: > en-US, *;q=0.9 > 06:58:11.407272 http.c:802 => Send header: Pragma: no-cache > 06:58:11.407275 http.c:802 => Send header: Git-Protocol: > version=2 > 06:58:11.407278 http.c:802 => Send header: > 06:58:11.407284 http.c:843 == Info: Request completely sent > off > 06:58:11.560463 http.c:790 <= Recv header, 0000000017 bytes > (0x00000011) > 06:58:11.560478 http.c:802 <= Recv header: HTTP/1.1 200 OK > 06:58:11.560503 http.c:790 <= Recv header, 0000000037 bytes > (0x00000025) > 06:58:11.560505 http.c:802 <= Recv header: Date: Mon, 01 Apr > 2024 03:58:11 GMT > 06:58:11.560509 http.c:790 <= Recv header, 0000000032 bytes > (0x00000020) > 06:58:11.560531 http.c:802 <= Recv header: Server: > Apache/2.4.54 (Debian) > 06:58:11.560534 http.c:790 <= Recv header, 0000000023 bytes > (0x00000017) > 06:58:11.560536 http.c:802 <= Recv header: X-Frame-Options: > Deny > 06:58:11.560541 http.c:790 <= Recv header, 0000000045 bytes > (0x0000002d) > 06:58:11.560544 http.c:802 <= Recv header: > Strict-Transport-Security: max-age=31536000 > 06:58:11.560548 http.c:790 <= Recv header, 0000000306 bytes > (0x00000132) > 06:58:11.560552 http.c:802 <= Recv header: > Content-Security-Policy: default-src https://files.gnupg.net; img-src > https://files.gnupg.net data:; style-src https://files.gnupg.net > 'unsafe-inline'; script-src https://files.gnupg.net; connect-src 'self'; > frame-src 'self'; frame-ancestors 'none'; object-src 'none'; form-action > 'self'; base-uri 'none' > 06:58:11.560557 http.c:790 <= Recv header, 0000000030 bytes > (0x0000001e) > 06:58:11.560559 http.c:802 <= Recv header: Referrer-Policy: > no-referrer > 06:58:11.560576 http.c:790 <= Recv header, 0000000040 bytes > (0x00000028) > 06:58:11.560579 http.c:802 <= Recv header: Expires: Fri, 01 > Jan 1980 00:00:00 GMT > 06:58:11.560582 http.c:790 <= Recv header, 0000000018 bytes > (0x00000012) > 06:58:11.560603 http.c:802 <= Recv header: Pragma: no-cache > 06:58:11.560606 http.c:790 <= Recv header, 0000000053 bytes > (0x00000035) > 06:58:11.560609 http.c:802 <= Recv header: Cache-Control: > no-cache, max-age=0, must-revalidate > 06:58:11.560620 http.c:790 <= Recv header, 0000000024 bytes > (0x00000018) > 06:58:11.560623 http.c:802 <= Recv header: Content-Encoding: > gzip > 06:58:11.560626 http.c:790 <= Recv header, 0000000023 bytes > (0x00000017) > 06:58:11.560628 http.c:802 <= Recv header: Vary: > Accept-Encoding > 06:58:11.560631 http.c:790 <= Recv header, 0000000022 bytes > (0x00000016) > 06:58:11.560634 http.c:802 <= Recv header: Content-Length: > 6939 > 06:58:11.560637 http.c:790 <= Recv header, 0000000059 bytes > (0x0000003b) > 06:58:11.560639 http.c:802 <= Recv header: Content-Type: > application/x-git-upload-pack-advertisement > 06:58:11.560655 http.c:790 <= Recv header, 0000000002 bytes > (0x00000002) > 06:58:11.560657 http.c:802 <= Recv header: > 06:58:11.560815 http.c:843 == Info: Connection #0 to host > dev.gnupg.org left intact > 06:58:11.567707 http.c:843 == Info: Couldn't find host > dev.gnupg.org in the .netrc file; using defaults > 06:58:11.567742 http.c:843 == Info: Found bundle for host: > 0x5f45ca40b310 [serially] > 06:58:11.567747 http.c:843 == Info: Can not multiplex, even > if we wanted to > 06:58:11.567771 http.c:843 == Info: Re-using existing > connection with host dev.gnupg.org > 06:58:11.567895 http.c:790 => Send header, 0000000316 bytes > (0x0000013c) > 06:58:11.567902 http.c:802 => Send header: POST > /source/gpgme.git/git-upload-pack HTTP/1.1 > 06:58:11.567923 http.c:802 => Send header: Host: > dev.gnupg.org > 06:58:11.567925 http.c:802 => Send header: User-Agent: > git/2.44.0 > 06:58:11.567928 http.c:802 => Send header: Accept-Encoding: > deflate, gzip, br, zstd > 06:58:11.567931 http.c:802 => Send header: Content-Type: > application/x-git-upload-pack-request > 06:58:11.567952 http.c:802 => Send header: Accept: > application/x-git-upload-pack-result > 06:58:11.567955 http.c:802 => Send header: Accept-Language: > en-US, *;q=0.9 > 06:58:11.567958 http.c:802 => Send header: Content-Encoding: > gzip > 06:58:11.567960 http.c:802 => Send header: Content-Length: > 3495 > 06:58:11.567963 http.c:802 => Send header: > 06:58:11.567967 http.c:843 == Info: upload completely sent > off: 3495 bytes > 06:58:14.636882 http.c:843 == Info: HTTP 1.0, assume close > after body > 06:58:14.636912 http.c:790 <= Recv header, 0000000036 bytes > (0x00000024) > 06:58:14.636918 http.c:802 <= Recv header: HTTP/1.0 500 > Internal Server Error > 06:58:14.636947 http.c:790 <= Recv header, 0000000037 bytes > (0x00000025) > 06:58:14.636969 http.c:802 <= Recv header: Date: Mon, 01 Apr > 2024 03:58:11 GMT > 06:58:14.636976 http.c:790 <= Recv header, 0000000032 bytes > (0x00000020) > 06:58:14.636979 http.c:802 <= Recv header: Server: > Apache/2.4.54 (Debian) > 06:58:14.636982 http.c:790 <= Recv header, 0000000023 bytes > (0x00000017) > 06:58:14.636985 http.c:802 <= Recv header: X-Frame-Options: > Deny > 06:58:14.636989 http.c:790 <= Recv header, 0000000306 bytes > (0x00000132) > 06:58:14.636993 http.c:802 <= Recv header: > Content-Security-Policy: default-src https://files.gnupg.net; img-src > https://files.gnupg.net data:; style-src https://files.gnupg.net > 'unsafe-inline'; script-src https://files.gnupg.net; connect-src 'self'; > frame-src 'self'; frame-ancestors 'none'; object-src 'none'; form-action > 'self'; base-uri 'none' > 06:58:14.636997 http.c:790 <= Recv header, 0000000030 bytes > (0x0000001e) > 06:58:14.637000 http.c:802 <= Recv header: Referrer-Policy: > no-referrer > 06:58:14.637003 http.c:790 <= Recv header, 0000000025 bytes > (0x00000019) > 06:58:14.637006 http.c:802 <= Recv header: Cache-Control: > no-store > 06:58:14.637009 http.c:790 <= Recv header, 0000000040 bytes > (0x00000028) > 06:58:14.637012 http.c:802 <= Recv header: Expires: Sat, 01 > Jan 2000 00:00:00 GMT > 06:58:14.637015 http.c:790 <= Recv header, 0000000033 bytes > (0x00000021) > 06:58:14.637018 http.c:802 <= Recv header: > X-Content-Type-Options: nosniff > 06:58:14.637028 http.c:790 <= Recv header, 0000000024 bytes > (0x00000018) > 06:58:14.637031 http.c:802 <= Recv header: Content-Encoding: > gzip > 06:58:14.637034 http.c:790 <= Recv header, 0000000023 bytes > (0x00000017) > 06:58:14.637037 http.c:802 <= Recv header: Vary: > Accept-Encoding > 06:58:14.637040 http.c:790 <= Recv header, 0000000045 bytes > (0x0000002d) > 06:58:14.637043 http.c:802 <= Recv header: > Strict-Transport-Security: max-age=31536000 > 06:58:14.637049 http.c:790 <= Recv header, 0000000022 bytes > (0x00000016) > 06:58:14.637052 http.c:802 <= Recv header: Content-Length: > 1185 > 06:58:14.637056 http.c:790 <= Recv header, 0000000019 bytes > (0x00000013) > 06:58:14.637059 http.c:802 <= Recv header: Connection: close > 06:58:14.637062 http.c:790 <= Recv header, 0000000040 bytes > (0x00000028) > 06:58:14.637065 http.c:802 <= Recv header: Content-Type: > text/html; charset=UTF-8 > 06:58:14.637068 http.c:790 <= Recv header, 0000000002 bytes > (0x00000002) > 06:58:14.637071 http.c:802 <= Recv header: > 06:58:14.637122 http.c:843 == Info: Closing connection > 06:58:14.637138 http.c:843 == Info: TLSv1.2 (IN), TLS alert, > close notify (256): > error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500 > fatal: the remote end hung up unexpectedly > > ?mer Fad?l Usta > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wk at gnupg.org Tue Apr 2 11:32:22 2024 From: wk at gnupg.org (Werner Koch) Date: Tue, 02 Apr 2024 11:32:22 +0200 Subject: Git server have some problems In-Reply-To: (=?utf-8?B?IsOWbWVyIEZhZMSxbA==?= USTA via Gnupg-devel"'s message of "Mon, 1 Apr 2024 08:46:57 +0300") References: Message-ID: <87bk6sds9l.fsf@jacob.g10code.de> On Mon, 1 Apr 2024 08:46, ?mer Fad?l USTA said: > on https part because i can clone with git://git.gnupg.org/gpgme.git but > couldnt via https://dev.gnupg.org/source/gpgme.git That are different boxes. For a few weeks dev.gnupg.org is often under DoS and we have to block larger net blocks from time to time. Salam-Shalom, Werner -- The pioneers of a warless world are the youth that refuse military service. - A. Einstein -------------- next part -------------- A non-text attachment was scrubbed... Name: openpgp-digital-signature.asc Type: application/pgp-signature Size: 247 bytes Desc: not available URL: From megamind6155 at nixnet.email Sun Apr 7 15:16:10 2024 From: megamind6155 at nixnet.email (megamind6155) Date: Sun, 7 Apr 2024 18:46:10 +0530 Subject: Output multiple hashes Message-ID: <6af3f826-d8c8-4880-955c-c650f96b46b2@nixnet.email> Hello, I wanted libgcrypt to print hashes of a buffer in various algorithms. for example if I have a buffer: char* buffer = "hello\n"; How do I get multiple hashes? For example, MD5 and SHA1? I've enabled both using `gcry_md_enable`, but I can only read using one algorithm using `gcry_md_read` Am I supposed to make 2 reads? What if I have many algorithms I want to use? Any help provided would be appreciated. Yours Faithfully, megamind6155. -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 236 bytes Desc: OpenPGP digital signature URL: From wk at gnupg.org Tue Apr 9 08:57:22 2024 From: wk at gnupg.org (Werner Koch) Date: Tue, 09 Apr 2024 08:57:22 +0200 Subject: Output multiple hashes In-Reply-To: <6af3f826-d8c8-4880-955c-c650f96b46b2@nixnet.email> (megamind's message of "Sun, 7 Apr 2024 18:46:10 +0530") References: <6af3f826-d8c8-4880-955c-c650f96b46b2@nixnet.email> Message-ID: <87il0r9g6l.fsf@jacob.g10code.de> On Sun, 7 Apr 2024 18:46, megamind6155 said: > I've enabled both using `gcry_md_enable`, but I can only read using > one algorithm using `gcry_md_read` Am I supposed to make 2 reads? What > if I have many algorithms I want to use? You need to specify the algorithm with gcry_md_read. Something like this: err = gcry_md_open (&md, 0, 0); if (err) { log_error ("%s: %s\n", fname?fname:"[stdin]", strerror(errno)); return; } if (!gcry_md_test_algo (GCRY_MD_MD5)) gcry_md_enable (md, GCRY_MD_MD5); gcry_md_enable (md, GCRY_MD_SHA1); if (!gcry_md_test_algo (GCRY_MD_RMD160)) gcry_md_enable (md, GCRY_MD_RMD160); if (!gcry_md_test_algo (GCRY_MD_SHA224)) gcry_md_enable (md, GCRY_MD_SHA224); if (!gcry_md_test_algo (GCRY_MD_SHA256)) gcry_md_enable (md, GCRY_MD_SHA256); if (!gcry_md_test_algo (GCRY_MD_SHA384)) gcry_md_enable (md, GCRY_MD_SHA384); if (!gcry_md_test_algo (GCRY_MD_SHA512)) gcry_md_enable (md, GCRY_MD_SHA512); while ((n=es_fread (buf, 1, DIM(buf), fp))) gcry_md_write (md, buf, n); if (es_ferror(fp)) log_error ("%s: %s\n", fname?fname:"[stdin]", strerror(errno)); else { gcry_md_final (md); if (!gcry_md_test_algo (GCRY_MD_MD5)) print_hex (md, GCRY_MD_MD5, fname); print_hex (md, GCRY_MD_SHA1, fname ); if (!gcry_md_test_algo (GCRY_MD_RMD160)) print_hex (md, GCRY_MD_RMD160, fname ); if (!gcry_md_test_algo (GCRY_MD_SHA224)) print_hex (md, GCRY_MD_SHA224, fname); if (!gcry_md_test_algo (GCRY_MD_SHA256)) print_hex (md, GCRY_MD_SHA256, fname ); if (!gcry_md_test_algo (GCRY_MD_SHA384)) print_hex (md, GCRY_MD_SHA384, fname ); if (!gcry_md_test_algo (GCRY_MD_SHA512)) print_hex (md, GCRY_MD_SHA512, fname ); } gcry_md_close (md); With print_hex() doing this: p = gcry_md_read (md, algo); n = gcry_md_get_algo_dlen (algo); Shalom-Salam, Werner -- The pioneers of a warless world are the youth that refuse military service. - A. Einstein -------------- next part -------------- A non-text attachment was scrubbed... Name: openpgp-digital-signature.asc Type: application/pgp-signature Size: 247 bytes Desc: not available URL: From tmz at pobox.com Wed Apr 10 18:08:24 2024 From: tmz at pobox.com (Todd Zullinger) Date: Wed, 10 Apr 2024 12:08:24 -0400 Subject: [PATCH gnupg] doc: Fix a few typos in agent/keyformat.txt Message-ID: -- Signed-off-by: Todd Zullinger --- agent/keyformat.txt | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/agent/keyformat.txt b/agent/keyformat.txt index e0c4df0f0..dadfed4eb 100644 --- a/agent/keyformat.txt +++ b/agent/keyformat.txt @@ -59,7 +59,7 @@ A name must start with a letter and end with a colon. Valid characters are all ASCII letters, numbers and the hyphen. Comparison of names is done case insensitively. Names may be used several times to represent an array of values. Note that the name "Key" is special -in that it is madandory must occur only once. +in that it is mandatory and must occur only once. *** Values Values are UTF-8 encoded strings. Values can be wrapped at any point, @@ -156,7 +156,7 @@ dialog window when card is not available. When the value is "no", a card operation is refused with GPG_ERR_UNUSABLE_SECKEY error. *** Backup-info -This gives information for a backup of the key. The follwoing fields +This gives information for a backup of the key. The following fields are space delimited: - Hexified keygrip (uppercase) to make it easy to identify the @@ -345,7 +345,7 @@ The currently defined protection modes are: ** Shadowed Private Key Format To keep track of keys stored on IC cards we use a third format for -private kyes which are called shadow keys as they are only a reference +private keys which are called shadow keys as they are only a reference to keys stored on a token: (shadowed-private-key @@ -395,7 +395,7 @@ This format is used to transfer keys between gpg and gpg-agent. * PUBKEYALGO is a Libgcrypt algo name * CURVENAME is the name of the curve - only used with ECC. * P1 .. PN are the parameters; the public parameters are never encrypted - the secrect key parameters are encrypted if the "protection" list is + the secret key parameters are encrypted if the "protection" list is given. To make this more explicit each parameter is preceded by a flag "_" for cleartext or "e" for encrypted text. * CSUM is the deprecated 16 bit checksum as defined by OpenPGP. This @@ -404,7 +404,7 @@ This format is used to transfer keys between gpg and gpg-agent. the old 16 bit checksum (above) is used and if it is "none" no protection at all is used. * PROTALGO is a Libgcrypt style cipher algorithm name - * IV is the initialization verctor. + * IV is the initialization vector. * S2KMODE is the value from RFC-4880. * S2KHASH is a libgcrypt style hash algorithm identifier. * S2KSALT is the 8 byte salt @@ -492,7 +492,7 @@ with "encrypted_octet_string" decoding to: (hash sha1 #0102030405060708091011121314151617181920#) ) -To compute the hash this S-expression (in canoncical format) was +To compute the hash this S-expression (in canonical format) was hashed: ((desc "List of system passphrases") -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: not available URL: From wk at gnupg.org Thu Apr 11 08:18:17 2024 From: wk at gnupg.org (Werner Koch) Date: Thu, 11 Apr 2024 08:18:17 +0200 Subject: [PATCH gnupg] doc: Fix a few typos in agent/keyformat.txt In-Reply-To: (Todd Zullinger via Gnupg-devel's message of "Wed, 10 Apr 2024 12:08:24 -0400") References: Message-ID: <87sezso21i.fsf@jacob.g10code.de> Thnaks. Salam-Shalom, Werner -- The pioneers of a warless world are the youth that refuse military service. - A. Einstein -------------- next part -------------- A non-text attachment was scrubbed... Name: openpgp-digital-signature.asc Type: application/pgp-signature Size: 247 bytes Desc: not available URL: From ben+freesoftware at benfinney.id.au Fri Apr 12 09:30:41 2024 From: ben+freesoftware at benfinney.id.au (Ben Finney) Date: Fri, 12 Apr 2024 17:30:41 +1000 Subject: GPGME: What does =?utf-8?B?4oCYMOKAmQ==?= (zero) =?utf-8?Q?=E2=80=98signature=2Esummary=E2=80=99?= value mean? Message-ID: <87jzl36nry.fsf@benfinney.id.au> Howdy, What is the meaning of a GPGME `signature` result with `summary` value 0 (zero)? The `verify` operation returns (among other things) a collection of `signature` results derived from the input data. Each `signature` is of type `gpgme_signature_t`; that object has a `summary` attribute, of type `gpgme_sigsum_t`. The value of `gpgme_sigsum_t` is a bitmap structure; the `gpgme_signature_t` documentation describes all the meanings of those flags. >From my reading of that documentation, zero is not a meaningful `gpgme_sigsum_t` value; the value should either have the `GPGME_SIGSUM_VALID` bit set (if the signature is valid), or some other combination of bits should be set. A zero `summary` (with no bits set) does not seem a possible result from that library. When I use the `verify` operation [0] (passing an inline signed data stream, read from a text file), the result is meaningful: no error, the `signature` results have the expected keys and timestamp etc, but each has a `summary` value of 0. What does this value mean; what user-level meaning does it represent? How is `summary` value 0 meaning different from `GPGME_SIGSUM_VALID`? How is its meaning different from any other possible `summary` value? [0]: If it matters, I am using the Python PyGPGME wrapper. From what I can tell the wrapper is simply exposing the GPGME interface with Python objects, so I believe the questions above are all about the underlying GPGME library API. -- \ ?A thing moderately good is not so good as it ought to be. `\ Moderation in temper is always a virtue; but moderation in _o__) principle is always a vice.? ?Thomas Paine Ben Finney From wk at gnupg.org Sun Apr 14 11:39:20 2024 From: wk at gnupg.org (Werner Koch) Date: Sun, 14 Apr 2024 11:39:20 +0200 Subject: GPGME: What does =?utf-8?B?4oCYMOKAmQ==?= (zero) =?utf-8?Q?=E2=80=98signature=2Esummary=E2=80=99?= value mean? In-Reply-To: <87jzl36nry.fsf@benfinney.id.au> (Ben Finney's message of "Fri, 12 Apr 2024 17:30:41 +1000") References: <87jzl36nry.fsf@benfinney.id.au> Message-ID: <8734romgfr.fsf@jacob.g10code.de> On Fri, 12 Apr 2024 17:30, Ben Finney said: > What is the meaning of a GPGME `signature` result with `summary` value 0 > (zero)? There might be a bug in the code. We have not touched it in the last 20 years, though. Firs the flags are computed. /* Calculate the red/green flag. */ if (sig->validity == GPGME_VALIDITY_FULL || sig->validity == GPGME_VALIDITY_ULTIMATE) { if (gpg_err_code (sig->status) == GPG_ERR_NO_ERROR || gpg_err_code (sig->status) == GPG_ERR_SIG_EXPIRED || gpg_err_code (sig->status) == GPG_ERR_KEY_EXPIRED) sum |= GPGME_SIGSUM_GREEN; } else if (sig->validity == GPGME_VALIDITY_NEVER) { if (gpg_err_code (sig->status) == GPG_ERR_NO_ERROR || gpg_err_code (sig->status) == GPG_ERR_SIG_EXPIRED || gpg_err_code (sig->status) == GPG_ERR_KEY_EXPIRED) sum |= GPGME_SIGSUM_RED; } else if (gpg_err_code (sig->status) == GPG_ERR_BAD_SIGNATURE) sum |= GPGME_SIGSUM_RED; Further on the SUM is not modified if we see no error or bad signature. Thus there are cases - depending on the signature validity and the error code when SUM might still be zero. A new error code emitted by gpg could result in this behaviour. Do you have an example? Salam-Shalom, Werner -- The pioneers of a warless world are the youth that refuse military service. - A. Einstein -------------- next part -------------- A non-text attachment was scrubbed... Name: openpgp-digital-signature.asc Type: application/pgp-signature Size: 247 bytes Desc: not available URL: From ben+freesoftware at benfinney.id.au Mon Apr 15 06:01:21 2024 From: ben+freesoftware at benfinney.id.au (Ben Finney) Date: Mon, 15 Apr 2024 14:01:21 +1000 Subject: GPGME: What does =?utf-8?B?4oCYMOKAmQ==?= (zero) =?utf-8?Q?=E2=80=98signature=2Esummary=E2=80=99?= value mean? References: <87jzl36nry.fsf@benfinney.id.au> <8734romgfr.fsf@jacob.g10code.de> Message-ID: <87frvn5l66.fsf@benfinney.id.au> Werner Koch via Gnupg-devel writes: > There might be a bug in the code. We have not touched it in the last > 20 years, though. Thank you, I hope it's a simple as a bug. > [?] there are cases - depending on the signature validity and the > error code when SUM might still be zero. A new error code emitted by > gpg could result in this behaviour. > > Do you have an example? Included in this message is a Python program ?verify_test.py?. That program makes use of the ?python-gpg? library, the Python wrapper of GPGME. The program includes inline a clear-signed message, and when run it will use ?gpg.Context.verify? to verify the message. It then reports the result of that call. Here is the session where I run the program: ===== $ python3 verify_test.py GnuPG verify message from file ??: ?gpg.Context.verify? returned result: VerifyResult(file_name=None, is_mime=0, signatures=[Signature(chain_model=False, exp_timestamp=0, fpr='6159E0F29E2FA412E0795C73F9B46AAC84420C82', hash_algo=8, is_de_vs=False, key=None, notations=[], pka_address=None, pka_trust=0, pubkey_algo=1, status=0, summary=0, timestamp=1713137533, validity=0, validity_reason=0, wrong_key_usage=False)]) Signature at index 0: Signature(chain_model=False, exp_timestamp=0, fpr='6159E0F29E2FA412E0795C73F9B46AAC84420C82', hash_algo=8, is_de_vs=False, key=None, notations=[], pka_address=None, pka_trust=0, pubkey_algo=1, status=0, summary=0, timestamp=1713137533, validity=0, validity_reason=0, wrong_key_usage=False) ===== You can see that the ?verify? call succeeds (no error is raised), and there is a single attached Signature. That Signature, though it has a valid timestamp and fingerprint, has ?0? for all of ?pka_trust?, ?status?, ?summary?, ?validity?, and ?validity_reason?. -------------- next part -------------- A non-text attachment was scrubbed... Name: verify_test.py Type: text/x-python Size: 2608 bytes Desc: Python program ?verify_test.py?, to demonstrate signature verification URL: -------------- next part -------------- -- \ ?When I was born I was so surprised I couldn't talk for a year | `\ and a half.? ?Gracie Allen | _o__) | Ben Finney From kloecker at kde.org Mon Apr 15 14:00:49 2024 From: kloecker at kde.org (Ingo =?ISO-8859-1?Q?Kl=F6cker?=) Date: Mon, 15 Apr 2024 14:00:49 +0200 Subject: GPGME: What does =?UTF-8?B?4oCYMOKAmSAoemVybykg4oCYc2lnbmF0dXJlLnN1bW1hcnnigJk=?= value mean? In-Reply-To: <87frvn5l66.fsf@benfinney.id.au> References: <87jzl36nry.fsf@benfinney.id.au> <8734romgfr.fsf@jacob.g10code.de> <87frvn5l66.fsf@benfinney.id.au> Message-ID: <12421620.O9o76ZdvQC@daneel> On Montag, 15. April 2024 06:01:21 CEST Ben Finney wrote: > Werner Koch via Gnupg-devel writes: > > Do you have an example? > > Included in this message is a Python program ?verify_test.py?. That > program makes use of the ?python-gpg? library, the Python wrapper of > GPGME. > > The program includes inline a clear-signed message, and when run it will > use ?gpg.Context.verify? to verify the message. It then reports the > result of that call. It would be helpful if you also gave us the public key. Because now I get ``` $ gpg --status-fd 2 gpg: WARNING: no command supplied. Trying to guess what you mean ... gpg: Go ahead and type your message ... ... [GNUPG:] NEWSIG gpg: Signature made Mo 15 Apr 2024 01:32:13 CEST gpg: using RSA key 6159E0F29E2FA412E0795C73F9B46AAC84420C82 [GNUPG:] ERRSIG F9B46AAC84420C82 1 8 01 1713137533 9 6159E0F29E2FA412E0795C73F9B46AAC84420C82 [GNUPG:] NO_PUBKEY F9B46AAC84420C82 gpg: Can't check signature: No public key ``` Please also provide the output you get when you run `gpg --status-fd 2` on the message. Regards, Ingo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part. URL: From ben+freesoftware at benfinney.id.au Wed Apr 17 04:08:12 2024 From: ben+freesoftware at benfinney.id.au (Ben Finney) Date: Wed, 17 Apr 2024 12:08:12 +1000 Subject: GPGME: What does =?utf-8?B?4oCYMOKAmQ==?= (zero) =?utf-8?Q?=E2=80=98signature=2Esummary=E2=80=99?= value mean? References: <87jzl36nry.fsf@benfinney.id.au> <8734romgfr.fsf@jacob.g10code.de> <87frvn5l66.fsf@benfinney.id.au> <12421620.O9o76ZdvQC@daneel> Message-ID: <8734rk68s3.fsf@benfinney.id.au> Ingo Kl?cker writes: > It would be helpful if you also gave us the public key. Oh, I had expected a GnuPG client would fetch the key? It's part of the signed message metadata, so it should be automatically fetched from the key servers, I'd expect. Regardless, here is the URL to download that public key: > Please also provide the output you get when you run `gpg --status-fd > 2` on the message. Here is the session: ===== $ gpg --status-fd 2 foo.txt.asc gpg: WARNING: no command supplied. Trying to guess what you mean ... [GNUPG:] PLAINTEXT 74 0 [GNUPG:] NEWSIG gpg: Signature made Mon 15 Apr 2024 09:32:13 AEST gpg: using RSA key 6159E0F29E2FA412E0795C73F9B46AAC84420C82 [GNUPG:] KEYEXPIRED 1446855895 [GNUPG:] KEYEXPIRED 1541729896 [GNUPG:] KEYEXPIRED 1650968464 [GNUPG:] KEY_CONSIDERED 517CF14BB2F398B0CB354855B8B24C06AC128405 0 [GNUPG:] SIG_ID R7hUtvOTHhmxxN8Fpqx8OxQtJ2w 2024-04-14 1713137533 [GNUPG:] KEYEXPIRED 1446855895 [GNUPG:] KEYEXPIRED 1541729896 [GNUPG:] KEYEXPIRED 1650968464 [GNUPG:] KEY_CONSIDERED 517CF14BB2F398B0CB354855B8B24C06AC128405 0 [GNUPG:] GOODSIG F9B46AAC84420C82 Ben Finney gpg: Good signature from "Ben Finney " [unknown] gpg: aka "Ben Finney (White Tree) " [unknown] gpg: aka "Ben Finney (Free Software Foundation) " [unknown] gpg: aka "Ben Finney (Debian) " [unknown] gpg: aka "[jpeg image of size 8917]" [unknown] gpg: aka "[jpeg image of size 6222]" [unknown] gpg: aka "Ben Finney " [unknown] gpg: aka "Ben Finney " [unknown] gpg: aka "Ben Finney " [unknown] gpg: aka "Ben Finney (Debian Project) " [unknown] [GNUPG:] VALIDSIG 6159E0F29E2FA412E0795C73F9B46AAC84420C82 2024-04-14 1713137533 0 4 0 1 8 01 517CF14BB2F398B0CB354855B8B24C06AC128405 [GNUPG:] KEYEXPIRED 1446855895 [GNUPG:] KEYEXPIRED 1541729896 [GNUPG:] KEYEXPIRED 1650968464 [GNUPG:] KEY_CONSIDERED 517CF14BB2F398B0CB354855B8B24C06AC128405 0 [GNUPG:] KEYEXPIRED 1446855895 [GNUPG:] KEYEXPIRED 1541729896 [GNUPG:] KEYEXPIRED 1650968464 [GNUPG:] KEY_CONSIDERED 517CF14BB2F398B0CB354855B8B24C06AC128405 0 [GNUPG:] TRUST_UNDEFINED 0 pgp gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 517C F14B B2F3 98B0 CB35 4855 B8B2 4C06 AC12 8405 Subkey fingerprint: 6159 E0F2 9E2F A412 E079 5C73 F9B4 6AAC 8442 0C82 ===== So, the key is expired; but this (correctly) does not cause the signature verification to fail. -- \ ?Some subjects are so serious that one can only joke about | `\ them.? ?Niels Bohr | _o__) | Ben Finney From wk at gnupg.org Mon Apr 29 10:05:08 2024 From: wk at gnupg.org (Werner Koch) Date: Mon, 29 Apr 2024 10:05:08 +0200 Subject: Very first Beta of GnuPG 2.6 available Message-ID: <87jzkg8uh7.fsf@jacob.g10code.de> Hi! Gniibe and me have been working on PQC Support in GnuPG for some time now. Now we have a first Beta version available. Because we have done no releases of the supporting libraries yet, a tarball with all sources is available: https://gnupg.org/ftp/gcrypt/snapshots/gnupg/gnupg-w32-2.5.0-beta465_20240426.tar.xz https://gnupg.org/ftp/gcrypt/snapshots/gnupg/gnupg-w32-2.5.0-beta465_20240426.tar.xz.sig Don't mind the w32 - it is the tarball we usually provide with a Windows installer. Building the installer works too but needs some fine tuning. Thus no binary yet. Before you build, please make sure to install the patch elf utility. Then run make -f build-aux/speedo.mk native and follow the printed instructions. To create a Kyber key, you need to first create a standard key and then use gpg --quick--add-key kyber to add a Kyber encryption subkey. You mal also use ky1024_bp256 or ky768_cv448 to create other variants. Sample keys are also provided in gnupg/tests/openpgp/samplekeys. Spec details will follow soonish. Salam-Shalom, Werner -- The pioneers of a warless world are the youth that refuse military service. - A. Einstein -------------- next part -------------- A non-text attachment was scrubbed... Name: openpgp-digital-signature.asc Type: application/pgp-signature Size: 247 bytes Desc: not available URL: