It *is* the shrinky dink that matters. You can't cut a duplicate Medeco key in metal. Medeco key teeth have an angular component. They are 3 dimensional keys, whereas your usual kwikset or schlage lock are 2 dimensional.
The tumblers in a Medeco lock require some rotation to unlock, as well as vertical lift. That's why this hack is so clever - the shrinky dink or plastic can twist as you jam them into the lock and push up with the backing spline.
Until this, Medeco locks were considered to be uncrackable.
If you don't understand that soliciting sex from a minor is illegal, and soliciting sex from an adult is not, then my guess is we'll see you on MSNBC sometime in the near future.
I see that there are quite a few people coming at this from an employee perspective, which is great. One thing that I've found that helps me *immensely* is to have high standards and high expectations of people, and to let them know that.
On the flip side, don't be a dick about it. Just make sure to let people know that you expect quality and after a little while (with some consistent nudging) you'll start getting it.
It makes life a ton easier as an architect and a manager when you have a solid base to work with.
Wouldn't using some sort of checksum routine on the users software when it runs and comparing to authorized checksums on a centralized authorization server prevent this particular problem?
There are also the considerations of a Chinese/Iranian/Other country having developed something similar to Echelon. Or using Van Eck phreaking, or one of a thousand other ways to intercept data. Let me bounce this off of the/.'ers - Perhaps the best idea would be to use a hybrid of offline/online encryption. Buy two copies of the same book. Who knows - the english version of 'The Red Book'? Number every letter in the first 9 pages in the book, and send messages like this: 1045170820013994 Which would translate into these letters: 1045 1708 2001 3994 Which translates into: Pg. 1, 45th Char = H Pg. 1, 708th Char = E Pg. 2, 1st Char = L Pg. 3, 994th Char = P What you end up with is a very low tech one-time pad. There are lots of ways to make this more secure. Buy more than one book. 'Encrypt' the isbn of the next keybook somewhere in the message, so you'll know what to use next. Add a number to every 4 number sequence, or better yet, use a larger number sequence. And of course, multiply the whole number string by a very large prime to throw things off a bit more. Sure it's tedious, and the messages will end up really long...But you don't want unencrypted messges laying around on your computer, no?
Slashdot Mirror
The pot called the kettle black.
I understand http://ky.gov/ has quite a lot of online gambling action.
Javascript has server side interpreters... Rhino & Tamarin come to mind.
Ugh, you can't copy Medico keys in metal without access to the special blanks.
I knew as soon as I hit submit, someone was going to be anal with the "OF COURSE THE KEYS R METAL LOL LOL LOL"
It *is* the shrinky dink that matters. You can't cut a duplicate Medeco key in metal. Medeco key teeth have an angular component. They are 3 dimensional keys, whereas your usual kwikset or schlage lock are 2 dimensional.
The tumblers in a Medeco lock require some rotation to unlock, as well as vertical lift. That's why this hack is so clever - the shrinky dink or plastic can twist as you jam them into the lock and push up with the backing spline.
Until this, Medeco locks were considered to be uncrackable.
If you don't understand that soliciting sex from a minor is illegal, and soliciting sex from an adult is not, then my guess is we'll see you on MSNBC sometime in the near future.
You should get some of the guys from HP's research facility to come and talk about why the memristor is such a huge deal.
Imagine a beowulf cluster of these!
Can someone explain what this means to us in laymans terms? I'm just a software geek. I know nothing of this "sun" you speak of.
I see that there are quite a few people coming at this from an employee perspective, which is great. One thing that I've found that helps me *immensely* is to have high standards and high expectations of people, and to let them know that.
On the flip side, don't be a dick about it. Just make sure to let people know that you expect quality and after a little while (with some consistent nudging) you'll start getting it.
It makes life a ton easier as an architect and a manager when you have a solid base to work with.
Do you guys play at Casino AZ. over on Indian Bend? It seems like I've seen a few of you down there a couple of times.
http://aperfectcircle.com/images/home_band.jpg
Wouldn't using some sort of checksum routine on the users software when it runs and comparing to authorized checksums on a centralized authorization server prevent this particular problem?
I believe this patent is for the iBot, which is one of Kamen's claims to fame. IANYM - I am not your mother.
There are also the considerations of a Chinese/Iranian/Other country having developed something similar to Echelon. Or using Van Eck phreaking, or one of a thousand other ways to intercept data. Let me bounce this off of the /.'ers - Perhaps the best idea would be to use a hybrid of offline/online encryption. Buy two copies of the same book. Who knows - the english version of 'The Red Book'? Number every letter in the first 9 pages in the book, and send messages like this: 1045170820013994 Which would translate into these letters: 1045 1708 2001 3994 Which translates into: Pg. 1, 45th Char = H Pg. 1, 708th Char = E Pg. 2, 1st Char = L Pg. 3, 994th Char = P What you end up with is a very low tech one-time pad. There are lots of ways to make this more secure. Buy more than one book. 'Encrypt' the isbn of the next keybook somewhere in the message, so you'll know what to use next. Add a number to every 4 number sequence, or better yet, use a larger number sequence. And of course, multiply the whole number string by a very large prime to throw things off a bit more. Sure it's tedious, and the messages will end up really long.. .But you don't want unencrypted messges laying around on your computer, no?