Mirror of https://lapo.it/asn1js/.
A parsing tool by lapo.it. Really useful for digging into certificates. Or if you find any random binary data that you suspect might be asn1, toss it into lapo's handy parsing tool.
Mirror of http://davidc.net/sites/default/subnets/subnets.html
Subnet tool by David C. Useful when you want to segregate your lan. There is a linking scheme that is useful if you want to share the subnets. Or you can also stick the link into your long-lived network documentation.
Mirror of httpbin.org.
http requests testing suite by Ken Reitz+ . Handy just for testing how a http client works or just verifying that you have connectivity.
➜ ~ curl https://httpbin.jskw.dev/get -s | jq
{
"args": {},
"headers": {
"Accept": "*/*",
"Connection": "close",
"Host": "httpbin.jskw.dev",
"User-Agent": "curl/7.68.0"
},
"origin": "44.55.66.77",
"url": "http://httpbin.jskw.dev/get"
}
➜ ~ curl https://httpbin.jskw.dev/get -s | jq -r '.origin'
44.55.66.77
Mirror of https://lesspass.com.
A so called "Sateless" password manager. It actually does allow you to syncronize some things (password requirements/usernames/other params) but it does not require that you syncronize passwords to a central database.
If you choose to sync to the database then I would recommend that you do not use a different "Master password" for signing into the password manager and generating application passwords. You do have to trust that the server doesn't sneak in any malicious javascript down the road. I've tried to mitigate this by having a fairly restrictive content security policy.
It actually is possible to encrypt (actually it's a hash...) the master password before using it to sign into the password manager, but it's too easy to accidently send your plaintext password to the server. It would be nice if it went through one round of hashing by default. It is kinda neat that you can just keep clicking the hash button to keep changing it until it's an emoji sequence you like, but, it's really not clear to the user what is going on. This would need to be a little more secure by default and transparent to the user before I could recommend this app.
Mirror of https://send.firefox.com/.
Requires basic auth if your not my ip allow list. I'm not really sure how I can make this public without being subject to the same kind of abuse that the original encountered.
Another more basic way to share files. Secured by haproxy basic auth, powered by python -m http.server.