From Atomicorp Wiki
Jump to: navigation, search


[edit] Introduction

Tortixd is the web console daemon for ASL.

[edit] Settings

There is currently only one user configurable setting for Tortixd. That is the Access Control List system for tortixd.

[edit] ACL system

If you want to block access to tortixd, except from certain IPs, just add the IPs to this file:


One IP or CIDR per line. For example:

Then reload the ASL security policy:

asl -s -f

This will block, and log, any access to port 30000 from IPs not on that list. Repeated attempts to connect will result in a shun of the offending IP as well.

If you want to allow all IPs to connect (this opens up the ASL web login page to everybody), add the following line to /etc/asl/firweall/tortixd-access-list:

[edit] Log files

Tortixd use the follow directory for its log files:


[edit] asl_access_log

This contains any access requests to the non-SSL protected ASL web console port. This is disable by default. By default the ASL web console will only allow connections to its SSL port. Therefore this file should be empty. If it is not, that means someone has enabled non-SSL access to the ASL web console.

[edit] asl_error_log

This contains general errors the ASL web console has encountered.

[edit] asl_ssl_access_log

This contains any access requests to the SSL protected ASL web console port. By default the ASL web console will only allow connections to its SSL port.

[edit] asl_ssl_error_log

This contains general errors with SSL support in the ASL web console, and other general errors the ASL web console may have encountered.

If you are having issues with setting up your own SSL certs, any errors will be logged in this file.

[edit] SSL certificates

If you wish to configure the ASL web console to use a different SSL certificate check with your SSL vendor for instructions for setting up SSL keys and certificates for Apache. Each SSL vendor may require you change different settings. The ASL web console SSL settings are provided in this file:


The following is provided as a courtesy, and should not be used unless you know what you are doing. Always follow the instructions of your SSL vendor.

[edit] Generic instructions

Step 1) Configure Apache to point to your SSL cert, key and CA bundle:

Important Note: These files must be in directories, and their permissions must be configured to allow the tortix user to read them. Unlike apache, for security reasons tortix does NOT start as root, and therefore cannot read any file on the system.


This is the path to your certificate file.


SSLCertificateFile /your/path/to/your.cert


This is the path to your secret key.


SSLCertificateKeyFile /your/path/to/your.key


This is the path to your certificate file. Your SSL provider will provide you with this file.


SSLCACertificateFile /etc/pki/tls/certs/ca-bundle.crt

Step 2)

Restart tortixd:

service tortixd restart

Note: If you have questions about generating SSL keys and certs, please contact your SSL vendor.

[edit] Errors

[edit] x509 certificate routines:X509_check_private_key:key values mismatch

This errors means the private key file (that you supplied via your configuration) does not match the certificate (that you supplied via your configuration). This can happen if you mix up the key and certificate. You can test this from the command line:

To make sure the files tally, display the modulus value of each file:

openssl rsa -noout -modulus -in FILE.key
openssl req -noout -modulus -in FILE.csr
openssl x509 -noout -modulus -in FILE.cer

If everything matches (same modulus), the files are compatible. If not, one of the file is not linked to the others.

Note: Modulus only applies on private keys and certificates using the RSA cryptographic algorithm. If you generated keys using ECC (Elliptic Curve Cryptography) private key or if your certificate is signed with ECC you won't find a modulus.

Personal tools