-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/03/2011 07:06 PM, sebastian nielsen wrote:
> Also found some on the internet, about Nexus S having a PN65N which
> according to sources of the internet, is a SmartMX security chip
> combined with a NFC chip.

It seems that it is in fact an NXP PN544.  Anyway having a secure element
integrated in the Nexus S would be great news, even if it take some time to be
able to use it.  But knowing that the chip can support a secure element does not
mean that there is one.

> 
> Any ideas on how to use this security chip? Eg writing data
> (generating/writing RSA keys or writing symmetric keys) into the chip,
> extracting generated _public_ keys and also use the keys for
> encryption/decryption?
> 
> Any ideas on how to do it in Android?

I was not able to find anything in the current AOSP, but I think that a lot of
work would be needed to have this.  First you need the integration of pcsclite,
similar to what seek-for-android did.  But after this someone need to write a
PKCS#11 provider implementation, similar to the SunPKCS11 provider.  I was not
able to find one, either in Apache Harmony or BouncyCastle, so that probably
something that had to be written from scratch.

After this, and assuming that the Nexus S really contains a secure element, any
Android app will be able to store/generate and use RSA/ECC keys in a secure way.

- -- 
Marc Petit-Huguenin
Personal email: [email protected]
Professional email: [email protected]
Blog: http://blog.marc.petit-huguenin.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk1yYcsACgkQ9RoMZyVa61fSMACfTmbS1RpO96mVm4D2QdpP5OBh
HUAAn2HuxgsciCfo89O01bJSIp0IsOgb
=nvN4
-----END PGP SIGNATURE-----

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to