full-disclosure - Re: Gmail and China's GFW

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <ECEB3944-BC42-476E-AADE-F00824D0DDBF@gmail.com>
Date: Mon, 21 Mar 2011 17:09:05 -0700
From: bk <chort0@...il.com>
To: nix@...roxylists.com, Full Disclosure <full-disclosure@...ts.grok.org.uk>
Subject: Re: Gmail and China's GFW


On Mar 21, 2011, at 4:53 PM, nix@...roxylists.com wrote:
>>> 
>>> Try it, you will get a connection timeout:
>>> 
>>> $ curl --connect-timeout 60 https://mail.google.com/
>>> curl: (28) SSL connection timeout
>>> 
>>> The same applies for Twitter, Facebook... Much more efficient than
>>> DNS/IP blocking!
>>> 
>> 
>> Thanks for the information. I was not actually aware of that you can block
>> with iptables using hex strings. Very nice.
>> 
> 
> Forgot to say, in terms of performance. It's better to use -j REJECT
> instead of DROP (then no timeout is caused and the connection is rejected
> with ICMP destination unreachable.
> 

Not if you want it to look like a problem with Google's infrastructure rather than an active block where initiator can see the source of the ICMP datagrams.

--
chort

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/