SOCKS proxy and data encryption while browsing website, how much privacy?

[postcd]

When i set proxy in web browser (FF, Chrome) and select SOCKS4 or SOCKS5 as a type.
And it will work (websites will open)...
PS: im using SSH proxy where i run this command on proxy server: ssh -f -N -D 0.0.0.0: portnumberhere localhost

1) then it means i can be sure that all data i submit on websites (web forms) are transfered encrypted/non readable?

2) What if i visit some HTTP webpage where are texts which represent some sensitive data like passwords. They are visible on that page. Can anyone on the way between server and my computer know these data in plain text or even those are encrypted?

3) Then another level. What about website URLs i visit, are they known to anyone on the way between me and server (example ISP) or they are unknown? Again assuming im using proxy the way described in the first paragraph of this topic.

Thank you alot

 

[beers]

Despite the 'Secure' portion of the name, SOCKS doesn't offer any encryption by itself.

 

[postcd]

Despite the 'Secure' portion of the name, SOCKS doesn't offer any encryption by itself.

Thank You, im using remote Linux server as the proxy. And i run this command to create proxy:

ssh -f -N -D 0.0.0.0:ortnumberhere localhost

then i set that server IP and port in my web browser and it works when socks5 checked.

So while it is SSH, can you please answer accordingly my initial questions (in case you know SSH)? Thank you alot

 

[beers]

Then that's tunneling over SSH instead of just SOCKS like you had outlined

1) You'd then have the same data protection as the SSH session, which may vary depending on the cipher used etc.
2) From you to your SSH endpoint will be encrypted, from your endpoint to the server would be cleartext.
3) The server would see the path back to your proxy server. Depending on the proxy headers the server may or may not be aware of the proxy.

 

[postcd]

1) You'd then have the same data protection as the SSH session, which may vary depending on the cipher used etc.

I found this in SSH output:
debug1: kex: server->client aes128-ctr hmac-md5 none
debug2: mac_setup: found hmac-md5
debug1: kex: client->server aes128-ctr hmac-md5 none
...
So does it mean "i can be sure that all data i submit on websites (web forms) are transfered encrypted/non readable?"

2) From you to your SSH endpoint will be encrypted, from your endpoint to the server would be cleartext.

So from proxy to my computer, no one can read plain text contents/source code of some http:// webpage which i open? Only if someone is between proxy and destination webserver?

3) The server would see the path back to your proxy server. Depending on the proxy headers the server may or may not be aware of the proxy.

so the website URLs i visit are unknown to anyone (even my ISP) between me and proxy server? Only are known to anyone between proxy and webserver?

Such SSH proxy then encrypt whole data flow from my OS to OS of my remote proxy server?

 

[beers]

Such SSH proxy then encrypt whole data flow from my OS to OS of my remote proxy server?

Yes, outside of that if you're using standard HTTP it's going to be clear text back over the internet to your destination.

 

[postcd]

Yes, outside of that if you're using standard HTTP it's going to be clear text back over the internet to your destination.

Yes, but that is not case when im opening HTTP webpage via mentioned proxy right?
Im still unsure as you did not responded to all my questions in previous post of mine, but thank you for your time.

 

[beers]

Yes, but that is not case when im opening HTTP webpage via mentioned proxy right?

Encrypted to proxy server, not encrypted from proxy server to destination server. If it's sensitive data like passwords you're still at risk of it being captured if you're using standard HTTP on port 80. Also, a lot of proxy configurations will tell the remote server that the data's been proxied and also give a 'forwarded for' address that points back to you.

Im still unsure as you did not responded to all my questions in previous post of mine, but thank you for your time.

It's pretty straightforward, data to proxy server secured by SSH. If the protocol is insecure then from the proxy to the destination will be cleartext.