| Age | Commit message (Collapse) | Author |
|---|
|
In line with Bug #318 and Bug #355, use SHA-512 instead of MD5 when
creating the initial vyos user password during installation.
Bug #579 http://bugzilla.vyos.net/show_bug.cgi?id=579
|
|
|
|
This reverts commit 593899accdff03af23e6bb6c7189ad4ed05a4d8e.
This commit reintroduced the inability to delete a user configured on
the system, which was resolved in bug #557. Reverting this for the
time being until a better fix can be implemented.
|
|
|
|
|
|
Any system based symlinks installed in the /etc/commit/post-hooks.d
directory were being deleted on either the initial start of the system
or subsequent reboots. This commit resolves this by excluding these
from the deletion process, while still tidying up other non system
symlinks.
This is required for bug #538 (enhancement request) to function as
intended and also enables the Vyatta bug fix 4718 (enhancement), to log
successful commits to syslog with commit type and user name, commited
on February 2012!
Bug #576 http://bugzilla.vyos.net/show_bug.cgi?id=576
|
|
|
|
Prevent the deletion of both the encrypted-password and public-keys
nodes for a user, ensuring that at least one of the methods is
available. Also prevent the deletion of the public keys for a user
if the encrypted password is set to "!".
Bug #574 http://bugzilla.vyos.net/show_bug.cgi?id=574
|
|
The fix for bug #557 now allows the encrypted-password Authentication
node to be deleted again, but this causes the config to fail on reboot,
leaving the user login node empty.
This fix checks for an empty / missing encrypted-password node on
reboot / config reload, either creating a new node or replacing the
existing one and assigning it the value of "!". This has the same
effect as the fix for bug #336, allowing the user to be set as only
using RSA based logins.
Bug #573 http://bugzilla.vyos.net/show_bug.cgi?id=573
|
|
Following the fix for bug #336 that prevents the deletion of the
encrypted password, which resulted in a broken config node on reboot,
it was no longer possible to delete users. This reverts the fix for
that bug.
Bug #557 http://bugzilla.vyos.net/show_bug.cgi?id=557
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Bug #519: Add dhcpv6 client-id option
|
|
|
|
Bug #508: Set correct dhclient configuration filename
|
|
|
|
|
|
Update the bridge priority node to set the default STP priority to the
standard of 32768 when it's deleted, and update the node help to
indicate the new default and possible values.
Bug #512 http://bugzilla.vyos.net/show_bug.cgi?id=512
|
|
Bug #512: Set default STP priority to 32768
|
|
|
|
|
|
|
|
Add the additional services that are supported by ddclient to the list
of service defaults. Also add a function to use this list to check for
the allowed protocols, and update the protocol node to use this.
Bug #507 http://bugzilla.vyos.net/show_bug.cgi?id=507
|
|
|
|
Update the default protocol used for the dslreports service in the
revised dynamic DNS system and remove the default server settings for
freedns as it's already defined in ddclient. Uodate the wording in the
server node to indicate it's only needed for custom services.
Bug #507 http://bugzilla.vyos.net/show_bug.cgi?id=507
|
|
Add flexibility to dynamic dns configuration (#507)
If this is proven problematic, we can revert and work more on it.
|
|
compatibility (#507)
|
|
|
|
Bug #385: Fix broken commit 6257dfa1464d460de74e258b6290d4890a885218
|
|
|
|
|
|
When the system is installed in a raid configuration, grub is installed
to the raid device instead of to the individual slave drives, resulting
in a failure to boot after installation. This commit identifies the
slave drives and ensures grub is installed to all of them (rather than
just the primary), resulting in a system that will boot following a
primary drive failure.
Bug #106 http://bugzilla.vyos.net/show_bug.cgi?id=106
|
|
|
|
Add the vyatta-dhcp3-client package to the list of dependencies with a
minimum version of 4.1.8+vyos2+lithium3, following changes to the ntp
updating routines.
|
|
Skip over either invalid ntp servers, or ntp server hostnames that have
failed to resolve correctly, and continue to process the rest of the
configuration.
Bug #94 http://bugzilla.vyos.net/show_bug.cgi?id=94
|
|
Update the new NTP updating routines so they operate outside of
configuration mode (dhcp triggered updates). This also requires
changes to the vyatta-dhcp3 package (see Bug #500)
Bug #94 http://bugzilla.vyos.net/show_bug.cgi?id=94
|
|
Bug #94 http://bugzilla.vyos.net/show_bug.cgi?id=94
|
|
When NTP is configured on the system, it not only acts as a client
for the configured servers, but also as a server. Although the server
is only available as a time source, it still represents a service that
the user hasn't specifically enabled.
This commit sets the default configuration of NTP to disallow all
external access, so the system acts purely as a client by default, and
also introduces the ability to configure which addresses / subnets are
allowed to both query and use it as a time source. If the servers
configured are specified as host names, these are resolved to IP
addresses before being added to ntp.conf, with the same process carried
out after name server changes.
syntax 'set system ntp client address'
Bug #94 http://bugzilla.vyos.net/show_bug.cgi?id=94
|
