from small one page howto to huge articles all in one place
 

search text in:





Poll
Which kernel version do you use?





poll results

Last additions:
using iotop to find disk usage hogs

using iotop to find disk usage hogs

words:

887

views:

95475

userrating:

average rating: 1.7 (83 votes) (1=very good 6=terrible)


May 25th. 2007:
Words

486

Views

210952

why adblockers are bad


Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

words:

161

views:

92370

userrating:

average rating: 1.3 (28 votes) (1=very good 6=terrible)


April, 26th. 2006:

Druckversion
You are here: manpages





VDE_CRYPTCAB

Section: User Commands (1)
Updated: December 6, 2006
Index Return to Main Contents
 

NAME

vde_cryptcab - Virtual Distributed Ethernet encrypted cable manager  

SYNOPSIS

vde_cryptcab [ -p portnum ] [ -s socketpath ] [ -c [remote_user@]host[:remote_portnum] ] [ -P pre_shared.key ]| [ -x ] [ -v [v][v][v] ] [ -k ] [ -d ]
 

DESCRIPTION

A vde_cryptcab is a distributed cable manager for VDE switches. It allows two VDE switches on two machines to communicate using a blowfish encrypted channel.

When used in client mode (i.e., with -c option), it generates a random blowfish key, and uses scp (1) to transfer the key to the remote server.

On the client side, the environment variable SCP_EXTRA_OPTIONS may be set in order to append options to the scp command line (this is useful for example when dropbear or another non-standard ssh client is used to transfer the blowfish key).

After a 4-way handshake phase to verify client credentials, server and client will exchange VDE datagrams encapsulating them into cryptograms that are sent via udp to each remote host.

On server side, one could run:


vde_cryptcab -s /tmp/vde2.ctl -p 2100
To start a multi-peer cryptcab server, accepting udp datagrams on port 2100, that connects each authenticated remote client to a different port of the switch. In fact, a new instance of vde_plug (1) is started and connected to the switch through local unix socket.

The command


vde_cryptcab -s /tmp/vde2.ctl -c foo@remote.machine.org:2100
will connect a client to the remote server, running on udp port 2100. At this point, on server side a verify for user "foo" credentials is required, typically it could be: host-based authentication, password challenge or public key authentication. See ssh (1) for more details about it.

If the two vde_switches run as daemon and they are connected to tap interfaces a level 2 encrypted tunnel is established.

 

OPTIONS

-p portnum
It is possible to decide which local udp port to use. When this option is not specified, cryptcab will use default udp port number, 7667.
-c [remote_user@]host[:remote_portnum]
run vde_cryptcab in client mode, trying to connect to host . Both remote_user and remote_portnum parameters are not required. If not specified, the same user running vde_cryptcab is used for authentication on server, and default udp port 7667 is used.
-s socketpath
specify the UNIX socket to be used by local programs for joining the VDE. The default value is "/tmp/vde.ctl".
-P pre_shared.keypath
if specified, vde_cryptcab will run in pre-shared key mode, instead of generating a random key to transmit with ssh. Given option is the path to the pre-shared symmetric key file to use for data encryption. The same key has to be used on both client and server.
-x
Disable symmetric key encryption.
-k
Send periodic "keepalive" packets to avoid server timeouts. Useful when you want to keep a low-traffic link available.
-d
Run as daemon.
-v
Verbose. (Use -vv -vvv or -vvvv for more verbosity)
 

KNOWN ISSUES

Encapsulating IP packets into session+udp layer results in real datagrams larger than tap device mtu. Since vde_cryptcab gets confused by packet fragmentation, the tap device mtu must be set to a smaller value than real interface mtu. Use ip(8) or ifconfig(8) to set up your tap device mtu.

Explicitly disabling encryption leads to obvious security problems. It is advised to avoid unencrypted mode (-x) in non-controlled networks.

 

NOTICE

Virtual Distributed Ethernet is not related in any way with www.vde.com ("Verband der Elektrotechnik, Elektronik und Informationstechnik" i.e. the German "Association for Electrical, Electronic & Information Technologies").

 

SEE ALSO

vde_switch(1), vdeq(1), vde_plug(1), vde_plug2tap(1), scp(1), ssh(1).
 

AUTHORS

VDE is a project by Renzo Davoli <renzo@cs.unibo.it>.

vde_cryptcab is a VDE component by Daniele Lacamera <root@danielinux.net>


 

Index

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
KNOWN ISSUES
NOTICE
SEE ALSO
AUTHORS


Please read "Why adblockers are bad".



Other free services
toURL.org
Shorten long
URLs to short
links like
http://tourl.org/2
tourl.org
.
Reverse DNS lookup
Find out which hostname(s)
resolve to a
given IP or other hostnames for the server
www.reversednslookup.org
rdf newsfeed | rss newsfeed | Atom newsfeed
- Powered by LeopardCMS - Running on Gentoo -
Copyright 2004-2013 Sascha Nitsch Unternehmensberatung UG(haftungsbeschränkt)
Valid XHTML1.1 : Valid CSS : buttonmaker
- Level Triple-A Conformance to Web Content Accessibility Guidelines 1.0 -
- Copyright and legal notices -
Time to create this page: 3.3 ms