meta-raspberrypi
letsencrypt
meta-raspberrypi | letsencrypt | |
---|---|---|
73 | 21 | |
497 | 30,878 | |
- | 0.4% | |
8.2 | 9.0 | |
8 days ago | 4 days ago | |
C | Python | |
MIT License | GNU General Public License v3.0 or later |
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.
meta-raspberrypi
- Damn Small Linux 2024
-
Still no love for WPA3 on the Raspberry Pi 5
How do you figure Pis have bad integration with Yocto?
https://github.com/agherzan/meta-raspberrypi
For what it's worth, the entire Pi lineup is also well supported by Buildroot. In-tree, no less.
- Ask HN: Are there any lean operating systems left?
- It's not an embedded Linux distribution – it creates a custom one for you
-
Most smartphones run Linux (modified kernel) as well as most servers in the world and some consoles but what other major things run a Linux kernel?
Embedded linux exactly. Major OEMs are using yocto. Check https://www.yoctoproject.org/
- Fazer uma distribuição Linux
-
Creating a minimal Debian system
Been there. You don't want alpine or debian. Good gpos, but what you want is Yocto, which will let you build exactly and only what you need piece by piece including only the kernel modules for your hardware, the exact applications you use and no extras, and with a little extra tweaking, you can wire in Mender for ota updates and the ability to push custom images to clients that need specialization, or even fully unlocked images for customers that need it, plus if you're using an SD card, you can send users recovery drives instead of shipping full devices or let them build their own images without your proprietary code
-
Distro that is only terminal, but still has the packages to install stuff?
I second Yocto. It's the kernel in use by the OpenBMC project
-
How to make your own distro?
One last "option" is yocto but tis is not good for desktop, but it can be a fun project.
- Como creo un SO?
letsencrypt
-
ACME with Google Domains using a DNS Zone in GCS DNS
This seems to be not implemented in certbot, yet: https://github.com/certbot/certbot/issues/6566
-
OpenSpeedTest in docker through DSM Reverse Proxy - incorrect upload speeds
If you do go with NPM or Traefik, under the covers it's using certbot to request/renew your certificates through Let's Encrypt using the DNS-01 challenge, meaning you can get wildcard certs and don't have to futz around with port forwards. Again I'd think Caddy has similar functionality, I just have not used it personally. Raw NGINX you probably don't want to try out yet considering it requires manually doing the configs
- Certbot run.bat file identified as batloader trojan by windows defender. Windows defender alerted me of a trojan which appears to simply be the startup batch script for certbot. Currently running full system scan, but I suspect it to be a false positive. Any ideas?
-
Snap Store administrators removed signal-desktop from Ubuntu Snap
certbot won't be missed. The code quality is pretty poor.
https://github.com/certbot/certbot/issues 5000 bugs and it most of it can be replaced by much smaller tools
-
Good Use Of Golang?
Here’s a good code reference (Python and rust): https://github.com/certbot/certbot
-
Let's Encrypt Certbot Not Working on FreeBSD
I am trying to migrate off of Linux and back to FreeBSD, but I hit a problem today. The Let's Encrypt Certbot is not installing. A bit surprising, given how important it is. So I thought I would notify the community Here is my bug report. https://github.com/certbot/certbot/issues/9394
-
How to update Certbot on Debian 11
Last release: https://github.com/certbot/certbot/releases (on 28th August 2022 = 1.29.0)
-
Uacme: ACMEv2 client written in plain C with minimal dependencies
Right? It’s so ridiculous how you’re supposed to use Snap to install certbot. The (well, one of..) GitHub discussion is just beyond the pale:
https://github.com/certbot/certbot/issues/8345#issuecomment-...
-
Let’s Encrypt Receives the Levchin Prize for Real-World Cryptography
It goes way beyond, since Let's Encrypt influence the ecosystem a lot and the standards that are used.
If you use Let's Encrypt, you are likely using Certbot, which means that everybody uses a tool that a central authority strongly recommends to you.
I wonder how they generate the key, for example, it may be using secp256r1: https://github.com/certbot/certbot/blob/5c111d0bd1206d864d7c...
-
Setting up nginx+letsencrypt as a reverse proxy
# nginx-ingress-https.conf events { } http { include mime.types; server { listen 443 ssl; listen [::]:443 ssl; server_name sg.horlick.me; ssl_certificate /etc/letsencrypt/live/sg.horlick.me/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/sg.horlick.me/privkey.pem; # taken from https://github.com/certbot/certbot/blob/master/certbot-nginx/certbot_nginx/_internal/tls_configs/options-ssl-nginx.conf ssl_session_cache shared:le_nginx_SSL:10m; ssl_session_timeout 1440m; ssl_session_tickets off; ssl_protocols TLSv1.2 TLSv1.3; ssl_prefer_server_ciphers off; ssl_ciphers "ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384"; ssl_dhparam /etc/ssl/certs/dhparam.pem; sendfile on; tcp_nopush on; tcp_nodelay on; location / { proxy_pass http://host.docker.internal:9090/; proxy_http_version 1.1; proxy_cache_bypass $http_upgrade; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Port $server_port; } } }
What are some alternatives?
hubris - A lightweight, memory-protected, message-passing kernel for deeply embedded systems.
acme.sh - A pure Unix shell script implementing ACME client protocol
Arduino - Arduino IDE 1.x
lego - Let's Encrypt/ACME client and library written in Go
ArduinoCore-avr - The Official Arduino AVR core
dehydrated - letsencrypt/acme client implemented as a shell-script – just add water
box64 - Box64 - Linux Userspace x86_64 Emulator with a twist, targeted at ARM64 Linux devices
Cloud-Init - unofficial mirror of Ubuntu's cloud-init
yoe-distro - Embedded Linux distribution optimized for product development (based on OE/Yocto)
dehydrated-bigip-ansible - Ansible based hooks for dehydrated to enable ACME certificate automation for F5 BIG-IP systems
stm32f4xx-hal - A Rust embedded-hal HAL for all MCUs in the STM32 F4 family
SaltStack - Software to automate the management and configuration of any infrastructure or application at scale. Get access to the Salt software package repository here: