On Friday 02 June 2006 11:38 pm, Mitchell Brown wrote: > Why is it insecure? I don't see the problem?
It's not the problem, it's the myriad of problems. Being a walking transponder means you can be tracked anywhere there is a reader. Suppose you use it to open your garage door. Your neighbors geeky, misguided kid goes out and buys an inexpensive reader and manages to get close enough to read the tag...if it's a door opener he might be able to read it from a large enough distance you'd never know. So now he's got the keys for your garage. They can be infected with viruses, overwritten if left unlocked, and, if someone REALLY wants it, instead of holding you up, they dig it out with whatever tool is handy...and they'd be digging for a while trying to find something that small. Don't say never...I'd put money on this happening in my life time. RFID has uses, and good ones at that. Injecting one as a personal identification system is not one of them. http://www.theregister.co.uk/2003/06/27/rfid_chips_are_here/ > > On 6/2/06, Nick Wiltshire <[EMAIL PROTECTED]> wrote: > > On Friday 02 June 2006 8:59 pm, Mitchell Brown wrote: > > > Did you happen to see that guy on Systm (the latest one)? Wow. Friggin > > > cool. He had two chips in each hand and had rigged up a standard HID > > > card-reader or whatever to his house, computer, and car. Pretty slick. > > > > And in most cases about as secure as putting your ip address, user name > > password in your email sig....ok maybe not quite, but it's pretty slack. > > > > > On 6/2/06, D Bhardwaj <[EMAIL PROTECTED]> wrote: > > > > Sounds like you are a prime candidate for an implanted rfid. > > > > Content-Type: multipart/alternative; > > > > boundary="----=_Part_15669_15218222.1149107819000" > > > > > > > > > > > > ------=_Part_15669_15218222.1149107819000 > > > > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > > Content-Transfer-Encoding: 7bit > > > > Content-Disposition: inline > > > > > > > > > Also, especially with that many accounts, you should *never* use > > > > > the > > > > > > > > same > > > > > > > > > password > > > > > for everything! *Ever*! > > > > > > > > Oh I know its bad. But what else can I do? I mean - how can I > > > > remember different passes for everything? :-/ > > > > > > > > ------=_Part_15669_15218222.1149107819000 > > > > Content-Type: text/html; charset=ISO-8859-1 > > > > Content-Transfer-Encoding: 7bit > > > > Content-Disposition: inline > > > > > > > > <blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: > > > > 0pt > > > > > > 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote"><div > > > > style="direction: ltr;">Also, especially with that many accounts, you > > > > should *never* use the same password > > > > <br>for everything! *Ever*!</div></blockquote><div><br>Oh I > > > > know its bad. But what else can I do? I mean - how can I remember > > > > different passes for everything? :-/<br></div><br> > > > > > > > > ------=_Part_15669_15218222.1149107819000-- > > > > > > > > > > > > _______________________________________________ > > > > clug-talk mailing list > > > > [email protected] > > > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > > > > **Please remove these lines when replying > > > > > > > > _______________________________________________ > > > > clug-talk mailing list > > > > [email protected] > > > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > > > > **Please remove these lines when replying > > > > _______________________________________________ > > clug-talk mailing list > > [email protected] > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > > **Please remove these lines when replying _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
