You should read it and understand it sometime. Again, tunneling doesn't require SSH, which stands for Secure SHell, a CLI protocol layered on top of a secure transport layer such as Secure Socket Layer (SSL), or Transport Security Layer (TLS). Off you go now moron...
Nice anecdote. It is 2017 and a lot of us don't live with our parents anymore. It is *extremely* common for people to want to know what is involved in it in 2017. Haven't you heard? Anyone can do it. It should be taught in elementary school!
I don't have a horse in this race, but don't conflate Messenger with email or text. The latter methods don't guarantee delivery or provide handshaking (we call those "connectionless").
The guy who has designed computers, written operating systems, knows that "I'm a firmware programmer" gives you no clout with regard to the current subject matter, and is laughing at your attempt to assert authority in a domain that has nothing to do with firmware programming. Why do you ask?
Right. Thats what I just said. The sH is for shell, i.e. CLI. Tunelling happens at the SSL/TLS layer. SSH is a protocol that leverages SSL (old school) or TLS (new school) to perform the tunneling.
It's a language for interfacing to computers dumbfuck. There isn't a single *computer* language on the planet that is designed to be understood by humans that computers just happen to understand. You truly are a fucking moron (waves hand with middle finger raised)
You should probably read the summary, which talks about the protocols the Microsoft version does and doesn't support. You should probably get a basic level of education on why open*SSL* was required by OpenSSH until 2014.
Don't confuse SSH with SSL. SSH is Secure Shell, which establishes an SSL connection for shells. Tunelling is done with SSL, though it is often done through the SSH tools. What is called *SSH* tunelling is actually just SSL tunelling over the SSH port.
OpenSSH hasn't required OpenSSL since 2014. Of course that doesn't mean it is a good idea to just use any old SSL lib, and Microsoft has a long history of being unable to do encryption right going back at least to LANMAN incompetence, so you would be an incompetent fool to trust this implementation.
Slashdot Mirror
You realize it is 2017 now, and that has been a concern for more than 20 years, right?
I didn't advocate for anything. I merely stated a fact.
Yes. You should select the option to place one on the Desktop next time you install it.
Go fuck yourself loser.
It doesn't implement encryption algorithms. It is a layer above them.
No, it means there are more idiots like you who think they know what it is.
You should read it and understand it sometime. Again, tunneling doesn't require SSH, which stands for Secure SHell , a CLI protocol layered on top of a secure transport layer such as Secure Socket Layer (SSL), or Transport Security Layer (TLS). Off you go now moron ...
Nice anecdote. It is 2017 and a lot of us don't live with our parents anymore. It is *extremely* common for people to want to know what is involved in it in 2017. Haven't you heard? Anyone can do it. It should be taught in elementary school!
Yeah. I wouldn't log in either if I were you.
I don't have a horse in this race, but don't conflate Messenger with email or text. The latter methods don't guarantee delivery or provide handshaking (we call those "connectionless").
Facebook isn't a force, it is a tool
Great. Now would be a good time to educate yourself. Your apology is accepted.
I logged in. You are an AC following up on your post with misinformation. See the difference?
If it says it on a blog it must be true!
The guy who has designed computers, written operating systems, knows that "I'm a firmware programmer" gives you no clout with regard to the current subject matter, and is laughing at your attempt to assert authority in a domain that has nothing to do with firmware programming. Why do you ask?
more often than not SSH uses SSL under the hood ... The rest of the time it uses TLS. I hope you decide to educate yourself someday!
It is definitely a fact that you are no expert on the subject. Thanks for making that super double clear though!
You are the moron. Thanks for asking.
Right. Thats what I just said. The sH is for shell, i.e. CLI. Tunelling happens at the SSL/TLS layer. SSH is a protocol that leverages SSL (old school) or TLS (new school) to perform the tunneling.
Oh really? Then tell us, where are the specs for the SSH encryption mechanism?
It's a language for interfacing to computers dumbfuck. There isn't a single *computer* language on the planet that is designed to be understood by humans that computers just happen to understand. You truly are a fucking moron (waves hand with middle finger raised)
You should probably read the summary, which talks about the protocols the Microsoft version does and doesn't support. You should probably get a basic level of education on why open*SSL* was required by OpenSSH until 2014.
Don't confuse SSH with SSL. SSH is Secure Shell, which establishes an SSL connection for shells. Tunelling is done with SSL, though it is often done through the SSH tools. What is called *SSH* tunelling is actually just SSL tunelling over the SSH port.
OpenSSH hasn't required OpenSSL since 2014. Of course that doesn't mean it is a good idea to just use any old SSL lib, and Microsoft has a long history of being unable to do encryption right going back at least to LANMAN incompetence, so you would be an incompetent fool to trust this implementation.
One double clicks on the PuTTY icon.