On Jan 29, 8:23*pm, Matthew Geier
wrote:
On Fri, 29 Jan 2010 02:44:17 -0800, CJB wrote:
embarrasment. The culprit was the Hillingdon Community Services card -
which seems to use the same technology as Oyster and was causing a
confict. An irritation 'cos now I have to keep them in separated.

*This is going to start happening more and more as various other
organisations start using non contact smart cards.

*The people who make the 'access control' system at my work have said
they want to replace the mag-strip readers with MiFare Classic readers
and replace all our cards. Oyster is Mifare Class - so the door reader at
work will one day cause any near by Oyster card to respond as well as the
'proper' access card, with the system probably objecting when it gets
responses from two cards instead of one.

The access control suppliers really should move on beyond Mifare
Classic for new smart card installations. OK, the simple hack of
access control systems has attacked those that do not even use the
security functions available with Mifare Classic (they attack schemes
that only read the card serial number), but attackers quickly learn
more. Access control should use Mifare DESFire and AES encryption now,
with provision for Mifare Plus (also in its AES version) later
(because Mifare Plus cards will cost less).