1. 29 Mar, 2017 1 commit
    • Pascal Bühler's avatar
      Add strict-prototypes warning if supported. · bb6ef8a3
      Pascal Bühler authored
      Ensure that all functions are correctly declared for c.
      There was one function in libsrtp that was not declared correctly
      and now it can be caught.
      
      This flags needed a custom program to check in configure, the built
      in function was invalid when using this flag.
      bb6ef8a3
  2. 27 Mar, 2017 9 commits
  3. 23 Mar, 2017 1 commit
  4. 22 Mar, 2017 4 commits
  5. 21 Mar, 2017 9 commits
    • Geir Istad's avatar
      README.md: Added more references. · 66c48fff
      Geir Istad authored
      Added ref. to SHA1, renamed RFCXXXX -> RFC XXXX for consistency, added
      ref. to AES-GCM used in SRTP.
      66c48fff
    • Geir Istad's avatar
      Update configure commands in README · a7ddc67d
      Geir Istad authored
      a7ddc67d
    • Geir Istad's avatar
      0c4bfcac
    • Geir Istad's avatar
      49848826
    • Geir Istad's avatar
      srtp.c: Update reference for default policies · 8b2f7b83
      Geir Istad authored
                           mandatory-to-impl.  optional  default
      
      encryption           AES-CM, NULL        AES-f8    AES-CM
      message integrity    HMAC-SHA1             -       HMAC-SHA1
      key derivation (PRF) AES-CM                -       AES-CM
      
      Table 1: Mandatory-to-implement, optional and default transforms in
      SRTP and SRTCP.
      8b2f7b83
    • Geir Istad's avatar
      srtp.c: Update draft reference to corresponding section in RFC7714 · 8c54918f
      Geir Istad authored
      "For the AEAD_AES_128_GCM algorithm, this keystream MUST be generated in
      the manner defined in [RFC6904], using the AES Counter Mode (AES-CM)
      transform. For the AEAD_AES_256_GCM algorithm, the keystream MUST be
      generated in the manner defined for the AES_256_CM transform. The
      originator must perform any required header extension encryption before
      the AEAD algorithm is invoked."
      8c54918f
    • Geir Istad's avatar
      README.md: We can have replay list different than 128 · a81bf0b8
      Geir Istad authored
      Right? Is this not linked to window size? I could not find any other
      meaningful mentions of replay <something> other than the window size:
      
      srtp/srtp.c:1191:   /* initialize replay database */
      srtp/srtp.c-1192-   /* window size MUST be at least 64.  MAY be larger.  Values more than
      srtp/srtp.c-1193-    * 2^15 aren't meaningful due to how extended sequence numbers are
      srtp/srtp.c-1194-    * calculated.   Let a window size of 0 imply the default value. */
      srtp/srtp.c-1195-
      srtp/srtp.c-1196-   if (p->window_size != 0 && (p->window_size < 64 || p->window_size >= 0x8000))
      srtp/srtp.c-1197-     return srtp_err_status_bad_param;
      a81bf0b8
    • Geir Istad's avatar
      README.md: We can set window size · 21dbac43
      Geir Istad authored
      srtp/srtp.c-1191-   /* initialize replay database */
      srtp/srtp.c:1192:   /* window size MUST be at least 64.  MAY be larger.  Values more than
      srtp/srtp.c-1193-    * 2^15 aren't meaningful due to how extended sequence numbers are
      srtp/srtp.c:1194:    * calculated.   Let a window size of 0 imply the default value. */
      srtp/srtp.c-1195-
      srtp/srtp.c-1196-   if (p->window_size != 0 && (p->window_size < 64 || p->window_size >= 0x8000))
      srtp/srtp.c-1197-     return srtp_err_status_bad_param;
      21dbac43
    • Geir Istad's avatar
      Mki added in PR #224 · d3d8ea0e
      Geir Istad authored
      d3d8ea0e
  6. 16 Mar, 2017 1 commit
  7. 14 Mar, 2017 4 commits
  8. 13 Mar, 2017 10 commits
  9. 10 Mar, 2017 1 commit