North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: FBI tells the public to call their ISP for help

  • From: Fred Baker
  • Date: Fri Jun 15 16:33:28 2007
  • Authentication-results: sj-dkim-3; [email protected]; dkim=pass (si g from cisco.com/sjdkim3002 verified; );
  • Dkim-signature: v=0.5; a=rsa-sha256; q=dns/txt; l=787; t=1181939464; x=1182803464; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; [email protected]; z=From:=20Fred=20Baker=20<[email protected]> |Subject:=20Re=3A=20FBI=20tells=20the=20public=20to=20call=20their=20ISP= 20for=20help |Sender:=20; bh=k/B+4ZVRdqC2uffkEPFOES2/2oKsPZip/6VgcOj5YJc=; b=QX/Mg2dmzLb0mG7doBQ5hFFSKXzkZbYa7iretWr4Y8UA4x1qaftc5OGAle6RFoGpKehvUiCI 7ZGe6KpG9D61qyUbnGWILYES1Ls63YLKz1p4ptgp1zS+0T2fnstD21U4;


On Jun 15, 2007, at 1:23 PM, Kevin Day wrote:

I've never tried it, but I've heard that they've been surprisingly helpful, even in cases where it was obviously not Microsoft's fault (directly, anyway). I'm not 100% positive that their policy explicitly allows OEM license holders to use that number, but from those I've talked to that have used it - they don't ask for any license information at all. After they've verified it fits their definition of a security problem, you're handed over to a tech to help you clean it up.

It is my understanding that they even support pirated software in this context; they figure it's better to fix the stuff and then figure out how to get the right stuff there than to wenge about its pedigree.