Sponsored Content
Top Forums UNIX for Advanced & Expert Users secure file transfer with public key Post 302273734 by Padow on Monday 5th of January 2009 04:14:40 PM
Old 01-05-2009
Download, compile, and install SSH. Use SFTP from the SSH package. This will encrypt the password as well as data during transmission. While GPG/PGP will encrypt the data, FTP is still not secure. Passwords are still send plain text via FTP.
Padow
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

SSH - Public key

When should one have to generate a public key on a Server when the public key is already created and used by other clients? Thanks, Rahul. (6 Replies)
Discussion started by: rahulrathod
6 Replies

2. AIX

How to use SSH Secure File Transfer tool from windows to AIX without password?

If I use SSh Secure File Transfer tool on Windows, I want to transfer file from windows to AIX without password, how to do it? (6 Replies)
Discussion started by: rainbow_bean
6 Replies

3. Cybersecurity

Secure File Transfer for Mainframe systems

Hi guys, I would like to transfer files from UNIX machine to Mainframe system (using UNIX machine as client). The transfer process needs to be secure (i.e. data sent thro network should be encrypted using 128-bit encryption algorithm). I came to know that SFTP server is not available for Mainframe... (3 Replies)
Discussion started by: sydneymoon
3 Replies

4. Shell Programming and Scripting

Question about secure file transfer

Hi all, I am running a large scale business and some time I have to transfer large and very important data files to my business partner. I fear about my data because there are many of my business competitors who will definitely try to steal my important data. So there is huge amount of risk... (0 Replies)
Discussion started by: camden
0 Replies

5. Shell Programming and Scripting

Secure File Transfer Protocol

Hi, Is there any protocol other than SFTP to transfer the file using secured connection SSH. ? Regards, Arthik (2 Replies)
Discussion started by: arthikbabu
2 Replies

6. Shell Programming and Scripting

secure upload using public key

Hi, i was provided with 1. Server IP (Remote) 2. Username and Password (worked when tested basic FTP) 3. Their Public key (GnuPG v1.0.6) They refuse when i upload using basic FTP and insists for encryption. I have Solaris 10 and Linux in my environment. How can i encrypt and upload... (0 Replies)
Discussion started by: prvnrk
0 Replies

7. UNIX for Dummies Questions & Answers

VSFTPD Public Key Help

Hi all Ive setup a VSFTPD server and im forcing SSL encryption. I have made a key and it works perfectly. I have a client who wants to connect but is using software that needs the key to be added before he can connect. Does he need me to send the key i created and that the VSFTPD.conf... (0 Replies)
Discussion started by: mokachoka
0 Replies

8. UNIX and Linux Applications

Central Location for all ssh Keys and Settings Unattended Secure File Transfer

I am developing an application that submits command line file transfers using ssh (Sun to Sun) and Tectia ssh (Sun to Windows Server) embedded in the code. Potentially many different trusted people will start the programs. Is there a way to have all the settings and keys localized so that there is... (0 Replies)
Discussion started by: PowersThatB
0 Replies

9. Solaris

Solaris 8 ssh public key authentication issue - Server refused our key

Hi, I've used the following way to set ssh public key authentication and it is working fine on Solaris 10, RedHat Linux and SuSE Linux servers without any problem. But I got error 'Server refused our key' on Solaris 8 system. Solaris 8 uses SSH2 too. Why? Please help. Thanks. ... (1 Reply)
Discussion started by: aixlover
1 Replies

10. UNIX for Advanced & Expert Users

Secure Copy - File Transfer between 2 server

Using RCP command we can transfer file from one server to another server. While transferring we can rename the file also e.g. File name = FILE123.txt (lying on Source server = oldserver) Target Server Name = newyour Renamed File = FILE456.txt rcp FILE123.txt newyour:./FILE456.txt... (1 Reply)
Discussion started by: Pash
1 Replies
DUPLOAD(1)							  Debian Project							DUPLOAD(1)

