SafeGuard LAN Crypt Administration Release Notes 3.80
Known to apply to the following Sophos product(s) and version(s)
SafeGuard LAN Crypt Administration 3.80
Microsoft SQL Server 2005 SP4
Microsoft SQL Server 2008 R2
Oracle Server 9i
Oracle Server 10g (see section known issues)
Oracle Server 11
Create Profiles for all Members Assign Certificates to all Members Copy User
Automatically set group permissions Show granted group permissions Extended logging information after permissions have changed
A friendly name can be specified for newly created certificates. Certificates can now be created without the critical extension 184.108.40.206.1.1.1.
Group policy Universal Token Interface no longer exists. Still relevant settings moved to LAN Crypt Configuration. Auditing (SGLOG) is no longer available. Database logging within the SafeGuard LAN Crypt Administration has to be used instead. The scripting API does no longer support remote security officer login
Database errors are now corrected during the migration Database migration wizard is started during the first login after migration
Resolved Issues (from 3.61)
API function WriteRule now accepts a specific key Several corrections in LDAP synchronization Users deleted in LDAP directory were not deleted Groups moved from one container to another container lost the security officer permissions Parent group of objects was not updated The In Use property of keys was reset in some situations Logging wizards can now be canceled Security officers created with an administration version 3.50 or below could not be deleted Signature certificate was not saved during the creation of a new security officer Fixed logging entry for GrantRightsOnGroupToSO and GrantRightsOnSOToSO Fixed some application crashes Eliminated the SQL timeout errors Scripting API does no longer show message boxes
Users deleted in LDAP directory were not deleted Groups moved from one container to another container lost the security officer permissions Parent group of objects was not updated
If objects are imported from a domain, you must specify the domain name and not the computer name in the server configuration! When configuring server logon data in central settings you should either enter only the domain name as server name or add the domain name as an alias. On the root level (e.g. domain), only 999 objects are displayed and imported.
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. If you need technical support please post a question to our community. Alternatively for licensed products open a support ticket.