htcpp
acme.sh
htcpp | acme.sh | |
---|---|---|
4 | 280 | |
10 | 36,617 | |
- | 1.2% | |
5.5 | 8.9 | |
about 1 year ago | 3 days ago | |
C++ | Shell | |
- | 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.
htcpp
-
Caddy is the first and only web server to use HTTPS automatically and by default
I'm always a bit bothered by them saying they are the "only" web server that can do this. First you can also just configure it in a way where it will not use HTTPS (e.g. if you provide an IP:port instead of a hostname). And if you do require specific configuration to enable HTTPS and automatically get certificates via ACME, then lots of other web servers can do this too. Even my own web server can do it: https://github.com/pfirsich/htcpp (see https://github.com/pfirsich/htcpp/blob/main/configs/acme.jom... for an admittedly much more complicated config).
-
Introducing co-uring-http, an HTTP server built on C++ 20 coroutines and `io_uring`
Cool stuff! I am currently converting my io_uring based HTTP server (https://github.com/pfirsich/htcpp) to using coroutines as well, so this is cool to see. (WIP library here: https://github.com/pfirsich/aiopp)
-
http sever testing tool
I recently built an HTTP(S) server myself (https://github.com/pfirsich/htcpp) and did not find something like you are looking for. If you also don't find anything (but please link it if you do!), consider just running your server on a publicly accessible VM and listening on port 80 and you will be bombarded by various people trying to break in. Most of it will be useless, like checks for unprotected phpMyAdmin and stuff like that, but I did find a few bugs that way. I even found some TLS issues (of course listen on 443 instead).
-
Who is using C++ for web development?
I am serving static HTML from a web server, which I have built myself using C++: https://github.com/pfirsich/htcpp. I am not sure if that even counts, but I'm kind of proud of it. And I use it to serve my personal website: https://theshoemaker.de.
acme.sh
-
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
-
This is Fine
People wonder why I like using the shell-based ACME client like dehydrated (or acme.sh):
* https://packages.debian.org/search?keywords=dehydrated
* https://github.com/acmesh-official/acme.sh
Versus the official client certbot:
* https://packages.debian.org/search?keywords=python3-certbot
A kludgy as very long shell scripts are (thought to be), I have a better chance of being able to go through all the code and understand it than a dozen(+) Python libraries.
What are some alternatives?
Wt - Wt, C++ Web Toolkit
letsencrypt - Certbot is EFF's tool to obtain certs from Let's Encrypt and (optionally) auto-enable HTTPS on your server. It can also act as a client for any other CA that uses the ACME protocol.
TreeFrog Framework - TreeFrog Framework : High-speed C++ MVC Framework for Web Application
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
bittyhttp - A threaded HTTP library for building REST services in C.
dehydrated - letsencrypt/acme client implemented as a shell-script – just add water
co-uring-http - High performance HTTP server built on C++20 coroutines and io_uring
lego - Let's Encrypt/ACME client and library written in Go
aiopp - Asynchronous IO for C++20
pterodactyl-installer - :bird: Unofficial installation scripts for Pterodactyl Panel
emsdk - Emscripten SDK
docker - ⛴ Docker image of Nextcloud