Timeline for Does a TLS-connection to a proxy-server encrypt the destination url's?
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 21, 2015 at 11:26 | vote | accept | ispiro | ||
| May 14, 2015 at 21:27 | comment | added | Steffen Ullrich | @ispiro: I was not aware of this functionality. But see my edited response. | |
| May 14, 2015 at 21:26 | history | edited | Steffen Ullrich | CC BY-SA 3.0 |
added 650 characters in body
|
| May 14, 2015 at 21:19 | comment | added | ispiro |
@SteffenUllrich a) Thanks. b) According to this answer it does. (See "Supported in FF 33+" on that answer.) (I haven't used a proxy yet. This is a preliminary question.) c) If you don't add the @ispiro before your comment, I don't get notified of it.
|
|
| May 14, 2015 at 21:13 | comment | added | Steffen Ullrich | Are you sure that Firefox supports speaking to a proxy with TLS? I doubt it. Did you try? I'm also not aware of any proxy implementation which supports speaking TLS to it. | |
| May 14, 2015 at 21:09 | comment | added | ispiro | I've edited the question to make it clear that I'm asking about a case where the connection to the proxy is secure. | |
| May 14, 2015 at 20:44 | history | edited | Steffen Ullrich | CC BY-SA 3.0 |
added 32 characters in body
|
| May 14, 2015 at 20:39 | history | edited | Steffen Ullrich | CC BY-SA 3.0 |
added 32 characters in body
|
| May 14, 2015 at 20:35 | comment | added | Steffen Ullrich | The idea of TLS is to have an end-to-end encryption with the target server. The proxy only creates a tunnel (i.e. forward TCP) but does not affect the end-to-end encryption itself. Having TLS only to the proxy is usually not the case, but you might have TLS interception at the proxy in which case you get one TLS connection between client and proxy and another one between proxy and target. | |
| May 14, 2015 at 20:33 | comment | added | Mike Ounsworth | It seems like a confusion point is who the TLS connection is with. If you only have a TLS connection with the server (and not with the proxy), then the server's address or hostname needs to be in the clear. But if you have a secure connection to the proxy (aka vpn?) then it would not. Is that correct? | |
| May 14, 2015 at 20:30 | history | edited | Steffen Ullrich | CC BY-SA 3.0 |
added 135 characters in body; added 66 characters in body
|
| May 14, 2015 at 20:23 | comment | added | Steffen Ullrich | Since the data must somehow reach the target and routing is done by IP address the IP address need to be known. And no, I'm talking about HTTP proxy connections (CONNECT method) where either the targets hostname is contained in the request and the proxy resolves it to get the target IP or the targets IP is included in the request. | |
| May 14, 2015 at 20:22 | comment | added | ispiro | It looks like you're answering about a regular TLS connection. That's not my question. I'm asking about when browsing is done through a proxy-server. | |
| May 14, 2015 at 20:21 | comment | added | ispiro |
ISP at least would know the target IP address, because this is needed to route your data to the target - I don't understand. Are you referring to the proxy's IP? If not - why would the ISP need to know the IP?
|
|
| May 14, 2015 at 20:19 | history | answered | Steffen Ullrich | CC BY-SA 3.0 |