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

About data input size #13

Open
MrZMN opened this issue Jul 26, 2023 · 1 comment
Open

About data input size #13

MrZMN opened this issue Jul 26, 2023 · 1 comment

Comments

@MrZMN
Copy link

MrZMN commented Jul 26, 2023

Dear contributors,

First of all, thank you so much for providing this amazing tool and kindly share it as open source.

I have a bit string of approx 40 Kbit length. When I was using the tool, I found that the 'Maurer's Universal test' gave a very weird result of -1.0. I subsequently checked the source code and found this boils down to that you have limited the input length to 387 Kbit, as suggested in the NIST codebook.

This makes totally sense to me. However, my question will be that: why not add such length limitations on other tests as well? For example, I notice the suggested minimal length of Spectrum test is 1000 bit, but I didn't see such constraints in the source code. Will this make results of certain cases (i.e., short bit strings as input) invalid?

Thank you again for your contributions! Well done!

Best,
Mo

@MrZMN
Copy link
Author

MrZMN commented Jul 26, 2023

Sry, as a supplement of what I said previously.

What I actually meant was: for certain tests where the input length doesn't follow the NIST suggestions, why not apply strict reject directly (such as the Maurer's Universal test); instead, add paddings (pls correct me if I'm wrong) like what you did in this tool.

Hope this is not a naive question

Best,
Mo

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

1 participant