ports
acme.sh
ports | acme.sh | |
---|---|---|
9 | 281 | |
148 | 37,220 | |
0.0% | 1.9% | |
10.0 | 8.9 | |
6 days ago | 4 days ago | |
Makefile | Shell | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ports
- Zero day RCE
- what opnsense ports do you use?
-
Dnscrypt-proxy package need to update
this was posted in github in late december then got reply not ready https://github.com/opnsense/ports/issues/165 since maintainer package have post in this sub why not try to asking here
- PSA for OPNsense users: OPNsense's attitude towards CVEs (and users)
-
OPNsense pf filter.log format
I know what the rest of the fields mean from reading filter.log description, but what are those 2 other fields?
- Find out outgoing calls to home
-
Running Nextcloud on OPNsense
The second idea was to try to install Nextcloud on FreeBSD using the OPNsense ports. Bad idea. Nextcloud has a lot of dependencies, it’s too complex to install and impossible to maintain.
-
FilterLog Change in 21.1.9_1 broke grok
I just did an update from 21.1.2(?) up to 21.1.9_1 and noticed that all my ELK stack > grafana data was no longer working for firewall logged info. I checked the available fields and all the important stuff is missing. Did an explore on the datasource and found the grokparsefailure tag. Quick google found that this patch updated the logfilter for the firewall. I found a previous thread here it provided a new description: ports/description.txt at master · opnsense/ports · GitHub as well as a new grok: OPNsense filterlog GROK patterns · GitHub OPNsense filterlog GROK patterns · GitHub
-
filterlog format change
It didn't change much: the ridentifier was always unused and now we add a label in its place, see https://github.com/opnsense/ports/blob/master/opnsense/filterlog/files/description.txt
acme.sh
-
Setting up a www subdomain on a self-hosted Ghost blog
server { listen 80; listen [::]:80; server_name www.myblog.lol; root /var/www/ghost/system/nginx-root; # Used for acme.sh SSL verification (https://acme.sh) location / { return 301 https://myblog.lol$request_uri; } location ~ /.well-known { allow all; } client_max_body_size 50m; }
-
Setting up a Homelab: Part 1 Proxmox and LetsEncrypt
A self-signed certificate was generated and used by Proxmox which will always generate a warning on the browser. I did not like seeing this when trying to work on my home lab. So, I started looking for ways to put a valid SSL certificate in Proxmox. During my research, I found that Proxmox could be made to integrate with acme.sh; a free SSL certificate generator powered by ACME(Let's Encrypt).
-
How to Build Email Server with Exim on Alma Linux 9
Next, we will install acme.sh, a command-line tool for managing SSL/TLS certificates. I prefer acme.sh over certbot, as it does not depend on the OS version. For more details about acme.sh, check its GitHub repo here.
-
Dehydrated: Letsencrypt/acme client implemented as a shell-script
A very relevant question. Acme.sh, a similar shell script ACME client, had a remote code execution problem last year.
https://github.com/acmesh-official/acme.sh/issues/4668
-
Ask HN: What is your experience with ZeroSSL?
As a result, any certificates issued (or renewed) after Feb 8th will not work on older Android devices (< 7.1.1), unless the ACME client has been configure to request an alternate certificate chain. The "alternate chain" workaround will also stop working on June 6th.
I need to support these older Android devices so I am looking for alternatives. I have seen ZeroSSL mentioned a few times; it is also the default CA for acme.sh (the ACME client I am using nowadays) [2]. They have a number of paid plans but ACME certificates are free [3].
I'll be testing this over the next few days, but I would also like to ask if people here have experience with ZeroSSL (good or bad :-). Any feedback would be helpful.
[1]: https://letsencrypt.org/2023/07/10/cross-sign-expiration.html
[2]: https://github.com/acmesh-official/acme.sh
[3]: https://zerossl.com/documentation/acme/
-
Why Certificate Lifecycle Automation Matters
Huh, the environment variable thing was specifically aimed at acme.sh which rather arbitrarily changed the config value from ACMEDNS_UPDATE_URL to ACMEDNS_BASE_URL, never acknowledged this in a changelog and then silently failed after an automatic upgrade as recommended by the default install:
https://github.com/acmesh-official/acme.sh/commit/2ce145f359...
It's also cleared out my .account.conf files when run on the suggested cron.
I've started using updown which also monitors my TLS certs simply because I no longer trust the process to work as documented.
-
The Bureau of Meteorology website does not support connections via HTTPS
It depends on your provider though. I can tell from experience that with OVH and their API, it's been easy to set up the automatic renewal via DNS verification. Apparently, the official client has support for the DNS API of 159 providers: https://github.com/acmesh-official/acme.sh/wiki/dnsapi
-
I made a tool for automatically updating the current and next (rollover) TLSA DNS records with acme.sh and the Cloudflare API
For the few people here that happen to run a self-hosted email server with acme.sh for TLS key/cert generation and Cloudflare for DNS management, I have made a tool that i personally use to get a perfect 100% score on Internet.nl's email test.
-
How to get LetsEncrypt certs from PfSense/ACME to other machines? (automated??)
All of this is to say it's a decent amount of work to save the hassle of deploying certbot or acme.sh on the remote machines, pick your poison.
-
Hosting at home & SSL
Here is a really solid guide for setting up the ACME DNS challenge with pretty much any DNS provider