-
Notifications
You must be signed in to change notification settings - Fork 81
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
handshake_failure #127
Comments
|
thanks @sanderux |
I'm on vacation now, I'll get to your problems first thing next week. |
@tomato42 do you need any more info from me to resolve this issue? |
Sorry for the delay, it doesn't look like I need any more information. In your example code:
it should be
But note that
To perform regular handshake you will need to use the |
i tried with handshakeClientSRP, but received error
i thought maybe because i was missing call to handshakeClientCert, but also fails
|
both for the How is the server you are trying to connect to configured? What cipher and protocol version is negotiated by |
when trying your suggest s_client command i receive
|
did you provide to s_client where to connect to? Full command line for youtube.com looks like this:
|
ok, added the missing params and get the following
|
the ciphers allowed by the server are |
understandable |
it may be because 0.3.8 implements the draft not the final version. I would strongly suggest to update the server, since it looks like it implements only the draft, it would indicate it was't updated since 2002... Lack of TLSv1.2 in such situation is rather minor issue... |
i mixed things up when using tlslite/tlslite-ng updated versions, which comply with RFC 5054, connection fails due to handshake_failure additionally, both the python code above for the client and my server application use the same constants.py file from tlslite directory, so even if the values are updated, they are updated for both |
so if you update both server and client, it still works? then I guess we can close this issue, can't we? |
no, i update both, but it doesn't work after the update |
then what's the problem now? does what's the server and client configuration? |
i do not install the library, rather use the source code in my project |
I know, that's why I'm asking for
preferably, full minimal reproducer - with the way to generate server certificate (if any), server verify db configuration, exact commands or code to run the server and the same for client There already are SRP test cases in the tests run through |
as this is sensitive company info, i will look into the test and test-local examples to try and figure out what is wrong with my implementation. i will close for now, until i find an exact issue or need more help |
Hi @tomato42 i tried again with latest 0.6.0 master (hash e6182d5), connecting with handshakeClientSRP
|
please try to reproduce in clean environment |
make sense as i just copied tlslite-ng over tlslite (which was version 0.3.8) will have to check |
Both |
FYI: I plan to release current master as version 0.6.0 in the next few days to a week (unless we identify that it's a bug in tlslite-ng code that causes your problems) |
i made a minimal server and successfully connected using handshakeClientSRP, so this seems to be an issue with my server implementation closing |
@tomato42 any update when version 0.6.0 will be released? |
as soon as I find an hour of time to prepare packages and push them to pypi |
aaand done. Have fun! :) |
thanks! |
continuing thread from tlslite, issue 113
call to handshakeClientAnonymous fails with handshake_failure
code used and error backtrace
The text was updated successfully, but these errors were encountered: