1. 06 May, 2017 1 commit
  2. 05 May, 2017 1 commit
  3. 03 May, 2017 2 commits
  4. 01 May, 2017 12 commits
  5. 30 Apr, 2017 1 commit
    • Luca Boccassi's avatar
      Problem: no way to deploy releases to OBS · f126da8b
      Luca Boccassi authored
      Solution: add new tokens to .travis.yml and change ci_deploy.sh
      script to use Github APIs to create a temporary branch at the tag,
      and the OBS APIs to trigger a source service run in the stable and
      draft release projects:
      network:messaging:zeromq:release-stable
      network:messaging:zeromq:release-draft
      
      The branch hack is unfortunately necessary as it is not possible to
      modify OBS sources with the token APIs, and it is also not possible
      to automatically fetch the latest tag in the service files.
      The temporary branch is immediately deleted.
      f126da8b
  6. 29 Apr, 2017 3 commits
  7. 28 Apr, 2017 4 commits
  8. 26 Apr, 2017 2 commits
    • Luca Boccassi's avatar
      Merge pull request #2550 from garlick/gssapi_test · 54b89858
      Luca Boccassi authored
      add simple GSSAPI test for make check
      54b89858
    • Jim Garlick's avatar
      gssapi: add a basic test for GSSAPI security · edd6b0ad
      Jim Garlick authored
      Problem: there is no test coverage for GSSAPI.
      
      Solution: add a test structured like the CURVE test.
      
      The test is not built if libzmq is not configured with
      --with-libgssapi_krb5. It will report SKIPPED status
      if the required environment is missing (see below).
      
      Environment:  KRB5_KTNAME and KRB5_CLIENT_KTNAME
      environment variables must point to a keytab file
      containing creds for a host-based test principal
      (see comment at top of source for details).
      Kerberos must be configured and a KDC containing the
      test principal must be running, otherwise the test
      will fail/hang.
      
      N.B. For now, the test must use the same principal for
      both client and server roles because it seems impossible
      to set them to different principals when they are
      threads in the same process.  Once one principal is
      cached in credential cache, attempts to acquire creds
      for a different "desired name" seem to be ignored and
      the cached principal is used instead.
      edd6b0ad
  9. 25 Apr, 2017 4 commits
  10. 24 Apr, 2017 5 commits
  11. 23 Apr, 2017 2 commits
  12. 22 Apr, 2017 1 commit
  13. 21 Apr, 2017 2 commits