OXIESEC PANEL
- Current Dir:
/
/
var
/
lib
/
snapd
/
sequence
Server IP: 139.59.38.164
Upload:
Create Dir:
Name
Size
Modified
Perms
📁
..
-
06/18/2025 09:10:01 AM
rwxr-xr-x
📄
certbot-dns-digitalocean.json
949 bytes
06/12/2025 09:50:09 PM
rw-r--r--
📄
certbot.json
3.09 KB
06/12/2025 09:50:09 PM
rw-r--r--
📄
core.json
3.57 KB
05/08/2025 11:44:45 PM
rw-r--r--
📄
core20.json
4.19 KB
06/14/2025 11:50:07 AM
rw-r--r--
📄
core24.json
4.2 KB
05/21/2025 08:15:08 AM
rw-r--r--
📄
hello-world.json
391 bytes
08/15/2024 06:40:18 AM
rw-r--r--
Editing: certbot.json
Close
{"sequence":[{"name":"certbot","snap-id":"wy7i66qPx4neXr6m9rTh7Y40h8EhtZFh","revision":"4557","channel":"latest/stable","links":{"contact":["https://github.com/certbot/certbot/issues"],"website":["https://certbot.eff.org"]},"contact":"https://github.com/certbot/certbot/issues","title":"certbot","summary":"Automatically configure HTTPS using Let's Encrypt","description":"The objective of Certbot, Let's Encrypt, and the ACME (Automated\nCertificate Management Environment) protocol is to make it possible\nto set up an HTTPS server and have it automatically obtain a\nbrowser-trusted certificate, without any human intervention. This is\naccomplished by running a certificate management agent on the web\nserver.\n\nThis agent is used to:\n - Automatically prove to the Let's Encrypt CA that you control the website\n - Obtain a browser-trusted certificate and set it up on your web server\n - Keep track of when your certificate is going to expire, and renew it\n - Help you revoke the certificate if that ever becomes necessary.\n"},{"name":"certbot","snap-id":"wy7i66qPx4neXr6m9rTh7Y40h8EhtZFh","revision":"4730","channel":"latest/stable","links":{"contact":["https://github.com/certbot/certbot/issues"],"website":["https://certbot.eff.org"]},"contact":"https://github.com/certbot/certbot/issues","title":"certbot","summary":"Automatically configure HTTPS using Let's Encrypt","description":"The objective of Certbot, Let's Encrypt, and the ACME (Automated\nCertificate Management Environment) protocol is to make it possible\nto set up an HTTPS server and have it automatically obtain a\nbrowser-trusted certificate, without any human intervention. This is\naccomplished by running a certificate management agent on the web\nserver.\n\nThis agent is used to:\n - Automatically prove to the Let's Encrypt CA that you control the website\n - Obtain a browser-trusted certificate and set it up on your web server\n - Keep track of when your certificate is going to expire, and renew it\n - Help you revoke the certificate if that ever becomes necessary.\n"},{"name":"certbot","snap-id":"wy7i66qPx4neXr6m9rTh7Y40h8EhtZFh","revision":"4737","channel":"latest/stable","links":{"contact":["https://github.com/certbot/certbot/issues"],"website":["https://certbot.eff.org"]},"contact":"https://github.com/certbot/certbot/issues","title":"certbot","summary":"Automatically configure HTTPS using Let's Encrypt","description":"The objective of Certbot, Let's Encrypt, and the ACME (Automated\nCertificate Management Environment) protocol is to make it possible\nto set up an HTTPS server and have it automatically obtain a\nbrowser-trusted certificate, without any human intervention. This is\naccomplished by running a certificate management agent on the web\nserver.\n\nThis agent is used to:\n - Automatically prove to the Let's Encrypt CA that you control the website\n - Obtain a browser-trusted certificate and set it up on your web server\n - Keep track of when your certificate is going to expire, and renew it\n - Help you revoke the certificate if that ever becomes necessary.\n"}],"current":"4737","migrated-hidden":false,"migrated-exposed-home":false}