Live data from Hacker News

Devzat – Chat over SSH, with some nice quality-of-life features

github.com

51–60 of 111 posts

Re: Devzat – Chat over SSH, with some nice quality-of-life features

#51
post #27

so sorry for it being down right now. hn hug of death is real

Guess it’s only useful as a toy :)

Or the person never expected more than a couple of hundred concurrent users and dimensioned the container or whatever after that.

I once wrote a similar chat, but much much worse in many ways, that could easily handle thousands of concurrent users, but hosted it on a 1mbit residential line. When Slashdot hit it I stood no chance.

Re: Devzat – Chat over SSH, with some nice quality-of-life features

#52

Earlier quoted context omitted.

Spoiler: set the user’s shell to any old binary, like a chat app.

Or in the authorized_keys file, prepend the public key with a specified command. This is then the only command that the user can execute when logging in with that particular key. To wit: command="/usr/bin/foo" ssh-ed25519 AAAA....

i had no idea about that, thank you!

Re: Devzat – Chat over SSH, with some nice quality-of-life features

#53
post #23

Cool, the source code is amazingly readable. Also love the sense of humor :-D such as https://github.com/quackduck/devzat/blob/main/commands.go#L1...

When I read this comment, thought good readability it’s got to be Go

The readability might be nice, but the way files are structured makes no sense to me.

In PHP/Typescript there’s always a direct correspondence between imports and file locations, but Go baffles me.

Re: Devzat – Chat over SSH, with some nice quality-of-life features

#54

As a gentle reminder, if you are forwarding your ssh-agent by default, you should connect with: ssh -o 'ForwardAgent no' $host So your secure identities are not exposed to a random ssh server ...

Forwarding your agent by default (to all hosts!) sounds like a terrible idea.

Re: Devzat – Chat over SSH, with some nice quality-of-life features

#56

Earlier quoted context omitted.

Spoiler: set the user’s shell to any old binary, like a chat app.

Or in the authorized_keys file, prepend the public key with a specified command. This is then the only command that the user can execute when logging in with that particular key. To wit: command="/usr/bin/foo" ssh-ed25519 AAAA....

I suppose this will also lock the user out of sftp and scp? Because otherwise they might be able to edit the authorized_keys file and run any command.

Re: Devzat – Chat over SSH, with some nice quality-of-life features

#59
post #56

Earlier quoted context omitted.

Or in the authorized_keys file, prepend the public key with a specified command. This is then the only command that the user can execute when logging in with that particular key. To wit: command="/usr/bin/foo" ssh-ed25519 AAAA....

I suppose this will also lock the user out of sftp and scp? Because otherwise they might be able to edit the authorized_keys file and run any command.

"I suppose this will also lock the user out of sftp and scp?"

No it wont! The specified command might provide sftp, scp, telnet or stream a film.

Post reply on HN