Changes committed to git://oss.sgi.com/nathans/pcp.git dev
qa/712 | 163 +++++++-------------------------------------
qa/712.out | 6 +
qa/713 | 144 ++++++++------------------------------
qa/713.out | 14 +--
qa/714 | 49 +++++++++++++
qa/714.out | 19 +++++
qa/GNUmakefile | 2
qa/common.secure | 153 +++++++++++++++++++++++++++++++++++++++++
qa/group | 2
src/libpcp/src/nss_server.c | 7 +
10 files changed, 298 insertions(+), 261 deletions(-)
commit 5b79afa12e4a380f0ea7b1125a9ba9e1fd3845d4
Author: Nathan Scott <nathans@xxxxxxxxxx>
Date: Tue Feb 19 12:03:20 2013 +1100
Add test 714 exercising SSL connection failure with invalid certificate
commit 4e2a83bde54412e67cda4dacac6381d37731bfcf
Author: Nathan Scott <nathans@xxxxxxxxxx>
Date: Tue Feb 19 11:55:50 2013 +1100
Bring the pmproxy SSL test back into the fold, with new style DBs
Abstracted much of the test code that was being duplicated in test
712 as well into a common.secure shared shell script for sourcing.
commit ba4847c2c42636cd9f0fadf1739c0dea7f675252
Author: Nathan Scott <nathans@xxxxxxxxxx>
Date: Tue Feb 19 10:06:14 2013 +1100
Add another case to 712 testing db-exists-but-no-certs case
commit 90db3cb7c812412920b0532f4684755607fdc927
Author: Nathan Scott <nathans@xxxxxxxxxx>
Date: Tue Feb 19 09:07:19 2013 +1100
Make the server side nssdb access check more liberal
Previously we were only erroring out if the database does
not exist at all (ENOENT). However, its also a possibility
that the permissions are such that the "pcp" user cannot
read it, as I came across in QA when not following the SSL
setup recipe to the letter (missed chmod, default is 0700).
|