Most box fans are about 19" wide. This fact came in handy years ago when I worked at an ISP. Our Ascend boxes (in an otherwise frigid data center) kept overheating, so we wire-tied a box fan to the front of the rack. Worked like a charm.
The only reason the BLM is calling for this freeze is because they are incompetent government nabobs. They cannot deal with the paperwork, so they are panicking and forcing a freeze in the market
The USPTO coped with a large amount of applications by approving a bunch of crappy applications. This was bad. The BLM is coping with a large amount of applications with a freeze on applications. This is... bad?
The point I'm trying to make is that there is less randomness in IPv6 addressing than most people assume. Problems that start out "prohibitive" (such as DES/WEP cracking and MD5 collisions) tend to become less so over time.
I see this "IPv6 will make scanning too hard" idea presented each time IPv6 is discussed on Slashdot. This goes against pretty much all experience I've had with telephony, cable, and ISP provisioning -- when addresses are doled out, they're doled out in evenly-spaced, predictable sequences. It also assumes that the state of the art in scanning technology won't advance.
When IPv6 does see widespread deployment I'd be interested to see how soon address space scanning optimization papers start showing up (if they haven't already).
Why not build your own? Old PPCs, SPARCs, Alphas, and Intels are cheap on eBay. The software to create your own compile farm is readily available (and in the case of Buildbot, decentralized).
Having your own farm means you don't compete for resources, and you're not beholden to some assh^W other organization's business case for shutting it down.
For my purposes, I don't care how much market share a particular platform has. Having a diverse build farm is useful for testing. Solaris will flag errors that Linux won't, and vice-versa. MSVC++ and gcc generate warnings for different problems. SPARC, PPC, Alpha, and Itanium processors catch things (particularly alignment errors) that x86 won't.
Samir: Hmm... well why don't you just go by Mike instead of Michael? Michael Bolton: No way. Why should I change? He's the one who sucks.
More seriously, false positives are usually due to a definition file that comes out well _after_ the software has been released. Testing beforehand won't accomplish anything at the expense of paying N dollars per year to multiple antivirus vendors.
In this particular case, it looks like WinPcap is being flagged. It came out on Jan 29th, and we started getting reports about 10 days later.
Slashdot Mirror
Not publicly. My experience has been:
1) Notice (or be notified of) a copyright or trademark offense.
2) Try to contact the company.
3) Get a reply from person 1 who:
a) Doesn't have the power to fix anything.
and/or
b) Doesn't care.
4) Go back and forth with person 1 for a few months.
5) Deal with person 2..n who:
a) Took over for person n-1 when they:
i) Quit.
ii) Went on vacation or maternity leave.
b) Is person n-1's supervisor or someone from a completely different department in another time zone (and who can't change anything or doesn't care).
This goes on for several months until I send an angry certified letter to the president of the company or hand the matter over to my lawyer.
It's quite possible that Psion are a gaggle of jerks. It's also possible that they've been trying to get this resolved privately with no joy.
...forestation rates have been on the rise in North America for over 100 years.
What about the rates over the last 200 years? 100 years ago was shortly after the railroads deforested the nation, was it not?
It's been 7000 years and the WHEEL still comes in just ONE SHAPE? WTF?
Two.
When do I get to DRM my medical and financial records? Or does this still only restrict consumers?
Most box fans are about 19" wide. This fact came in handy years ago when I worked at an ISP. Our Ascend boxes (in an otherwise frigid data center) kept overheating, so we wire-tied a box fan to the front of the rack. Worked like a charm.
Is something a meme if it predates the word "meme"?
You forgot 'lsof -o'.
The only reason the BLM is calling for this freeze is because they are incompetent government nabobs. They cannot deal with the paperwork, so they are panicking and forcing a freeze in the market
The USPTO coped with a large amount of applications by approving a bunch of crappy applications. This was bad. The BLM is coping with a large amount of applications with a freeze on applications. This is ... bad?
My first thought wasn't priceless. It was "eeewwwww!" I have no idea what an entire nation might secrete, and I don't want to know.
I used to use this one.
A better name would have been "drunken traveling salesman."
You can add Wireshark to the list.
In the traces I've seen the RSTs come in pairs, with the sequence numbers differing by 12503.
Song Artist Amazon ITMS
Genius of Love Tom Tom Club No Yes
Can we have a UTF-8 cutover day, too?
The point I'm trying to make is that there is less randomness in IPv6 addressing than most people assume. Problems that start out "prohibitive" (such as DES/WEP cracking and MD5 collisions) tend to become less so over time.
I see this "IPv6 will make scanning too hard" idea presented each time IPv6 is discussed on Slashdot. This goes against pretty much all experience I've had with telephony, cable, and ISP provisioning -- when addresses are doled out, they're doled out in evenly-spaced, predictable sequences. It also assumes that the state of the art in scanning technology won't advance.
When IPv6 does see widespread deployment I'd be interested to see how soon address space scanning optimization papers start showing up (if they haven't already).
How is DSL not shared? Do you think you're the only one using the backplane bandwidth of your DSLAM?
Why not build your own? Old PPCs, SPARCs, Alphas, and Intels are cheap on eBay. The software to create your own compile farm is readily available (and in the case of Buildbot, decentralized).
Having your own farm means you don't compete for resources, and you're not beholden to some assh^W other organization's business case for shutting it down.
For my purposes, I don't care how much market share a particular platform has. Having a diverse build farm is useful for testing. Solaris will flag errors that Linux won't, and vice-versa. MSVC++ and gcc generate warnings for different problems. SPARC, PPC, Alpha, and Itanium processors catch things (particularly alignment errors) that x86 won't.
Front crank? Did you buy a tandem?
Samir: Hmm... well why don't you just go by Mike instead of Michael?
Michael Bolton: No way. Why should I change? He's the one who sucks.
More seriously, false positives are usually due to a definition file that comes out well _after_ the software has been released. Testing beforehand won't accomplish anything at the expense of paying N dollars per year to multiple antivirus vendors.
In this particular case, it looks like WinPcap is being flagged. It came out on Jan 29th, and we started getting reports about 10 days later.
...then why do you have a spokesperson?
The "cool" one.
I'd pay good money for a DeWALT laptop, even if it was a rebranded toughbook.