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

Seclore 3.11.0.0 Release Announcement (1st February, 2020)

Desktop Client 3.9.0.0

  1. Introducing Universal Protection for protecting any file format with sensitive enterprise information.
    1. Earlier, a user could protect only a limited number of file formats using Right-click >> Seclore It or the ‘Seclore It’ button in Outlook.
    2. With this new feature, users can now protect any file format on their desktop or in Outlook.
    3. For standard file formats (i.e. MS Office, PDF, Text and Images) Advanced Protection enforces WHO (users or groups), WHAT (Read, Edit, Print etc), WHEN (date and time expiry) and WHERE (device and location).
    4. For all other formats, Universal Protection enforces WHO (users or groups), WHEN (date and time expiry) and WHERE (device and location).
    5. When an authorized recipient opens a file with Universal Protection, he/she is granted Full Control permission.
    6. The Universal Protected file opens in read-only mode and if the user edits and tries to save the file, he/she will be prompted to ‘Save As’.
    7. Authorized recipients can also Unprotect these files.
    8. Universal Protection will automatically apply the HTML wrapper i.e. Sample.mp4 will be protected as Sample.mp4.html.
    9. This feature needs to be explicitly enabled on the Policy Server along with the HTML wrapping feature.
    10. The Policy Server also supports Agentless Access for these files, that allows authorized users to get an unprotected copy of the document without using an agent.
    11. Requires Policy Server 3.8 or higher.
  2. End of Advanced Protection support for certain outdated file extensions.
    1. Certain file formats will not be supported by Seclore for Advanced Protection, going forward.
    2. These file formats will be included under Universal Protection and the permissions granted for Universal Protection will be applicable.
    3. When the Policy Server is updated and the Desktop Client is not updated, files in these formats, which were previously protected using Advanced Protection, will continue to grant the previously applied permissions.
    4. When the Desktop Client is updated, files in these formats, which were previously protected using Advanced Protection, will prompt the user to get the file re-protected using Universal Protection from the owner on access.
    5. This is regardless of the Policy Server being updated or not.
  3. Fixed the issue where the PowerPoint files (protected and unprotected) stopped functioning when a user moved through a list of files in the File Explorer with the Preview Pane enabled.
    1. Before the change: When a user enabled the Preview Pane (View >> Preview Pane) in the File Explorer and moved through a list of files, PowerPoint files open in the background stopped functioning.
    2. This particular behaviour was not observed for other Microsoft Office file formats as preview is disabled for file formats like Word and Excel.
    3. After this change: PowerPoint files will function and remain open as expected even with the Preview Pane enabled in the File Explorer.
  4. Fixed the issue where the default browser icon was displayed for a HTML wrapped file.
    1. Before the change: When Desktop Client was installed in the system, the original file format icon (Word, Excel, PowerPoint, etc.) was not displayed for HTML-wrapped files.
    2. Instead, the default browser (for example, Chrome icon) was displayed.
    3. This usually occurred after restarting the system.
    4. This was previously rectified by running the Repair Installation tool of the Desktop Client (Click on the Seclore tray icon >> Repair Installation >> OK).
    5. After the change: The default file format icon will be displayed for HTML-wrapped files throughout.
    6. Exception: Files with .smail extensions will continue to display the default browser icon or HTML icon.
  5. Fixed the issue where the default file format icon was not displayed for HTML-wrapped files when a copy of the file was created or when an HTML-wrapped file was downloaded multiple times.
    1. Instead, the default browser icon was displayed.
  6. Fixed the issue where the lengthy email IDs of the file owners spilled over the permission widget of an open protected file.
    1. Before the change: When the user clicked the ‘S’ button in an open protected document, the email ID of the owner spilled over the permission widget.
    2. After the change: For lengthy email IDs, part of the email ID is visible, and three dots are added after that.
    3. The user can hover over the dots and view the complete email ID as a tooltip.
  7. Fixed the issue where Outlook stopped functioning when the user clicked on the ‘Seclore It’ button for protecting emails and attachments.
    1. Before the change: While composing an email from the Outlook application when the user clicked on the ‘Seclore It’ button from the Menu ribbon, Outlook stopped functioning.
    2. This issue was observed for users with Policy Server version 3.7.4.0 and above.
    3. After the change: When the user clicks the ‘Seclore It’ button on the Menu ribbon in the Outlook application, the Seclore options will be displayed, as expected.


