There is no Delete and no DeletePin.
 
One can import key parameters into existing key objects (e.g. setP, setQ), if the requestor has sufficient subject rights.
 
 
-------
 
Beyond the scope of the title, but related to the issue in question:
 
Whether this act under the MuscleCard Framework deletes the previous key parameters is unknown. If the card is US controlled commodity-chip technology, assume it does NOT. Do not assume the chips you buy conform to security evaluation reports cited by vendors, either. To pass export muster, the chips will have bond-out options, that are (quite correctly) not disclosed in the security target - being issues "beyond the defined boundary". In one legal manipulation of the representation of assurance, the chips were tested while still on the wafer - as conforming to the "goals of the security target". By the time they were in the package, life had changed...
 
Raychem makes irradiated doped-polymer passivation layers whose properties depend on the frequency and temperature. In a cryogenic vacuum chamber, the eeprom may reveal more to a probe than it did to the API! And of course, there are lots of eeprom technologies available now, with different electrical and physical characteristics. In a multichip ICC, you really don't know what your getting, from the spec sheet, until you probe it.
 
University VLSI labs have the appropriate probing equipment, if you want to go play.
 
----- Original Message -----
Sent: Thursday, December 09, 2004 2:13 AM
Subject: [Muscle] A question about MUSCLE Card Framework

Good mornig,
 
Is there a function for delete key?
 
Thanks you very much
 
 
Matteo Ferrara
 


_______________________________________________
Muscle mailing list
[EMAIL PROTECTED]
http://lists.drizzle.com/mailman/listinfo/muscle
_______________________________________________
Muscle mailing list
[EMAIL PROTECTED]
http://lists.drizzle.com/mailman/listinfo/muscle

Reply via email to