Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Simple Unix Chat

the-dam.org

Post reply on HN
Print view View original

51–60 of 175 posts

Re: Simple Unix Chat

#51

Post by slooonz »

eyelidlessness wrote: post #4

> suc does all that by leveraging SSH, UNIX’s access control API, and UNIX’s text-based modularity. On any fair metric, this should inflate the volume of code metric for any project (whether leveraging those APIs directly or not). It would still favor this implementation on that front, and there are still other merits to the approach besides code volume. But something does irk me about touting supposed minimalism whi…

By that argument, you should count the codebase of the whole browser against slack.

Re: Simple Unix Chat

#52

Post by eyelidlessness »

dclowd9901 wrote: post #42
eyelidlessness wrote: post #40

Earlier quoted context omitted.

It’s pretty valid disingenuity. It’s just also pretty valid to identify as such.

Did the title contain the disclaimer? I only found it after visiting the page.

I didn’t even see the disclaimer reading the page, I must have skipped it because it was pretty obvious.

Re: Simple Unix Chat

#53

Post by [deleted] »

eyelidlessness wrote: post #4

> suc does all that by leveraging SSH, UNIX’s access control API, and UNIX’s text-based modularity. On any fair metric, this should inflate the volume of code metric for any project (whether leveraging those APIs directly or not). It would still favor this implementation on that front, and there are still other merits to the approach besides code volume. But something does irk me about touting supposed minimalism whi…

[deleted]

Re: Simple Unix Chat

#54

Post by simonjgreen »

Gigachad wrote: post #38
bandrami wrote: post #22

Earlier quoted context omitted.

I once was in a meeting about which web authentication framework to use for a site that ran so long because of bikeshedding that I implemented during the meeting and demoed at the end a solution based on the fact that HTTP already provides an authentication facility.

HTTP auth is vastly insufficient for most use cases. You are missing passwords resetting, 2FA, bot/abuse detection, and probably a whole collection of other stuff. I’m also not sure if passwords manager extensions can prefill them. As well as the fact that the login form is only 1% of what an auth library does.

They didn't actually say they used basic Auth :) (although it's a reasonable assumption)

I think the principal here is not reinventing wheels.

Re: Simple Unix Chat

#55

Post by rakoo »

See also ii (https://tools.suckless.org/ii/) doing something similar but on irc directly: use a single standard file for all conversation, auth and access is managed by the irc network directly and there are many UIs already. Like the article, a plugin is anything that reads a file and writes into another.

Re: Simple Unix Chat

#56

Post by TeMPOraL »

lynx23 wrote: post #45
spicybright wrote: post #8

In case you're passing over this because it sounds like click bait (it KIND OF is), this was actually a good read to me. It goes over a utility called "suc" (Simple Unix Chat) that implements server functionalities from Slack, Discord, etc. using a very small codebase. The novel part is it leverages existing unix tools and methodology instead of re-inventing them. - Auth is handled by SSH. - Channels are just a file…

Wait, KISS is a novelty? :-)

Novelty? More like the ways of our great grandparents.

Re: Simple Unix Chat

#57

Post by linschn »

onetom wrote: post #43

what do i do after i sign up to the-dam.org ? i did not get any email after the payment and ssh-ing doesn't work either. (i just get a `Permission denied (publickey)`)

To HN readers: this has been sorted out, adding user is a semi-manual process and I was asleep :)

Re: Simple Unix Chat

#58

Post by linschn »

59nadir wrote: post #47
onetom wrote: post #43

what do i do after i sign up to the-dam.org ? i did not get any email after the payment and ssh-ing doesn't work either. (i just get a `Permission denied (publickey)`)

Same for me. I suspect maybe they add the public keys manually and haven't gotten around to it yet.

That's exactly what happened :) thank you.

Re: Simple Unix Chat

#59

Post by lloeki »

mappu wrote: post #14

Most current distros prevent you from making setuid bash scripts, on security grounds. But you can get most of the same effect with a specific sudoers entry.

> Most current distros prevent you from making setuid bash scripts

_any_ shebang script really... except perl scripts, because perl has taint mode turned on automatically when uid != euid

https://perldoc.perl.org/perlsec#Taint-mode

Note that there may be a fundamental race condition on some systems:

https://perldoc.perl.org/perlsec#Shebang-Race-Condition

Also see the noted use of `sudo -T`:

https://perldoc.perl.org/perlsec#Using-Sudo

I lament the recent removal of taint mode from Ruby :( as tainting is a powerful mechanism that could go way beyond scripts: imagine Rack / Rails #html_safe but via tainting so it could have worked more thoroughly (e.g concatenate/interpolate/format a tainted user string into a SQL snippet would blow up, preventing a whole class of SQL injections by design)

Some folks used to use taint for CGI/mod_perl to such great effect. It's not a magic bullet by any means (security is hard!) but it's a really effective tool still.

Post reply on HN