letsencrypt
signal-desktop
Our great sponsors
letsencrypt | signal-desktop | |
---|---|---|
21 | 13 | |
30,850 | 33 | |
0.6% | - | |
9.0 | 8.8 | |
17 days ago | 10 days ago | |
Python | Shell | |
GNU General Public License v3.0 or later | GNU Affero General Public License v3.0 |
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.
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; } } }
signal-desktop
- Signal is back 🙌
- Hostile behavior by the Signal team
-
Snap Store administrators removed signal-desktop from Ubuntu Snap
The AGPLv3 only requires that you make the source available, that can even be on request. But that's not what's going on here. The code used to build their snap [is available](https://github.com/snapcrafters/signal-desktop/blob/master/s...), and they just tear apart the official .deb to repackage, meaning you can offer the source just by pointing people upstream, that's valid and often done.
- cant install signal?!
- Linux Snap package not updated
-
Failed to start Daemon Snapd
``` snap info --verbose signal-desktop name: signal-desktop summary: Signal Desktop health: status: unknown message: health has not been set publisher: Snapcrafters store-url: https://snapcraft.io/signal-desktop contact: https://github.com/snapcrafters/signal-desktop/issues license: unset description: | Private messaging from your desktop. commands: - signal-desktop notes: private: false confinement: strict devmode: false jailmode: false trymode: false enabled: true broken: false ignore-validation: false base: core18 snap-id: r4LxMVp7zWramXsJQAKdamxy6TAWlaDD tracking: latest/stable refresh-date: 18 days ago, at 22:02 CET channels: latest/stable: 5.30.0 2022-02-10 (383) 196MB - latest/candidate: ↑ latest/beta: ↑ latest/edge: 5.32.0 2022-02-17 (384) 227MB - installed: 5.30.0 (383) 196MB -
-
Is Signal snap safe? Because is not from the official developer
Would it be possible to update the Signal branding and license? They changed a while ago but Snap Store kept the old ones.
What are some alternatives?
acme.sh - A pure Unix shell script implementing ACME client protocol
Signal-Desktop - A private messenger for Windows, macOS, and Linux.
lego - Let's Encrypt/ACME client and library written in Go
snapcraft - Package, distribute, and update any app for Linux and IoT.
dehydrated - letsencrypt/acme client implemented as a shell-script – just add water
LibreSignal - LibreSignal • The truly private and Google-Free messenger for Android.
Cloud-Init - unofficial mirror of Ubuntu's cloud-init
libsignal - Home to the Signal Protocol as well as other cryptographic primitives which make Signal possible.
dehydrated-bigip-ansible - Ansible based hooks for dehydrated to enable ACME certificate automation for F5 BIG-IP systems
meta-raspberrypi - Yocto/OE BSP layer for the Raspberry Pi boards
SaltStack - Software to automate the management and configuration of any infrastructure or application at scale. Get access to the Salt software package repository here:
rauc - Safe and secure software updates for embedded Linux