mleku on Nostr: so, i decided i needed yet another mleku domain, so now i have mleku.net migrated my ...
so, i decided i needed yet another mleku domain, so now i have mleku.net
migrated my NIP-05 to it now, so my NIP-05 name is _@n.mleku.net or just n.mleku.net
this server is rented for a whole year, and is tiny, all it is doing is reverse proxy and forwarding ports to the wireguard subnet, the SSH is not exposed but instead only the wireguard so it won't get irritating logs full of bruteforce attempts on the SSH login
plus for the hell of it i used p256 curve keys on the ssh because it's almost secp256k1 lol
would be kinda cool to be able to take the #golang wireguard implementation and add BIP-340 keys and build in an integral interface to the user shell, effectively replace both SSH and wireguard into one single service... but maybe some day in the future
it was quite entertaining reading up on the use of ECDSA NIST p256 curve keys for SSH, it loudly claims that it widely regarded that the NIST approved curves are probably backdoored by the NSA and thus they are unpopular
funny how secp256k1 gets tarred with the same brush by so many "experts" in elliptic curve cryptography when the K curves, whose factors were devised by Koblitz, were specifically chosen by Satoshi because they could not have been backdoored
anyhow, the other thing is now all my git hosting is coming out of my hp G3 mini PC sitting on the shelf behind my pc and i want to actually switch it up to become my router at some point since i'm downstream of the main house router anyway... i also should get a few spare short ethernet cables and ask my landlord's gopher to come so i can poke into the network cabling box in the garage to actually connect up my bedroom and second loungeroom ethernet sockets, so i have more freedom to rearrange my seat
doing normal git hosting via SSH is fine but i want to have http as well and the instructions i have found so far on how to do this kinda suck, but i suspect that i can throw together a http accessible git hosting server for minimal https web hosting so i can serve dependencies from it directly and set up more entries in my lerproxy that let me have all my git repos as subdomains, eg replicatr.mleku.net slog.mleku.net lerproxy.mleku.net etc etc
doesn't seem that anyone has actually done much work to make such self hosting easy so i guess probably i'm going to build something.... i've written git handling code in Go before, that probed the current repository to extract the parent commit hash and other details, and i know it can do the whole shebang, at least the important parts of the whole shebang, commits, tags, fetch, pull, clone, branches and i suspect when i dig it up it'll actually have more or less in the examples a full http host service so i can have my precious subdomains
#deardiary #devstr #wireguard #selfhosted #ellipticcurve #nsa #backdoor #nist #golang #ecdsa
migrated my NIP-05 to it now, so my NIP-05 name is _@n.mleku.net or just n.mleku.net
this server is rented for a whole year, and is tiny, all it is doing is reverse proxy and forwarding ports to the wireguard subnet, the SSH is not exposed but instead only the wireguard so it won't get irritating logs full of bruteforce attempts on the SSH login
plus for the hell of it i used p256 curve keys on the ssh because it's almost secp256k1 lol
would be kinda cool to be able to take the #golang wireguard implementation and add BIP-340 keys and build in an integral interface to the user shell, effectively replace both SSH and wireguard into one single service... but maybe some day in the future
it was quite entertaining reading up on the use of ECDSA NIST p256 curve keys for SSH, it loudly claims that it widely regarded that the NIST approved curves are probably backdoored by the NSA and thus they are unpopular
funny how secp256k1 gets tarred with the same brush by so many "experts" in elliptic curve cryptography when the K curves, whose factors were devised by Koblitz, were specifically chosen by Satoshi because they could not have been backdoored
anyhow, the other thing is now all my git hosting is coming out of my hp G3 mini PC sitting on the shelf behind my pc and i want to actually switch it up to become my router at some point since i'm downstream of the main house router anyway... i also should get a few spare short ethernet cables and ask my landlord's gopher to come so i can poke into the network cabling box in the garage to actually connect up my bedroom and second loungeroom ethernet sockets, so i have more freedom to rearrange my seat
doing normal git hosting via SSH is fine but i want to have http as well and the instructions i have found so far on how to do this kinda suck, but i suspect that i can throw together a http accessible git hosting server for minimal https web hosting so i can serve dependencies from it directly and set up more entries in my lerproxy that let me have all my git repos as subdomains, eg replicatr.mleku.net slog.mleku.net lerproxy.mleku.net etc etc
doesn't seem that anyone has actually done much work to make such self hosting easy so i guess probably i'm going to build something.... i've written git handling code in Go before, that probed the current repository to extract the parent commit hash and other details, and i know it can do the whole shebang, at least the important parts of the whole shebang, commits, tags, fetch, pull, clone, branches and i suspect when i dig it up it'll actually have more or less in the examples a full http host service so i can have my precious subdomains
#deardiary #devstr #wireguard #selfhosted #ellipticcurve #nsa #backdoor #nist #golang #ecdsa