[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #8319 [Flashproxy]: Check if flashproxy-client.exe works on Windows XP
#8319: Check if flashproxy-client.exe works on Windows XP
------------------------+---------------------------------------------------
Reporter: dcf | Owner: dcf
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: Flashproxy | Version:
Keywords: | Parent:
Points: | Actualpoints:
------------------------+---------------------------------------------------
Comment(by dcf):
Replying to [comment:9 kenwoo]:
> Abour email method, actually my hosts file has many lines about google
mail server.
> (173.194.79.108 gmail-imap.l.google.com
> 173.194.79.108 gmail-pop.l.google.com
> 173.194.79.108 gmail-smtp.l.google.com
> 173.194.79.108 gmail-smtp-in.l.google.com
> 173.194.79.108 gmail-smtp-msa.l.google.com
> 173.194.79.108 gmr-smtp-in.l.google.com
> 173.194.79.108 googlemail-imap.l.google.com
> 173.194.79.108 googlemail-pop.l.google.com
> 173.194.79.108 googlemail-smtp.l.google.com
> 173.194.79.108 imap.gmail.com
> 173.194.79.108 pop.gmail.com
> 173.194.79.108 smtp.gmail.com
> 173.194.79.108 imap.googlemail.com
> 173.194.79.108 pop.googlemail.com
> 173.194.79.108 smtp.googlemail.com
> 173.194.79.108 smtp1.google.com
> 173.194.79.108 smtp3.google.com
> 173.194.79.108 smtp-out.google.com
> 173.194.79.108 smtp-out3.google.com
> 173.194.79.108 mail-attachment.googleusercontent.com
> 173.194.79.108 gmail-smtp-in.l.google.com
> 173.194.79.108 alt1.gmail-smtp-in.l.google.com
> 173.194.79.108 alt2.gmail-smtp-in.l.google.com
> 173.194.79.108 alt3.gmail-smtp-in.l.google.com
> 173.194.79.108 alt4.gmail-smtp-in.l.google.com)
> But email method is not working.
>
> 2013-02-24 15:40:44 flashproxy-reg-email: Failed to register: Public key
does not match pin: got a5ba9523f2dc350a51ef72d87d1c3ad3cbaf12ce but
expected 1926a5cb3fd7e48328188946e73ade84f55787dc
> 2013-02-24 15:40:44 flashproxy-reg-email exited with status 1.
For me, smtp.gmail.com and gmail-smtp-in.l.google.com have different IP
addresses. It is probably not correct to use 173.194.79.108 for gmail-
smtp-in.l.google.com. That is why you are seeing a certificate pinning
failure. These are the IP addresses I have.
{{{
smtp.gmail.com. 158 IN CNAME gmail-smtp-
msa.l.google.com.
gmail-smtp-msa.l.google.com. 49 IN A 74.125.25.109
gmail-smtp-msa.l.google.com. 49 IN A 74.125.25.108
gmail-smtp-in.l.google.com. 267 IN A 74.125.25.27
}}}
You might try 74.125.25.27 for the address.
I get the same pinning failure if I run the command
{{{
./flashproxy-reg-email --smtp smtp.gmail.com
Failed to register: Public key does not match pin: got
a5ba9523f2dc350a51ef72d87d1c3ad3cbaf12ce but expected
1926a5cb3fd7e48328188946e73ade84f55787dc
}}}
Therefore I think the problem is that you are communicating with the wrong
server.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/8319#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs