README.md in rbnacl-3.2.0 vs README.md in rbnacl-3.3.0
- old
+ new
@@ -53,19 +53,17 @@
## Supported platforms
You can use RbNaCl anywhere you can get libsodium installed (see below).
RbNaCl is continuously integration tested on the following Ruby VMs:
-* MRI 2.0, 2.1, 2.2
-* JRuby 1.7 (in both 1.8/1.9 mode)
-* Rubinius HEAD (in both 1.8/1.9 mode)
+* MRI 2.0, 2.1, 2.2, 2.3
+* JRuby 1.7, 9000
-In theory Windows should be supported, although there are not yet any
-reports of successful Windows users.
-
## Installation
+Note: [Windows installation instructions are available](https://github.com/cryptosphere/rbnacl/wiki/Windows-Installation).
+
### libsodium
**NOTE: Want to avoid the hassle of installing libsodium? Use the
[rbnacl-libsodium](https://github.com/cryptosphere/rbnacl-libsodium) gem**
@@ -136,20 +134,10 @@
[signatures]: https://github.com/cryptosphere/rbnacl/wiki/Digital-Signatures
[macs]: https://github.com/cryptosphere/rbnacl/wiki/Authenticators
[hashes]: https://github.com/cryptosphere/rbnacl/wiki/Hash-Functions
[rdoc]: http://rubydoc.info/github/cryptosphere/rbnacl/master/frames
-## Security Notes
-
-NaCl itself has been expertly crafted to avoid a whole range of
-side-channel attacks, however the RbNaCl code itself has not been
-written with the same degree of expertise. While the code is
-straightforward it should be considered experimental until audited
-by professional cryptographers.
-
-That said, it's probably still a million times better than OpenSSL...
-
## Reporting Security Problems
If you have discovered a bug in RbNaCl of a sensitive nature, i.e.
one which can compromise the security of RbNaCl users, you can
report it securely by sending a GPG encrypted message. Please use
@@ -205,7 +193,7 @@
* Make your changes and send a pull request
* If your changes look good, we'll merge 'em
## License
-Copyright (c) 2012-14 Jonathan Stott, Tony Arcieri.
+Copyright (c) 2012-2015 Jonathan Stott, Tony Arcieri.
Distributed under the MIT License. See LICENSE.txt for further details.