Skip to content
Snippets Groups Projects
This project is mirrored from https://github.com/smallstep/pkcs11-proxy. Pull mirroring updated .
  1. Jan 29, 2013
  2. Jan 28, 2013
  3. Jan 21, 2013
  4. Jan 18, 2013
  5. Jan 17, 2013
  6. Jan 16, 2013
  7. Jan 15, 2013
  8. Jan 14, 2013
  9. Jan 09, 2013
  10. Jan 08, 2013
  11. Jan 07, 2013
    • Fredrik Thulin's avatar
      d4092d33
    • Fredrik Thulin's avatar
      Remove obsolete input data checks. · 35589e58
      Fredrik Thulin authored
      Remove a bunch of input data checks now that byte buffers support
      NULL data length pointers in order to be as transparent as possible.
      35589e58
    • Fredrik Thulin's avatar
      Check pkcs11_initialized "everywhere". · 3922334c
      Fredrik Thulin authored
      Since PKCS#11 module initialization is done globally on the server side,
      the real PKCS#11 modules check for initialization is made a no-op. The
      only place it is possible to check for proper initialization by the
      application is here - on the client side.
      3922334c
    • Fredrik Thulin's avatar
      proto_read_byte_buffer: Support undefined buffer size. · 095eff3e
      Fredrik Thulin authored
      A number of PKCS#11 functions take a pointer to a buffer size as
      argument. To be a transparent proxy of PKCS#11 calls, it is necessary to
      support invoking these functions with a NULL pointer. pkcs11-proxy used
      to send the buffer size as an integer and create a pointer to the integer
      on the server side, but this is different to the backend PKCS#11 module
      in some cases.
      
      E.g. the C_Encrypt call is specified to have side effectes (finalizing)
      when called with a NULL encrypted data length. The softhsm test suite
      exposed that these side effects never occured because the NULL data length
      pointer was conveyed as a valid pointer to the integer zero.
      
      Since an additional uint8_t was added to "byte buffers", this is an
      backwards incompatible change. As such, the version number in the protocol
      greeting was increased (GCK_RPC_HANDSHAKE).
      095eff3e
  12. Dec 21, 2012
  13. Dec 20, 2012
  14. Dec 19, 2012
  15. Dec 18, 2012
Loading