From: Juliusz Chroboczek <jch@irif.fr>
To: galene@lists.galene.org
Subject: [Galene] Re: Command-line client for Galene file transfer
Date: Sun, 30 Apr 2023 14:35:10 +0200 [thread overview]
Message-ID: <87zg6pzgxt.wl-jch@irif.fr> (raw)
In-Reply-To: <875y9d1u42.wl-jch@irif.fr>
> a native command-line client for file transfer.
To answer in public the question I got by private mail:
- the transfer is peer-to-peer, the server is only used for NAT
traversal and for exchanging cryptographic keys; hence, you're not
putting any significant load on the server if you use this to backup
the collection of movies that you legally acquired;
- the transfer is encrypted end-to-end; however,
(1) the server gets to learn the filenames and file sizes;
(2) the server can trivially mount an MiTM attack.
so you must use a trusted server if you wish to preserve a semblance
of privacy.
I am fairly confident that the latter caveat also applies to Zoom's
"end-to-end" encryption. Do not trust any software, especially if you
didn't write it yourself.
-- Juliusz
prev parent reply other threads:[~2023-04-30 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-30 11:34 [Galene] " Juliusz Chroboczek
2023-04-30 12:35 ` Juliusz Chroboczek [this message]
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://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zg6pzgxt.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=galene@lists.galene.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