From: Christoph Anton Mitterer <calestyo@scientia.net>
To: "Swâmi Petaramesh" <swami@petaramesh.org>
Cc: Martin Steigerwald <martin@lichtvoll.de>, linux-btrfs@vger.kernel.org
Subject: Re: send/receive for encrypted backup purposes
Date: Fri, 08 Jan 2016 15:07:21 +0100 [thread overview]
Message-ID: <1452262041.6727.15.camel@scientia.net> (raw)
In-Reply-To: <4248922.XAnqWXRFKA@vajra>
[-- Attachment #1: Type: text/plain, Size: 776 bytes --]
On Fri, 2016-01-08 at 15:02 +0100, Swâmi Petaramesh wrote:
> Le vendredi 8 janvier 2016, 15:00:46 Christoph Anton Mitterer a écrit
> :
> > Shouldn't any crypto that can read from stdin and write to stdout
> > do
> > that?
> > E.g. simply ssh.
> >
> > hostA$ btrfs send foo | ssh hostB btrfs receive bar
>
> It works, I do this on a regular basis…
One should perhaps only ask some SSH experts, whether their crypto is
actually safe for such use case.
I mean depending on what kind of data is send (e.g. often repeating
patterns and so on) some crypto schemas may be more pron to statistical
attacks than other.
But I wouldn't see much problems... ssh has rather problems with
statistical attacks when measuring keystroke times...
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]
next prev parent reply other threads:[~2016-01-08 14:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 13:44 send/receive for encrypted backup purposes Martin Steigerwald
2016-01-08 14:00 ` Christoph Anton Mitterer
2016-01-08 14:02 ` Swâmi Petaramesh
2016-01-08 14:07 ` Christoph Anton Mitterer [this message]
2016-01-08 14:40 ` Austin S. Hemmelgarn
2016-01-08 14:49 ` Christoph Anton Mitterer
2016-01-08 15:04 ` Austin S. Hemmelgarn
2016-01-08 15:01 ` Austin S. Hemmelgarn
2016-01-09 19:05 ` Christoph Biedl
2016-01-11 12:50 ` Austin S. Hemmelgarn
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=1452262041.6727.15.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin@lichtvoll.de \
--cc=swami@petaramesh.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 NNTP newsgroup(s).