Choosing best location for authorized_keys!

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat Choosing best location for authorized_keys!
# 1  
Old 05-24-2012
Choosing best location for authorized_keys!

Hello Friends,

I am trying to troubleshoot one scenario for the customer. In their server configuration, each vhost has it's own user. The option is to shell access chrooted.
The question is where would be the best place to store the authorized_keys file so that we can ssh in from the deployment server (SVN) without requiring user interaction?

The solution is needed for the deployment strategies from internally hosted SVN server to some of the websites.

I will appreciate the help in this matter.

Respectfully,
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Appending authorized_keys on multiple servers using ssh

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

How to find a existing file location and directory location in Solaris box?

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

File created in a different location instead of desired location on using crontab

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

Centrilized authorized_keys (AuthorizedKeysFile) for sshd

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

Shell Script for Copy files from one location to another location

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

authorized_keys and passwordless login

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

sftp using authorized_keys in unix

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

Will Password change affect authorized_keys?

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

monitoring SSH authorized_keys

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

monitoring SSH authorized_keys

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 or Register to Ask a Question
RUSH(8) 							      Gnurush								   RUSH(8)

NAME
rush - a restricted user shell SYNOPSIS
rush [-F STRING] [-f DIR] [-n NUM] [--forward] [-H] rush {-v | -h | --usage} DESCRIPTION
GNU rush is a restricted user shell (R-U-SH), designed for sites that provide only limited remote access to their resources. This could be Subversion or Git repositories, upload sites accessible only by Scp, or similar services. Using a sophisticated configuration file, GNU rush gives the administrator complete control over the command lines that users are able to execute, as well as over the access to and usage of system resources. Usually virtual memory, CPU time, etcetera, are determined by this system wide configuration. OPTIONS
-c COMMAND Specify a command to run. -C TEST | --security-check=TEST Configure security checks for the main configuration file. -d NUM | --debug=NUM Set debugging level. --show-default Disply the built-in default configuration. -t | --test | --lint [FILE] Run in test mode. The optional argument FILE determines the location of an alternate configuration file to be used. In case also the option '-c' is specified, then rush will emulate normal processing for the given command, but will not actually execute it. -u NAME | --user=NAME Emulate shell access by the user NAME. The option '--test' is implied. The use of this option is allowed only for root and in conjunction with the further option '-c'. -v | --version Display program version. -h | --help Display a short help message. --usage Display a concise usage summary. SEE ALSO
The full documentation for GNU Rush is maintained as a Texinfo manual. If the info and rush programs are properly installed at your site, the command info rush should give you access to the complete manual. See also rushlast(1) and rushwho(1). AUTHOR
This text was written by Mats Erik Andersson for the Debian project, since the original source supplies a documentation only in the form of a GNU Texinfo manual. GNU Rush 1.7 December 2010 RUSH(8)