vyatta-cfg-system.git/lib, branch master 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=master 2017-09-21T05:22:59+00:00 Fix problem with path and permissios for usermod 2017-09-21T05:22:59+00:00 Mihail Vasiliev mickvav@gmail.com 2017-09-21T05:22:59+00:00 urn:sha1:9435cbeb57cfcf40c35071c7a4f2b8a4861d83c6 After vyos moved to non-root commits we need to become root to modify existing users. login: force vyatta user's to have vbash as shell 2013-05-02T21:35:23+00:00 Stephen Hemminger shemming@brocade.com 2013-05-02T21:35:23+00:00 urn:sha1:06de833692473549d168081461cc089dbefb8365 If account already existed in passwd file, but then same user added to Vyatta config, force the shell to be vbash. This fixes case of autologin on initial livecd boot where the autologin happens as 'vyatta' but gets bash instead of vbash as shell. Allow deleting unknown user 2012-08-17T20:07:55+00:00 Stephen Hemminger shemminger@vyatta.com 2012-08-17T20:07:55+00:00 urn:sha1:8d5f6cdd84b95644502eb7115dbca03754549b74 Bug 8287 If user doesn't exist in passwd file that is fine. 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.