Seclore Lite for Mac 3.4.0.0

  1. Introducing Universal Protection for protecting any file format with sensitive enterprise information.
    1. Earlier, a user could protect only a limited number of file formats using Right-click >> Seclore It or the ‘Seclore It’ button in Outlook.
    2. With this new feature, users can now protect any file format on their desktop or in Outlook.
    3. For standard file formats (i.e. MS Office, PDF, Text and Images) Advanced Protection enforces WHO (users or groups), WHAT (Read, Edit, Print etc), WHEN (date and time expiry) and WHERE (device and location).
    4. For all other formats, Universal Protection enforces WHO (users or groups), WHEN (date and time expiry) and WHERE (device and location).
    5. When an authorized recipient opens a file with Universal Protection, he/she is always given Full Control permission.
    6. The Universal Protected file opens in read-only mode and if the user edits and tries save the file, he/she will be prompted to ‘Save As’.
    7. Authorized recipients can also Unprotect these files.
    8. Universal Protection will automatically apply the HTML wrapper i.e. Sample.mp4 will be protected as Sample.mp4.html.
    9. This feature needs to be explicitly enabled on the Policy Server along with the HTML wrapping feature.
    10. The Policy Server also supports Agentless Access for these files, that allows authorized users to get an unprotected copy of the document without using an agent.
    11. Requires Policy Server 3.8 or higher.
  2. Fixed the issue where emails sent from Outlook using ‘Seclore It’ were sent unprotected, if the HTML wrapping feature was disabled in the Policy Server.
    1. Before the change: When the HTML wrap feature is disabled in the Policy Server, if the user invokes the ‘Seclore It’ option in Outlook, the email and attachments are always sent unprotected.
    2. After the change: In this scenario, attachments will be sent protected, as expected.
    3. Note: The option to protect the email body is not available when the HTML wrapping feature is disabled in the Policy Server.
  3. Fixed the issue faced where creating a new Microsoft Excel workbook from a template was not working as expected.
    1. Before the change: When the user created a new Workbook from a template, the application would shut down unexpectedly.
    2. After the change: This issue has now been fixed.
  4. Fixed the issue where a protected and HTML-wrapped file got unwrapped if an unauthorized user unprotects it.
    1. Before the change: When an unauthorized user attempts to unprotect a file with HTML-wrapping, it removes the HTML format. i.e. Sample.docx.html converts to Sample.docx, even though it doesn’t get unprotected.
    2. After the change: The issue has been fixed and the HTML format is retained.
  5. Fixed the rare issue where certain file formats (docm, docx, xlsm and xlsx) were not getting protected from a network shared folder.
    1. Before the change: Sometimes when the user performs a Right-click >> Seclore It on an individual file in a certain format (i.e. docx, docm, xlsx or xlsm), stored on a network shared folder, it would not get protected.
    2. If the user tries to a Right-click >> Seclore It on the parent folder containing these files, they were still getting protected.
    3. After the change: The files get protected, as expected.
  6. Fixed the issue where protected files placed on network shared folders were not getting converted to Agentless format (HTML-wrapped).
    1. Before the change: If the user does a Right-click>> Convert to Agentless Format on a protected file stored on a network shared folder, it would not work as expected.
    2. After the change: The files are successfully HTML-wrapped.
  7. Fixed the rare issue where the Seclore operations returned an error message when performed on some network shared folders.
  8. Fixed the issue where the agent becomes unresponsive if the user tries to protect a file that is already open.
    1. Before the change: When a user does a Right-click >> Seclore It on an open, unprotected file, the file would not be protected.
    2. The agent also became unresponsive to any further commands.
    3. After the change: The file gets protected and the agent works as expected.


