vyatta-cfg-system.git/lib, branch debian/0.16.5Vyatta 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.16.52009-12-18T19:15:39+00:00User deletion update2009-12-18T19:15:39+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-12-18T19:15:39+00:00urn:sha1:42144158c9036f4801289905a316de4a2b7a772e
1. Allow deleting user still logged in (Bug 5067)
2. Don't allow deleting self, because that would mean killing current
process.
Redefine meaning of protected-user2009-12-09T22:51:15+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-12-09T22:51:15+00:00urn:sha1:59c50771a80bd57b9f0c82505799909b022d3023
A entry in protected-user means that the Vyatta config system should
just leave it alone. This is intended for root, and other special
accounts.
Original code didn't work during admin anyway because of missing
sudo.
Allow root account to not exist2009-12-08T22:49:39+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-12-08T22:49:39+00:00urn:sha1:f956bfc6ee753fbbf251a7c43e7ad2573aa89c83
If root account is deleted, disable it rather than removing it from
passwd file and confusing everything.
Fix configure of user2009-12-07T19:38:53+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-12-07T19:38:53+00:00urn:sha1:17b7a875e114c6765ec5940dda8a067b5e51da1c
Previous change broke setup of root account because 'uid = 0' looks
like false so useradd called when usermod was intended.
Fix code that generates authorized keys2009-12-05T04:23:15+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-12-05T04:23:15+00:00urn:sha1:b614be8960a38c4a31c85f2ece5777fa01df86f3
This now works.
loadkey vyatta scp://user@host/~/.ssh/id_rsa.pub
Rearrange the public-key configuration schema2009-12-04T23:42:35+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-12-04T23:32:42+00:00urn:sha1:103371d47c0d3ea4c28901810e11127de3855d5d
New syntax:
system login user vyatta authentication public-key user@remote type ssh-rsa
Set modes of created authorization key (and directory)2009-12-03T23:13:24+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-12-03T23:13:24+00:00urn:sha1:a3dd4c078da9aefabef4a24d0af2e4382d9f74a1
sshd is picky about modes (and it should be), so make sure
and chmod the file.
Update .ssh/authorized_keys as part of the login update2009-12-03T20:07:50+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-12-03T20:07:50+00:00urn:sha1:bb4083fa12386e9417e4dbae38325deb03d821e7Simply Radius server update2009-12-03T00:17:23+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-12-03T00:17:23+00:00urn:sha1:249f7eae3d1374e8e22e35113c89fc32eacdbf91
Rather than complex sed editing, just regenerate whole file.
Fix library include2009-11-06T13:52:14+00:00Robert Baysrbays@roatan.(none)2009-11-06T13:52:14+00:00urn:sha1:92834105d2a01ca61a91a15672c8492e2b8371b2