On Fri, May 21, 2010 at 11:28 AM, David Dyer-Bennet <d...@dd-b.net> wrote:
> I thought I remembered a "none" cipher, but couldn't find it the other
> year and decided I must have been wrong. I did use ssh-1, so maybe I
> really WAS remembering after all.
It may have been in ssh2 as well, or at least the commercial version
.. I thought it used to be a compile time option for openssh too.
> Seems a high price to pay to try to protect idiots from being idiots.
> Anybody who doesn't understand that "encryption = none" means it's not
> encrypted and hence not safe isn't safe as an admin anyway.
Well, it won't expose your passwords since the key exchange it still
encrypted ... That's good, right?
Circling back to the original topic, you can use ssh to start up
mbuffer on the remote side, then start the send. Something like:
#!/bin/bash
ssh -f r...@${recv_host} "mbuffer -q -I ${SEND_HOST}:1234 | zfs recv
puddle/tank"
sleep 1
zfs send -R tank/foo/bar | mbuffer -O ${RECV_HOST}:1234
When I was moving datasets between servers, I was on the console of
both, so manually starting the send/recv was not a problem.
I've tried doing it with netcat rather than mbuffer but it was
painfully slow, probably due to network buffers. ncat (from the nmap
devs) may be a suitable alternative, and can support ssl and
certificate based auth.
-B
--
Brandon High : bh...@freaks.com
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