Policy Server 3.8.0.0

  1. Introducing Universal Protection for protecting any file format with sensitive enterprise information.
    1. Earlier, a user could protect only a limited number of file formats using Right-click >> Seclore It or the ‘Seclore It’ button in Outlook.
    2. With this new feature, users can now protect any file format on their desktop or in Outlook.
    3. For standard file formats (i.e. MS Office, PDF, Text and Images) Advanced Protection enforces WHO (users or groups), WHAT (Read, Edit, Print etc), WHEN (date and time expiry) and WHERE (device and location).
    4. For all other formats, Universal Protection enforces WHO (users or groups), WHEN (date and time expiry) and WHERE (device and location).
    5. When an authorized recipient opens a file with Universal Protection, he/she is granted Full Control permission.
    6. The Universal Protected file opens in read-only mode and if the user edits and tries to save the file, he/she will be prompted to ‘Save As’.
    7. Authorized recipients can also Unprotect these files.
    8. Universal Protection will automatically apply the HTML wrapper i.e. Sample.mp4 will be protected as Sample.mp4.html.
    9. This feature needs to be explicitly enabled on the Policy Server along with the HTML wrapping feature.
    10. The Policy Server also supports Agentless Access for these files, that allows authorized users to get an unprotected copy of the document without using an agent.
  2. Introducing collaboration of MS O365 and Seclore for enhanced security of your documents on the cloud.
    1. Now, you can edit and save your changes (if you have the required permissions) in the documents shared through SharePoint Online and OneDrive.
    2. No need to download to edit shared documents from SharePoint Online and OneDrive.
    3. External users can also edit documents if they have Edit permission from the document links shared with them.
  3. Introducing the new and improved Seclore Online Editor with enhanced UI.
    1. The look and feel of the new Seclore Online Editor are similar to the corresponding Microsoft Office applications.
    2. Important functional buttons such as Save, Print, Undo and Redo are moved to the Only Office title bar for better visibility.
    3. In addition to the Only Office title bar, another title bar will be visible for Seclore-protected documents.
    4. This new title bar will display the customer logo, Read-only (in case of read-only files), Edit button (for integration workflows) and the download button.
    5. The Edit button appears only when a file is opened in the Read-only mode in case of integration workflows like opening protected files from SharePoint online.
    6. The Edit button is not visible in the Edit mode.
    7. For non-integration workflows, documents open in the view depending on the granted permission.
    8. The download button is moved from the inside of the document to the Seclore title bar.
    9. In Read-only mode, only the option to download the Seclore agent is visible on clicking the download button.
    10. In Edit mode, the options to download the Seclore agent and to download the protected copy of the file.
  4. Now, the online help package is released separately from the Policy Server package and needs to be downloaded and placed in the PS package.
    1. This will ensure the latest online help for the Seclore products with the latest feature explained.
    2. If the online help package is not downloaded and available, an error message is displayed.
  5. Fixed the issue where Seclore Lite for Mac installation package was downloaded on iPad after clicking on Download Seclore in the buffer file.
    1. Before the fix: If a user does not have Seclore app for iOS installed in their iPad and opened a protected file from email, the buffer file was displayed in the browser.
    2. On clicking the Download Seclore option, Seclore Lite for Mac was downloaded instead of redirecting the user to the App store.
    3. This was observed in the iPadOS 13.
    4. After the fix: The user is redirected to the App store from where they can download the Seclore Lite app for iOS or iPadOS.
  6. Fixed the issue where the owner of the excluded Hot folder was not changed once the owner of the parent Hot Folder changed.
    1. Before the fix: When the owner of a parent Hot Folder was changed, the exclude Hot Folder inside the parent Hot Folder was still tagged to the previous owner.
    2. After the fix: The parent of the excluded Hot Folder changes automatically to the owner of the parent Hot Folder.
  7. Fixed the alignment of all the columns in the Activities tab, Files tab, Hot Folder Cabinets list and List Enterprise Application page.
    1. Before the fix: The alignment was affected when zoomed in or out.
    2. In case of large Activity IDs and File IDs, the number spilled in the neighbouring column.
    3. After the fix: The alignment is adjusted according to the screen size and resolution, and large values do not overlap or spill in the neighbouring columns.
  8. Removed the Active Directory Operating System Version field from the AD Configuration page as it does not accept any other values apart from 2000, 2003 and 2008. 
    1. As the field is now obsolete and did not accept any other value, it has been removed from the page.
  9. Fixed the issue where the UI of the error page, stating that the browser is unsupported, was not properly displayed.
  10. Fixed the issue where when a file owner searched for a file in the Policy Server using the File ID, an error message was displayed instead of successfully displaying the file in the results.
  11. Fixed the issue where a redistributor was able to approve access request even after the rights of the redistributor on the protected file had expired.
    1. Before the fix: When an unauthorized user requests for access to a protected file, the request is sent to the owner as well as redistributors of the file.
    2. The redistributor, with expired rights on the protected file, was able to approve such access request.
    3. This resulted in the expiration of the link for the owner and other redistributors with rights to the file.
    4. Additionally, the requestor did not receive access to the file.
    5. After the fix: The redistributor, with expired rights on the protected file, cannot approve access request on a protected file.
    6. An error message will be displayed instead.
  12. Fixed the issue where the user was able to see the buffer file in an Unsupported Browser with the options to either open the protected file or download the agent.
    1. Before the fix: When a user opened an HTML wrapped file in an unsupported browser, the buffer file was displayed with options to open the file in the Seclore Online Editor or to download the agent.
    2. After clicking either of the two options, the Unsupported Browser page was displayed.
    3. After the fix: The Unsupported Browser page is displayed when a user tries to open an HTML wrapped protected file in an unsupported browser.


