From 07fd2aa9a58cc86dd447826865ca317cad92fd45 Mon Sep 17 00:00:00 2001
From: Mounir IDRASSI <mounir.idrassi@idrix.fr>
Date: Mon, 14 Jan 2019 10:42:19 +0100
Subject: Update Release Notes and language files for version 1.24-Beta1. Add
 signed Windows drivers.

---
 Translations/Language.ru.xml | 2 ++
 1 file changed, 2 insertions(+)

(limited to 'Translations/Language.ru.xml')

diff --git a/Translations/Language.ru.xml b/Translations/Language.ru.xml
index a63e91d4..5790e18a 100644
--- a/Translations/Language.ru.xml
+++ b/Translations/Language.ru.xml
@@ -1429,6 +1429,8 @@
     <entry lang="ru" key="CONFIRM_ALLOW_WINDOWS_DEFRAG">ВНИМАНИЕ: Дефрагментация несистемных разделов/дисков может способствовать утечке метаданных об их содержимом или вызывать проблемы со скрытыми томами, которые могут в них находиться.\n\nПродолжить?</entry> 
     <entry lang="en" key="VIRTUAL_DEVICE">Virtual Device</entry>
     <entry lang="en" key="MOUNTED_VOLUME_NOT_ASSOCIATED">The selected mounted volume is not associated with its drive letter in Windows and so it can not be opened in Windows Explorer.</entry>
+    <entry lang="en" key="IDC_CLEAR_KEYS_ON_NEW_DEVICE_INSERTION">Clear encryption keys from memory if a new device is inserted</entry>
+    <entry lang="en" key="CLEAR_KEYS_ON_DEVICE_INSERTION_WARNING">IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">
-- 
cgit v1.2.3