Index: third_party/usrsctp/README.chromium |
diff --git a/third_party/usrsctp/README.chromium b/third_party/usrsctp/README.chromium |
index 087a03fcb5aad2c284d5300efa8b46389f26b3d6..a3224eaddba39498bad612a5d48ddaf1c4f8e7c3 100644 |
--- a/third_party/usrsctp/README.chromium |
+++ b/third_party/usrsctp/README.chromium |
@@ -2,13 +2,14 @@ Name: usrsctp |
URL: http://sctp-refimpl.googlecode.com/svn/trunk/KERN/usrsctp |
Version: 0 |
Date: 16 March 2013 |
-Revision: 8439 |
+Revision: 8554 |
License: New BSD License |
License File: LICENSE |
Security Critical: yes |
Description: |
-The usrsctplib provides implementation of SCTP protocol which fully supports RFC 2960 |
+The usrsctplib provides implementation of SCTP protocol which fully supports |
+RFC 2960 |
as well as updates and enhancements from the following Internet Drafts: |
draft-ietf-tsvwg-sctpcsum-05.txt |
draft-ietf-tsvwg-sctpimpguide-05.txt |
@@ -19,8 +20,13 @@ as well as updates and enhancements from the following Internet Drafts: |
draft-iyengar-sctp-cacc-00.txt |
Local Modifications: |
-usrsctplib provides its own SHA1 implementations as part of the library. Since chrome |
-already has the support of both NSS and OPENSSL which already has the implementation |
-of SHA1, Chromium will not include the SHA1 from usrsctplib. |
-Overrides folder has the necessary changes to strip existing SHA1 implementation in |
-usrsctplib and use OPENSSL or NSS implementation based on the platform type. |
+usrsctplib provides its own SHA1 implementations as part of the library. Since |
+chrome already has the support of both NSS and OPENSSL which already |
+implementats SHA1, Chromium will not include the SHA1 from usrsctplib. |
+ |
+Overrides folder has the necessary changes to strip the existing SHA1 |
+implementation in usrsctplib and use OPENSSL or NSS implementation based on the |
+platform type. |
+ |
+To re-create the patch file run: |
+diff -PcrB usrsctplib overrides/usrsctplib > localchanges.patch |