Choosing best location for authorized

Choosing best location for authorized_keys!

Operating Systems Linux Red Hat Choosing best location for authorized_keys!

05-24-2012

Registered User

4, 0

Join Date: May 2012

Last Activity: 6 February 2019, 3:37 PM EST

Posts: 4

Thanks Given: 0

Thanked 0 Times in 0 Posts

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,

user3528

View Public Profile for user3528

Find all posts by user3528

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...

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

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...

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...

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.

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...

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.

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,

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...

10. Shell Programming and Scripting

monitoring SSH authorized_keys

LEARN ABOUT DEBIAN

monkeysphere-authentication

MONKEYSPHERE-AUTHENTICATION(8)					  System Commands				    MONKEYSPHERE-AUTHENTICATION(8)

NAME

       monkeysphere-authentication - Monkeysphere authentication admin tool.

SYNOPSIS

       monkeysphere-authentication subcommand [args]

DESCRIPTION

       Monkeysphere  is  a framework to leverage the OpenPGP Web of Trust (WoT) for key-based authentication.  OpenPGP keys are tracked via GnuPG,
       and added to the authorized_keys files used by OpenSSH for connection authentication.

       monkeysphere-authentication is a Monkeysphere server admin utility for configuring and managing SSH user authentication through the WoT.

SUBCOMMANDS

       monkeysphere-authentication takes various subcommands:

       update-users [USER]...
	      Rebuild the monkeysphere-controlled authorized_keys files.  For each specified account, the user ID's listed in the account's autho-
	      rized_user_ids file are processed.  For each user ID, gpg will be queried for keys associated with that user ID, optionally querying
	      a keyserver.  If an acceptable key is found (see KEY ACCEPTABILITY in monkeysphere(7)), the key is added to  the	account's  monkey-
	      sphere-controlled  authorized_keys  file.  If the RAW_AUTHORIZED_KEYS variable is set, then a separate authorized_keys file (usually
	      ~USER/.ssh/authorized_keys) is appended to the monkeysphere-controlled authorized_keys file.  If no accounts are specified, then all
	      accounts on the system are processed.  `u' may be used in place of `update-users'.

       keys-for-user USER
	      Output  to stdout authorized_keys lines for USER.  This command behaves exactly like update-users (above), except that the resulting
	      authorized_keys lines are output to stdout, instead of being written to the monkeysphere-controlled authorized_keys file.

       refresh-keys
	      Refresh all keys in the monkeysphere-authentication keyring.  If no accounts are specified, then all accounts on the system are pro-
	      cessed.  `r' may be used in place of `refresh-keys'.

       add-id-certifier KEYID|FILE
	      Instruct	system	to trust user identity certifications made by KEYID.  The key ID will be loaded from the keyserver.  A file may be
	      loaded instead of pulling the key from the keyserver by specifying the path to the file as the argument, or  by  specifying  `-'	to
	      load from stdin.	Using the `-n' or `--domain' option allows you to indicate that you only trust the given KEYID to make identifica-
	      tions within a specific domain (e.g. "trust KEYID to certify user identities within the @example.org domain").   A  certifier  trust
	      level  can be specified with the `-t' or `--trust' option (possible values are `marginal' and `full' (default is `full')).  A certi-
	      fier trust depth can be specified with the `-d' or `--depth' option (default is 1).  `c+' may be used  in  place	of  `add-id-certi-
	      fier'.

       remove-id-certifier KEYID
	      Instruct system to ignore user identity certifications made by KEYID.  `c-' may be used in place of `remove-id-certifier'.

       list-id-certifiers
	      List key IDs trusted by the system to certify user identities.  `c' may be used in place of `list-id-certifiers'.

       version
	      Show the monkeysphere version number.  `v' may be used in place of `version'.

       help   Output a brief usage summary.  `h' or `?' may be used in place of `help'.

	      Other commands:

       setup  Setup the server in preparation for Monkeysphere user authentication.  This command is idempotent and run automatically by the other
	      commands, and should therefore not usually need to be run manually.  `s' may be used in place of `setup'.

       diagnostics
	      Review the state of the server with respect to authentication.  `d' may be used in place of `diagnostics'.

       gpg-cmd
	      Execute a gpg command, as the monkeysphere user, on the monkeysphere authentication `sphere' keyring.  This takes a single  argument
	      (i.e. multiple gpg arguments need to be quoted all together).  Use this command with caution, as modifying the authentication sphere
	      keyring can affect ssh user authentication.

SETUP USER AUTHENTICATION

       If the server will handle user authentication through monkeysphere-generated authorized_keys files, the server must be told which keys will
       act as identity certifiers.  This is done with the add-id-certifier command:

       # monkeysphere-authentication add-id-certifier KEYID

       where KEYID is the key ID of the server admin, or whoever's certifications should be acceptable to the system for the purposes of authenti-
       cating remote users.  You can run this command multiple times to indicate that multiple certifiers are trusted.	You  may  also	specify  a
       filename  instead of a key ID, as long as the file contains a single OpenPGP public key.  Certifiers can be removed with the remove-id-cer-
       tifier command, and listed with the list-id-certifiers command.

       A remote user will be granted access to a local account based on the appropriately-signed and valid keys associated with user IDs listed in
       that  account's	authorized_user_ids file.  By default, the authorized_user_ids file for an account is ~/.monkeysphere/authorized_user_ids.
       This can be changed in the monkeysphere-authentication.conf file.

       The update-users command is used to generate authorized_keys files for a local account based on the user IDs listed in the account's autho-
       rized_user_ids file:

       # monkeysphere-authentication update-users USER

       Not  specifying USER will cause all accounts on the system to updated.  The ssh server can use these monkeysphere-generated authorized_keys
       files to grant access to user accounts for remote users.  In order for sshd to look at the monkeysphere-generated authorized_keys file  for
       user authentication, the AuthorizedKeysFile parameter must be set in the sshd_config to point to the monkeysphere-generated authorized_keys
       files:

       AuthorizedKeysFile /var/lib/monkeysphere/authorized_keys/%u

       It is recommended to add "monkeysphere-authentication update-users" to a system crontab, so that user keys are  kept  up-to-date,  and  key
       revocations and expirations can be processed in a timely manner.

ENVIRONMENT

       The following environment variables will override those specified in the config file (defaults in parentheses):

       MONKEYSPHERE_MONKEYSPHERE_USER
	      User to control authentication keychain. (monkeysphere)

       MONKEYSPHERE_LOG_LEVEL
	      Set the log level.  Can be SILENT, ERROR, INFO, VERBOSE, DEBUG, in increasing order of verbosity. (INFO)

       MONKEYSPHERE_KEYSERVER
	      OpenPGP keyserver to use. (pool.sks-keyservers.net)

       MONKEYSPHERE_CHECK_KEYSERVER
	      Whether or not to check the keyserver when making gpg queries. (true)

       MONKEYSPHERE_AUTHORIZED_USER_IDS
	      Path  to	user's authorized_user_ids file. %h gets replaced with the user's homedir, %u with the username.  (%h/.monkeysphere/autho-
	      rized_user_ids)

       MONKEYSPHERE_RAW_AUTHORIZED_KEYS
	      Path to regular ssh-style authorized_keys file to append to monkeysphere-generated authorized_keys.  `none' means not to add any raw
	      authorized_keys file.  %h gets replaced with the user's homedir, %u with the username. (%h/.ssh/authorized_keys)

       MONKEYSPHERE_PROMPT
	      If set to `false', never prompt the user for confirmation. (true)

       MONKEYSPHERE_STRICT_MODES
	      If  set to `false', ignore too-loose permissions on known_hosts, authorized_keys, and authorized_user_ids files.	NOTE: setting this
	      to false may expose users to abuse by other users on the system. (true)

