Hi arun,
Hope u are doing good.
I concur with qwal, there are two ways to accept an encryption key :
a. through email
b. through a exported file
If he has accepted through email, then you can check his email for some probable dates, . The first thing is check the properties of the ID file, when it is last modified, that should give you some clue.
I believe Qwal has worked lot on this ID registering stuff in openntf, may be he might have some more ideas in his bag (hacking a id and checking etc :)
-Partha
Main Topics
Browse All Topics





by: qwaleteePosted on 2005-01-18 at 13:38:51ID: 13077010
Well you can at least tell how old it is by the date created.
Otherwise, the only thing you can do is look for the fil that was imported. If it was sent using thebuilt-in "send encryption key" function in the User ID security dialog, it will have a subject like:
Encryption key "Test" is attached. You may insert this key into your ID file by using the Actions menu "Accept Encryption Key..." option.
...and the file name will be ~~tmpid.idk. He will probably have accepted it shortly after the delivered date f the message. You can also look at the last accessed date of the message, but that's not really accurate, as he may have opened the doc at a later date, or be looking at a different rreplica than the one he used to accept the key.
If it was sent to him in another way, the filename is usually document.key, thogh it may be some other name, or even a different extension. But I would guess the extension will PROBABLY match, so look on his hard drive for .key files. Of course, he may have thrown it away, received it on a floppy, or been using a different PC at the time.
One other thing to do is see if there are old copies of the ID file lying around somewhere. Note the mod date on them before using them. Then switch to it and see if it has the key. If not, you know he PROBABLY accepted it later. If present, he certainly, at least in this copy of the ID, accepted it earlier than the mod date of the file that you noted -- which is now gone of course :)