unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: bo0od <bo0od@riseup.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 43770@debbugs.gnu.org
Subject: bug#43770: Geeks think securely: VM per Package (trustless state to devs and their apps)
Date: Fri, 2 Oct 2020 22:18:24 +0000	[thread overview]
Message-ID: <c561674e-ef70-d36f-c991-f89a18d2d656@riseup.net> (raw)
In-Reply-To: <87mu14e7k5.fsf@elephly.net>

Hey,

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)

ThX!

Ricardo Wurmus:
> 
> Hi,
> 
> this does not look like an actionable bug report.  What is it exactly
> that ought to be done in your opinion?
> 




  reply	other threads:[~2020-10-02 22:25 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 [this message]
2020-10-05 14:00     ` Ludovic Courtès
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

  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=c561674e-ef70-d36f-c991-f89a18d2d656@riseup.net \
    --to=bo0od@riseup.net \
    --cc=43770@debbugs.gnu.org \
    --cc=rekado@elephly.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 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).