EncryptionConfigurationDialog EncryptionConfigurationDialog 0 0 445 481 Encryption Configuration unnamed 11 6 encryptMessagesBG Encryption unnamed 11 6 encryptionAlgorithmLA Encryption &algorithm: encryptionAlgorithmCO storeEncryptedCB Store saved messages &encrypted false Check to store messages encrypted <qt> <h1>Store Messages Encrypted</h1> When this box is checked, sent messages are stored encrypted like they were sent. This is not recommended, as you will not be able to read the messages any longer if a necessary certificate expires. <p> However, there may be local rules that require you to turn this option on. When in doubt, check with your local administrator. </qt> encryptAllPartsRB Encr&ypt all message parts true Check to have all message parts encrypted by default <qt> <h1>Encrypt All Message Parts By Default</h1> If this option is selected, all parts of a message (i.e. the main message body and all attachments) are encrypted by default. <p> This is a default setting, you can still override it for each individual message. </qt> askEachPartRB Ask &before encrypting each part Check to be asked for each part whether to encrypt <qt> <h1>Ask Before Encrypting Each Part</h1> When this option is selected, you will be asked for each part of the message (i.e. the main message body as well as all attachments) individually whether you want the part to be encrypted. </qt> dontEncryptRB &Don't encrypt messages Check for not encrypting a message by default <qt> <h1>Don't Encrypt Messages</h1> If this option is selected, messages are not encrypted by default. <p> This is a default setting, you can still override it for each individual setting. </qt> Triple-DES encryptionAlgorithmCO Selects the encryption algorithm <qt> <h1>Encryption Algorithm</h1> An algorithm is a description for the computer on how it should perform a certain task. The encryption algorithm describes how the computer applies your recipient's key to your message so that only the intended receiver can read the message. <p> The selection of a certain encryption algorithm determines how easy or how difficult it is to intercept and read a message. However, all algorithms provided in the SPHINX environment are considered to be very safe. Generally, the default will work just fine here. <p> This setting is a default, you can override it for each individual message. </qt> Spacer19 Horizontal Expanding 20 20 certBG Certificates unnamed certificatePathCheckBG NoFrame unnamed 0 Spacer1_2_2 Horizontal Fixed 20 20 pathMayEndLocallyCB Check can end with locally sa&ved certificate Check to end with locally saved certificate. <qt> <h1>Certificate Check Can End With Locally Saved Certificate</h1> If this option is checked, the check of the certificate chain can end with a locally saved certificate. <p> Locally saved certificates are your own certificates as well as the certificates of communication partners and certification authorities (CAs). </h1> alwaysCheckRootRB Always c&heck to root certificate true Check here to check up to the root certificate <qt> <h1>Always Check Certificate Path To Root Certificate</h1> If this option is turned on, the certificate path belonging to the receiver's certificate will always be checked all the way to the root certificate. </qt> checkCertificatePathCB Check certificate &path true Check here to have the whole certificate path checked <qt> <h1>Check Certificate Path</h1> If this option is turned on, the whole path of the receiver's certificate up to the root will be checked. <p> Note that it is not possible to turn off checking the receiver's certificate itself. </qt> crlBG NoFrame unnamed 0 useCRLsCB &Use certificate revocation lists (CRLs) true Check to use CRLs <qt> <h1>Use Certificate Revocation Lists (CRLs)</h1> A certificate revocation list contains certificates that have been withdrawn and should not be used for encryption purposes any longer. A user may wish to have his or her certificate revoked because he or she suspects that the certificate's integrity has been compromised (e.g. somebody has guessed the PIN). <p> It is recommended to use CRLs for maximum security. In the configuration dialog for certificate and CRL management, you can select where to retrieve the CRLs from. </qt> warnCRLExpireCB Warn if CRL e&xpires in less than true Check to be warned if a CRL expires in the near future <qt> <h1>Warn If CRL Expires In The Near Future</h1> If this box is checked, you will be warned if one of the CRLs you are using is about to expire in the near future. </qt> warnCRLExpireSB days 999 7 Number of days before warning <qt> <h1>Warn If CRL Expires In The Near Future</h1> In this field you can specify how soon before a CRL expires you are warned about this expiry. <p> The recommended setting for the SPHINX environment is 7 days. </qt> Spacer1_2 Horizontal Fixed 20 20 Spacer8 Horizontal Expanding 20 20 alwaysEncryptToSelfCB Always encrypt &to self true Check to have encrypted messages also encrypted using your own key. <qt> <h1>Always encrypt to self</h1> If this box is checked, encrypted messages sent by you will also be encrypted using your own key. <p> It is recommended to leave this option turned on to enable you to read the messages you have sent. </qt> encryptionSettingsBG Warnings unnamed 11 6 warnUnencryptedCB &Warn when trying to send unencrypted messages true Check to be warned when sending unencrypted messages. <qt> <h1>Warn When Trying To Send Unencrypted Messages</h1> If this box is checked, you will be warned when you try to send parts of or the whole message unencrypted. <p> It is recommended to leave this option turned on for maximum integrity. </qt> warnChainCertificateExpiresSB days 999 14 Select the number of days here <qt> <h1>Warn If A Certificate In The Chain Expires</h1> Select the minimum number of days all certificates in the chain should be valid without issuing a warning. <p> The recommended SPHINX setting is 14 days. </qt> warnChainCertificateExpiresCB Warn if a certificate in &the chain expires in less than true Check to be warned if the certificate expires soon <qt> <h1>Warn If Certificate Expires</h1> If this option is checked, then you will be warned when trying to use a certificate for encrypting that expires within the specified amount of days. <p> It is recommended to keep this option turned on to avoid using certificates that expire in the near future. </qt> warnReceiverCertificateExpiresSB days 999 14 Select the number of days here <qt> <h1>Warn If Encryption Certificate Expires</h1> Select the minimum number of days the encryption certificate should be valid without issuing a warning. <p> The recommended SPHINX setting is 14 days. </qt> warnReceiverCertificateExpiresCB Warn if &receiver certificate expires in less than true Check to be warned if the certificate expires soon <qt> <h1>Warn If Certificate Expires</h1> If this option is checked, then you will be warned when trying to use a certificate for encrypting that expires within the specified amount of days. <p> It is recommended to keep this option turned on to avoid using certificates that expire in the near future. </qt> Spacer7 Horizontal Expanding 20 20 warnReceiverNotInCertificateCB Warn if receiver's email address is &not in certificate true Check to be warned if the address is not in the certificate <qt> <h1>Warn If Receiver's Email Address Is Not In Certificate</h1> If this option is checked, a warning is issued if the email address of the receiver is not contained in the certificate used for encrypting. <p> It is recommended to leave this option turned on for maximum security. </qt> Spacer17 Vertical Expanding 20 20 warnReceiverCertificateExpiresCB toggled(bool) warnReceiverCertificateExpiresSB setEnabled(bool) warnChainCertificateExpiresCB toggled(bool) warnChainCertificateExpiresSB setEnabled(bool) checkCertificatePathCB toggled(bool) alwaysCheckRootRB setEnabled(bool) checkCertificatePathCB toggled(bool) pathMayEndLocallyCB setEnabled(bool) useCRLsCB toggled(bool) warnCRLExpireCB setEnabled(bool) useCRLsCB toggled(bool) warnCRLExpireSB setEnabled(bool) warnCRLExpireCB toggled(bool) warnCRLExpireSB setEnabled(bool) encryptAllPartsRB askEachPartRB dontEncryptRB warnUnencryptedCB useCRLsCB warnCRLExpireCB warnCRLExpireSB encryptionAlgorithmCO warnReceiverCertificateExpiresCB warnReceiverCertificateExpiresSB warnChainCertificateExpiresCB warnChainCertificateExpiresSB warnReceiverNotInCertificateCB storeEncryptedCB checkCertificatePathCB alwaysCheckRootRB pathMayEndLocallyCB