19·
15 days agoLMDE - the emergency escape hatch for mint. gotta love the forethought.
qprimed
…just this guy, you know.
- 0 Posts
- 16 Comments
Joined 1 year ago
Cake day: May 7th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
65536 levels of nested goodness, bae-bae!
sigh. here we go again…
unzips archive
10·1 month agoexactly. I have been begging multiple ISPs for direct IPv6 allocations for 10+ years now. its always “we are internally testing - not available for distribution yet”. the most recent request from me was less than 3 months ago when I needed a IPv4 /29 for a remote site. figured I would see if I could also get a nice sized IPv6 allocation as well. nope. just gotta keep paying a premium for that dwindling IPv4 address space.
Hurricane Electric is to be commended for their public IPv6 tunnels, but without direct allocations from your immediate upstream, its just play.
10.0.0.0/8172.16.0.0/12192.168.0.0/16🎶 a whole new wooorrrld… 🎶
there is no fix more permanent than a temporary one.
edit: as I literally sit here inspecting the nat tables on a couple of edge routers.
6·2 months agoAROS (Amiga) Research Operating System
would run in an emulator or bare metal boot from separate media.
GPL3 tries to deal with this “tivoization”
but every API change brings it closer to perfection! cant stop, wont stop!
the API change high is such a rough addiction to break.
2·4 months agoheh, forgot about the standalone web server in certbot. thats a good ephemeral option.
if you are able to run a public web server, then certificate issuance via certbot http challenge works pretty well. the web server can serve a really simple static page with little to nothing on it - but of course its another potential vector into your network.
if your public domain DNS makes use of a supported dns provider or you run your own publically accessible dns server, then dns certbot challenges are great and more flexible than http.
others may suggest neat work arounds for the http challenge issue, but if you have access to a supported dns service I would look at that option. certbot has helpers for quite a few public services as well as support for self hosted dns servers. I run my own public dns servers, so thats the option I chose and use certbot hooks, cron and bash scripts to rsync the updated carts to the propr hosts for the various services I run privately and publicly.
if you are using http cert retrieval, certbot needs a place put the temp. token to authenticate your contrrol of the domain your are creating a certificate for. usually that will be the same webserver you want to serve the certificate from.
if you are not running an actual weberver on port 80 that certbot can insert a token for, certbot cannot complete.
this is, of course, in addition to other possible issues such as ISP port blocking - but without a web server listening on TCP/80, you will have to use other authorization methods (like DNS) to generate a cert.
are you actually running a web server on that host? iirc, certbot will place a temporary token to be served by your web server (Apache, etc.) to show that you actually control the domain you are requesting a cert for.
I switched to DNS based retrieval as soon as let’s encrypt offered it, so its been years since I retrieved certs via http.
15·6 months agono kidding. this particular FWP was… unpleasant.
everyone needs a good
vicehobby.
ONE OF US! ONE OF US!
but seriously, modern FOSS distros (yes, debian is modern, damnit!) are amazingly good. you have an exceptionally high probablility of switching and staying switched.