One thing that the scanner vendors often say when confronted by privacy zealots is "Come on! It is impossible to reconstruct a real fingerprint from the stuff we scan, so your police-state fears are mathematically impossible."
Turns out this is untrue
The worst thing about the GPL is it is from the same folks who brought the world Emacs. The BSD licencse, to its credit, is from the people who brought us vi, a vastly superior editor.:^)
It may have been known abt since 5/22, sure. But how long was this "script" running undetected on CardSystems' equipment?
Two possibilities spring to mind immediately (and of course others are possible as well):
1. An insider did this. 2. Unpatched boxes were subverted and this really is a break-in.
Either way, these folks had unauthorized, undetected code running and snarfing up some of their most critical data. That isn't good for the company image. Moreover, we *know* that the snarfed data made its way out of the organization (i.e., it wasn't just being dumped to a file which somebody found), because this was only detected when it caused SOMEBODY ELSE"S fraud detection systems to trigger. This is bad. Somebody got evil code in. Somebody got evil code to run undetected. Somebody got evil code to transmit data out (or did the data walk out in an employee's iPod? Hmmmm....).
MasterCard dropped this bomb for a reason. The press (I'm looking at you, Bob Sullivan) needs to be asking the right questions.
First to support your hardware, eh? Well, you must have some spankin' new HW. UNIX (!= Linux) has been available for the i386 for a hell of a long time. Think NET2. Think BSDI. If it wasn't for the efforts of folks you are dissing with your "End of Discussion" claptrap, UNIX would still be encumbered, and your HW would be a boat anchor or a Winblows box.
"right-to-work" doesn't have anything to do with giving notice, or with some legally-required advance warning of impending dismissal. It simply means that employees cannot be required to join/be members of a union in order to work at a given place. It is the opposite of "closed shop", in other words.
The term typically used to describe "we can fire you anytime, for any reason" and "you can quit whenever you want, for whatever reason" is 'employment at will'.
The client-side portion of the architecture aggressively prefetches content. It's a two-stage proxy, really, and the issue some people have with it is that the content in the portion on the end-user's hard drive is not content that the user asked for, but content that the proxy predicts the user will soon ask for.
Theo talks about how OpenBSD uses various available processor features to increase system attack resilience, w/minimal performance impact. The design choices made for architectures with differing degrees of per-page protection are presented. The concepts are not at all OpenBSD-specific, although the implementation discussed is, of course, OpenBSD.
This is one of those great things, like the SMTP protocol, which work great in one environment, but become absolute nightmares in another, less friendly one. Difference is, the folks who came up with this feature should have known that today's network environment makes a feature like this stupid to the extreme. I guess it was just too cool not to put in. Sigh.
The flag code does not criminalize anything. This is left to the states, and many have laws criminalizing 'flag abuse'.
From the U.S. Flag Code:
Criminal penalties for certain acts of desecration to the flag were contained in Title 18 of the United States Code prior to 1989. The Supreme Court decision in Texas v. Johnson; June 21, 1989, held the statute unconstitutional. This statute was amended when the Flag Protection Act of 1989 (Oct. 28, 1989) imposed a fine and/or up to 1 year in prison for knowingly mutilating, defacing, physically defiling, maintaining on the floor or trampling upon any flag of the United States. The Flag Protection Act of 1989 was struck down by the Supreme Court decision, United States vs. Eichman, decided on June 11, 1990.
Of course the state laws are of dubious constitutionality;^)
Sorry to have submitted a dupe. I don't read the NYT, and I saw this via a somewhat esoteric web site, and when it wasn't up on today's/. already, I figured it hadn't been submitted. My bad for not reading/. yesterday;^).
Anyway, the obvious thing to do is see what domain names Avi and cohorts have registered recently, to see what they will obliterate next.
If this guy hooks up with Matt "Locksmiths ph33r my 7eet sk1llz" Blaze (linkage) it will be rather amusing.
On a serious note, why don't these firms just hire Avi, Ross Anderson, or Markus Kuhn up front, and save embarrassment and retooling?
Slashdot Mirror
but keeping a veg alive *in NJ* should be called "reaching Quinlan status". Prior art, one might say.
1st?
"It is no secret that two species who would not produce viable offspring together will try to avoid mating with each other."
I guess my couch is of the same species as my dog.
is still dead.
Back to you, Jane.
They're all hanging at the ren faire with the rest of the SCA contingent.
One thing that the scanner vendors often say when confronted by privacy zealots is "Come on! It is impossible to reconstruct a real fingerprint from the stuff we scan, so your police-state fears are mathematically impossible." Turns out this is untrue
"shutdown"? Don't molly-coddle 'em.
# kill -9 1
The worst thing about the GPL is it is from the same folks who brought the world Emacs. The BSD licencse, to its credit, is from the people who brought us vi, a vastly superior editor. :^)
It may have been known abt since 5/22, sure. But how long was this "script" running undetected on CardSystems' equipment?
Two possibilities spring to mind immediately (and of course others are possible as well):
1. An insider did this.
2. Unpatched boxes were subverted and this really is a break-in.
Either way, these folks had unauthorized, undetected code running and snarfing up some of their most critical data. That isn't good for the company image. Moreover, we *know* that the snarfed data made its way out of the organization (i.e., it wasn't just being dumped to a file which somebody found), because this was only detected when it caused SOMEBODY ELSE"S fraud detection systems to trigger. This is bad. Somebody got evil code in. Somebody got evil code to run undetected. Somebody got evil code to transmit data out (or did the data walk out in an employee's iPod? Hmmmm....).
MasterCard dropped this bomb for a reason. The press (I'm looking at you, Bob Sullivan) needs to be asking the right questions.
First to support your hardware, eh? Well, you must have some spankin' new HW. UNIX (!= Linux) has been available for the i386 for a hell of a long time. Think NET2. Think BSDI. If it wasn't for the efforts of folks you are dissing with your "End of Discussion" claptrap, UNIX would still be encumbered, and your HW would be a boat anchor or a Winblows box.
I, for one, welcome our new MacIntel overlords.
Arrrgh! This is what I get for not scrolling down far enough.
Was kremvax affected?
If someone fled a freedom-hating, oppressive nation and obtained citizenship in the West, they were considered heroic.
Now, if they do the same thing, we keep a close eye on them, because their place or birth makes them inherently untrustworthy.
Nice.
Ross Anderson and colleagues present a great deal of information on what chip and pin does and doesn't do at http://www.chipandspin.co.uk/
A quick definition or two:
"right-to-work" doesn't have anything to do with giving notice, or with some legally-required advance warning of impending dismissal. It simply means that employees cannot be required to join/be members of a union in order to work at a given place. It is the opposite of "closed shop", in other words.
The term typically used to describe "we can fire you anytime, for any reason" and "you can quit whenever you want, for whatever reason" is 'employment at will'.
It is more than a caching proxy.
The client-side portion of the architecture aggressively prefetches content. It's a two-stage proxy, really, and the issue some people have with it is that the content in the portion on the end-user's hard drive is not content that the user asked for, but content that the proxy predicts the user will soon ask for.
http://cvs.openbsd.org/papers/auug04/
Theo talks about how OpenBSD uses various available processor features to increase system attack resilience, w/minimal performance impact. The design choices made for architectures with differing degrees of per-page protection are presented. The concepts are not at all OpenBSD-specific, although the implementation discussed is, of course, OpenBSD.
" He's complaining about people who think there is some big cooperation between Apple and KDE when there really isn't."
Complaining about idiots never works.
This is one of those great things, like the SMTP protocol, which work great in one environment, but become absolute nightmares in another, less friendly one. Difference is, the folks who came up with this feature should have known that today's network environment makes a feature like this stupid to the extreme. I guess it was just too cool not to put in. Sigh.
Why don't you show them a computer animation of somebody cool, like an astronaut, firefighter, or football player?
Hey all --
/. already, I figured it hadn't been submitted. My bad for not reading /. yesterday ;^).
Sorry to have submitted a dupe. I don't read the NYT, and I saw this via a somewhat esoteric web site, and when it wasn't up on today's
Anyway, the obvious thing to do is see what domain names Avi and cohorts have registered recently, to see what they will obliterate next.
If this guy hooks up with Matt "Locksmiths ph33r my 7eet sk1llz" Blaze (linkage) it will be rather amusing.
On a serious note, why don't these firms just hire Avi, Ross Anderson, or Markus Kuhn up front, and save embarrassment and retooling?