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

New startup sells coffee through SSH

terminal.shop

Post reply on HN
Print view View original

141–150 of 430 posts

Re: New startup sells coffee through SSH

#141

Post by melodyogonna »

jethro_tell wrote: post #138
Scarblac wrote: post #74

Earlier quoted context omitted.

Still, it identifies you so it can be used to track you over visits to many different stores-over-ssh, just like third party cookies.

Lol, the subset of people buying coffee via ssh and shopping elsewhere via ssh is going to be insanely small, they can probably already more or less track you. Additionally, you're probably giving a shipping address and using a card number of some sort. Its extremely difficult to shop anonymously online for physical goods.

> Lol, the subset of people buying coffee via ssh and shopping elsewhere via ssh is going to be insanely small

Yeah, nerds. In the FAQ there is the question "What is SSH", and the answer is - "If you have to ask then it's not for you".

Edit: Seems the FAQ may have been updated or this simply wasn't part of the online version, https://imgur.com/a/igjGCFM here is a section of the FAQ sent to my email.

Re: New startup sells coffee through SSH

#142

Post by umbra07 »

tiptup300 wrote: post #100
fouc wrote: post #43

Earlier quoted context omitted.

I love TUI (as in text-based user interfaces) so much more than GUI. It always felt like a far more peaceful and productive environment.

As long as I have ctrl+c/v copy and pasting I'm right there with you.

don't you mean yy and p?

Re: New startup sells coffee through SSH

#144

Post by bee_rider »

orblivion wrote: post #84

So unless you mean to exclusively sell coffee to users who don't have a white terminal background, you may want to consider your color scheme. I was missing the white text. (I know this is considered an atrocity by some, but I happen to not really care enough about my terminal color to change the default)

The atrocity was committed by whoever set that default, we can work out a plea deal as long as you rat them out.

Re: New startup sells coffee through SSH

#145

Post by glennpratt »

fragmede wrote: post #47
rvnx wrote: post #40

One safety tip: disable SSH Agent Forwarding before you connect, otherwise the remote server can theoretically reuse your private key to establish new connections to GitHub.com or prod servers (though this host is unlikely malicious). https://www.clockwork.com/insights/ssh-agent-hijacking/ (SSH Agent Hijacking)

The full command you want is: ssh -a -i /dev/null terminal.shop to disable agent forwarding, as well as to not share your ssh public key with them, but that's just a little less slick than saying just: ssh terminal.shop to connect.

I'm curious why you added `-i /dev/null`. IIUC, this doesn't remove ssh-agent keys.

If you want to make sure no keys are offered, you'd want:

  ssh -a -o IdentitiesOnly=yes terminal. Shop
I'm not sure if the `-i` actually prevents anything, I believe things other than /dev/null will still be tried in sequence.

Re: New startup sells coffee through SSH

#146

Post by PaulDavisThe1st »

A lot of people don't know that before Amazon started, there was a company out of Portland, OR called Bookstacks selling books via a telnet interface. In the early days, Bezos was quite worried about their potential to get "there" first (wherever "there" was going to be). It was a fairly cool interface, at least for 1994.

[ EDIT: worried to the point that we actually implemented a telnet version of the store in parallel with the http/html one for a few months before abandoning it ]

Re: New startup sells coffee through SSH

#150

Post by leni536 »

nomel wrote: post #125
rvnx wrote: post #40

One safety tip: disable SSH Agent Forwarding before you connect, otherwise the remote server can theoretically reuse your private key to establish new connections to GitHub.com or prod servers (though this host is unlikely malicious). https://www.clockwork.com/insights/ssh-agent-hijacking/ (SSH Agent Hijacking)

Is it not standard practice to make different keys for different important services? I have a private key for my prod server, a private key for GitHub, and a private junk key for authenticating to misc stuff. I can discard any without affecting anything else that's important. If I authenticated with my junk key, would my other keys still be at risk?

It's a good practice, but it's somewhat against the grain of ssh defaults. It's not surprising that many people stick to the defaults.
Post reply on HN