11-06-2018
Great, I believe this should do the trick very well, I will test it tomorrow morning. I have 2 questions;
1) Why some ':' at the beginning?
2) Doesn't the 'one_user' 'one_host' 'one_sshkey' variables needs to be defined before using them? like one_user = $(...)
Thanks
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello,
I'm wondering if anyone has a step-by-step instruction set for setting up ssh keys? I've gone through many of the manuals online (most seem to be from the same source) and it's a little bit unclear when the documentation is talking about the server versus the client machine. I'm missing... (1 Reply)
Discussion started by: sysera
1 Replies
2. UNIX for Dummies Questions & Answers
Hello*! I have problems with public keys. On one side i have Solaris 10, and on other side is HP UNIX. I created public keys on Solaris with "ssh-keygen -t rsa", append id_rsa.pub key to ~user/.ssh/authorized_keys on remote machine, and tried to connect with ssh without password. But for some... (1 Reply)
Discussion started by: ghost01
1 Replies
3. UNIX for Dummies Questions & Answers
Hi everyone,
i wanted to generate ssh keys so that i can include the public key in the remote sever, so that for subsequent logins, i can do away with the keying in of the password. I consulted the man ssh-keygen man pages. "..Normally each user wishing to use SSH with RSA or DSA... (1 Reply)
Discussion started by: new2ss
1 Replies
4. Shell Programming and Scripting
I have 2 systems A and B
I need to do a passwd less authentication inorder to send a file from system B to system A automatically(using sftp)
for this i did the following
I generated ssh-keygen -t dsa on system B, copied this key(id_dsa.pub) into the authorized_keys file on system A... (1 Reply)
Discussion started by: ramky79
1 Replies
5. Red Hat
Hi,
I've generated and posted pub. keys in the source system and the target. However, it is still prompting me for the password.
Steps that I have taken.
1. Generated ssh keys : ssh-keygen. It created two files.
1. .ssh/id_rsa
2. .ssh/id_rsa.pub.
2.... (10 Replies)
Discussion started by: Afi_Linux
10 Replies
6. Shell Programming and Scripting
Hi frnz,
I work in an environment, where I need to login to multiple UNIX sessions(Always types my password when prompted for)
I heard of ssh keys which provides us a valid authentication and that avoids us typing the password.
Now I want to generate the ssh keys and use in my... (2 Replies)
Discussion started by: dnam9917
2 Replies
7. OS X (Apple)
Not specifically a mac question, but it's what I am using.
I am setting up some replication for some file shares using rsync. The problem is that I am being given a little bit of a twist - I'm supposed to use a non-admin account to do it with.
I have 2 boxes - Master and Slave with 1... (2 Replies)
Discussion started by: kleinboy
2 Replies
8. Solaris
Hello,
I could use some help with my ssh keys and agent.
This is the issue. I have 2 different UNIX systems at work. One is the normal Solaris servers with my uid being the same throughout all the servers. I now have a different system for my desktop. A contractor came in and installed some SUN... (0 Replies)
Discussion started by: bitlord
0 Replies
9. UNIX for Beginners Questions & Answers
Hi - If iam logged on to server A, on 4 putty windows using SSH ... and out of these 4 logged-in sessions, in one of the sessions if i did SSH from server A to server B;
i would now have 4 putty windows sessions ... of which 3 are actively logged on to Server A while 1 putty window is actively... (2 Replies)
Discussion started by: i4ismail
2 Replies
LEARN ABOUT DEBIAN
date::manip::migration5to6
Date::Manip::Migration5to6(3pm) User Contributed Perl Documentation Date::Manip::Migration5to6(3pm)
NAME
Date::Manip::Migration5to6 - how to upgrade from 5.xx to 6.00
SYNOPSIS
When upgrading from Date::Manip 5.xx to 6.00, a few changes may be necessary to your scripts.
The Date::Manip::Changes5to6 document lists in more detail the ways in which Date::Manip changed, but very few of these actually entail
changes to your script.
It should be noted that once the changes are made to your script, it will no longer run correctly in 5.xx.
NECESSARY AND SUGGESTED CHANGES
The following changes are necessary, or strongly suggested:
Reading config files with Date_Init
If you use Date_Init to read any config files (if you do business mode calculations, you probably do), you should remove all of the
following config variables from your call to Date_Init:
GlobalCnf=FILE
PersonalCnf=FILE
PathSep=*
IgnoreGlobalCnf=*
PersonalCnfPath=*
and replace them with:
ConfigFile=FILE
where FILE is now the full path to a config file. Also, the ConfigFile argument should be the first argument in Date_Init.
Date_ConvTZ
The Date_ConvTZ function has changed. It should now take 3 arguments:
$date = Date_ConvTZ($date,$from,$to);
If $from is not given, it defaults to the local time zone. If $to is not given, it defaults to the local time zone.
The date is converted from the $from time zone into the $to time zone. Both should be any time zone (or alias) supported by
Date::Manip.
The old $errlevel argument is no longer handled.
ConvTZ and TZ config variables
If you use either the ConvTZ or TZ config variables, you should replace them with either SetDate or ForceDate. See the
Date::Manip::Config document for information.
The TZ variable will continue to work until Dec 2013 at which point it will be removed.
Other deprecated config variables
The following config variables have been deprecated, but will continue to function (though they will be removed at a future date):
IntCharSet (removed Oct 2012)
TZ (removed Dec 2013)
The following variables have been removed. If you use any of them, you may need to modify your scripts:
GlobalCnf
PersonalCnf
PathSep
IgnoreGlobalCnf
PersonalCnfPath
ConvTZ
Internal
TodayIsMidnight
DeltaSigns
UpdateCurrTZ
ResetWorkdDay
today, yesterday, tomorrow
If you parse the strings "today", "yesterday", or "tomorrow" in order to get the time now, or 24 hours in the past/future, this will no
longer work. These strings now refer strictly to the date (so "today" is the current day at midnight, "yesterday" is the previous day
at midnight, etc.).
To get the time now, 24 hours ago, or 24 hours in the future, you would need to parse the strings "now", "-24:00:00", or "+24:00:00"
respectively.
Do not use Memoize
In 5.xx, it was documented that you could use the module Memoize to speed up Date::Manip, especially when sorting dates.
This information is no longer accurate. Using Memoize in conjunction with Date::Manip should have little impact on performance, and may
lead to incorrect results, especially if you change config variables.
Please see the Date::Manip::Changes5to6 (GENERAL CHANGES) document for more information.
If you find other instances where it is necessary to modify your script, please email me so that I can add that information to this
document.
BUGS AND QUESTIONS
Please refer to the Date::Manip::Problems documentation for information on submitting bug reports or questions to the author.
SEE ALSO
Date::Manip - main module documentation
LICENSE
This script is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
AUTHOR
Sullivan Beck (sbeck@cpan.org)
perl v5.14.2 2012-06-02 Date::Manip::Migration5to6(3pm)