unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@pragmatique.xyz>
To: guix-devel@gnu.org
Subject: Re: Building a secure communications server
Date: Sat, 13 May 2017 11:31:28 +0000	[thread overview]
Message-ID: <nycvar.YAK.7.76.1705131044130.680@ybpnyubfg> (raw)
In-Reply-To: <20170513060327.GA20242@thebird.nl>

On Sat, 13 May 2017, Pjotr Prins wrote:

> In light of recent political attacks on E-mail servers in France and
> the USA and in light of the current worm attack I think it is very
> clear we need communication servers we can trust. I am running my own
> E-mail server and with the progress we are making in GNU Guix (system
> configuration, image creation) I think we are close to creating a
> solution that others can use. What I want achieve is that we can fire
> up an image on a VPS with safe communications. It would contain a mail
> server and webmail. The user will have option to allow users to only
> communicate internally and, perhaps, keep incoming mail in one account
> keeping mail in 'escrow'.
>
> This image should be state-of-the-art in security setup. Guix can help
> greatly there. Part of the security will come from the fact that these
> machines are not centrally hosted. An alternative to protonmail, for
> example. We should be able to lose a few servers as long as we get
> notified somehow that they have been compromised. This is a biological
> model of defence.
>
> Who wants to help me create such a solution? It has to be a team
> effort. If you need bread we can also try and find some money. In fact
> it would be great to get someone full time hacking on this.
>
> Who wants to run such a server? We also need users. I would have set
> up a couple of such instances today for teams on the road in
> Asia/Africa.
>
> I realise this may take some resources from Guix development, but I
> think it is justified and it may gain Guix more attention and
> traction!
>
> Pj.
>
>
>
>

10 or 13 years ago something similar was my motivation. A project
which can be regarded as the base of some of my current work.
Its name was "arda/libertad". It was supposed to be an re-implementation
of the R-Plan, an Orangebook Autistici/Inventati came up with for
resilent servers running in an global network.

Logic and Progression drove me to distributed networks and ultimately
abandon the plan of using server based technologies, rely as little
as possible on servers even if it takes years of development.

That said, what you wrote is something I talked about with
people in Netherlands until 1 or 2 years ago the contact just
dropped. I think the very fragmented groups of anarchists in Netherlands
is one group of people who is interested. There are other groups,
but in general you have to be clear:
do you want people with prior knowledge in system administration to
use the 'spawn a VM' system, or do want to people without any prior
interest or knowledge in system administration to use this?
I tend towards the last option, but it depends on the system you
want to design.
This is still one of the reasons I am working on GuixSD and the
system I create with GuixSD. I don't want to talk about specific
groups or people, but there's huge value for easy to use systems
for the people running their own factories, people who fight against
oppression in their country, etc, last not least for everyone if
you design a system in a way that it can be used by anyone dead simple.

Some of the projects I am working on are vaguely oriented
around the R-Plan with extensions of own ideas. To some degree we could 
colaborate.
I can't work fulltime on this, but expertise and exchange of knowledge
is useful since we are working with the same system.
Once university starts my work on free software will, at least for a 
while, no longer be fulltime but since I am working towards a
business within the next 4 years I will continue to work on it.
It would probably help if I could be more specific as I have multiple
plans in parallel which involve GuixSD, but I am working on the separation
of interests.

Public documentation at the moment is rare, but in case you want to talk 
about ideas here is the fingerprint of my pubkey: 
17A9D52A7EE8885AB35D819DA58C87D08AFD4FAD

The link to R-Plan: https://www.autistici.org/who/rplan/

  parent reply	other threads:[~2017-05-13 11:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-13  6:03 Building a secure communications server Pjotr Prins
2017-05-13  6:30 ` Pjotr Prins
2017-05-13 11:31 ` ng0 [this message]
2017-05-13 11:50   ` Pjotr Prins
2017-05-13 11:34 ` Arun Isaac
2017-05-13 14:33   ` Ludovic Courtès
2017-05-17 11:51     ` Pjotr Prins
2017-05-17 12:26       ` Clément Lassieur
2017-05-17 13:04         ` Pjotr Prins
2017-05-17 13:06           ` Pjotr Prins
2017-05-19  9:01         ` Ludovic Courtès
2017-05-19 14:49           ` onionmail + bitmessage Fox
     [not found] ` <a242d07c.AEAAKHxcPkwAAAAAAAAAAAO9s5IAAAACwQwAAAAAAAW9WABZFu9_@mailjet.com>
2017-05-13 11:53   ` Building a secure communications server Pjotr Prins

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=nycvar.YAK.7.76.1705131044130.680@ybpnyubfg \
    --to=ng0@pragmatique.xyz \
    --cc=guix-devel@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.
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).