FILES

       /etc/monkeysphere/monkeysphere-authentication.conf
	      System monkeysphere-authentication config file.

       /etc/monkeysphere/monkeysphere-authentication-x509-anchors.crt										or
       /etc/monkeysphere/monkeysphere-x509-anchors.crt
	      If  monkeysphere-authentication  is  configured  to query an hkps keyserver, it will use X.509 Certificate Authority certificates in
	      this file to validate any X.509 certificates used by the keyserver.  If the monkeysphere-authentication-x509 file  is  present,  the
	      monkeysphere-x509 file will be ignored.

       /var/lib/monkeysphere/authorized_keys/USER
	      Monkeysphere-controlled user authorized_keys files.

       ~/.monkeysphere/authorized_user_ids
	      A  list  of OpenPGP user IDs, one per line.  OpenPGP keys with an exactly-matching User ID (calculated valid by the designated iden-
	      tity certifiers), will have any valid authorization-capable keys or subkeys added to the given  user's  authorized_keys  file.   Any
	      line with initial whitespace will be interpreted as ssh authorized_keys options applicable to the preceding User ID.

AUTHOR

       This  man  page	was  written  by: Jameson Rollins <jrollins@finestructure.net>, Daniel Kahn Gillmor <dkg@fifthhorseman.net>, Matthew Goins
       <mjgoins@openflows.com>

SEE ALSO

       monkeysphere(1), monkeysphere-host(8), monkeysphere(7), gpg(1), ssh(1), sshd(8), sshd_config(5)

monkeysphere							   July 3, 2010 				    MONKEYSPHERE-AUTHENTICATION(8)

Red Hat