Hello, On Feb 14, 2011, at 11:08 PM, NdK wrote:
> On 14/02/2011 17:52, Andreas Jellinghaus wrote: > >> I have no clue about myeid, but some other cards are only 32k for example. >> reserving 8192 would be 25% and that is only one directory file... > Well, javacards have a limit of 32k of data, IIUC, so it's more or less > the maximum for single-app javacards. MyEID have a 3F00 file of 32k, so > I think that's the real available size for the primary app (please > correct me if I'm wrong). 32k stems from the fact that the main data type of a java card is signed short. Yet the EEPROM size of modern cards is 64, 128 or even more K-s. I don't know the details but I would not be surprised if API generated objects like non-transient keys (which are not stored as char arrays in term of Java code) get mostly allocated separately from that 32K ? Maybe Toni knows more. > But I'm still missing some useful details (like typical keysize, how > much space does a key need in index files & so on)... Looking at that index file might help? Also, every applet will take some memory for internal bookkeeping, so it is not simply 1:1. > >> and a fine tuning for each different card and driver: I don't think anyone >> has the time and manpower for that. > Since I have the card and some time, I volunteer to fine tune it so that > a card contains the maximum of useful data :) Great! -- @MartinPaljak.net +3725156495 _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
