| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
Will try a new approach to use the same entry point for all actions
connected to the firewall profiles configuration.
|
| |
|
|
|
|
|
|
|
| |
In commit d7a8babb19bcc1107daff0cc5673bc32b0ed785b the check if the
configuration value 'eurephiadm_xslt_path' was set in the database
looked in the wrong configuration area. Fixed this and it now copies
the value over from the database configuration.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added two extra ./configure arguments, --xslt-path which defines the
root directory for all eurephia specific XSLT templates (defaults to
/usr/share/eurephia/xslt) and --eurephiadm-xslt which defines the path
eurephiadm will use for its XSLT templates (defaults to
/usr/share/eurephia/xslt/eurephiadm)
Added an extra configuration paramet for eurephiadm
(eurephiadm_xslt_path), which can be used to override the compiled in
default values
|
| |
|
|
|
|
|
|
| |
Do proper conversion from char * to xmlChar *. Need to figure out a
better way how to return xmlChar * to char * when returning strings
which may contain UTF-8.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Due to the current implementation of SHA512 salts, it could be
experienced as if the application hung on wrong passwords. This is
because the rounds count for the passwords are scrambled, with values
based on the given password. When a wrong password is given, this will
also result in getting a wrong salt length and hash rounds for the
following hash calculation.
Due to this, the extracted rounds value from the salt string could
return some really high number of rounds on wrong
passwords (possibly the max value if integer). And this is why the
"hang" is experienced.
To avoid this, a check is added to make sure the rounds is not
unreasonably much higher than the configured max rounds values. If the
descrambled rounds number from the salt exceeds max rounds * 1.5, the
password (most probaly) is wrong. In this case we do a sleep() to slow
down bruteforce attacks and return NULL.
The drawback is if the maxrounds later on is changed to a value which
hits this scenario:
passwordsalt_rounds > maxrounds_cfg * 1.5
In this case these old passwords will be invalidated by that
configuration change. This is considered to be a feature and not a bug.
The reason for mulitiplying by 1.5, is to allow a little room for a
degrading the max rounds setting. By adjusting the max rounds up again,
these passwords will be valid again.
Added also a sleep() when wrong username is attempted.
|
|
|
|
|
|
|
|
| |
When calling eDBadminGetCertificateInfo(...) or
eDBadminDeleteCertificate(...) with a search XML document using
common_name or organisation and these fields contained spaces, no
certificates would be deleted. This is because space is replaced with
underscore in the database.
|
|
|
|
|
|
|
|
|
| |
When doing certs --delete --help, wrong help text was shown.
When trying to delete certificates with common name or organisation as
search fields, no certificates was found. This is another fix after the
commit 3c35318429e33c98c2d7fac8943dfc6ff40359c7 which changed some of
the XML tags for the certificate table.
|
| |
|
|
|
|
|
| |
Added in addition missing GPLv2 only remarks where it was missing
from commit 0712bce6f387121e37501ec323e3da89ce4300c3
|
| |
|
|
|
|
|
| |
Made sure we only include needed include files and checked that
the copyright headers are equal and correct
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Only listing of user access levels are implemented.
|
|
|
|
|
|
| |
This lastlog command will list all entries of eurephia
sessions. This list can also be filtered by giving
proper arguments.
|
| |
|
|
|
|
|
| |
Had to also extend the FIELD_* assignments to allow two
new fields to be mapped
|
| |
|
|
|
|
|
|
| |
This function will return an XML document with data extracted
from the eurephia_adminaccess table. Search criterias are
defined by the search XML doc given as input.
|
|
|
|
| |
Just to honour those who have contributed directly or indirectly
|
| |
|
|
|
|
| |
Also removed debug info as well
|
|
|
|
|
|
|
| |
In commit 3c35318429e33c98c2d7fac8943dfc6ff40359c7 the field
mapping was simplified for some fields, but the XML document
used for registering certificates was never updated to reflect
these chanages.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Run the utils/eurephia_init program to setup and do the initial
configuration of eurephia. It needs 2 required arguments
--database-driver <path to database driver>
--database-args <arguments to the db driver>
This utility will then guide you through a setup for the
different configuration parameters used by eurephia.
|
|
|
|
| |
Implemented eDBadminEditAdminAccess(...) function in db driver
|
| |
|
| |
|
| |
|
|
|
|
| |
Follow up from commit 062a3c92343a5fa371f8637f8bca88aacca14cc4
|
|
|
|
|
|
|
|
|
|
| |
This to make it clearer that passwdhash(...) is not good for password
hashing, but suitable when you need a quick hashing algorithm.
The eurephia_quick_hash(...) are now used for password caching hashing,
and is still suitable here since the salt used for the passwords are in
memory only and never written to disk, as they are supposed to be
temporary hashes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This new function, eurephia_pwd_crypt(...) implements a modified SHA512
hashing algorithm based on the SHA512 crypt implementation proposed by
Ulrich Drepper for glibc.
The original implementation adds support for variable hashing rounds.
The eurephia version implements dynamic hashing rounds, controlled by
minimum and maximum rounds set in the configuration. If not set, it
will minimum use 5000 rounds and maximum 7500 rounds. The amount of
rounds is supposed to be random.
In addition to this, the salt information is now encoded into a hex
value. In this value the salt length and the hash rounds are defined.
This hex value is then encoded (quasi crypt) based on a modulus of the
sum of the characters in the password + the password length. So if you
give the wrong password, you will also get the wrong salt length and the
wrong number of hashing rounds used.
The default salt length is also increased to 32 bytes (256 bit)
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This makes it possible to compile it on some older versions
of the SQLite3 library
|
|
|
|
| |
eurephia_randstring(...) function
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is to prepare eurephia-auth plugin to use other and
more CPU intensive hashing algorithms for passwords. In addition,
open sessions will now not be rejected/closed due to wrong
password if the user changes the password with an open session
running.
The patch adds a new server_salt attribute in the eurephiaCTX
structure. This is used as a temporary salt and is created of
random data when OpenVPN is started.
When a user is being authenticated (eurephia.c/eurephia_userauth)
a authentication session (not the same as a 'normal' session) is
opened and checked for a cached password. If it does not exist
or match, normal password check will be done against the user
database. If a cached password is found and matches, it is
considered to be authenticated.
The cached password uses the SHA512 algorithm, together with the
eurephiaCTX->server_salt.
|
|
|
|
| |
hashing algorithms
|
| |
|