10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi
I have an ssh 'for' loop script to login and put a key on multiple servers. I need to append a file on each server but the command which works ok from the prompt does not work via the script. I have
cat filename | ssh user@servername "cat >>append.file.name"
I have tried to 'spawn' this in... (0 Replies)
Discussion started by: Grueben
0 Replies
2. Shell Programming and Scripting
Hi
This is my third past and very impressed with previous post replies
Hoping the same for below query
How to find a existing file location and directory location in solaris box (1 Reply)
Discussion started by: buzzme
1 Replies
3. Shell Programming and Scripting
Hi,
I am logging to a linux server through a user "user1" in /home directory.
There is a script in a directory in 'root' for which all permissions are available including the directory. This script when executed creates a file in the directory.
When the script is added to crontab, on... (1 Reply)
Discussion started by: archana.n
1 Replies
4. UNIX for Advanced & Expert Users
Hi
Little background on what I want to achieve and why I do this. I have a RHEL server with users logging in via ssh. I want to start using public keys instead of passwords with ssh. But public key is as good as a rotten tomato if it is unpassphrased and I cannot guarantee that all users will... (4 Replies)
Discussion started by: bortek
4 Replies
5. Shell Programming and Scripting
Create a script that copies files from one specified directory to another specified directory, in the order they were created in the original directory between specified times. Copy the files at a specified interval. (2 Replies)
Discussion started by: allways4u21
2 Replies
6. Red Hat
I am trying to set up ssh/scp to be able to login in w/o using a password. The man pages for ssh and ssh-keygen explain how to do this.
So, using "rsa1" style, I created the public and private keys by way of ssh-keygen, then added the contents of "$HOME/.ssh/identity.pub" to a newly created... (6 Replies)
Discussion started by: mcrouch_2003
6 Replies
7. Shell Programming and Scripting
I am creating public and private key for sftp in ksh.
then copy the name1.pub file into /.ssh/authorized_keys directory in remote server.
Now my question is how to write that script which do not ask me for the password from prompt.
please help.
thanks in advance. (1 Reply)
Discussion started by: rinku
1 Replies
8. Solaris
Hello gurus,
I have question. I have enabled ssh on the servers.
I am planning to change the oracle user's(os user) password. If I change the password will it affect the authorized_keys? Do I need to regenerate it.
Thanks, (2 Replies)
Discussion started by: oracleuser
2 Replies
9. UNIX for Advanced & Expert Users
Hi,
We have around 200 SUN Servers in production environment and I have one box from where I manage all the servers. It's setup such that I can SSH from my box onto all the 200 servers with without supplying password. It is working fine but sometimes we notice the keys getting changed and asking... (1 Reply)
Discussion started by: prvnrk
1 Replies
10. Shell Programming and Scripting
Hi,
We have around 200 SUN Servers in production environment and I have one box from where I manage all the servers. It's setup such that I can SSH from my box onto all the 200 servers with without supplying password. It is working fine but sometimes we notice the keys getting changed and asking... (0 Replies)
Discussion started by: prvnrk
0 Replies
LOGIN_DUO(8) BSD System Manager's Manual LOGIN_DUO(8)
NAME
login_duo -- second-factor authentication via Duo login service
SYNOPSIS
login_duo [-d] [-c file] [-h host] [-f user] [command [args...]]
DESCRIPTION
login_duo provides secondary authentication via the Duo authentication service, executing the user's login shell or command only if success-
ful.
The following options are available:
-c Specify an alternate configuration file to load. Default is /etc/duo/login_duo.conf
-d Debug mode; send logs to stderr instead of syslog.
-h Specify the remote IP address for this login (normally taken from the SSH_CONNECTION environment variable, if set).
-f Specify an alternate Duo user to authenticate as.
If login_duo is installed setuid root (the default), these options are only available to the super-user.
After successful Duo authentication, the user's login shell is invoked, or if an alternate command or SSH_ORIGINAL_COMMAND environment vari-
able is specified, it will be executed via the user's shell with a -c option.
CONFIGURATION
The INI-format configuration file must have a ``duo'' section with the following options:
host Duo API host (required).
ikey Duo integration key (required).
skey Duo secret key (required).
groups If specified, Duo authentication is required only for users whose primary group or supplementary group list matches one of the
space-separated pattern-lists (see PATTERNS below).
failmode On service or configuration errors that prevent Duo authentication, fail ``safe'' (allow access) or ``secure'' (deny access).
Default is ``safe''.
pushinfo Send command to be approved via Duo Push authentication. Default is ``no''.
An example configuration file:
[duo]
host = api-deadbeef.duosecurity.com
ikey = SI9F...53RI
skey = 4MjR...Q2NmRiM2Q1Y
pushinfo = yes
If installed setuid root (the default), login_duo performs Duo authentication as a dedicated privilege separation user, requiring that the
configuration file be owned and readable only by this user.
PATTERNS
A pattern consists of zero or more non-whitespace characters, '*' (a wildcard that matches zero or more characters), or '?' (a wildcard that
matches exactly one character).
A pattern-list is a comma-separated list of patterns. Patterns within pattern-lists may be negated by preceding them with an exclamation mark
('!'). For example, to specify Duo authentication for all users (except those that are also admins), and for guests:
groups = users,!wheel,!*admin guests
EXAMPLES
login_duo can be enabled system-wide by specifying its full path as a ForceCommand in sshd_config(5) to capture any SSH remote login (includ-
ing subsystems, remote commands, and interactive login):
ForceCommand /usr/local/sbin/login_duo
Similarly, a group of administrators could require two-factor authentication for login to a shared root account by specifying login_duo as
the forced command for each public key in ~root/.ssh/authorized_keys:
command="/usr/local/sbin/login_duo -f alice"
ssh-rsa AAAAB2...19Q== alice@example.net
command="/usr/local/sbin/login_duo -f bob"
ssh-dss AAAAC3...51R== bob@example.net
A user without root access could configure their own account to require Duo authentication via the same ~/.ssh/authorized_keys forced command
mechanism and a user-installed (non-setuid) login_duo.
FILES
/etc/duo/login_duo.conf
Default configuration file path
AUTHORS
login_duo was written by Duo Security <duo_unix@duosecurity.com>
NOTES
When used to protect remote SSH access, only interactive sessions support interactive Duo login. For scp(1), sftp(1), rsync(1), and other
ssh(1) remote commands, login_duo automatically tries the user's default out-of-band factor (smartphone push or voice callback) and disables
real-time login progress reporting to provide a clean shell environment.
BSD
September 3, 2010 BSD
