vyatta-cfg-system.git/lib, branch debian/0.19.74 Vyatta system-level configuration templates/scripts (mirror of https://github.com/vyos/vyatta-cfg-system.git) https://git.amelek.net/vyos/vyatta-cfg-system.git/atom?h=debian%2F0.19.74 2010-05-24T17:44:05+00:00 Don't enable PAM Radius by default 2010-05-24T17:44:05+00:00 Stephen Hemminger stephen.hemminger@vyatta.com 2010-05-24T17:10:35+00:00 urn:sha1:f37b24ae59372da6361b4acf9755270061bdc857 The pam-config mechanism will insert Radius pam module if it is in /usr/share/pam-configs. Therefore hold off installing file until Radius really needed. Ignore comments in level file 2010-04-26T21:49:14+00:00 Stephen Hemminger stephen.hemminger@vyatta.com 2010-04-26T21:49:14+00:00 urn:sha1:5e55ab28a732d0082c803f1e473936a3d9c92f22 Standard practice to ignore lines starting with # fixes commit warning when run invoked via the api--getlogin() may return an undefined value as the process is a child process 2010-03-17T21:13:25+00:00 Michael Larson slioch@slioch.vyatta.com 2010-03-17T21:13:25+00:00 urn:sha1:74ae8c9cdbbd318c928e57288b60396affb9cf9a invoked indirectly via the gui (not a normal shell logged in user generated event). Better version of forcing user logout 2010-03-15T17:43:58+00:00 Stephen Hemminger stephen.hemminger@vyatta.com 2010-03-15T17:43:58+00:00 urn:sha1:fa0e2d31d5964c7d7bb0f8d34b568d065cf38890 Use warning and hup signal to force user to log out. Use userdel -f to force removal of user 2010-03-15T16:17:46+00:00 Stephen Hemminger stephen.hemminger@vyatta.com 2010-03-15T16:17:46+00:00 urn:sha1:87c0562ee477ebc37248c00cdcfe93ecfcf31102 This is the documented way to remove user that is still logged in. It also removes home directory, which is necessary as well. Force user process to die 2010-03-12T17:31:51+00:00 Stephen Hemminger stephen.hemminger@vyatta.com 2010-03-12T17:31:51+00:00 urn:sha1:5173409c3325717f2306d03fec79059efe14e566 Bug 5067 Use more persuasive kill to make processes exit, which allows user to be deleted. Handle empty set of public keys 2010-02-19T20:15:14+00:00 Stephen Hemminger stephen.hemminger@vyatta.com 2010-02-19T05:35:30+00:00 urn:sha1:19d3c520ba13678e0388052340f1639ce02d0679 Bug 5362 If no keys configured; still make an empty .ssh/authorized_keys file. This handles case of keys being deleted from configuration and gives notice to user that file will be overwritten. Add support for options in keyfile 2010-02-17T20:45:03+00:00 Stephen Hemminger stephen.hemminger@vyatta.com 2010-02-17T20:00:12+00:00 urn:sha1:3577a4f420d71c8d1040341776a2039ce232b7dd The sshd file format has optional options; copy them to a placeholder node and generate to authorized_keys Better error message when wrong number of arguments. Change owner of created authorized key file 2010-02-02T23:27:36+00:00 Stephen Hemminger stephen.hemminger@vyatta.com 2010-02-02T23:27:36+00:00 urn:sha1:34760e13a35d21f08050a4285f8a12eb37bbf9da Otherwise sshd ignores it! Run login update as root 2010-02-02T23:01:22+00:00 Stephen Hemminger stephen.hemminger@vyatta.com 2010-02-02T22:57:03+00:00 urn:sha1:868fb51d85439d2cb045cf810f23943c60c42c41 Need ability to open file of new user (to load authorized key). So move sudo to template.