logo
Free, unlimited AI code reviews that run on commit
git-lrc git-lrc GitHub Install Now We'd appreciate a star git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt

SASL::XGoogleToken - Implementation of SASL NTLM mechanism for Tcl

Authors

       Pat Thoyts

Bugs, Ideas, Feedback

       This  document,  and  the package it describes, will undoubtedly contain bugs and other problems.  Please
       report such in the category sasl of the TcllibTrackers  [http://core.tcl.tk/tcllib/reportlist].   Please
       also report any ideas for enhancements you may have for either package and/or documentation.

       When proposing code changes, please provide unifieddiffs, i.e the output of diff-u.

       Note  further  that  attachments  are strongly preferred over inlined patches. Attachments can be made by
       going to the Edit form of the ticket immediately after its creation, and then using the left-most  button
       in the secondary navigation bar.

Category

       Networking

Description

       This  package  provides  the  XGoogleToken  authentication  mechanism  for  the Simple Authentication and
       Security Layer (SASL).

       Please read the documentation for package sasl for details.

Keywords

       SASL, XGoogleToken, authentication

Name

       SASL::XGoogleToken - Implementation of SASL NTLM mechanism for Tcl

Synopsis

       package require Tcl8.59

       package require SASL::XGoogleToken?1.0.2?

________________________________________________________________________________________________________________

Tls Security Considerations

       This package uses the TLS package to handle the security for https urls and other socket connections.

       Policy decisions like the set of protocols to support and what ciphers to use are not the  responsibility
       of  TLS,  nor  of  this  package  itself  however.   Such  decisions  are the responsibility of whichever
       application is using the package, and are likely influenced by the set of servers  the  application  will
       talk to as well.

       For        example,        in        light        of        the        recent        POODLEattack
       [http://googleonlinesecurity.blogspot.co.uk/2014/10/this-poodle-bites-exploiting-ssl-30.html]  discovered
       by  Google  many  servers  will  disable  support  for  the  SSLv3  protocol.   To handle this change the
       applications using TLS must be patched, and not this package, nor TLS itself.  Such a  patch  may  be  as
       simple as generally activating tls1 support, as shown in the example below.

                  package require tls
                  tls::init -tls1 1 ;# forcibly activate support for the TLS1 protocol

                  ... your own application code ...

See Also