Windows 3.1 下的 GPT client
source link: https://blog.gslin.org/archives/2023/06/28/11240/windows-3-1-%e4%b8%8b%e7%9a%84-gpt-client/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Windows 3.1 下的 GPT client
前幾天在 Hacker News 上看到「Show HN: WinGPT – AI assistant for Windows 3.1 (dialup.net)」這篇，原始文章「WinGPT: AI Assistant for Windows 3.1」在介紹 Windows 3.1 下的 GPT client。
雖然反差很大 (一個 20 世紀的 GUI 環境配上最新科技)，但從 Hacker News 的討論可以看到，最熱烈的是在 16-bit 環境下實作 TLS 1.3 連線，也就原文裡的這段，提到了他是原生支援 TLS 1.3：
WinGPT connects to the OpenAI API server natively with TLS 1.3, so it doesn't require a proxy on a modern machine to terminate TLS. To see how I did this and some of the challenges, take a look at Modern TLS on 16-bit Windows. (As you'll see on that page, this is not a secure implementation).
不過他不是從零開始解，而是基於 wolfSSL 的實作，因為 wolfSSL 有支援 16-bit compiler，就不需要從零開始：
WolfSSL stood out among the pack as it had explicit 16-bit compiler support while being fully-featured and well-supported.
這是讓人看到會「蛤？」的東西 XD
Related
MaxCDN 將中止 TLS 1.0 的支援
這一槍開的好早，MaxCDN 宣佈因為安全性問題，決定從下個禮拜就中止對 TLS 1.0 的支援：「We're Disabling TLS 1.0 Support on March 18, 2016」。 而且新聞稿也寫的超怪： After sunsetting TLS 1.0 at MaxCDN, we will continue to support TLS 1.1 and TLS 1.2, though we highly recommend TLS 2.0 for your toolset. It’s currently the fastest and most secure cryptographic protocol available, though…
March 12, 2016In "CDN"
Cloudflare 同時支援 TLS 1.2 與 TLS 1.3 的過程
Cloudflare 算是很早就參與 TLS 1.3 發展的廠商。在參與過程中他們希望讓支援 TLS 1.3 draft 的瀏覽器可以開始使用 TLS 1.3 draft，但又不希望因為 draft 頻繁修改而導致本來的使用者受到影響，所以就找了方法讓兩者並存：「Know your SCM_RIGHTS」。 這個方法就是 SCM_RIGHTS，可以讓另外一個 process 存取自己的 file description。 You can use UNIX-domain sockets to pass file descriptors between applications, and like everything else in UNIX connections are files. 所以他們的作法就是先讀取 TLS 裡 Client Hello 的資料，如果裡面有看到想要使用 TLS 1.3…
December 1, 2018In "CDN"
記錄 Firefox/Chrome 在 TLS 的 Session Key 供 Wireshark 使用
以往要看 TLS traffic，需要用 mitmproxy 之類的軟體擋在中間，這需要在 client 端安裝對應的 CA root certificate。 而剛剛在「Decrypting TLS Browser Traffic With Wireshark – The Easy Way!」這篇文章裡面提到了如何讓 Firefox 與 Chrome 記錄下 TLS 的 Session Key，然後倒給 Wireshark 使用。(文章裡有提到需要 dev 版本，不確定是因為新版支援的關係，還是這個功能限制在 dev 版才能用) 方法是在執行時設定 SSLKEYLOGFILE 這個環境變數，指定寫到某個檔案裡。不論是在 Windows & MacOSX & Linux 都一樣。 之後就可以把 Session Key 丟給 Wireshark 處理了，就像是這樣：(原文的範例)
February 14, 2015In "Browser"
Leave a Reply
Your email address will not be published. Required fields are marked *
Comment *
Name *
Email *
Website
Notify me of follow-up comments by email.
Notify me of new posts by email.
To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Learn More)
Post navigation
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK