I am testing the following command to transfer a file from my server (AIX 5.2) to another server. I was able to generate the keys and sent them the public key.
Based on the output from the command it looks like it is authenticating correctly, but the file is not getting sent or they tell me they are not getting it. Can you take a look at the above command and let me know if it is not correct. I am currently doing this from the command line, but will script it when I get it working. Below is output from the comman execution.
Any thoughts. I want to determine if the problem is on my side or theirs. Thank you.
Hi,
How do i know if the files are transferred succesfully when i use SCP to transfer files between 2 servers.
One more is i am trying to send all the files in a single shot by using * to save the connection time. So can i know when the scp breakes in the middle
scp $sourcepath/*... (9 Replies)
Hi Frdz
I have a problem like.
I need to transfer a file from source to destination (different systems with different IPs) using "scp" command and before transfer the file i have to check the file is available in destination or not, if it is there no need to transfer, otherwise we have to... (5 Replies)
I have a shell script which uses SCP command to transfer the files from one server to another server. The files are getting transferred successfully, but the problem is the files transferred to the destination server didnot have the permissions as that of the files on the source server.
Command... (5 Replies)
Hi ,
I want to transfer one file having 6GB(after compression) which is in .cpk format from one server to other server.
I tried scp command as well as FTP and also split the file then transfer the files thru scp command. At last i am facing the data lost and connection lost issue.
Generally it... (2 Replies)
I am not able to throw a file from server173 to server067
i.e.
wlsuser@server173> scp /tmp/harsha.txt wlsuser@server067:/tmp
fails
However, I am able to pull a file from server173 onto server067's /tmp dir
wlsuser@server067> scp wlsuser@server173:/tmp/harsha.txt /tmp... (2 Replies)
Whenever I transfer file through SCP between two server it gives below given message.....Is there a way to avoid it....
Target server : newyork
$ scp ABC27801.iue newyork:./iABC/x0017801.iue
Message
=====
This system is for the use of authorized users only. Individuals using this... (1 Reply)
I have 3 AIX server namely - Server 1 , Server 2 and Server 3.
And have done SCP setup between Server 1 and Server 2 so that i dont have to give password when i transfer file from Server 1 to Server 2 by setting public key between the server.
Q1. If the unix password of the target server... (3 Replies)
On unix AIX server, when I am trying to transfer file from one directory to another directory on the same server through a program(where i call the script) it gives error "Lost Connection". (5 Replies)
I am trying to transfer a zip file of around 30 MB in my automation script using scp from system A to B.
When I manually do scp, file is complete transferred but when automation shell script runs it, zip file is not completely transferred.
Stack Trace while doing manual :
Executing:... (1 Reply)
Discussion started by: Shaishav Shah
1 Replies
LEARN ABOUT DEBIAN
vde_cryptcab
VDE_CRYPTCAB(1) General Commands Manual VDE_CRYPTCAB(1)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 use-
ful 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 crypto-
grams 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 net-
works.
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>
Virtual Distributed Ethernet December 6, 2006 VDE_CRYPTCAB(1)