Live data from Hacker News

Late.sh – a command-line Clubhouse for computer people

late.sh

71–80 of 141 posts

Re: Late.sh – a command-line Clubhouse for computer people

#71
post #54
post #49

This is a really cool idea, and very appealing. Also very nice that it looks usable with just an SSH client. It would be useful if it was explained what the companion client is for? Another small personal gripe: I think you should either remove the 1 line copy/paste sh install on the homepage, or add a link to a git repo on the homepage. I know it's possible to view the sh by visiting it, but a raw text file doesn't…

Not to mention that a webserver can be configured to show one sh file when a regular browser visits and another when curl etc. gets it. Show one thing, install another.

[deleted]

Re: Late.sh – a command-line Clubhouse for computer people

#72
post #54
post #49

This is a really cool idea, and very appealing. Also very nice that it looks usable with just an SSH client. It would be useful if it was explained what the companion client is for? Another small personal gripe: I think you should either remove the 1 line copy/paste sh install on the homepage, or add a link to a git repo on the homepage. I know it's possible to view the sh by visiting it, but a raw text file doesn't…

Not to mention that a webserver can be configured to show one sh file when a regular browser visits and another when curl etc. gets it. Show one thing, install another.

So download it with curl and read it first before executing it from your local disk.

Re: Late.sh – a command-line Clubhouse for computer people

#73
post #66

Earlier quoted context omitted.

Okay, but why is that something to be concerned about? How would one be able to probe to see if a server recognizes a public key? Why does that matter?

so, i used my public key. can someone please tell me what i should be worried about now?

If I have your public key I could probe a server to see if it recognizes that public key. Which would tell me information you might not want to be leaked.

Re: Late.sh – a command-line Clubhouse for computer people

#75
post #72
post #54

Earlier quoted context omitted.

Not to mention that a webserver can be configured to show one sh file when a regular browser visits and another when curl etc. gets it. Show one thing, install another.

So download it with curl and read it first before executing it from your local disk.

read it ? we dont do what kind of stuff here, i got my army of reader agents.

Re: Late.sh – a command-line Clubhouse for computer people

#76
post #66

Earlier quoted context omitted.

Okay, but why is that something to be concerned about? How would one be able to probe to see if a server recognizes a public key? Why does that matter?

so, i used my public key. can someone please tell me what i should be worried about now?

l33t h4xx0r5

Re: Late.sh – a command-line Clubhouse for computer people

#77
post #68
post #61

Reminder to be cautious about leaking public keys. Once you leak your public key it could be used to check if another server recognizes that leaked public key.

Surely you shouldn't be leaking your username. I could use it to see if another server recognised 'h43z'....

OpenSSH server is designed not to reveal whether a username exists.

Re: Late.sh – a command-line Clubhouse for computer people

#78
post #72
post #54

Earlier quoted context omitted.

Not to mention that a webserver can be configured to show one sh file when a regular browser visits and another when curl etc. gets it. Show one thing, install another.

So download it with curl and read it first before executing it from your local disk.

Except you can't really be sure, still: http://web.archive.org/web/20250622061208/https://www.idontp...
Post reply on HN