2020-09-September

SEM

MGR-3933

Error in event log after Satellite Registration

A timing issue when registering an SEM account with CMDS can occur and cause an error with Performance Policies

SEM

MGR-3930

Data Center AD OU Path cannot be edited once value is set

In the Smartcrypt Appliance, once a Datacenter OU was defined, it was not able to be updated.

SEM

MGR-3927

Device record check optimization on master/slave are different

When a TDE Agent would sync with a replica in a SEM Cluster, an etag drift could occur and updates in policy would not take place on the agent.

SEM

MGR-3892

Policy failure with one TDE Key

TDE Key retirement calculation eliminated all TDE Keys from being passed out, so the TDE Agent was not getting any TDE Keys to use.

SEM

MGR-3855

Primary server still referred to as master

As part of renaming the Master node to the primary node, all visible labels were planned to be updated. A few were missed.

SEM

MGR-3817

Cluster - Replica warning still says "make changes on master"

As part of renaming the Master node to the primary node, all visible labels were planned to be updated. A few were missed.

SEM

MGR-1270

Cannot set "Verbose Logging User Ids" on replica nodes

When needing detailed logging for a specific user, a replica node would fail trying to set the value.

SEM

MGR-3854

Unable to use reset all log levels button on support page on non-primary

When on a replica support page, resetting the log levels would fail

SEM

MGR-3849

Admin API for Active Directory Connectors order should use PUT

Admin API using wrong type of update for an Active Directory Connector

SEM

MGR-3809

Admin API - Policy contingency_groups always includes Satellite email, contrary to UI

Admin API mishandling the contingency group field on archive policies

SEM

MGR-3836

Cluster Replica tried to write to database during AppSettings initialization

An initializer for PKMetadataServer.AppSettings had attempted to INSERT into the database and failed because the database was (rightly) read-only

SEM

MGR-3835

SameSiteStrict cookies in MDS to support modern browser updates

Modern browsers are becoming more strict on how /which cookies are allows. 

SEM

MGR-3832

Support page, typo in "pronouncable" password hash

Typo on pronounceable hash on the support page, introduced with master password rotation

SEM

MGR-3782

UpdateProcessor for RemediationAction got stuck complaining about nonexistent non-uniform Locker

A background queue that handles large updates could fail and repeatedly error

Windows Client

ARC-2395

Prompt for passphrase when decrypting several archives with right click option

Contingency key enabled archives when decrypted in mass (more than 1) were causing a prompt when the Smartkey should've been used

Windows Client

ARC-2327

Replace + re-zip not working

When working with a multi-file archive the items added back to the zip might not be the last version the user worked on.

Windows Client

ARC-2319

Partial Performance Policy Sync Offline

Agent will misbehave if the SEM went offline after the agent only synced 1 time as the agent doesn't have the details of the performance policy

Agent

ARC-2345

Updating file filter on remediation does not re-scan data

File filters being updated were not triggering re-scans in the agents.

Agent

ARC-2310

Re-encryption always aborts on error, even if configured not to

With the Admin API, however, it's actually possible to configure such lockers and assignments (and with SMDS 18.6 it's much easier to configure them this way), and it turns out that this flag doesn't actually work - if a single non-decryptable file is encountered inside an archive, the Agent (or Service) still aborts the entire operation.

Agent

ARC-2410

Password change (SID) causes unlink on second login

When an unmanaged user (or local user) changes their unmanaged password, a new SID is created and posted to the server. When a 2nd device logged requires entry of the new password, a new SID object is stored on the client, but the old SID is not discarded. This extra SID causes failure when checking the validity of the metadata on startup.

CLI

ARC-2336

Archivedate option works incorrectly with TGZ/TBZ archives

For simple archives such as ZIP and TAR, this works correctly, but for embedded archive types such as TGZ (TAR.GZ) and TBZ (TAR.BZ2) it ends up using today's date and time, presumably because it's getting them from the TAR file itself rather than its contents.