System Administration
25
•
url
: link destination URL
Additionally, you can name a link, specify a comment, and make the presence of the link on the home page
conditional on a profile.
4.2.5. Password hashing
The user settings on the firebrick have password control (as well as optional OATH one time pad restrictions).
In the config this is entered as a simple password, but when accessed you will see that the password has been
replaced with a hash.
The FireBrick supports a number of hash functions for passwords, but on any successful login may change the
in-memoty config to use the current preferred password hash function. This is done if a very old hash is being
used. This is not automatically saved, but any view/edit of the config will see the new hash and on save will
record the new hash. This allows FireBrick to more to more secure password hash functions in future whilst
maintaining backward compatibility.
If making a config file independantly you can generate the hashes yourself in most cases. The supported hash
codings ar as follows. For salted hashes, the salt is the additional bytes after the number of bytes for the hash.
• FB105#[10 bytes of hex]: A legacy for the old FB105 password hashing, used by the FB105 conversion tool.
• MD5#[16 to 19 bytes of hex]: The first 16 bytes are an MD5 hash of the password appended with up to 3
bytes of salt.
• SHA1#[20 to 31 bytes of hex]: The first 20 bytes are an SHA1 hash of the password appended with up to
11 bytes of salt.
• SHA256#[32 to 47 bytes of hex]: The first 32 bytes are an SHA256 hash of the password appended with
up to 15 bytes of salt.
The preferred has is SHA256 with 15 bytes of salt.
4.3. Software Upgrades
FB2700 users benefit from FireBrick's pro-active software development process, which delivers fast fixes of
important bugs, and implementation of many customer enhancement requests and suggestions for improvement.
As a matter of policy, FireBrick software upgrades are always free to download for all FireBrick customers.
To complement the responsive UK-based development process, the FB2700 is capable of downloading and
installing new software directly from Firebrick's servers, providing the unit has Internet access.
This Internet-based upgrade process can be initiated manually (refer to Section 4.3.3.1), or the FB2700 can
download and install new software automatically, without user intervention.
If the unit you want to upgrade does not have Internet access, then new software can be uploaded to the unit
via a web browser instead - see Section 4.3.4.
Caution
Software upgrades are best done using the Internet-based upgrade process if possible - this ensures
the changes introduced by Breakpoint releases are automatically accounted for (see Section 4.3.1.1)
Software upgrades will trigger an automatic reboot of your FB2700 - this will cause an outage in routing,
and can cause connections that are using NAT to drop. However, the FB2700 reboots very quickly, and in
many cases, users will be generally unaware of the event. You can also use a profile to restrict when software
upgrades may occur - for example, you could ensure they are always done over night. The reboot will close