SAS...ken(3tcl)

💖 SASL::XGoogleToken — the 3tcl era 💖

okay bestie, welcome to the manual page for SASL::XGoogleToken, straight out of the SASL manual set (section 3tcl, iykyk). this is the one that handles XGoogleToken auth, and yes, the NAME line literally says it's "Implementation of SASL NTLM mechanism for Tcl" — a whole ✨ situation ✨. let's get into it 🫶

---

🌸 NAME 🌸

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

---

✨ SYNOPSIS ✨

package require Tcl 8.5 9

package require SASL::XGoogleToken ?1.0.2?

that ?1.0.2? is optional, so don't stress, you can just grab the default 💅

---

🦋 DESCRIPTION 🦋

so this package is the plug that gives you the XGoogleToken authentication mechanism for the Simple Authentication and Security Layer (SASL). it's giving authentication, it's giving SASL, it's serving exactly what it says on the tin.

fr fr though — go read the documentation for the package sasl for the details. that's where the real tea is 💖

---

🔐 TLS SECURITY CONSIDERATIONS 🔐

bestie, listen. this package leans on the TLS package to handle all the security for https urls and other socket connections. that's the whole vibe. 🎀

BUT — and this is the important part — policy decisions like which protocols to support and which ciphers to use? not the responsibility of TLS, and not the responsibility of this package either. nope. that's on whichever application is using the package, and it's lowkey gonna be influenced by the set of servers your app is talking to. it's all connected, bestie 🌈

for example — and this one is a whole saga — in light of the recent POODLE attack discovered by Google:

http://googleonlinesecurity.blogspot.co.uk/2014/10/this-poodle-bites-exploiting-ssl-30.html

many servers will disable support for the SSLv3 protocol. to handle that change, the applications using TLS must be patched — not this package, and not TLS itself. periodt. and sometimes the patch is literally as simple as generally activating tls1 support, like this:

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

... your own application code ...

that's it. that's the fix. iconic 🧚

---

👑 AUTHORS 👑

Pat Thoyts

(we love them, we thank them, no cap 💜)

---

💀 BUGS, IDEAS, FEEDBACK 💀

okay so real talk — this document, and the package it describes, will undoubtedly contain bugs and other problems. undeniably. it's giving "software". 😭 please report them in the category sasl of the Tcllib Trackers:

http://core.tcl.tk/tcllib/reportlist

also please report any ideas for enhancements you may have for either the package and/or the documentation. we want the glow-up 🫶

when you're proposing code changes, please provide unified diffs, i.e. the output of diff -u.

also note — and this is the key detail — attachments are strongly preferred over inlined patches. you can make an attachment 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. go forth and attach, bestie ✨

---

🎀 KEYWORDS 🎀

SASL, XGoogleToken, authentication

---

🌈 CATEGORY 🌈

Networking

---

💅 COPYRIGHT 💅

Copyright (c) 2006, Pat Thoyts <patthoyts@users.sourceforge.net>

---

and that's the whole page, bestie 🦋 this was tcllib, version 1.0.2, section 3tcl, SASL::XGoogleToken — slay, stay authenticated, and remember: patch your application, not this package 💖✨🎀