passwordless but secure auth, unencrypted traffic

Currently I have configured ssh passless remote access for file copying. It works but has this flow, that de/crypting traffic costs cpu power and network bandwidth.

So are there any other options to have secure remote auth(key based), but clear-text transfer?

I'm on CentoOS 5 and FC.
I know there's ssh "cipher none" patch - but i'm not after patching ssh which comes with the OS.
Any other ideas?
LVL 43
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

NFSv3 + iptables = no keys
NFSv4 ?
ravenplAuthor Commented:
iptables is not the replacement for ssh keys, if it was, then rsh would be the really fine solution here.
keys = encryption
open rsh or nfs only for one ip and no other
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

ravenplAuthor Commented:
> keys = encryption
No. keys mean authentication, not necessarily encryption.

> open rsh or nfs only for one ip and no other
what about other users on same machines?
NFS configures for users
man exports
ravenplAuthor Commented:
From the question
"So are there any other options to have secure remote auth(key based), but clear-text transfer?"
cjl7freelance for hireCommented:
Kerberos + ftp
Kerberos FTP would have been my suggestion as well.
ravenplAuthor Commented:
May I ask how it works? I never set up any krb server.
What is the authentication token while authenticating? With ssh it's the pub/priv keypair.

Still I would prefer something like ssh/rsh, since the copied data is duplicated into two localtions.
Currently I have something like
tar -options | ssh -options remote_command # where remote_command is more less "tea /1/file1 | cat > /2/file2"
Kerberos works on the basis of tickets.  Tickets usually have an expiration time on them, so they are valid for whatever period you set them for.

Additionally, kerberos can also handle the encryption for you if you want (I know in your case, you don't want it)

rsh is the predecessor to ssh, and provides the same functionality; running commands on a remote server, but in an "insecure" manner.  (rsh = remote shell, ssh = secure shell.)  For the current method you're using, rsh would be appropriate.

If you prefer to use ftp, there's many clients that allow you to insert a password automatically.  I'm biased towards the ncftp tools ncftpget and ncftpput, which allow batch mode operation, however even the command-line ftp client supports auto-login (`man 5 netrc`).

It's unclear whether you are specifically looking for a public/private key authentication mechanism, or simply want automated file transfer that's unencrypted, but uses some sort of authentication (be it password or public/private keys).

Kerberos is a heavy-handed solution to the problem, and isnt really offering a strong solution.  Kerberos is meant to provide a single sign-on solution, where you use your password for the initial authentication, and then use the "ticket" provided as a token.  You might use a secure method to obtain the ticket (a unique token, proving you've authenticated), and then insecure methods to transfer the ticket.

Within the vein of Kerberos, a more appropriate solution might be something like S/Key authentication; you pre-generate a number of pass-phrases, that are one-time-use.  But again, it doesn't sound like that's what you want.

It sounds like what you want is the ability to transfer data between two servers, in the clear, in a readily automated fashion, but where someone must have a credential of some type (which is probably stored in a script) to do so; e.g. another non-root user on the source server cannot just copy the files over.

NFS, FTP or RSH would be good solutions, assuming the above is true.  NFS provides an IP-based ACL, and the permissions are limited based on source UID; unless someone has root on the source system, they can't get to the data.  RSH allows you a similar method to what you're using now, but a pass-phrase instead of a DSA/RSA key, and non-encrypted.  FTP is built for file transfer, but wont operate in a streaming mode, as you're doing; it can be automated.

Lastly, you could also use other non-preferred methods, such as an HTTP-based script, TFTP (password-less, Trivial FTP), netcat, etc.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
How much data are you trying to transfer and what so of link do you have?
ravenplAuthor Commented:
> How much data are you trying to transfer and what so of link do you have?
0.5 TB via 1gbit eth.

Thanx guys for Your opinions.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.