The session at ekoparty revealed the technical details about how the exploit works and the vulnerability it exploits. The vulnerability has been known for quite a while.
The vulnerability affects SSL/TLS ciphers that use the Cipher Block Chaining (CBC) mode. These include the popular AES and Triple-DES encryption methods. The easiest way to mitigate the vulnerablity is to switch to an encryption algorithm that doesn't use CBC, like those based on the RC4 stream cipher.
Interestingly enough, Google websites don't use CBC based encryption. They use the RC4 encryption cipher instead.
Domino Server BEAST Mitigation - With Internet Site Documents
- In the Domino Administrator Client, open the 'Configuration' tab and expand 'Web' and 'Internet Sites'.
- Open the Internet Site Document for the server.
- Click on the 'Security' tab.
- Under 'SSL Options' section, change the 'Protocol Version' to 'V3.0 only'.
- Under the 'SSL Security' section, modify the list of SSL ciphers so that only the following ciphers are selected:
- RC4 encryption with 128-bit key and MD5 MAC
- RC4 encryption with 128-bit key and SHA-1 MAC
- RC4 encryption with 40-bit key and MD5 MAC
- Save the Internet Site Document.
- Restart the HTTP task.
Domino Server BEAST Mitigation - Without Internet Site Documents
There does not seem to be a way to specify the SSL protocol version for Domino without using Internet Sites. There is a SSL Protocol Version field on the server document, however it states that it does not apply to the HTTP task.
With that said, I look forward to the day that there is TLS support for Lotus Domino. (And data-at-rest encryption that is stronger than RC4, but that's for another day.)