MoonshotAI / MoonshotAI/kimi-cli

Kimi Code CLI 1.37.0 在 Ubuntu 22.04 + OpenSSL 3.0 环境下的硬编码兼容性问题

Open
#1,986 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
11.4k
Forks
1.3k
Avg merge
9h 47m
Merged PRs (30d)
2

Description

What version of Kimi Code CLI is running?

kimi, version 1.37.0

Which open platform/subscription were you using?

Ubuntu 22.04

Which model were you using?

kimi-for-coding

What platform is your computer?

Linux 6.8.0-107-generic x86_64 x86_64

What issue are you seeing?

(base) ran@ran-Ubuntu:~/cloudapi$ "/home/ran/.config/Code/User/globalStorage/moonshot-ai.kimi-code/bin/kimi/kimi"
╭───────────────────────────────────────────────╮
│ │
│ ▐█▛█▛█▌ Welcome to Kimi Code CLI! │
│ ▐█████▌ Send /help for help information. │
│ │
│ Directory: ~/cloudapi │
│ Session: 9a5e9109-3a35-4ec0-92e6-6ea431877c │
│ 83 │
│ Model: not set, send /login to login │
│ │
│ Tip: Spot a bug or have feedback? Type /fee │
│ dback right in this session — every report │
│ makes Kimi better. │
│ │
╰───────────────────────────────────────────────╯
Select a platform (↑↓ navigate, Enter select, Ctrl+C cancel):

  1. Kimi Code
    2. Moonshot AI Open Platform (moonshot.cn)
    3. Moonshot AI Open Platform (moonshot.ai)
    Login failed: [Errno 1] [SSL: SSLV3_ALERT_BAD_RECORD_MAC] sslv3 alert bad record mac (_
    ssl.c:2711)
What steps can reproduce the bug?

我在VScode中login,但是遇到了SSL问题

What is the expected behavior?

No response

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported login flow with Kimi Code CLI 1.37.0 on Ubuntu 22.04 and the stated Linux environment, then inspect the CLI's login path around the reported SSL error. Done means the same platform can complete login without the SSLV3_ALERT_BAD_RECORD_MAC failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, python, ubuntu
Domain
authentication, cli, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.