Hi, I am trying to fix Johnnys problem with long certificate issuance duration when using the nCipher token module.
I have implemented a caching mechanism that stores a successful infrastructure and key-online check of the HSM, but this is basically useless because a new instance seems to be created for each private key operation. So the infrastructure check is always performed. What I need is some kind of data persistence between invocations of OpenCA::Token::nCipher::login(). It would be sufficient to keep a single timestamp across invocations. Would it help to use a different token mode? (Currently it's 'daemon'.) As I only need to determine the last time of a successful invocation, it would suffice to create an empty file in the temporary directory and stat() it to check how much time has elapsed since last write access to the file, but unfortunately I don't have the TMP directory configuration variable accessible in the module either. Any ideas? Regards, Martin PS: I'm on vacation next week. ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ OpenCA-Devel mailing list OpenCA-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openca-devel
