From: Arun Isaac <arunisaac@systemreboot.net>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: Building a secure communications server
Date: Sat, 13 May 2017 17:04:38 +0530 [thread overview]
Message-ID: <51f03a37.AEAAKHxcPksAAAAAAAAAAAOtZhgAAAACwQwAAAAAAAW9WABZFu9_@mailjet.com> (raw)
In-Reply-To: <20170513060327.GA20242@thebird.nl>
> What I want achieve is that we can fire up an image on a VPS with safe
> communications.
VPSs may be a start. But, I'm not comfortable with them long term. We
should push for users to self-host their own infrastructure. It should
be something like the FreedomBox project.
https://freedomboxfoundation.org/
The FreedomBox project is based on Debian. Perhaps, we can build
something similar, but based on Guix.
Currently, I self-host my blog, email, XMPP, GNU Social, and a few other
services on my home ADSL connection with an Intel NUC running Parabola
GNU/Linux. At some point in the future, I will migrate it to Guix.
> What would be a good webmail service to run over https? Should be
> simple and secure (these go together, as you know). And should it run
> over imap? I think we'll need to provide imap anyway.
Roundcube is what I use. I don't know if there are better options.
https://roundcube.net/
next prev parent reply other threads:[~2017-05-13 11:35 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
2017-05-13 11:50 ` Pjotr Prins
2017-05-13 11:34 ` Arun Isaac [this message]
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=51f03a37.AEAAKHxcPksAAAAAAAAAAAOtZhgAAAACwQwAAAAAAAW9WABZFu9_@mailjet.com \
--to=arunisaac@systemreboot.net \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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).