22.12.2012 Views

Front cover - IBM Redbooks

Front cover - IBM Redbooks

Front cover - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Saved passwords<br />

The Sametime client password is stored in the connect.ini file if the user chooses<br />

to have the password “remembered.” Deleting this line in the connect.ini file will<br />

prompt the user for their password. It is encrypted in the connect.ini using the<br />

RSA RC2 block cipher, with an encryption key that is 40 bits long. The encryption<br />

process also uses unique information about every machine, thereby preventing<br />

the file from being used on another workstation.<br />

Network encryption<br />

Sametime chats with Sametime users are automatically secured with encryption<br />

if all participants use Sametime 1.5 or higher.<br />

Attention: If any participant is using an earlier version of Sametime, or is an<br />

external user (for example, AOL)), the chat is not encrypted.<br />

File transfers are automatically encrypted. This encryption uses the RSA RC2<br />

block cipher with a 128 bit key. This encryption algorithm will not work outside of<br />

the Sametime Connect client.<br />

All chat activity between Sametime 2.5 and 3.0 clients and the Sametime 3.0x<br />

server is always encrypted, regardless of whether the “Encrypt all meetings”<br />

setting is selected on the server or not.<br />

However, Sametime clients from releases prior to 2.5 contain settings that enable<br />

users to conduct unencrypted chats. If a Sametime client from a release prior to<br />

2.5 connects to a Sametime 3.0 server, the chat is either encrypted or<br />

unencrypted depending on the client settings.<br />

For instant meetings security, you need to select the “Secure meeting” option to<br />

ensure that your meeting is encrypted. Encryption ensures that no one outside<br />

your meeting can read your messages.<br />

The Sametime user’s “buddy list” is saved in the vpuserinfo (vpuserinfo.nsf)<br />

database. This database is one of the three databases that are created at<br />

installation time and used for deploying Sametime applications. The two others<br />

are the Secrets database (stauths.nsf) and the tokens database (stautht.nsf).<br />

The VPUserInfo database stores information used to restrict whom a user can<br />

see or who can see the user. This information is configured with the Connect<br />

client.<br />

It is important to note that the information in the buddy list is not encrypted when<br />

sent to the server.<br />

Chapter 12. Security features of other Lotus products 543

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!