Hi,
I’m not really sure if this is the correct forum for my question or not.
I’ve been told by a friend that local archive files taken using lotus notes up to 6.5 are not secure if another person is using the same PC and can find his way to the archive file, knowing that the version used is not the multi user version.
My questions now,
If I upgrade the client to 8.5 will this overcome the problem and enforce the ACL from the user’s mail file?
If not, what other solution can help in this matter ?
I do not prefer a solution that involves reinstalling 6.5 multi user version.
Can anyone specify which versions had this problem and from which version it was solved ?
Thanks.
Subject: database properties
Check the database properties (File>Database>Properties or File>Application Properties).On the first tab, in the Settings section, look for an “Encryption Settings” button. click it.
This reveals your encryption settings.
What your friend is referring to is that in earlier versions of Notes, the Default was “do not locally encrypt”, and in r8 and later the default is “Locally Encrypt this…”. This is true for any local replica, not just archives.
For your needs, you can select “Locally Encrypt this” and click Ok. Your Notes client will compact the database and apply the encryption. Then your archive will be encrypted, and only your NotesID will be able to access it.
Subject: All about encrypting local databases ?
Thank you Maria for your feedback.
So you what you are telling is basically that any client prior to 8, will not encrypt the local archive (and any other local replica) and thus, it can be accessed by others ?
If the client is upgraded to notes 8 or higher, the archive will be encrypted even if it was not encrypted before ?
Am I getting this right ?
Thanks once again.
Subject: Need to encrypt it again
I think what she meant is when you create a local replica for the first time, the default setting in R8 is to encrypt the db. Existing local replica encryption setting won’t be changed when you upgrade the client.
This setting can be set in the Setup Policy and/or you can also enforce it using Desktop Policy.