mlmmj.mlmmj.org archive mirror
 help / color / mirror / Atom feed
From: "A. Schulze" <sca@andreasschulze.de>
To: mlmmj@mlmmj.org
Subject: [mlmmj] state of mlmmj-archiver (and mlmmj.org)
Date: Mon, 15 Apr 2019 19:25:01 +0000	[thread overview]
Message-ID: <5b5d9093-fc91-56d4-c9e8-425cab50d70b@andreasschulze.de> (raw)

Hello,

the author of https://git.cryptomilk.org/projects/mlmmj-webarchiver.git told me off-list he's fine if
that work will be transferred to https://gitlab.com/mlmmj.

He's currently not subscribed to any mlmmj related list. Reason TLS compatibility issues.

And - to be honest - it's reasonable. The mlmmj.org domain is using really,really outdated crypto:
no HTTPS at all and tls1.0 maximum for SMTP :-/

This is a major barrier for participants.

Andreas

- https://internet.nl/site/mlmmj.org/510595/
- https://www.hardenize.com/report/mlmmj.org/1555355696


             reply	other threads:[~2019-04-15 19:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 19:25 A. Schulze [this message]
2019-04-16 19:46 ` [mlmmj] state of mlmmj-archiver (and mlmmj.org) Geert Stappers
2019-04-17 20:30 ` Geert Stappers

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=5b5d9093-fc91-56d4-c9e8-425cab50d70b@andreasschulze.de \
    --to=sca@andreasschulze.de \
    --cc=mlmmj@mlmmj.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 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).