>vim yaonet_key
An ssh key is a huge string of numbers and letters, this sort of implies that they typed it out and edited it themselves.
This is the one line I would take issue with. >chmod 600 yaonet_key
This hides the key from other users on the system.
Borderline psychotic that he types 600 instead of a=,u+rw but I guess some people prefer that. >ssh -i yaonet_key root@thatIP
This logs them into a remote terminal using that key on the computer at that IP as the root user. >ls >ls /
It's odd that the home directory is empty, and I'm not sure if it just hasn't printed yet, but if it hasn't / being empty is wrong.
Overall reasonable. I've done stuff like this before.
That would take like a minute at least. That bit is kind of ridiculous, but I guess if you can't do it any other way then you can't do it any other way.
But it should take like a solid minute of non-stop typing to do.
wow ur such a hacker!
I'm not trying to boast about it, just trying to be helpful and explain OP's pic.
>600 instead of a=,u+rw
shorter
i also write it like that, the longer way is for troglodytes who can't do bin2dec in their head or don't remember the mask
I guess if you are chmoding a shit ton of files at the command line it would be worth it, but I don't tend to change file permissions very often beyond +x.
They didn't have a copy of the key and their autist roommate memorized it by complete coincidence without knowing what it actually was, so he had to SING it to them over the phone bit by excruciating bit, since that's how he memorized it.
>600 instead of a=,u+rw
shorter
i also write it like that, the longer way is for troglodytes who can't do bin2dec in their head or don't remember the mask
> An ssh key is a huge string of numbers and letters, this sort of implies that they typed it out and edited it themselves.
This is the one line I would take issue with.
Literally the exact shot before this is them creating the full key elsewhere to ref as yaonetkey you braindeadlet. Who would type the full key into the terminal anyways?
>Literally the exact shot before this is them creating the full key elsewhere to ref as yaonetkey you braindeadlet.
>An ssh key is a huge string of numbers and letters, this sort of implies that they typed it out and edited it themselves
idk i'd say its actually pretty realistic
in the show i think they got the key from someone else and he is probably just taking a quick look at it to make sure its a regular ssh key format and not something else
>in the show i think they got the key from someone else and he is probably just taking a quick look at it to make sure its a regular ssh key format and not something else
Sorry, haven't watched the show so I only have the image to go off.
>vim yaonet_key
It didn't occur to you that he may have opened the file to yank the key in perhaps from the clipboard. Are you autistic?
>It didn't occur to you that he may have opened the file to yank the key in perhaps from the clipboard
No, I don't usually have private ssh keys in my clipboard. It's usually faster to just copy the file than to copy its contents.
I don't think I've every opened a private ssh key in an editor before, that's why it seemed odd to me that he would do it. It's also kind of insecure since editors can create backups with the file contents in other locations.
Also, get rekt frickr, I was right (see
>this sort of implies that they typed it out and edited it themselves
I reviewed the scene and in fact they do exactly that. They lose the key because one of them sperged out, but another autist somehow managed to remember the entire key sequence, so he recites it as yet another guy types it into vim.
>An ssh key is a huge string of numbers and letters, this sort of implies that they typed it out and edited it themselves
idk i'd say its actually pretty realistic
in the show i think they got the key from someone else and he is probably just taking a quick look at it to make sure its a regular ssh key format and not something else
>vim yaonet_key
He probably copypasted the key text from elsewhere. Seems very plausible. >chmod 600 yaonet_key
This is completely fine and necessary for OpenSSH to accept the key. >ssh -i yaonet_key root@thatIP
The command itself is fine, HOWEVER: SSH asks for a password at login. This means that the key was wrong. If the person already knows the password, setting up the key was completely useless. >ls
It's fine for this to list nothing, especially for the root account since root's home directory is often empty, except for some dotfiles, which aren't shown by ls by default. >ls /
This command has not been executed yet, note the lack of a prompt below it.
The commands themselves are all reasonable, the SSH key vs. password thing isn't.
>The command itself is fine, HOWEVER: SSH asks for a password at login. This means that the key was wrong. If the person already knows the password, setting up the key was completely useless.
Unless that's part of the plot and the next thing the person says is something along the lines of >"Something's wrong, the key wasn't used. Someone might've messed with the server. OOPS, why did I type in the password in plaintext to login when there's clearly something suspicious going on?"
But that'd filter 99.9% of the potential audience, so they'll stick with >"I'm in"
..
..
Another possibility which is probably not possible with any version of OpenSSH I'm familiar with, would be that you can set it to require both key and password for extra security, though you're still passing a plaintext password over an unencrypted channel so I dunno.
Here's the scene for reference: https://youtube.com/watch?v=S8K464ImU0c
They only have the key, no password. >though you're still passing a plaintext password over an unencrypted channel
No idea what you're referring to with that.
2 years ago
Anonymous
>No idea what you're referring to with that.
An SSH key is an example of a "shared" secret used to open an encrypted (hopefully secure) channel between client and host. When you have a key, every message you send, including the start of it, can be encrypted for security. This is one of the reasons why using a key is considered more secure.
When you authenticate with a password instead, there is no established shared secret, so the initial authentication has to be done unencrypted. Otherwise, the server has no means of decrypting the encrypted gibberish you send. Once authenticated, a shared secret is generated and used to encrypt all future communication between server and client. But you still had to send that password in plaintext.
But yeah, you point out that they don't have a password, so the image is wrong.
2 years ago
Anonymous
What do you think SSH host keys are? Passwords aren't sent unencrypted over SSH, holy shit. The channel isn't necessarily secure unless you actually verify that key to be the right one, but it sure as hell isn't unencrypted.
>this sort of implies that they typed it out and edited it themselves
I reviewed the scene and in fact they do exactly that. They lose the key because one of them sperged out, but another autist somehow managed to remember the entire key sequence, so he recites it as yet another guy types it into vim.
chmod octal file – change the permissions of file
to octal, which can be found separately for user,
group, and world by adding:
● 4 – read (r)
● 2 – write (w)
● 1 – execute (x)
add these values for permissions you want to set, the sums arrayed left to right for user,group, and others, in that order.
Data file in a shared directory, everyone is able to modify: a+rw-x 0666 -rw-rw-rw-
Data file which anyone can read, but only owner can modify: a+r,u+w,go-wx 0644 -rw-r--r--
Data file which anyone can read, which shouldn't get changed: a+r-wx 0444 -r--r--r--
Confidential data: u+rw-x,go-rwx 0600 -rw-------
Confidential data that shouldn't get modified: u+r-wx,go-rwx 0400 -r--------
Executable program which everyone can use: a+rx,u+w,go-w 0755 -rwxr-xr-x
Secret program: u+rwx,go-rwx 0700 -rwx------
info "(coreutils)Mode Structure" # More details
stat -c '%A %a %n' /* # List files/folders in current directory by symbolic and octal chmod mode, and filename.
To complete on the previous answers, I'll mention that the IP can't possibly exist because of the 264. IP4 uses four bytes, so each of the values must be between 0 and 255.
It's most probably intentionally incorrect though, to stop wannabe hackers from trying to ssh into a real IP.
???
no
thank you
>vim yaonet_key
An ssh key is a huge string of numbers and letters, this sort of implies that they typed it out and edited it themselves.
This is the one line I would take issue with.
>chmod 600 yaonet_key
This hides the key from other users on the system.
Borderline psychotic that he types 600 instead of a=,u+rw but I guess some people prefer that.
>ssh -i yaonet_key root@thatIP
This logs them into a remote terminal using that key on the computer at that IP as the root user.
>ls
>ls /
It's odd that the home directory is empty, and I'm not sure if it just hasn't printed yet, but if it hasn't / being empty is wrong.
Overall reasonable. I've done stuff like this before.
wow ur such a hacker!
>passive aggressive reply
He actually types the whole ssh key character by character in the scene.
That would take like a minute at least. That bit is kind of ridiculous, but I guess if you can't do it any other way then you can't do it any other way.
But it should take like a solid minute of non-stop typing to do.
I'm not trying to boast about it, just trying to be helpful and explain OP's pic.
I guess if you are chmoding a shit ton of files at the command line it would be worth it, but I don't tend to change file permissions very often beyond +x.
>I don't tend to change file permissions very often beyond +x
neither do i, but knowing what umask is, whenever i do, it's always just 3 characters
They didn't have a copy of the key and their autist roommate memorized it by complete coincidence without knowing what it actually was, so he had to SING it to them over the phone bit by excruciating bit, since that's how he memorized it.
I love Big Head
>600 instead of a=,u+rw
shorter
i also write it like that, the longer way is for troglodytes who can't do bin2dec in their head or don't remember the mask
>bin2dec
anon?
>Borderline psychotic that he types 600 instead of a=,u+rw
you must be actually moronic. count the characters
inb4
>but muh octal is complicated
actual moron.
>Borderline psychotic that he types 600 instead of a=,u+rw
I just remember a few common permission numbers like 777, 750,, 644, 600, 444
> An ssh key is a huge string of numbers and letters, this sort of implies that they typed it out and edited it themselves.
This is the one line I would take issue with.
Literally the exact shot before this is them creating the full key elsewhere to ref as yaonetkey you braindeadlet. Who would type the full key into the terminal anyways?
>Literally the exact shot before this is them creating the full key elsewhere to ref as yaonetkey you braindeadlet.
>in the show i think they got the key from someone else and he is probably just taking a quick look at it to make sure its a regular ssh key format and not something else
Sorry, haven't watched the show so I only have the image to go off.
>It didn't occur to you that he may have opened the file to yank the key in perhaps from the clipboard
No, I don't usually have private ssh keys in my clipboard. It's usually faster to just copy the file than to copy its contents.
I don't think I've every opened a private ssh key in an editor before, that's why it seemed odd to me that he would do it. It's also kind of insecure since editors can create backups with the file contents in other locations.
Also, get rekt frickr, I was right (see
).
>get rekt frickr
Imagine being so pathetic that winning some inconsequential internet argument makes your little clit hard.
>mom anonymous from 4chin hurt my feelings again!
>t. porn addict
YWNBAW
Being obsessed with other men touching their dicks is EXACTLY as pathetic as being a troony
>calling someone a troony is EXACTLY as pathetic as being a troony
YWNBAW
>An ssh key is a huge string of numbers and letters, this sort of implies that they typed it out and edited it themselves
idk i'd say its actually pretty realistic
in the show i think they got the key from someone else and he is probably just taking a quick look at it to make sure its a regular ssh key format and not something else
>vim yaonet_key
It didn't occur to you that he may have opened the file to yank the key in perhaps from the clipboard. Are you autistic?
>Borderline psychotic that he types 600
it's faster than what you would type
>vim yaonet_key
He probably copypasted the key text from elsewhere. Seems very plausible.
>chmod 600 yaonet_key
This is completely fine and necessary for OpenSSH to accept the key.
>ssh -i yaonet_key root@thatIP
The command itself is fine, HOWEVER: SSH asks for a password at login. This means that the key was wrong. If the person already knows the password, setting up the key was completely useless.
>ls
It's fine for this to list nothing, especially for the root account since root's home directory is often empty, except for some dotfiles, which aren't shown by ls by default.
>ls /
This command has not been executed yet, note the lack of a prompt below it.
The commands themselves are all reasonable, the SSH key vs. password thing isn't.
>The command itself is fine, HOWEVER: SSH asks for a password at login. This means that the key was wrong. If the person already knows the password, setting up the key was completely useless.
Unless that's part of the plot and the next thing the person says is something along the lines of
>"Something's wrong, the key wasn't used. Someone might've messed with the server. OOPS, why did I type in the password in plaintext to login when there's clearly something suspicious going on?"
But that'd filter 99.9% of the potential audience, so they'll stick with
>"I'm in"
..
..
Another possibility which is probably not possible with any version of OpenSSH I'm familiar with, would be that you can set it to require both key and password for extra security, though you're still passing a plaintext password over an unencrypted channel so I dunno.
Here's the scene for reference: https://youtube.com/watch?v=S8K464ImU0c
They only have the key, no password.
>though you're still passing a plaintext password over an unencrypted channel
No idea what you're referring to with that.
>No idea what you're referring to with that.
An SSH key is an example of a "shared" secret used to open an encrypted (hopefully secure) channel between client and host. When you have a key, every message you send, including the start of it, can be encrypted for security. This is one of the reasons why using a key is considered more secure.
When you authenticate with a password instead, there is no established shared secret, so the initial authentication has to be done unencrypted. Otherwise, the server has no means of decrypting the encrypted gibberish you send. Once authenticated, a shared secret is generated and used to encrypt all future communication between server and client. But you still had to send that password in plaintext.
But yeah, you point out that they don't have a password, so the image is wrong.
What do you think SSH host keys are? Passwords aren't sent unencrypted over SSH, holy shit. The channel isn't necessarily secure unless you actually verify that key to be the right one, but it sure as hell isn't unencrypted.
>this sort of implies that they typed it out and edited it themselves
I reviewed the scene and in fact they do exactly that. They lose the key because one of them sperged out, but another autist somehow managed to remember the entire key sequence, so he recites it as yet another guy types it into vim.
yeah and it actually made sense because they used a shorter ed25519 key
whoever did technical consulting for the series did an amazing job
>This hides the key from other users on the system.
A private key must have these permission otherwise it won't be accepted by the ssh client.
Here because you morons are all dancing around this stupid scene and morons like
and many more are arguing over this scene.
what film/series is this?
Silicon Valley
https://www.imdb.com/title/tt2575988/
chmod octal file – change the permissions of file
to octal, which can be found separately for user,
group, and world by adding:
● 4 – read (r)
● 2 – write (w)
● 1 – execute (x)
add these values for permissions you want to set, the sums arrayed left to right for user,group, and others, in that order.
Data file in a shared directory, everyone is able to modify: a+rw-x 0666 -rw-rw-rw-
Data file which anyone can read, but only owner can modify: a+r,u+w,go-wx 0644 -rw-r--r--
Data file which anyone can read, which shouldn't get changed: a+r-wx 0444 -r--r--r--
Confidential data: u+rw-x,go-rwx 0600 -rw-------
Confidential data that shouldn't get modified: u+r-wx,go-rwx 0400 -r--------
Executable program which everyone can use: a+rx,u+w,go-w 0755 -rwxr-xr-x
Secret program: u+rwx,go-rwx 0700 -rwx------
info "(coreutils)Mode Structure" # More details
stat -c '%A %a %n' /* # List files/folders in current directory by symbolic and octal chmod mode, and filename.
I miss Silicon Valley. The dream in S1 was alive. I like to think Mike Judge uses 'Heavy Makeup' for the next iteration's opening.
To complete on the previous answers, I'll mention that the IP can't possibly exist because of the 264. IP4 uses four bytes, so each of the values must be between 0 and 255.
It's most probably intentionally incorrect though, to stop wannabe hackers from trying to ssh into a real IP.
>not using umask
heh
Why not. His key didnt work so he used password