Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use branch master and feature/tlsv1.3 to scan the same ip+port, the results of secure_renegotiation and scts are different #342

Open
chushuai opened this issue Jul 29, 2022 · 1 comment

Comments

@chushuai
Copy link
Contributor

Use branch master and feature/tlsv1.3 to scan the same ip+port, The results of secure_renegotiation and scts are different

func TestTls(t *testing.T){
	tests := []string{ "138.201.124.182:10250"}
	for _, test := range tests {
		conn, err := Dial("tcp", test, &Config{
			InsecureSkipVerify: true,
		})
		data, _ := json.Marshal(conn.GetHandshakeLog())
		fmt.Println(string(data))
		if err != nil {
			fmt.Println("failed to connect: " + err.Error())
		}
	}

}

image

@mzpqnxow
Copy link
Contributor

mzpqnxow commented Sep 7, 2023

The tls1.3 branch includes tls1.3 support and also includes other enhancements- anything added to the upstream golang tls code since the (very old) tls implementation was lifted from upstream- at least 5 years ago

This includes (at least) early renegotiation handling. I'm not certain but I believe the portable ciphers profile is also exclusive to the tls1.3 branch for no particular reason aside from the fact that those interested in "better" tls support were using that branch

You can see part of this if you track the zcrypto portion of zmap/zgrab2#334

tl; dr; this is expected behavior as far as I know

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants