You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
chee rabbits 7b4c74f3c3 Update readme.md 11 months ago
bin keep the bin 2 years ago
boops initial_commit 2 years ago
config keep the bin 2 years ago
own what does it mean to succeed 11 months ago
succeed fix url 2 years ago
website initial_commit 2 years ago
.gitignore what does it mean to succeed 11 months ago
index.js dont die when listening is hard 11 months ago
jsconfig.json Subsequential commit 2 years ago
package-lock.json Subsequential commit 2 years ago
package.json Subsequential commit 2 years ago
readme.md Update readme.md 11 months ago

readme.md

snootauth

ssh-based web logins

when you click listen in the browser, it starts a GET request which makes the server open a unix socket that's owned by your user in /snoot/auth/socks/your-uid.sock.

there is an ssh server running on port 2424, (config) which has a ForceCommand setting set to a command called succeed that writes the word success to the socket belonging to your user at which point it immediately exists and says "Thank-you! you can return to your browser"

the GET request to listen receives the "success" and returns, setting a cookie for you on the snoot you are on

and now there is a file that is only read-writeable by the snoot whose site the user is trying to log in to (and the snootauth program, so it can delete or replace them)

so in the snoot's site's server, when you receive a cookie, you can check if it matches the cookie in /snoots/auth/sessions/{their-name}.{my-name}