github-auth3 VS 0x0

This is incompatible with using curl as your client, but one “hacker-friendly way to do auth” is to use Github’s public SSH keys API.

You can stand up an (SCP/SFTP-subprotocol-only) SSH server, and then configure it to call[1] a check on GitHub’s API to map the user’s SSH key to a GitHub username.

From there, you can do whatever you like to continue the auth process: let any GitHub user in; only let GitHub users in from a specific GitHub org; keep an LDAP directory of GitHub usernames such that you can attach metadata to them like “is banned” or “has used up their upload credits for the day” or “is on plan tier X”; etc.

Then, set up automatic local user instantiation per remote user; populate /etc/skel with just the right set of limited files to allow the user to upload into one “spool” directory; and then have an inotify-like daemon that watches for files to be closed in that directory and handles them from there (e.g. uploading them to an S3 bucket, etc.)

[1] As it happens, I wrote an OpenSSHD plugin for exactly this: https://github.com/tsutsu/github-auth3

http://0x0.st works for me

Minimal file hosts like https://catbox.moe or http://0x0.st work nice in my opinion, here's an example link: https://files.catbox.moe/zamm2d.jpg

The only catch is most of them set a time limit on uploads, but you might be able to (ab)use archive.org if you want the files to stay online forever.

Looks similar to 0x0.st

major OOPS here, ( I feel like the sorcerer's apprentice)expression "curl -F'[email protected]' https://0x0.st" returns message that "-F" is badly used, and trying it without the "-F" results in failure . . . oops!

I dont use go$hit drive so I use 0x0.st to upload files for sharing (it uses curl).

curl -F'[email protected]' https://0x0.st

# censor usernames from log sed -iE "s/$USER/$(printf "%${#USER}s")/g" mem.log` # upload curl -F'[email protected]' https://0x0.st

> It was purely decorative, but ugly decoration that only appealed to other brutalist architects, meant to trick people into thinking it was some "raw" construction element sticking out.

That's really funny, because I've seen websites that tries to appeal to "hacker"/"minimalist" aesthetics doing the same thing.

An example: the file-hosting service https://0x0.st. When you try to visit a link to a non-existing file, it will crash with a trace message that exposes the offending code block from `fhost.c`.

Wow, so RAW and BRUTAL. It's even written in C, so hacker-ish! Until you find out that the error message is _fake_: https://git.0x0.st/mia/0x0/src/branch/master/templates/404.h...

The server is actually written in Python and it generates a randomized, fake C-looking trace message for its 404 page.

I'm going to go on a limb and say it's automod because of my file host ( https://0x0.st ) also testing if this comment gets removed or not

First cd into the log directory and run the following command. curl -F '[email protected]' https://0x0.st