Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

libssh2_userauth_keyboard_interactive_ex callback and memory allocation

未关闭
#1,078 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
32/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
c

调研方向

Start from libssh2_userauth_keyboard_interactive_ex and the documented contract that callback-supplied password strings are free(3)ed by the library. Compare that path with libssh2_session_init_ex custom allocators and how the session allocator is used elsewhere. Decide whether the library should free via the session allocator (or stop freeing) so a Windows DLL and the app share one heap. There is no named test; done means the callback strings are released with the same allocator the session uses, without breaking existing callers.

由索引模型根据 Issue 内容生成。

描述

bug documentation

Describe the bug

The function libssh2_userauth_keyboard_interactive_ex calls a function in the app to return a set of passwords.

These passwords are documented as: String values will be free(3)ed by the library.

This is a problem on (for example) Windows when libssh2 is used as a DLL, as then they use memory models that cannot be shared between an application and the DLL.

This happens on git master and this issue has probably always existed. It can be circumvented by providing custom memory functions using libssh2_session_init_ex.

主要语言
C
星标
1.6k
派生
646
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

libssh2/libssh2 的其他 Issue

查看 libssh2/libssh2 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。