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

-equivalenceAlgorithms Select Error #113

Closed
5angjun opened this issue May 6, 2024 · 6 comments
Closed

-equivalenceAlgorithms Select Error #113

5angjun opened this issue May 6, 2024 · 6 comments

Comments

@5angjun
Copy link

5angjun commented May 6, 2024

image

Hi there.

I'm someone who really interested in your project.

But i think there is bit a error in README.md.

When i try to run handshake test, that would be error in parameter.

How should i do?

I have a trouble because i can't known this whole source code.

Can you give some ideas?

Thanks.

@kostis
Copy link
Contributor

kostis commented May 6, 2024

Hi @5angjun and thanks for your interest in DTLS-Fuzzer!

The README file clearly needs some care and affection (i.e. a major update) because it corresponds to version of the tool before some major updates to its code base took place. So, some examples there may not work as described anymore.

Still, in this particular case the parsing problem you experienced was caused by some extraneous trailing white space characters in the args/openssl/learn_openssl_server_psk file. A commit I just pushed fixes that issue. Please try it again and see whether things now work or fail at some other point for you and let us know.

@5angjun
Copy link
Author

5angjun commented May 7, 2024

Thanks for suggesting the solution. But the following error occurred:
image

Can you test openssl in readme.md in a completely clean state?
I seems unstable in current version. but i can execute it in usenix20 branch.

@5angjun
Copy link
Author

5angjun commented May 7, 2024

I can run without -queries options. But i don't know that it ensure the perfect model learning.
Because it doesn't end until now. ( I start learning before 2hours ago...)

Can you give me a some solution?
image

@kostis
Copy link
Contributor

kostis commented May 7, 2024

Great that you are achieving some progress!

Quite often, when dealing with (complex) protocol implementations, there is no such thing as perfect model learning; the learning is usually approximate, for a number of reasons, but the learned model (the last hypN.dot file produced) is quite accurate and useful.

Instead of using a fixed number of queries (the -queries option you have tried) to force learning to terminate, you can try to use a limited number of rounds (-roundLimit option, i.e. the N above) or simply interrupt the learning process after some time (e.g. 10 hours) and use the last hypothesis which has been generated.

@5angjun
Copy link
Author

5angjun commented May 8, 2024

Thanks for helping me.

I finally got the hypothesis through this.

Really thanks.

image

@5angjun 5angjun closed this as completed May 8, 2024
@actyp
Copy link

actyp commented May 12, 2024

There has been a point, when ProtocolState-Fuzzer was integrated in this repo.

The usenix20-artifact branch is before the integration and the master branch is after the integration, so they have some significant changes.

The -queries parameter, for instance, was renamed after the integration to -eqvQueries (or the full name -equivalenceQueryBound), as it refers to the maximum number of queries of certain equivalence algorithms. This is specified in the ProtocolState-Fuzzer repo.

That is why, an error was raised if you used the -queries parameter in the main branch. If you want, you can use -eqvQueries instead.

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

3 participants