o: <[EMAIL PROTECTED]> |
|cc:
|
| Subject: Re:
If that's the case, why not right Jerry Fallwell a letter about
Verisign's unchristian activities, and get the bible belt on their ass?
I'd like to see them respond to a camera crew and evangelist asking
them:
"Exactly why do I see a verisign ad when I visit ___"
Fill _ with:
v
| If Verisign are stupid enough to do this, let's make sure
| they get ALL the traffic :-).
The idea was to keep them from getting paid. No web hits = no clicks on
sponsored links.
| Also port 80 isn't the biggest problem: think mail think
| what happens if something returns legal DNS entr
05-14
OrgTechHandle: EB637-ARIN
OrgTechName: Bonner, Eric
OrgTechPhone: +1-912-527-4306
OrgTechEmail: [EMAIL PROTECTED]
- Original Message -
From: "Adam D. Barratt" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 17, 2003 6:53 AM
Subject: Re: [SAt
Giles Coochey wrote, Wednesday, September 17, 2003 10:50 AM
> Don't do that!
Why not?
> gate# host sitefinder.verisign.com
> sitefinder.verisign.com has address 12.158.80.10
That's rather irrelevant - 64.94.110.11 never was the address of sitefinder.
It is, however, the IP returned by the wildc
ECTED]
Subject: Re: [SAtalk] Re: The Verisign folly
On Tue, Sep 16, 2003 at 10:26:50PM -0700 Steve Thomas wrote :
> router(config)# access-list 101 deny tcp any host 64.94.110.11 eq 80
Don't do this.
If Verisign are stupid enough to do this, let's make sure they get ALL the
traffic :-).
On Tue, Sep 16, 2003 at 10:26:50PM -0700 Steve Thomas wrote :
> router(config)# access-list 101 deny tcp any host 64.94.110.11 eq 80
Don't do this.
If Verisign are stupid enough to do this, let's make sure they get ALL the
traffic :-).
Also port 80 isn't the biggest problem: think mail thin
On Tue, Sep 16, 2003 at 12:36:01PM -0500, Rich Puhek is rumored to have said:
>
> We haven't null-routed it, nor have our upstream providers. Traceroute
> goes through fine, pings die, webpages don't come up.
router(config)# access-list 101 deny tcp any host 64.94.110.11 eq 80
:)
The pings cou
Lance A. Brown wrote:
On Tue, 2003-09-16 at 13:03, Rich Puhek wrote:
On a side note, the tactic appears to have backfired... 64.94.110.11
appears to be unpingable, and If I try typing a "made-up" domain into a
browser, the page times out. Perhaps Verisign is suffering the /. effect?
Several
On Tue, 2003-09-16 at 13:03, Rich Puhek wrote:
> On a side note, the tactic appears to have backfired... 64.94.110.11
> appears to be unpingable, and If I try typing a "made-up" domain into a
> browser, the page times out. Perhaps Verisign is suffering the /. effect?
Several ISPs have null-rout
10 matches
Mail list logo
