Redian新闻
>
authentication and secret key establishment
avatar
authentication and secret key establishment# Security - 系统安全
c*o
1
I have a client/server application need to communicate securely. The client
needs to input username/passwd to access the server and the client knows the
public key of the server (Ku). My two-way authentication and secret key
establishment protocol is as follows:
1. The client sends Ku(username||passwd||N1) to the server. N1 is a random
number generated by the client in this session.
2. The server decrypts the message using the private key and verify the
username/passwd by consulting a database.
avatar
c*a
2
What about a replay attack?
N1 seems redundant and insecure here. U may refer to Kerberos for session key
and ticket issueing.

【在 c*****o 的大作中提到】
: I have a client/server application need to communicate securely. The client
: needs to input username/passwd to access the server and the client knows the
: public key of the server (Ku). My two-way authentication and secret key
: establishment protocol is as follows:
: 1. The client sends Ku(username||passwd||N1) to the server. N1 is a random
: number generated by the client in this session.
: 2. The server decrypts the message using the private key and verify the
: username/passwd by consulting a database.

avatar
c*o
3
N1 is against replay attack because it's a random number each time. Also it's
used to authenticate the server since only the server can decrypt the first
package containing N1.
Kerberos is too complex for this simple case, that's why I disign this
protocol.

【在 c*****a 的大作中提到】
: What about a replay attack?
: N1 seems redundant and insecure here. U may refer to Kerberos for session key
: and ticket issueing.

相关阅读
logo
联系我们隐私协议©2024 redian.news
Redian新闻
Redian.news刊载任何文章,不代表同意其说法或描述,仅为提供更多信息,也不构成任何建议。文章信息的合法性及真实性由其作者负责,与Redian.news及其运营公司无关。欢迎投稿,如发现稿件侵权,或作者不愿在本网发表文章,请版权拥有者通知本网处理。