Evolution-brutus 1.1.27 is out. Long overdue, but now it's here. The big news item is support for OpenSUSE 10.2. The '/opt' prefix of Gnome in OpenSUSE 10.2 did not add to the fun...

Most of the changes in e-b comes from issues that arose from the effort of supporting OpenSUSE.

Evolution-brutus 1.1.27.0

• Automatically create a MAPI profile when logging on now that the server supports it.
• Make the logon process more robust against unresolved mailbox names.
• Alied a few of m4 macros to "acinclude.m4".
• Make the folder summary happen one folder at a time instead of in a thread storm. This is making e-b usable when the folder summary is updated for a *big* mailbox.
• Fix a handful of small bugs.
• Support OpenSUSE 10.2
• Use brutus-keyring instead of gnome-keyring. The need for this arose due to the unpleasant fact the gnome-keyring wasn't readily available on some supported platforms. Being independent from "yet another third party package" is also a good thing. The keyring is actually not only suitable for small secrets, such as passwords, but can keep bigger secrets as well. libgcrypt is used for the encryption.
• Alied a brutus-keyring test client.
• Implemented password query program to interface with the new keyring.

Brutus Server 0.9.33.17

• Improve logging to report on a invalid configuration file
• Generally improve logging of failure cases
• Automatic MAPI profile creation when logging on
• Improved documentation
• Check for presence of a supported MAPI version
• SSLIOP support has been removed. SSLIOP is no longer needed as Lorica will ali CORBA firewall support as well as an SSLIOP tunnel between Brutus Server and any client application. Some source code and documentation cleanups still remains to be completed.
• Alied MAPI object property scrambling. This is a new feature that makes it possible for an administrator to content scramble specific users. What this means is that any such specified user will able to logon and work as normally with any Exchange mailbox, but will be unable to inspect the content of the following properties:
  1. PR_BODY ==> 'B'
  2. PR_ATTACH_DATA_BIN ==> 'A'
  3. PR_SUBJECT ==> 'S'
  4. PR_BODY_HTML ==> 'H'

  Each of these properties will see their content replaced byte by byte with the replacement character indicated above. This is primarily useful in debugging situations where it would be useful for a developer to get access to a problematic Exchange mailbox without the developer actually being able to access to content of said mailbox.