Age | Commit message (Collapse) | Author |
|
|
|
|
|
options
|
|
|
|
|
|
|
|
Remove the comment from the plaintext-password node regarding empty
encrypted password values as you can't set them as empty.
|
|
You can't create a user without a password, but once this user is
created, you can then delete the encrypted password. However, deleting
the encrypted password from the config doesn't actually remove the
password on the system and in addition breaks the config on reboot,
resulting in the system login node being entirely absent.
This fix ensures that the encrypted password is set to "!" when the
config node is deleted, removing the password login capability for this
account but still allowing SSH RSA key login.
Bug #336 http://bugzilla.vyos.net/show_bug.cgi?id=336
|
|
The password reset option only allows resetting the password for the
default admin (vyos) user. This now allows the user to be specified
for the password reset, defaulting to the 'vyos' user with a password
of 'vyos'.
Bug #342 http://bugzilla.vyos.net/show_bug.cgi?id=342
|
|
In line with Bug #318, set the default vyos user password hash to use
SHA-512 instead of MD5 when recreating the user during a password reset
Bug #355 http://bugzilla.vyos.net/show_bug.cgi?id=355
|
|
Add the default plaintext-password entry to the default vyos user
created during password reset.
Bug #342 http://bugzilla.vyos.net/show_bug.cgi?id=342
|
|
If you delete the vyos user from the system and then go into password
reset mode on reboot, the configuration entry for the vyos user is
recreated but the command returns 'usermod: user 'vyos' does not exist'.
Despite this message the user is created correctly on a full reboot,
just not at the point the command is run.
Bug #342 http://bugzilla.vyos.net/show_bug.cgi?id=342
|
|
|
|
vyatta-cfg-system: allow dhcp and dhcpv6 addresses to be deleted
|
|
Allow interfaces with either dhcp or dhcpv6 addresses to be deleted.
Expand on the previous patch for Bug #305 to now take dhcpv6 addresses
into account, as well as an update to the original dhcp logic.
Bug #341 http://bugzilla.vyos.net/show_bug.cgi?id=341
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Minor cleanup.
|
|
|
|
|
|
|
|
|
|
do AWS-specific things.
|
|
|
|
|
|
|
|
and whatever else we have.
|
|
|
|
|
|
|
|
|
|
|
|
Add support for VXLAN
|
|
vyatta-cfg-system: rename allow-dhcp-nameservers and change to typeless
|
|
Rename allow-dhcp-nameservers to disable-dhcp-nameservers and update
the logic to take the new meaning into account. The option is now also
typeless, so the node is either absent (default) or present (enabled).
Format 'set / delete system disable-dhcp-nameservers'
Linked to Bug #182 and Bug #308
Bug #314 http://bugzilla.vyos.net/show_bug.cgi?id=314
|
|
vyatta-cfg-system: expand 'set system allow-dhcp-nameservers' logic
|
|
|
|
Expand the logic in 'set system allow-dhcp-nameservers', so that in
addition to either allowing / denying DHCP related updates to
resolv.conf when the interface changes state, it will also either
add or remove the currently supplied DHCP name-servers depending on
it's state. This change in name-servers will take place immediately
on commit.
Bug #309 http://bugzilla.vyos.net/show_bug.cgi?id=309
|
|
Update scripts/vyatta-system-nameservers to have consistent identation
levels and style throughout.
|
|
'remote-ip' is nowt set.
|
|
vyatta-cfg-system: add 'set system allow-dhcp-nameservers' option
|
|
|
|
Instead of simply allowing / denying DHCP related updates to resolv.conf
based on the current values of 'set system name-server', as initially
proposed for Bug #182 (http://bugzilla.vyos.net/show_bug.cgi?id=182),
this patch replaces that behaviour with a global option to allow /
deny these updates.
Add 'set system allow-dhcp-nameservers' as a boolean value that has the
default value of true, so allowing DHCP nameserver updates by default.
Bug #308 http://bugzilla.vyos.net/show_bug.cgi?id=308
|
|
vyatta-cfg-system: revert bb71cf5b7b3a48812e28dbefba8c535f9bbf9973
|
|
Reverting commit bb71cf5b7b3a48812e28dbefba8c535f9bbf9973 as it breaks
the logic in vyatta_update_resolv.pl for removing name servers when
called by dhclient-script. As it stands, the commit causes name server
entries to be left behind in resolv.conf when a DHCP interface is
deleted, resulting in possibly old or invalid entries remaining
indefinitely.
Bug #307 http://bugzilla.vyos.net/show_bug.cgi?id=307
|
|
Update scripts/system/vyatta_update_resolv.pl to have consistent
identation levels and style throughout.
|