Seclore for O365

  1. Introducing collaboration of MS O365 and Seclore for enhanced security of your documents on the cloud.
    1. Now, you can edit and save your changes (if you have the required permissions) in the documents shared through SharePoint Online and OneDrive.
    2. No need to download to edit shared documents from SharePoint Online and OneDrive.
    3. External users can also edit documents if they have Edit permission from the document links shared with them.
    4. Requires Policy Server 3.8.0.0 or higher
    5. Requires Seclore Online 3.1.0.0 or higher
  2. Support for edit and save back for Seclore-protected files in O365.
    1. Microsoft Azure authentication is introduced in O365.
    2. Now users can directly login and access Seclore-protected files using their Microsoft IDs.
    3. As mentioned in the ticket above, they can edit and save the changes back in the document directly on SharePoint Online and OneDrive.


Email Auto Protector 3.3.0.0

  1. Support for protection of non-standard file formats (Universal Protection).
    1. Admins can include non-standard file formats while creating rules in the Email Auto Protector rule console.
    2. These files will be provided with full control and they will be HTML wrapped for added protection.


Mail Portal 3.1.0.0

  1. Introducing Universal Protection for protecting any file format with sensitive enterprise information.
    1. Earlier, among the file sent by an external user, only a limited number of file formats were received by the internal user as protected.
    2. With this new feature, all file formats will be received by the internal user protected and HTML wrapped.
    3. For standard file formats (i.e. MS Office, PDF, Text and Images) Advanced Protection enforces WHO (users or groups), WHAT (Read, Edit, Print etc), WHEN (date and time expiry) and WHERE (device and location).
    4. For all other formats, Universal Protection enforces WHO (users or groups), WHEN (date and time expiry) and WHERE (device and location).
    5. When an authorized recipient opens a file with Universal Protection, he/she is granted Full Control permission.
    6. The Universal Protected file opens in read-only mode and if the user edits and tries to save the file, he/she will be prompted to ‘Save As’.
    7. Authorized recipients can also Unprotect these files.
    8. Universal Protection will automatically apply the HTML wrapper i.e. Sample.mp4 will be protected as Sample.mp4.html.
    9. This feature needs to be explicitly enabled on the Policy Server along with the HTML wrapping feature.
    10. The Policy Server also supports Agentless Access for these files, that allows authorized users to get an unprotected copy of the document without using an agent.


Seclore Decryption Server 3.1.0.0

  1. Support for non-standard file formats (Universal Protection).
    1. Non-standard file formats will also be unprotected in addition to the standard file formats.


PST Decryption Server 1.1.0.0

  1. Support for non-standard file formats (Universal Protection).
    1. Non-standard file formats will also be unprotected in addition to the standard file formats.


Server SDK 4.4.0.0

  1. Fixed the issue where email was sent with unprotected attachments when HTML wrap feature was disabled in the Policy Server and email body protection was enabled in Email Auto Protector rules.
    1. Before the change: When an email with attachments were protected and sent with the HTML wrap feature disabled in the Policy Server and email body protection enabled in Email Auto Protector ruled, the email was sent but with the attachments unprotected.
    2. After the change: The email is sent in such a scenario with the email body unprotected and the attachments protected but unwrapped.
  2. Introducing support for Universal Protection where non-standard file formats will be protected using full control rights and HTML wrapped for added security.
  3. Support for updated HTML buffer files.
Login or Signup to post a comment