From: Pierre Neidhardt <mail@ambrevar.xyz>
To: John Soo <jsoo1@asu.edu>
Cc: guix-devel@gnu.org
Subject: Re: TLS certificates for web browsers in guix environment --container
Date: Tue, 21 Apr 2020 18:17:58 +0200 [thread overview]
Message-ID: <87o8rkq0cp.fsf@ambrevar.xyz> (raw)
In-Reply-To: <94FBCA48-A4AC-4340-B9E3-DA6CEB333545@asu.edu>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
It works!
--8<---------------cut here---------------start------------->8---
guix environment -C -N --expose=/etc/machine-id --expose=/etc/ssl/certs/ \
--share=$HOME/.local/share/eolie/=$HOME/.local/share/eolie/ \
--ad-hoc dbus eolie coreutils nss-certs -- \
env DISPLAY=$DISPLAY eolie
--8<---------------cut here---------------end--------------->8---
Note that the "--expose=/etc/ssl/certs/" is important.
Should we consider this a bug? If not, then should we document
it?
Maybe this could be automated a bit.
--8<---------------cut here---------------start------------->8---
guix size webkitgtk glib-networking
--8<---------------cut here---------------end--------------->8---
does not return nss-certs. So if we made nss-certs an input of
webkitgtk (or glib-networking?), we would not need nss-certs in the guix
environment invocation.
Finally, I'm not sure how to fix the /etc/ssl/certs issue. Why do we
have to put it under /etc/ in the first place?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-04-21 16:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 13:03 TLS certificates for web browsers in guix environment --container Pierre Neidhardt
2020-04-21 15:45 ` John Soo
2020-04-21 16:17 ` Pierre Neidhardt [this message]
2020-04-21 16:36 ` Leo Famulari
2020-04-21 20:50 ` Pierre Neidhardt
2020-04-22 7:15 ` Konrad Hinsen
2020-04-22 19:33 ` Leo Famulari
2020-05-03 9:19 ` Pierre Neidhardt
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8rkq0cp.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=jsoo1@asu.edu \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).