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

Discussion: Recommendations? #3

Open
grandamp opened this issue Nov 5, 2016 · 1 comment
Open

Discussion: Recommendations? #3

grandamp opened this issue Nov 5, 2016 · 1 comment

Comments

@grandamp
Copy link
Owner

grandamp commented Nov 5, 2016

Anyone?

@bob-fontana
Copy link

Hello Todd,

Disregard this. Looking at the project, it looks like it’s all there. It should be simple to turn on FINE logging and get what we need using your example applications.

Thanks,

Bob

From: Bob Fontana
Sent: Saturday, November 5, 2016 6:32 AM
To: grandamp/SCVPAPI [email protected]
Subject: RE: [grandamp/SCVPAPI] Discussion: Recommendations? (#3)

Todd,

I have been working with Jordan Packham on the SCVP Functional Requirements Test Cases (FRTC). On a related topic, we had a meeting Thursday with Chi Hicky to discuss what would be involved in automating PD-VAL testing. Note that Chi also wants to remove the PD-VAL product list and include PD-VAL as part of SCVP testing.

I was given the task of researching a way to script this. Scripting the use of an API to test SCVP servers would be easy if we had an SCVP API. The script would need to be able to create fault paths prior to calls to the API so that we can observe whether the server conforms to the various RFCs. Jordan was going to distribute notes on this, but essentially, the testing will consist of 6 parts: PKITS tests and conformance with Common, FBCA, SSP, and PIV-I profiles and then conformance with the SCVP profile itself.

Jordan and I would like to add client-side logging into the SCVP client profile so that we can use the API to turn on detailed logging, and then inspect the contents of the requests and the responses rather than have to sniff the wire, capture the transmission, break it all down, etc. If it were built into the client, we could look for the values we are interested in and verify that they are what we expect, all scripted using bash, perl, etc. The FRTC that we’ve been working on contains the fields that we need to view if you would like us to share it with you.

Would you like these comments in the form of github issues?

Bob Fontana | Lab Director, FIPS 201 PACS Testing Program
Mobile: +1.561.212.7450
Email: [email protected]:[email protected]

From: Todd Johnson [mailto:[email protected]]
Sent: Friday, November 4, 2016 9:27 PM
To: grandamp/SCVPAPI <[email protected]mailto:[email protected]>
Subject: [grandamp/SCVPAPI] Discussion: Recommendations? (#3)

Anyone?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com//issues/3, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ASbsRrSpKCj-EfnP-1ldlmguxLAnXkfGks5q69tKgaJpZM4KqIDP.

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