Check numbers are incrimental and of limited permutation, again making the hash easy to brute force. If the hash changes with each check, it also becomes harder for retailers to identify bad checks based on account number. You're going to end up turning away legitimate customers money, and gain no security. By the time the check hits the bank, the fraud has been done. Also, "once extracted is verified to the name printed on the check"? Depending on your bank, this is already done. I signed a check with my right hand instead of left once(couldn't hold the pen because I messed my hand up), and I got a call a few days later about it. I'm with WaMu.
Given that a one way hash can't really be reversed, that idea doesn't make much sense in the way that you posted it. A one way hash at first makes sense, except in reality it doesn't, as currently deployed. The numbers on your check have a routing number and account number. Both are numeric values with relatively few permutations when contrasted against case sensitive alphanumeric hashing. The routing numbers of banks are also no secret. Put simply, it'd be a trivial matter to brute force the hash with the simple numeric values we use today.
Why the hell did you link to a slideshow? That site's slow as hell for me(rest of the net's fine), and the images weren't even loaded by the time it decided it was time to switch slides. The net isn't meant to be like a powerpoint presentation. Worse was the fact that adblock caught the "pause" button.
The "binary explosive" plot involved TATP, triacetone triperoxide. Synthesis of AP requires time, ventilation, and an ice bath. The precipitate is NOT a liquid, it is a crystaline organic peroxide.
Correct. Someone would likely notice the throughput on the fiber doubling, and it makes little sense anyway. Just forward the conversations/packets you're interested in on the already existing fiber.
You don't need 4 more cables, just inject select data into the already laid fiber. It's been demonstrated(AT&T) that you can do DPI on high-throughput fiber links, it's not that difficult to remote into whatever box you dropped off into the bottom of the ocean.
Yes, but that doesn't stop the trolls and karma whores from bringing up an issue that plauged *first generation* flash devices, in order to appear insightful.
This sort of makes sense, and *could* be testable, try to break out of the virtual machine. The question is, if we find a buffer overflow in the universe, what happens if our shellcode causes a BSOD?
I'm rather annoyed with companies these days. Are you fucking Apple? NO!!! Then don't make an iProduct, if not that, then because prepending 'i' infront of 'x word in the dictionary' is fucking stupid in the first place, you consumerist whore.
Not posted AC, bitches.
(last explitive added to spite the lameness filter)
Slashdot Mirror
Er, wpa_supplicant should work just fine regardless of your card....
Check numbers are incrimental and of limited permutation, again making the hash easy to brute force. If the hash changes with each check, it also becomes harder for retailers to identify bad checks based on account number. You're going to end up turning away legitimate customers money, and gain no security. By the time the check hits the bank, the fraud has been done. Also, "once extracted is verified to the name printed on the check"? Depending on your bank, this is already done. I signed a check with my right hand instead of left once(couldn't hold the pen because I messed my hand up), and I got a call a few days later about it. I'm with WaMu.
Given that a one way hash can't really be reversed, that idea doesn't make much sense in the way that you posted it. A one way hash at first makes sense, except in reality it doesn't, as currently deployed. The numbers on your check have a routing number and account number. Both are numeric values with relatively few permutations when contrasted against case sensitive alphanumeric hashing. The routing numbers of banks are also no secret. Put simply, it'd be a trivial matter to brute force the hash with the simple numeric values we use today.
You mean /.?
Why the hell did you link to a slideshow? That site's slow as hell for me(rest of the net's fine), and the images weren't even loaded by the time it decided it was time to switch slides. The net isn't meant to be like a powerpoint presentation. Worse was the fact that adblock caught the "pause" button.
But then where will I hide from the day star? It's trying to kill me, you know.
Is it me, or is everyone's sarcasm meter broken and pointing in the wrong direction? On the plus side, the pessimism meter's working.
That's the Fantastic Four, not Transformers, stupid!
Nobody plans to be #2.
How the hell did this get modded off topic?
The "binary explosive" plot involved TATP, triacetone triperoxide. Synthesis of AP requires time, ventilation, and an ice bath. The precipitate is NOT a liquid, it is a crystaline organic peroxide.
See: http://roguesci.org/chemlab/energetics/acetone_peroxide.html
Correct. Someone would likely notice the throughput on the fiber doubling, and it makes little sense anyway. Just forward the conversations/packets you're interested in on the already existing fiber.
DPI(Deep packet inspection) devices can do OSI layer 7(application specific layer) inspection, that is, all the data going over the line.
You don't need 4 more cables, just inject select data into the already laid fiber. It's been demonstrated(AT&T) that you can do DPI on high-throughput fiber links, it's not that difficult to remote into whatever box you dropped off into the bottom of the ocean.
Yes, but that doesn't stop the trolls and karma whores from bringing up an issue that plauged *first generation* flash devices, in order to appear insightful.
Do you honestly think that "terrorists" are communicating over plain text? Are you fucking nuts?
Unless there is a reason to update. Quicktime has a horrible record of security. As of right now, see CVE-2008-0036, CVE-2008-0033, and CVE-2008-0032.
You miss the point. Updating quicktime should *not* break adobe.
It's interesting to me that over the millions of years of evolution life has gone through, we're still using the same basic outlines for anatomy.
If your computer can't handle 65535 simultanious SYN packets, you've got problems.
Removing the DRM doesn't shaft Apple. It's still playing on the person's iPod.
This sort of makes sense, and *could* be testable, try to break out of the virtual machine. The question is, if we find a buffer overflow in the universe, what happens if our shellcode causes a BSOD?
Mandatory innoculations, coming to an installation of society near you!
You know, the funny thing is this won't stop a thing. You'll just see coke starting to get mixed with short lived immunosuppressants.
I'm rather annoyed with companies these days. Are you fucking Apple? NO!!! Then don't make an iProduct, if not that, then because prepending 'i' infront of 'x word in the dictionary' is fucking stupid in the first place, you consumerist whore.
Not posted AC, bitches.
(last explitive added to spite the lameness filter)
This is going to be interesting to see go down... what will Microsoft's response be??