Changes committed to git://oss.sgi.com/pcp/pcp.git dev
CHANGELOG | 3 +++
VERSION.pcp | 2 +-
build/rpm/fedora.spec | 3 +++
configure | 2 +-
configure.in | 2 +-
debian/changelog | 6 ++++++
src/libpcp/src/secureconnect.c | 10 ++++++----
src/libpcp/src/secureserver.c | 12 ++++++------
8 files changed, 27 insertions(+), 13 deletions(-)
commit 62a3429078493100c285c13d5c1cfe2c91d70245
Merge: b1e4c20 1c117e4
Author: Nathan Scott <nathans@xxxxxxxxxx>
Date: Thu Nov 7 08:51:34 2013 +1100
Merge branch 'fche/dev' of ../pcpfans into dev
commit 1c117e4fae76eb8e94377ad620a8cec39794ea88
Author: Frank Ch. Eigler <fche@xxxxxxxxxx>
Date: Wed Nov 6 08:28:37 2013 -0500
PCP NSS support: use "domestic" rather than "export" cipher suite
Modern versions of NSS are starting to disable the obsolete and
puny-security "export" suite of ciphers. We certainly shouldn't
limit ourselves to them.
commit b1e4c200ffaa528ecae86d0447e9c1ecb362cdfb
Author: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed Nov 6 17:38:12 2013 +1100
Bump versions to annotate current development pcp version
commit 1a8772fe4a767692b8dd1f043f93f7acc5e43ef2
Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Mon Nov 4 20:58:51 2013 +1100
configure.in - fix HAVE_CONST_DIRENT test
At some point either the gcc pixies messed with compile-time checking
or the pcp pixies changed the compilation flags so gcc does insane
compile-time checking.
The sample C code was generating an error because the first and second
arguments to scandir() were NULL. Don't even start to think about a
parallel universe in which this is ever a good idea!
The consequence was that HAVE_CONST_DIRENT is never set, even when
the scandir() callback routine should have a const struct dirent *
argument, so we assume struct dirent * and end up with compilation
errors on some platforms.
|