From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: bug#46258: Potential security weakness in Guix services
Date: Fri, 05 Feb 2021 15:16:39 +0100 [thread overview]
Message-ID: <c6164b827beb62aa8f8f276473081eb7cf557110.camel__24498.4769307607$1612534675$gmane$org@telenet.be> (raw)
In-Reply-To: <56adb5efa894304c27beba99b07e2f8cfd8ee7cb.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 456 bytes --]
On Fri, 2021-02-05 at 13:20 +0100, Maxime Devos wrote:
> On Fri, 2021-02-05 at 10:57 +0100, Ludovic Courtès wrote:
> > [...]
> [...]
>
> I'll try to implement this API in Scheme (using the FFI), and post
> it at https://notabug.org/mdevos/things. I'll post a follow-up
> messsage once I've implemented the basics (openat, chmodat,
> chownat).
Ping!
https://notabug.org/mdevos/things/src/a0715e6758ad43252e16993dcf688a25156057f3/fs-at.scm
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
parent reply other threads:[~2021-02-05 14:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <56adb5efa894304c27beba99b07e2f8cfd8ee7cb.camel@telenet.be>]
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='c6164b827beb62aa8f8f276473081eb7cf557110.camel__24498.4769307607$1612534675$gmane$org@telenet.be' \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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.
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).