Virtru experienced a notice incident on October 31, 2023 affecting Virtru Secure Email Clients, lasting 5d 21h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 31, 2023, 07:49 PM UTC
We have been made aware of an issue where users are unable to access certain Drive files via a shared hyperlink. The direct hyperlink never brings the user to the specific file. The workaround is to go to Drive and search for the file directly, then click to open it. The issue only occurs when trying to access a file shared via a direct link. We are working to resolve this issue as soon as possible and will provide another update as soon as we have one.
- identified Oct 31, 2023, 11:26 PM UTC
We have identified the issue and are continuing to work on a fix. We will provide another update as soon as we have one.
- identified Nov 01, 2023, 02:13 PM UTC
We are continuing to work on a fix for this issue. We will provide another update as soon as we have one.
- identified Nov 01, 2023, 06:46 PM UTC
We have engineered a potential fix. We are working to test and validate the fix now. As soon as it passes testing, we will begin the process of releasing the update.
- identified Nov 01, 2023, 10:45 PM UTC
We are addressing a few issues we found in testing. We will provide another update as soon as we have one.
- identified Nov 02, 2023, 02:29 PM UTC
We are continuing to work through some issues with the release build that need to be addressed before we can release. We are still working to get a fix out ASAP and will continue to provide updates. Thanks for your patience and understanding. As a reminder: The workaround is to go to Drive and search for the file directly, then click to open it. The issue only occurs when trying to access certain file types shared via a direct link.
- identified Nov 02, 2023, 09:13 PM UTC
We are continuing to work on a fix for the issue.
- identified Nov 03, 2023, 04:03 PM UTC
We have addressed the remaining blockers and are retesting everything as we speak. As soon as that is complete, we plan to submit this to the Chrome Store for review. We will provide another update by end of day.
- identified Nov 03, 2023, 08:34 PM UTC
The build with the fix is almost complete and through the quality assurance process. Once complete, we will submit it to the Chrome Store asap (likely over the weekend). If all goes to plan, we expect to release the fix early next week.
- monitoring Nov 06, 2023, 03:16 PM UTC
A fix has been implemented and released in v5.5.2. We continue to monitor the situation to ensure the issue is fully resolved.
- resolved Nov 06, 2023, 05:22 PM UTC
This incident has been resolved.