From: Bill <wch1m1@gmail.com>
To: selinux@tycho.nsa.gov
Subject: Re: [SUSPECTED SPAM] SELinux/Docker blog on passing socket descriptors between containers.
Date: Tue, 10 May 2016 11:29:36 -0400 [thread overview]
Message-ID: <5731FE60.8080505@gmail.com> (raw)
In-Reply-To: <561c08fe-01b4-33ab-ed0b-0441e7f12a21@redhat.com>
This sort of works sandbox -i [path to be copied]?
On 05/09/2016 01:21 PM, Daniel J Walsh wrote:
> http://danwalsh.livejournal.com/74421.html
>
> _______________________________________________
> Selinux mailing list
> Selinux@tycho.nsa.gov
> To unsubscribe, send email to Selinux-leave@tycho.nsa.gov.
> To get help, send an email containing "help" to
> Selinux-request@tycho.nsa.gov.
>
--
William Chimiak
Laboratory for Telecommunication Sciences
prev parent reply other threads:[~2016-05-10 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 17:21 [SUSPECTED SPAM] SELinux/Docker blog on passing socket descriptors between containers Daniel J Walsh
2016-05-10 15:29 ` Bill [this message]
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=5731FE60.8080505@gmail.com \
--to=wch1m1@gmail.com \
--cc=selinux@tycho.nsa.gov \
--cc=w.chimiak@ieee.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 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.