all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jack Hill <jackhill@jackhill.us>
To: 47331@debbugs.gnu.org
Cc: Raghav Gururajan <rg@raghavgururajan.name>
Subject: bug#47331: Psi (and Psi-plus) aren't able to validate certificates
Date: Mon, 22 Mar 2021 19:50:20 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.21.2103221936100.8138@marsh.hcoop.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]

Hi Guix,

I'm using Guix System with commit 17b408e6a219d64643717cfde16ce04eea0a4590 
and both the psi and psi-plus package are unable to validate the 
certificate of the XMPP server when connecting. When logging into an 
account, a popup error appears saying "The member.fsf.org certificate 
failed the authenticity test. Invalid CA certificate." Clicking on 
"details…" results in the attached screenshot. It appears that a valid 
certificate is being presented by the server, but psi doesn't have 
certificate authority in its trust store. I've tried it with both psi 
installed in my default user profile and nss-certs installed in the system 
profile as well and with `guix environment --ad-hoc psi nss-certs -- psi`.

My environment variable appear to be set correctly:

jackhill@alperton ~$ env|grep -i ssl
GIT_SSL_CAINFO=/etc/ssl/certs/ca-certificates.crt
SSL_CERT_DIR=/run/current-system/profile/etc/ssl/certs
SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt

The problem appears across different XMPP servers. I've tried the ones 
for member.fsf.org, duke.edu, and hcoop.net. The IM Observatory doesn't 
report any problems with the configuration of member.fsf.org [0]. I see 
the exact same problem and error messages with both psi and psi-plus.

[0] https://www.xmpp.net/result.php?id=1481007

Best,
Jack

[-- Attachment #2: Type: image/png, Size: 67275 bytes --]

                 reply	other threads:[~2021-03-22 23:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.21.2103221936100.8138@marsh.hcoop.net \
    --to=jackhill@jackhill.us \
    --cc=47331@debbugs.gnu.org \
    --cc=rg@raghavgururajan.name \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.