share-file-systems
acme-dns
Our great sponsors
share-file-systems | acme-dns | |
---|---|---|
34 | 37 | |
122 | 1,969 | |
- | - | |
8.7 | 0.0 | |
about 2 months ago | 12 days ago | |
TypeScript | Go | |
GNU Affero General Public License v3.0 | MIT License |
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.
share-file-systems
-
Lcl.host: fast, easy HTTPS in your local dev environment
Some things I learned about trusted localhost HTTPS:
* Windows is the easiest... by far. There is only one trust store and its extremely easy to access at different levels of trust. Firefox has its own trust store so you can either add your certs to both the Windows store AND the Firefox trust store or flip a config in Firefox to tell it to use the Windows trust store like everyone else.
* Linux is a challenge because you have to add your certificates to the OS trust store and then each browser has their own trust stores.
* MacOS is pretty close to impossible, at least fully automated. If the cert is not registered with a third party of the OS's choosing the cert will not be trusted in the browser. The way around this is to manually add your localhost cert chain to the MacOS keychain.
If anybody wants an example here is something I wrote a ways back in JS (but please be warned its specific to my application:
* Build the certificate chain - https://github.com/prettydiff/share-file-systems/blob/master...
* Install the cert by OS type - https://github.com/prettydiff/share-file-systems/blob/master...
That second sample also installs pcap so that I can serve on localhost over ports 80/443.
-
We have used too many levels of abstractions and now the future looks bleak
Some developers believe everything is always a framework or any attempt to avoid frameworks creates a new framework. I cannot help these people. Any non-religion is a cult type nonsense of affirming the consequent fallacy.
Otherwise a valid example is this one file that creates a complete OS-like GUI in the browser awaiting content typically populated from WebSocket messaging: https://github.com/prettydiff/share-file-systems/blob/master...
-
Os.js β open-source JavaScript web desktop platform with a window manager
I wrote a similar concept around private internet access to your file system. Itβs at https://github.com/prettydiff/share-file-systems
The window and state management can be demoed on my personal site at https://prettydiff.com
-
Ask HN: Tell us about your project that's not done yet but you want feedback on
File sharing and soon remote execution over the internet cross OS. Private and no servers.
https://github.com/prettydiff/share-file-systems
-
Meta Forced to Reveal Anonymous Facebook User's Identity
Done: https://github.com/prettydiff/share-file-systems/blob/master...
You would need a warrant to extract the messages/identity directly from a person's computer as there is nothing otherwise to obtain.
-
More encryption means less privacy (2016)
Perhaps this is true in the context of the web. But I got tired of watching the web as a platform continuously repeat the same mistakes so I started working on something different. In the last day or two I was finally able to functionally prove my competing idea in a way that forcefully imposes privacy with complete Zero Trust conformance.
https://github.com/prettydiff/share-file-systems/blob/master...
-
Bfs 3.0: The Fastest Find Yet
I am performing a similar file system tree navigation asynchronously in Node.js which is just a shallow API over the C Linux FS APIs.
I can see you are using opendir and closedir functions? What is the benefit from using the opendir function[1] when readdir[2] can be called on a location directly? Is the benefit that opendir returns a file descriptor for use in opening a stream to gather directory object descriptors?
[1] https://man7.org/linux/man-pages/man3/opendir.3.html
[2] https://man7.org/linux/man-pages/man3/readdir.3.html
Your project is probably more mature but if you want an alternate approach to examine here is I have been doing it: https://github.com/prettydiff/share-file-systems/blob/master...
I considering changing my use of readdir to use the withFileTypes option so that it returns a list of directory entries (objects of artifact name and type) instead of a list of conditions to discern types like I am doing on lines 382-432.
-
Easy HTTPS for your private networks
Solved.
Solved for both Windows and Linux (Debian, Arch, Fedora). I might have unlikely solved this of OSX as well, but I am not buying Apply hardware just to test it.
What my solution does is check for certificates created by the project during a build step. If the certificates don't exist it creates them, installs them in the OS, and also install them in the browser. Installation in the browsers is required in Linux and only for FireFox in Windows. These are cert chains containing a self-signed root, intermediary CA, and a local domain cert.
I have these certs configured to work with my own domains so that I can connect to a subdomain addressed to a loopback IP and the cert recognizes that domain, but the domain "localhost" works as well. Sometimes its nice to access a real domain to avoid any restrictions imposed upon accessing address "localhost". You just have to change the domains at the bottom of your OpenSSL option files.
Here is how I solved it with vanilla TypeScript in Node.js (also requires locally installed OpenSSL:
* OpenSSL option file 1 - https://github.com/prettydiff/share-file-systems/blob/master...
* OpenSSL option file 2 - https://github.com/prettydiff/share-file-systems/blob/master...
* Certificate library - https://github.com/prettydiff/share-file-systems/blob/master...
* Certificate interface from build tool - https://github.com/prettydiff/share-file-systems/blob/master...
* Certificate installation - https://github.com/prettydiff/share-file-systems/blob/master...
If you have any questions just open a Github issue on the project.
-
Ask HN: Who wants to be hired? (June 2023)
Email: [email protected]
15 years experience with JavaScript, 6 years experience with TypeScript. I am currently writing a Node based OS in TypeScript to solve for decentralization (not Web3): https://github.com/prettydiff/share-file-systems
I understand performance aggressively enough far beyond the comfort of most developers: https://github.com/prettydiff/wisdom/blob/master/performance...
-
Ask HN: Are you working on a big software project? Happy with the architecture?
I started a JS based file sharing application a few years back. It started as a thought experiment of just exposing the file system to the browser in a familiar OS kind of user interface. As new features are added over time it has become more like a high level OS.
https://github.com/prettydiff/share-file-systems
Some architectural decisions I made:
* Micro-service based
* I am now using WebSockets for all services and communication. That has proven in the application to be 7x faster than HTTP.
* I have a universal format wrapping all service messaging, kind of like sending a letter in an envelope. This allows me to using a single service end point for all services and a single means of service monitoring.
* I did not like the existing test automation solutions based upon CDP, because they are too slow and fragile. Also, they do not provide support for a peer-to-peer experience. So I wrote my own test automation solution for testing in the browser and its much faster and predictable.
* I am using an identity based authentication mechanism to restrict access to known users/devices.
* I just write to the file system instead of using a database for data storage. This allows for much faster application start up times and lowers complexity. The performance difference is insignificant after accounting for that in most cases opening a file is more costly than arbitrarily writing to the file system.
* I figured out how to install certificates using automation in both Windows and Linux which allows me to run the application using encrypted transmission protocols (https/wss) on localhost.
acme-dns
-
Subdomain.center β discover all subdomains for a domain
Getting a wildcard certificate from LE might be a better option, depending on how easy the extra bit of if plumbing is with your lab setup.
You need to use DNS based domain identification, and once you have a cert distribute it to all your services. The former can be automated using various common tools (look at https://github.com/joohoi/acme-dns, self-hosted unless you are only securing toys you don't really care about, if you self host DNS or your registrar doesn't have useful API access) or you can leave that as an every ~ten weeks manual job, the latter involves scripts to update you various services when a new certificate is available (either pushing from where you receive the certificate or picking up from elsewhere). I have a little VM that holds the couple of wildcard certificates (renewing them via DNS01 and acmedns on a separate machine so this one is impossible to see from the outside world), it pushes the new key and certificate out to other hosts (simple SSH to copy over then restart nginx/Apache/other).
Of course you may decide that the shin if your own CA is easier than setting all this up, as you can sign long lived certificates for yourself. I prefer this because I don't need to switch to something else if I decide to give friends/others access to something.
- Easy HTTPS for your private networks
-
I've created a solution for managing internal domains, how do I selfhost this more?
As someone else said, itβs a huge pain to run your own dns services. However, if you want some separation, I recently saw https://github.com/joohoi/acme-dns
-
LeGo CertHub v0.9.0 with Docker Support
v0.9.1 is out and natively supports both https://github.com/joohoi/acme-dns and any dns provider available in https://github.com/acmesh-official/acme.sh
-
How do you deal with SSL certs management?
I have set up an acme-dns server to answer ACME DNS Challenges: https://github.com/joohoi/acme-dns
- How to configure and use acme-dns?
-
What is a good alternative if port 80 is blocked?
The DNS challenge can be easily automated using https://github.com/joohoi/acme-dns - you do need an IP you can run a DNS server on though.
-
Setting up ssl on AGH
If your server is not accessible over the internet, you can still use Let's Encrypt or ZeroSSL to get a certificate. You'll just need to set up a DNS Challenge for things to work. This is a little more complicated, but can work even if your DNS provider doesn't have an API. For example, I use Google Domains and Google DNS (not cloud DNS) for my DNS server, but I've got an instance of acme-dns running on VPS box that handles the DNS auth for me. It's how every machine on my local network has valid certificates - but I annoyingly need to renew them every 90 days.
-
Did Manjaro just forget to renew the SSL certificate?
It's a bit more involved, but you can set up wildcard certificates to update automatically. Certbot has some pre-made plugins for this for several DNS providers. If yours is not on that list, there's a tool called acme-dns which is a minimal DNS server you can run on your server and delegate _acme-challenge.yourdomain.com to. If you don't want to run that on your own, you can also use the publicly hosted server/API for it.
-
Reverse proxy for internally hosted services
In case you're not already familiar with it: one thing I'd recommend is using https://github.com/joohoi/acme-dns to obtain the certificates. You basically just point the subdomain you need wildcard certs for at that DNS server (a one time thing, ie you don't have to do this every three months), and the related tool https://github.com/acme-dns/acme-dns-client can get the certificates in a nice, automated, way without you ever having to expose the private reverse proxy to the Internet.
What are some alternatives?
DsHidMini - Virtual HID Mini-user-mode-driver for Sony DualShock 3 Controllers
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
Redis - Redis is an in-memory database that persists on disk. The data model is key-value, but many different kind of values are supported: Strings, Lists, Sets, Sorted Sets, Hashes, Streams, HyperLogLogs, Bitmaps.
lego - Let's Encrypt/ACME client and library written in Go
Clendar - Clendar - Minimal Calendar app. Written in SwiftUI.
duckdns - Caddy module: dns.providers.duckdns
userbase - Create secure and private web apps using only static JavaScript, HTML, and CSS.
acme-dns-server - Simple DNS server for serving TXT records written in Python
circles-ios - E2E encrypted social networking built on Matrix. Safe, private sharing for your friends, family, and community.
acme.sh - A pure Unix shell script implementing ACME client protocol
PhotoPrism - AI-Powered Photos App for the Decentralized Web ππβ¨
dehydrated - letsencrypt/acme client implemented as a shell-script β just add water