is it possible to run this code in windows? #145
Comments
bitstream111
changed the title
|
At the moment no. You could attempt to run it via Cygwin if you can find the necessary packages. It is easiest to set up on a Linux machine. A docker container is in the works though which will work on any platform that supports docker. |
|
See the Windows10 branch. @skbhaskarla had success compiling on Windows after finding versions of the libraries needed and compiling with clang. We don't have any compilation instructions available yet though. |
|
can you provide any link where he uploaded his work |
|
The "Windows10" branch is associated with this project. |
|
Thanks for the link @joshuaehill. Is it possible to get a Windows wiki. Should one still find the libraries or should the included dll's take care of everything? The makefile refers to some folders, for example. |
|
I think that the tool's Wiki is available for updates. I don't do either development or testing using this tool on Windows, so I'm not a particularly good source for this information. |
|
@joshuaehill: For better or worse, not everyone is on Lynux. The closest I have handy is a Raspberry Pi and it is not exactly a tool for entropy testing, even its most "powerful" model. One would hope at least to get advice on getting the libraries you have chosen to use in your programs. |
|
It is relatively easy to set up a virtual machine using freely available
software. With an Ubuntu VM you would be able to download all packages by
following the instructions provided.
We have a Dockerfile we can share for running via an Ubuntu container.
Because of these tools, we are not actively working on supporting Windows
natively.
…On Wed, May 12, 2021, 5:37 AM ucb ***@***.***> wrote:
@joshuaehill <https://github.com/joshuaehill>: For better or worse, not
everyone is on Lynux. The closest I have handy is a Raspberry Pi and it is
not exactly a tool for entropy testing, even its most "powerful" model.
One would hope at least to get advice on getting the libraries you have
chosen to use in your programs.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#145 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATQXELRMFWF5F54MYOO2DDTNJD5JANCNFSM4O3SH3PQ>
.
|
|
Thank you for your clarification @celic . How do you share a Dockerfile? After exe files are built, can they be used outside of VM/Docker or are they platform dependent? |
|
The Dockerfile is instructions for docker to build the container. It will
build platform specific code because the container specifies the platform.
It would technically be possible to pull the binaries off the container but
I wouldn't recommend it. The Dockerfile specifies an entry point to submit
files for the tool to run, with the parameters.
…On Wed, May 12, 2021, 2:09 PM ucb ***@***.***> wrote:
Thank you for your clarification @celic <https://github.com/celic> .
How do you share a Dockerfile?
After exe files are built, can they be used outside of VM/Docker or are
they platform dependent?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#145 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATQXEJCDJ57BUE6RJDLWSDTNK76ZANCNFSM4O3SH3PQ>
.
|
|
Hi @celic, thank you for the response. Should I write a PM to you to get a link to the docker file? I also have a naive question as a beginner: how often are labs expected (aka required) to use the tool directly (using the raw data from the vendor) versus getting test results from the vendor, where the vendor would run the tool on the raw data? |
|
I'll try to include the Dockerfile in the repository here soon.
At the moment labs are expected to run this tool on data either collected
by the vendor or collected by the lab. See SP 800-90B for details on those
requirements. They are very specific.
In the future, NIST will have a server run this tool against files uploaded
by the lab (same data collection rules will apply). At that point the lab
may run the tool locally if they wish to help write the entropy report, or
use results from the server. Either way using the server will eventually be
mandatory.
FYI the server utilizes the Dockerfile to run the code. Information on that
is available in the ESV-Server repository.
…On Sun, May 16, 2021, 4:15 PM ucb ***@***.***> wrote:
Hi @celic <https://github.com/celic>, thank you for the response. Should
I write a PM to you to get a link to the docker file?
I also have a naive question as a beginner: how often are labs expected
(aka required) to use the tool directly (using the raw data from the
vendor) versus getting test results from the vendor, where the vendor would
run the tool on the raw data?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#145 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATQXELPBGMA43EQD25ICQDTOARUJANCNFSM4O3SH3PQ>
.
|
|
Thank you again, @celic. Just to clarify: are there any circumstances where the lab can outsource running the tool to the vendor (and utilize the output of the tool's function only)? What is the expected timeline for "the future" where NIST will have a server running this tool? What are the minimum recommended specs for running the tool locally within "reasonable" time? I have generated a CSR and sent a request for access to the ESV demo. |
|
Feel free to send me an email with these questions.
***@***.*** I'm out for the day and will respond tomorrow.
Thanks.
…On Mon, May 17, 2021, 6:21 PM ucb ***@***.***> wrote:
Thank you again, @celic <https://github.com/celic>.
Just to clarify: are there any circumstances where the lab can outsource
running the tool to the vendor (and utilize the output of the tool's
function only)?
What is the expected timeline for "the future" where NIST will have a
server running this tool?
What are the minimum recommended specs for running the tool locally within
"reasonable" time?
I have generated a CSR and sent a request for access to the ESV demo.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#145 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATQXEK2NOVMJG66QAHB7ETTOGJG7ANCNFSM4O3SH3PQ>
.
|
No description provided.
The text was updated successfully, but these errors were encountered: