HomeSort by relevance Sort by last modified time
    Searched refs:close_notify (Results 1 - 9 of 9) sorted by null

  /external/chromium_org/net/third_party/nss/ssl/
ssl3prot.h 77 close_notify = 0, enumerator in enum:__anon14289
sslsecur.c 1103 * required to send a close_notify alert before closing the write side
1104 * of the connection. The other party MUST respond with a close_notify
1107 * of the close to wait for the responding close_notify alert before
1110 * The second sentence requires that we send a close_notify alert when we
1111 * have received a close_notify alert. In practice, all SSL implementations
1112 * close the socket immediately after sending a close_notify alert (which is
1113 * allowed by the third sentence), so responding with a close_notify alert
1115 * we don't respond with a close_notify alert.
1140 (void) SSL3_SendAlert(ss, alert_warning, close_notify);
1166 (void) SSL3_SendAlert(ss, alert_warning, close_notify);
    [all...]
ssl3con.c     [all...]
  /external/chromium_org/third_party/tlslite/tlslite/
errors.py 44 AlertDescription.close_notify: "close_notify",\
tlsrecordlayer.py 211 if alert.description != AlertDescription.close_notify:
298 This function will block until it has exchanged close_notify
344 AlertDescription.close_notify, AlertLevel.warning)):
349 # close_notify alert, thus leaving us hanging if we're
361 if alert.description == AlertDescription.close_notify:
694 #close_notify. In any case, we're going to close the
696 #a close_notify, but ignore any socket errors, since
699 alert.description == AlertDescription.close_notify:
707 alertMsg.create(AlertDescription.close_notify,
715 AlertDescription.close_notify
    [all...]
constants.py 96 close_notify = 0 variable in class:AlertDescription
tlsconnection.py     [all...]
  /prebuilts/devtools/tools/lib/
bcprov-jdk15on-1.48.jar 
  /prebuilts/tools/common/m2/repository/org/bouncycastle/bcprov-jdk15on/1.48/
bcprov-jdk15on-1.48.jar 

Completed in 325 milliseconds