Senhasegura app certificate update
The default senhasegura installation includes a self-signed 512-bit SSL certificate. Senhasegura recommends that you change this certificate for a valid market certificate.
You can use crt or cer for the certificate and a file extension key for the key, without any password in the key file.
Access the menu Orbit ➞ Panel➞ Certificates to access the screen where you can upload a new pair of certificate files and your key.
The file upload screen will be displayed on 1 upload the .crt file and on 2 the .key file.
After uploading, the screen will display the new certificates.
To validate the certificate .crt use the following command:
openssl x509 -noout -modulus -in <certificate.crt> | openssl md5
In <certificate.crt> insert the certificate name, as in example below <ss.crt>
Then, to validate the certificate validation key use the command, rename certificate.key according to your key:
openssl rsa -noout -modulus -in <certificate.key> | openssl md5
Related Articles
Senhasegura upgrade
Before execute Senhasegura update ALWAYS execute a SNAPSHOT in your hypervisor! Snapshots in Senhasegura instances must be done with the instance powered off, to make sure that the rollback will be possible. Info Validate that the instance has access ...Senhasegura - System key agent was not properly initialized
Ukoliko se nakon nadogradnje ili promjene postavki pojavi ova poruka napravite sljedeće: 1. Logirajte se preko ssh konzole (port 59022). 2. Upišite “sudo su” naredbu da bi postali root. 3. Zatim upišite naredbu “orbit application init” (potvrdite sa ...N-sight Patch Management update
In the week of February 6th, N-sight patch management will receive a major update. As a part of this update, N-sight patching will be updated to align with Microsoft classifications, and third-party products can be configured individually. The ...N-sight RMM agent losing connection
There is an issue in the current Windows GA Agent (v10.13.2), which is causing some servers to incorrectly show as overdue. It also fixes an issue related to Take Control policies not being adhered to in some cases. We encourage you to upgrade to ...Offsite copies to Immutable Wasabi Buckets keep failing with "InvalidRetentionPeriodSet"
It seems that after the data has been copied, an attempt is made to delete older jobs based on the retention, but Wasabi is not allowing that. The retention period is not set directly in the Wasabi Console but by VM Backup when setting up the backup ...