SSH forwarding saves the day!
Jan. 3rd, 2007 09:27 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
I totally forgot that I could do that until this morning. :P
So... A SSH connection into b with a port-forwarding (tunnel) mapping of local port: 8995 remote port: pop.gmail.com:995 later, I'm able to download all my emails. Even the monster 11 MB one and two other emails that contained singing drafts. ^^;;
The only problem is that this, of course, sort of defeats the value of SSL, since now the CN (complete name) in Google's server certificate doesn't match what was passed in (the local cert + tunnel). But since I trust
testing4l, that's not a major issue at the moment. Also, this is only meant to be a temporary solution for me to check my emails (LJ comments, visa/work-related emails, etc.) until connectivity returns to normal.
I haven't investigated whether web access to Gmail could be similarly forwarded, but perhaps it's possible (maybe not over port 80, though).
So... A SSH connection into b with a port-forwarding (tunnel) mapping of local port: 8995 remote port: pop.gmail.com:995 later, I'm able to download all my emails. Even the monster 11 MB one and two other emails that contained singing drafts. ^^;;
The only problem is that this, of course, sort of defeats the value of SSL, since now the CN (complete name) in Google's server certificate doesn't match what was passed in (the local cert + tunnel). But since I trust
![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
I haven't investigated whether web access to Gmail could be similarly forwarded, but perhaps it's possible (maybe not over port 80, though).