SCFS in CardI was trying to put a configuration file (something like this) in a smartcard to store multiple keys in one smartcard for the Kerberos/smartcard project.
To avoid it, we should take advantage of the .i file of scfs. I suggest that we implement a set of functions to access smartcard files in UNIX style, i.e., open, close, read, write, lseek, and fgets will be really nice to parse config files.
And ... my dream is that every smartcard has .i file in its directory, and .i is updated on every access (not just via scfs). This way, we can use UNIX style files in smartcard from outside (via scfs) and from inside (via the functions). I suggest to implement the functions and write a document to convince smartcard vendors to implement UNIX metadata like .i by default, or to let us implement it for them.
How do you think?