Search results

  • * To achieve its design goal of [[w:Authenticated encryption|authenticated encryption]], gocryptfs implements a AES-EME encryption mode (for filenames * [[RFC:5297|RFC 5297]] Synthetic Initialization Vector (SIV) Authenticated Encryption Using the Advanced Encryption Standard (AES)
    5 KB (779 words) - 15:40, 22 January 2022
  • ...to avoid relaying. In order to prevent anonymous users from spamming, only authenticated and trusted users will be able to send emails. Using this configuration implies that only authenticated users can send mails. You can see this from {{ic|smtpd_client_restrictions}
    6 KB (919 words) - 10:15, 29 June 2021
  • * Para alcançar seu objetivo de [[w:Authenticated encryption|encriptação autentificada]], gocryptfs implementa um modo de e ...tools.ietf.org/html/rfc5297 RFC5297] Synthetic Initialization Vector (SIV) Authenticated Encryption Using the Advanced Encryption Standard (AES)
    5 KB (790 words) - 22:06, 15 April 2021
  • * Para lograr su objetivo de diseñar un [[wikipedia:Authenticated encryption|cifrado autenticado]], gocryptfs implementa un modo de cifrado A ...tools.ietf.org/html/rfc5297 RFC5297] Synthetic Initialization Vector (SIV) Authenticated Encryption Using the Advanced Encryption Standard (AES)
    6 KB (864 words) - 13:57, 6 August 2020
  • If you are receiving the "Network error: Peer certificate cannot be authenticated with given CA certificates", try adding the following line to your .config/
    3 KB (434 words) - 15:38, 3 October 2021
  • # and restrict it to local clients and SASL authenticated clients only
    4 KB (495 words) - 17:05, 3 July 2021
  • ...hich provide to DNS clients (resolvers) origin authentication of DNS data, authenticated denial of existence, and data integrity, but not availability or confidenti
    4 KB (572 words) - 10:30, 8 May 2021
  • The Git protocol is not encrypted or authenticated, and only allows read access.
    5 KB (705 words) - 12:26, 16 January 2022
  • With this it is important to note that messages coming from authenticated clients are treated (by default) by the same ACL as messages coming from ot ...ents being an open relay. This setup has multiple security flaws (e.g. all authenticated users may use any mail address). If added to an existing configuration, it
    16 KB (2,496 words) - 14:42, 29 July 2021
  • Now only authenticated users can connect. To add users to the PureDB we need to create a {{ic|/etc
    4 KB (684 words) - 13:03, 5 September 2021
  • === Not authenticated to mount filesystems ===
    12 KB (1,871 words) - 07:23, 21 January 2022
  • -- Data is authenticated: yes -- Data is authenticated: no
    13 KB (1,899 words) - 21:47, 6 January 2022
  • -- Data is authenticated: yes -- Data is authenticated: no
    12 KB (1,689 words) - 18:19, 16 June 2021
  • ...o the following steps. Note that participants to the meeting are still not authenticated! ...o the following steps. Note that participants to the meeting are still not authenticated!
    19 KB (2,544 words) - 21:15, 17 May 2021
  • ...does the same, except it increments a counter when a code is successfully authenticated. To handle desynchronization of the counter, the authenticating party can a
    5 KB (687 words) - 08:58, 17 December 2021
  • 8 KB (563 words) - 07:21, 22 January 2022
  • At least one of the client and the server, and optionally both, should be authenticated. Either a pre shared secret, or a key and certificate pair, can be used for
    6 KB (868 words) - 14:50, 23 August 2021
  • === Not authenticated to mount filesystems ===
    14 KB (761 words) - 07:24, 21 January 2022
  • Now you can be authenticated with ''user2'' as username and ''123'' for password.
    6 KB (859 words) - 14:54, 17 January 2022
  • -- Data is authenticated: yes -- Data is authenticated: no
    22 KB (780 words) - 18:41, 23 December 2021

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)