Please click on any of the following questions below to view their answers.

Why must I sign a letter of confidentiality before receiving the M.O.S.T. Toolz™ Kit?

In order to supply you with the essential technical data needed to use the kit, CardLogix must share sensitive information, which, if misused, could harm our intellectual property and the security of your application. We follow industry standards for confidentiality that protects both seller and buyer.

What types of cards ship with the M.O.S.T. Toolz™ Development Kit?

M.O.S.T Cards that are all symmetric key functionality with the T=0 interface. Typically the included cards are 2 each: CLXSU512KJ4/T=0ED Limited Life (64kByte memory), 1 each, CLXSU442KF5/T=0 -(55K Byte memory) with a fixed demo card file system, CLXSU512KJ4/T=0ED - (64kByte memory) with a fixed demo card file system, and a CLXSU256KJ4/T=0ED - (32kByte memory)) with a fixed demo card file system.

We reserve the right to substitute cards based on inventory or customer requirements.

Does the M.O.S.T.™ COS allow for electronic purse files on the chip? If yes, how many purses are allowed per card?

Our COS allows you to design up to ten purses on the chip. There is a practical limit to the number of files due to the overhead needed to build the file structure, passwords, access codes etc., that occupy the same physical area as the card data.

Does this tool allow me to develop Java Cards?

No, we recommend other open source tools for this job, please talk to your CardLogix representative for Java card samples and tools.

If I am using an already installed PC/SC reader can't I just develop on it?

Due to the inconsistencies in adhering to the ISO and PC/SC specifications across a wide variety of readers and from manufacturer to manufacturer; CardLogix has chosen to support the readers shipped in the kit for the development process. But after card development, we fully support any PC/SC compliant reader with Winplex® and our cards.

Can I choose the level of protection on files that are created?

Yes, The M.O.S.T. Card File Creation Utility enables the issuer to pre-set all of the card and file attributes before production. You tell us what you want via your own file structure since the protection is pre-programmed at the factory.

Since M.O.S.T.® Cards are file-based is any file created during the manufacturing process? If so, can this file be personalized? Is this file unprotected, protected, or protected by programming?

We re-create and fuse the files you design during our manufacturing process. This includes all of the files attributes regarding security and keys that you put in your file supplied to us. CardLogix can further customize a card to your requirements for protection (serialized, loaded with information, transport protected or certificate loaded) based on a customer supplied specification.

Is the CardLogix M.O.S.T.® Card Operating System interoperable with other card operating systems?

Card operating systems do not function in the same way as a computer OS, therefore interoperability cannot be defined in the same terms. The CardLogix M.O.S.T.™ Card Operating System (COS) executes standard ISO 7816-4 commands as well as the CardLogix enhanced command set. This makes CardLogix cards functionally compatible with other COS, which have these commands in common.

Do M.O.S.T. Cards® support PKI Encryption such as RSA and elliptical curve(ECC)?

No, The M.O.S.T. Card® family does not support these function on chip. If that is a requirement please refer to our Credentsys Card Family for this type of device. That is not to say that the card cannot be a secure container for a Digital Certificate or customized token scheme. The M.O.S.T. Card®family supports many different types of symmetric key encryption methods such as DES TDES, AES and SHA-1 and SHA-256. Unique digital signatures can be created using the on-board hashing functions such as SHA.

What is a CFS?

“CFS” is an acronym for Card File System. It is the formatted EEEPROM area that contains the issuer's data and files. The M.O.S.T. Card File Creation Utility is designed for a developer or issuer to predetermine a cards data security.