Get Session Challenge 命令详情
更新时间：2025/06/26
在Gitcode上查看源码修订记录
| openUBMC版本号 | 修订日期 | 修订人 | 修订内容 |
|---|---|---|---|
| 25.06 | 2025/06/26 | pengqiang-gs | 初稿，新增命令详情 |
基本信息
功能说明
标准命令，获取挑战之后的会话标识。 This command is sent in unauthenticated format. While a Session ID is returned from the response to the Get Session Challenge command, the session must be activated using the Activate Session command before it can be used for sending other authenticated commands.
权限
ReadOnly
命令信息
请求信息
| 字节顺序 | 域取值说明 |
|---|---|
| 1 | Authentication Type for Challenge [7:4] - reserved [3:0] - requested Authentication Type 0h = none. No hashing or authentication done on session packets. Authentication Code field is not present. 1h = MD2 2h = MD5 3h = reserved 4h = straight password / key 5h = OEM proprietary all other = reserved |
| 2 | User Name. Sixteen-bytes. All 0’s for null user name (User 1) |
响应信息
| 字节顺序 | 域取值说明 |
|---|---|
| 1 | Completion Code 81h = invalid user name 82h = null user name (User 1) not enabled |
| 2:5 | Temporary Session ID. LS byte first. This is a provision for a temporary Session ID that can be given out to parties that have requested challenges, but have not yet activated a session. It can be used as a mechanism to help protect against denial of service attacks by grabbing all free Session IDs. |
| 6:21 | Challenge string data |
命令样例
样例1：获取当前 BMC 的会话
- 请求：``
- 响应：