Radmin Server possesses the following mechanisms for protecting
user privacy:
All data is transferred using strong 256-bit AES
encryption.
For the user authentication and session key setup
Diffie-Hellman based key exchange with 2048 bit key size is used. A
password is never transmitted between a local and remote
computer.
A highly secure, self-testing code that makes it nearly
impossible to modify the program's executable file.
Either password security or Windows security is used. It is
impossible to connect to Radmin Server without a password or
Windows security rights.
Passwords for connections are not saved, so they cannot be
stolen.
The list of saved user IDs and passwords (in hash form) is
protected on the server side, so only the remote computer's
administrator can access it.
There are special built-in delays that prevent attempts to
guess a password (so-called 'brute-force attacks' or 'dictionary
attacks').
You can configure the IP filter to allow connections only from
specified IP addresses.
You can configure Radmin Server to request the remote
computer's user permissions for each incoming connection.
Connection attempts can be recorded in an event log and/or text
file.
Radmin Server has numerous
built-in security functions, but the safest practice is to make
sure that a password is sufficiently complex (not something like
"111111" that can be guessed on the first attempt) and that it is
not stored in an easily accessible location. Refer to the 'Safety tips' section for more tips.
The server encountered an internal error or
misconfiguration and was unable to complete
your request.
Please contact the server administrator at
webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred,
and the actions you performed just before this error.
More information about this error may be available
in the server error log.
Additionally, a 500 Internal Server Error
error was encountered while trying to use an ErrorDocument to handle the request.
Radmin Server has numerous
built-in security functions, but the safest practice is to make
sure that a password is sufficiently complex (not something like
"111111" that can be guessed on the first attempt) and that it is
not stored in an easily accessible location. Refer to the 'Safety tips' section for more tips.