hackjutsu/Lepton

"SELF_SIGNED_CERT_IN_CHAIN" error behind self-signed SSL network

Open

#250 建立於 2017年12月12日

在 GitHub 查看
 (14 留言) (0 反應) (0 負責人)JavaScript (9,902 star) (502 fork)batch import
help wantedmore information needed

描述

The more we know about your system and use case, the more easily and likely we can help.

Environment info

  • OS: Win 10

  • App Version (Command/Ctrl + ,): Who knows / Doesn't matter: Who knows: Theres no way to tell from the application when its stuck not logging in Doesn't matter: The behavior is the same between 1.5.0 and 1.5.1-alpha

Description of the problem / feature request / question:

No version of Lepton has never logged in to GitHub for me. I have deleted the C:\Users<username>\AppData\Roaming\Lepton\ folder multiple times - it has zero effect

If possible, provide a sample gist or screenshot:

image

If possible, provide the log files

  • Mac: ~/Library/Application Support/Lepton/logs
  • Windows: C:\Users\<username>\AppData\Roaming\Lepton\logs
  • Linux: ~/.cached/Lepton/logs

The debug mode is recommended when producing the logs. You can send your log file to cosmo.lepton@gmail.com if don't want to post it here.

2017-12-12T22.45.02.250Z.log

貢獻者指南

技術棧
javascriptnodejselectron
領域
authenticationdesktop
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
Node.jsElectron basicsSSL/TLS
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
Investigate the error handling in Lepton's network requests, particularly in the GitHub authentication flow. The log file shows the certificate error; check if the app uses the `request` library or Node's `https` module. Consider adding an option to ignore self signed certificates or use environment variable `NODE TLS REJECT UNAUTHORIZED`. Refer to the log file attached in the issue and any related discussions in the comments.