NAME
dupload - utility to upload Debian packages SYNOPSIS
dupload [options] [changes_file | dir] ... DESCRIPTION
dupload is a tool that enables Debian developers to easily upload their packages to the Debian archive. At least for chiark the upload procedure is somewhat error prone (upload to Incoming/, move it to queue/). dupload checks each non-option argument to find readable files or directories. It parses the files as .changes files, or tries to find such files in the given directories. dupload will warn if the name of the file doesn't end with ".changes". Further processing is done chdir'ed into the directories of the changes files. dupload tests the available checksums and size for each file listed in the .changes file, and fails if it finds a mismatch. If all this goes well, dupload checks if there is an .upload file with the basename of the .changes file. If the file to be uploaded is recorded to have already been uploaded to the specified host, it is skipped. dupload will stop and verify if it sees you try to upload a package with a non-US Section field to a host that is neither non-us.debian.org, security.debian.org nor has the "nonus" option set to 1. After the list of files to upload is finished, dupload tries to connect to the server and upload. Each successfully uploaded file is recorded in the .upload log file. If all files of a package are processed, the .changes file is mailed to the announcement address specified in the configuration file. If files with package.announce, package_UPSTREAMVER.announce, or package_UPSTREAMVER-DEBIANREV.announce exist, these files get prepended to the announcement. UPSTREAMVER and DEBIANREV are to be replaced with actual version numbers. For example, if your package is called foobar, has upstream version 3.14, and Debian revision 2: If you only want the announcement to be made with only ONE upload, you name it foobar_3.14-2.announce. If you want it to be made with every upload of a particular upstream version, name it foobar_3.14.announce. If you want it made with every upload of a given package, name it foobar.announce. Please note: Some mail readers (like elm w/ PGP extensions) don't show mail contents outside of the signed part of a message. Login and password If no login (username) is defined in the configuration file, "anonymous" is used. The password is derived from your login name and your hostname, which is common for anonymous FTP logins. For anonymous logins only, you can provide the "password" in the configuration file. For logins other than "anonymous", you're asked for the password. For security reasons there's no way to supply it via the commandline or the environment. FTP / scp / rsync The default transfer method is FTP. Alternative methods are scp/SSH and rsync/SSH. For scp and rsync, the default login is taken from your local user name. The scp/SSH method only works properly if no password is required (see ssh(1)). When you use scp, it is recommended to set the "method" keyword to "scpb", which will transfer all files in a batch. If you are using an upload queue, use FTP because it's fast. If you are using an authenticated host, always use scp or rsync via SSH, because FTP transmits the password in clear text. OPTIONS
-d --debug [level] Enable more verbose output from the FTP module. -f --force Upload regardless of the transfers logged as already completed. -k --keep Keep going, skipping packages whose checksums don't match. -c --configfile Read the file ./dupload.conf (if it exists). Warning: this is a security risk if you are in a directory where other people can write. That's why it is not the default (unlike the previous versions). --no Dry run, no files are changed, no upload is attempted, only tell what we would do. --nomail Supress announcement for this run. You can send it later by just calling dupload again w/o this option. Note that this option is by default implied for all hosts with the "dinstall_runs" option set to 1. --mailonly Acts as if --no has been specified and but sends the announcements, unconditionally. --noarchive Adds a "X-No-Archive: yes" header so that the announcement will not be archived. You can use the per-host "archive" option in the configuration file. -p --print Print the "database" as read from the config files and exit. If a host is specified via option --to, only this host's entry is displayed. -q --quiet Be quiet, i.e. supress normal output. -t --to nickname optional Upload to nickname'd host. nickname is the key for doing lookups in the config file. You can use the "default_host" configuration option to specify a host without --to. -V --Version Prints version and exits. FILES
Configuration The configuration files are searched as follows (and read in this order, overriding each other): /etc/dupload.conf ~/.dupload.conf Other Various Debian package files are used by dupload: .dsc, .changes, .deb, .orig.tar.gz, .diff.gz dupload itself writes the log file package_version-debian.upload, and the additional announcement files package.announce, package_upstreamver.announce, and package_upstreamver-debianrev.announce. Announcement addresses By default, the announcement addresses are unset because dinstall sends mails instead. BUGS
dupload is tested on Debian systems only. It shouldn't require too much effort to make it run under others systems, though, it's written in Perl. AUTHOR
/COPYRIGHT Copyright 1996 Heiko Schlittermann, 1999 Stephane Bortzmeyer dupload is free software; see the GNU General Public Licence version 2 or later for copying conditions. There is no warranty. SEE ALSO
dupload.conf(5) dupload 2.7.0 February 2011 DUPLOAD(1)
All times are GMT -4. The time now is 09:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy