Liquid error: undefined method `name' for nil:NilClass

3.12.0.0 Release Announcement (1st April, 2020)

Desktop Client 3.9.2.0

  1. Introducing automatic HTML wrapping when files are protected using the Seclore agent.
    1. After this release, when a user protects a file using right-click >> Seclore It!, the file gets protected as well as HTML wrapped automatically.
    2. This will remove the additional step of HTML wrapping a file after protecting it.
    3. HTML wrapping must be enabled in the Policy Server configuration page.
    4. This ensures consistency with files protected using Universal Protection files which are HTML wrapped automatically.
    5. If HTML wrapping is disabled, the file will only get protected and HTML wrapping will not be applied to it.
    6. In the right-click context menu, the ‘Convert to agentless format’ option is changed to ‘Convert to HTML format’’.
    7. To convert an HTML wrapped file to the native format, ‘Convert to native format’ option is added in the right-click context menu.
    8. This feature will not be available in the presence of Boldon James classification or Seclore-classification based protection.
  2. Introducing Universal Protection for Symantec and Forcepoint Endpoint DLP based protection.
    1. Earlier, files with standard formats were discovered by Symantec and Forcepoint DLPs and protected using Seclore.
    2. Files with non-standard formats were not protected.
    3. After this release, non-standard file formats will be protected using Universal Protection when discovered by Symantec and Forcepoint Endpoint DLPs.
    4. These files will be protected with full control to the authorized user and they will be HTML wrapped automatically after protection.
  3. Adding GDPR compliance to Seclore.
    1. When user logs in on the Policy Server or agents, the ‘Terms of Service’ and ‘Privacy Policies’ will be available to the user to view.
    2. These will inform the user of the kind of information Seclore will collect and how it will be used.
    3. If the user agrees, they can enable the check box on the login page and proceed to login.
  4. Fixed the issue when a protected Word or Excel file was saved as unprotected when saving to OneDrive using the AutoSave option.
    1. Before the fix: The user opened a protected Word or Excel file with less than Full Control permission.
    2. When the user clicked the AutoSave option and configured it to be saved on OneDrive, the file was saved as an unprotected file.
    3. After the fix: The AutoSave option will be disabled for protected Word and Excel files.
    4. The user will have to upload and save such files manually (File >> Save/Save As).
  5. Made the error messages informative in case the Seclore agent is not able to process a user action.
    1. Now the user will be able to know the nature of the error from the error message itself.
    2. This will help the users and system administrators to resolve the issue at the earliest for uninterrupted use of Seclore.
  6. Fixed the issue where the Seclore icon was not visible on the taskbar when the agent was active on the Desktop.
    1. Before the fix: The Seclore icon on the taskbar appeared black when the agent was active on the Desktop.
    2. After the fix: The Seclore lock icon will be visible on the taskbar when the agent is active on the Desktop.
  7. Fixed the issue where the users with no access or expired access could view the buffer file or the data itself after RAR.
    1. Before the fix: For a user who did not have access to a protected file, the RAR dialogue box appeared.
    2. After the user requested access permission to the protected document, the buffer file was displayed.
    3. For a user with expired access, after RAR the document opened with the data.
    4. After the fix: After RAR, in both the scenarios mentioned above, the document will close.
    5. Users will have access to the document and can view it only after the owner of the protected file assigns or renews permissions.


Seclore for Mac 3.4.2.0

  1. Introducing automatic HTML wrapping when files are protected using the Seclore agent.
    1. After this release, when a user protects a file using right-click >> Seclore It!, the file gets protected as well as HTML wrapped automatically.
    2. This will remove the additional step of HTML wrapping a file after protecting it.
    3. HTML wrapping must be enabled in the Policy Server configuration page.
    4. This ensures consistency with files protected using Universal Protection files which are HTML wrapped automatically.
    5. If HTML wrapping is disabled, the file will only get protected and HTML wrapping will not be applied to it.
    6. If Seclore agent is not available, the file opens in Seclore Online.
    7. In the right-click context menu, the ‘Convert to agentless’ option is changed to ‘Convert to HTML’.
    8. To convert an HTML wrapped file to the native format, ‘Convert to native format’ option is added in the right-click context menu.
  2. Introducing Universal Protection for Endpoint protection.
    1. Earlier, files with standard formats were discovered by Endpoint and protected using Seclore.
    2. Files with non-standard formats were not protected.
    3. After this release, non-standard file formats will be protected using Universal Protection when discovered by Endpoint scanner.
    4. These files will be protected with full control to the authorized user and they will be HTML wrapped automatically after protection.
  3. Adding GDPR compliance to Seclore.
    1. When user logs in on the Policy Server or agents, the ‘Terms of Service’ and ‘Privacy Policies’ will be available to the user to view.
    2. These policies will inform the user of the kind of information Seclore will collect and how it will be used.
  4. Adding support for capturing product metrics for right-click >> Seclore It! and for advanced and universal protection in case of protection through Seclore button in Outlook.
  5. Fixed the issue where a new Word document was saved as a protected file when created after opening a protected Word document.
    1. Before the fix: The user opened a protected Word document.
    2. He opened a new document by either using File >> New or Cmd+N shortcut.
    3. The new document opened with the same watermark as the open protected document.
    4. On editing and saving the new document, it was saved as a protected document.
    5. After the fix: The new document will be created without a watermark and will be saved as an unprotected document after edit and save.


Policy server 3.8.2.0

  1. Adding GDPR compliance to Seclore.
    1. When user logs in on the Policy Server, the ‘Terms of Service’ and ‘Privacy Policies’ will be available to the user to view.
    2. These will inform the user of the kind of information Seclore will collect and how it will be used.
    3. If the user agrees, they can enable the check box on the login page and proceed to login.
  2. Introducing the capability of downloading an unprotected copy of a protected file open in the Seclore Online Editor.
    1. When a protected file is opened in the Seclore Online Editor and the user clicks on the download icon, ‘Download Unprotected Copy’ option will be available in the drop down.
    2. On selecting this option, the unprotected copy of the file will be downloaded.
    3. This option will be available only if the ‘Download Unprotected’ flag is enabled in the Policy Server.
    4. The user must also have Full Control on the protected file to download an unprotected copy.
  3. Fixed the issue where error page was displayed in certain cases when the user tried to login to the Policy Server using Microsoft credentials.
    1. Before the fix: When the user opened a protected file from Microsoft application like SharePoint Online, an error page was displayed when Microsoft based authentication was either disabled or not configured.
    2. After the fix: The Policy Server login page will now be displayed in the above-mentioned scenario.
  4. Now create an enterprise application for Digital Guardian DLP Encryptor from the Custom Application option.
    1. Earlier, you could directly select the Digital Guarding DLP Encryptor from the Select Enterprise Application Type window.
    2. Starting this release, you’ll have to select the Custom Application from the Select Enterprise Application Type window for creating a Digital Guarding DLP Encryptor.
  5. Added support for Oracle 18c and 19c database versions.
Login or Signup to post a comment