From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Moving from Lastpass to Bitwarden
Date: Sat, 20 Feb 2021 08:29:00 +0000 [thread overview]
Message-ID: <20210220082900.32829325@digimed.co.uk> (raw)
In-Reply-To: <20210220030721.u4sdzeoxrjrtiflf@aurora>
[-- Attachment #1: Type: text/plain, Size: 1400 bytes --]
On Fri, 19 Feb 2021 22:07:21 -0500, Kusoneko wrote:
> That is also what I use. I also personally use my phone with KeepassDX
> for when I'm not next to my personal PC, and I have the databases synced
> together through Syncthing. However, on the topic of Syncthing, I
> haven't had any issue so far, but I also haven't been able to find
> anywhere if the thing encrypts traffic that's sent from anywhere to
> anywhere else. From what I understand of Syncthing though, it seems to
> give each machine a unique ID, let's you give them names and then
> specify a shared folder, then using the local networks it can find
> other devices running Syncthing, and on the wider internet, it seems to
> connect to some random "discovery servers" that seem like their purpose
> is to act as a way to have the devices find each other if they're on
> other networks so that the shared directories stay synced at all times.
That's correct. Syncthing is P2P, the only traffic that goes through
their servers is for discovery. If even that is too much for you, you can
run your own discovery server.
> I just wish I knew if the files are encrypted e2e or not when using
> this.
According to Syncthing's own FAQ "Data that is sent over the network is
compressed (optionally) and encrypted (always). "
--
Neil Bothwick
Bagpipe for free: Stuff cat under arm. Pull legs, chew tail.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-02-20 8:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 0:04 [gentoo-user] Moving from Lastpass to Bitwarden Dale
2021-02-17 7:03 ` Arve Barsnes
2021-02-17 8:01 ` Dale
2021-02-17 21:16 ` Rich Freeman
2021-02-18 5:08 ` Dale
2021-02-18 10:20 ` Dr Rainer Woitok
2021-02-18 10:37 ` Dale
2021-02-17 8:07 ` Raphaël Badertscher
2021-02-17 9:44 ` John Covici
2021-02-17 12:15 ` Dale
2021-02-17 12:30 ` Neil Bothwick
2021-02-17 12:51 ` Dale
2021-02-19 21:05 ` Spackman, Chris
2021-02-17 20:49 ` [gentoo-user] " Grant Edwards
2021-02-18 14:22 ` [gentoo-user] " Frank Steinmetzger
2021-02-18 15:04 ` Neil Bothwick
2021-02-18 15:36 ` John Covici
2021-02-18 16:02 ` Neil Bothwick
2021-02-18 20:14 ` Frank Steinmetzger
2021-02-18 21:23 ` [gentoo-user] " Grant Edwards
2021-02-18 16:07 ` [gentoo-user] " Dale
2021-02-18 20:38 ` Frank Steinmetzger
2021-02-20 3:07 ` Kusoneko
2021-02-20 8:29 ` Neil Bothwick [this message]
2021-02-19 23:22 ` [gentoo-user] " Grant Edwards
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=20210220082900.32829325@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.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