From: "Ludovic Courtès" <ludo@gnu.org>
To: bo0od <bo0od@riseup.net>
Cc: 43770-done@debbugs.gnu.org
Subject: bug#43770: Geeks think securely: VM per Package (trustless state to devs and their apps)
Date: Mon, 05 Oct 2020 16:00:55 +0200 [thread overview]
Message-ID: <87zh50wz54.fsf@gnu.org> (raw)
In-Reply-To: <c561674e-ef70-d36f-c991-f89a18d2d656@riseup.net> (bo0od@riseup.net's message of "Fri, 2 Oct 2020 22:18:24 +0000")
Hi,
bo0od <bo0od@riseup.net> skribis:
> Actually what i wanted to say but seems i missed it, This security
> design can be engineered and implemented when Guixsd released based on
> GNU-Hurd Kernel. Because its going to be totally new kernel and having
> this feature is without question the best security feature for the
> future of security within operating systems.
>
> Otherwise we gonna fall into the same cycle of trust to outside
> package developers and their codes without preventive mechanism
> against if its malicious one.
>
> If you mean the bug report is not the place for this request, then i
> dont know where because i already discussed it in the IRC channel.(if
> there is somewhere else i can report this just tell me)
It’s great to share your views of what you think should be done from a
security standpoint. There’s little more we contributors can say other
than: yes, we agree, we’re working in this direction, and it’s going to
be a long journey.
What could help though is if people like you come and join us on that
journey. I very much encourage you to play with Guix System and in
particular with the “childhurd” service that has recently landed and
should be of interest to you.
For now I’m closing the bug because as Ricardo wrote, it’s not a bug
report per se.
Thank you,
Ludo’.
next prev parent reply other threads:[~2020-10-05 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 18:01 bug#43770: Geeks think securely: VM per Package (trustless state to devs and their apps) bo0od
2020-10-02 19:44 ` Ricardo Wurmus
2020-10-02 22:18 ` bo0od
2020-10-05 14:00 ` Ludovic Courtès [this message]
2020-10-02 19:45 ` raingloom
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=87zh50wz54.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=43770-done@debbugs.gnu.org \
--cc=bo0od@riseup.net \
/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.