All Versions
11
Latest Version
Avg Release Cycle
186 days
Latest Release
2031 days ago

Changelog History
Page 1

  • v5.1.0 Changes

    April 20, 2019
    • โšก๏ธ Update to Swift 5
    • ๐Ÿ‘‰ Uses CommonCrypto modular headers (available since 4.2)
  • v5.0.3 Changes

    April 16, 2018
    • โš  #272. Correct warnings related to incorrect memory access. The previous code was invalid Swift (it accessed a value inside its own withUnsafeBytes block), but happened to work.
    • โœ‚ Removes a Data.init work-around that is no longer needed.
    • #252. Use semver for tags rather than custom RNCryptor-# tags.
  • v5.0.2 Changes

    November 09, 2017

    ๐Ÿš€ This is a minor release that fixes some build configuration issues.

    • โšก๏ธ Update Swift Package Manager support
    • โšก๏ธ Update Linux support
    • โž• Add tvOS support
    • โšก๏ธ Update to Xcode 9.1 settings
    • โšก๏ธ Update to Swift 4 (no code changes; completely backward compatible)
    • โœ‚ Remove code coverage from Release builds (necessary for Carthage)
  • v5.0.1 Changes

    September 27, 2016
    • ๐Ÿ”’ Perform final decryption after HMAC validation. Fixes #185. This improves security very slightly. There is no known or proposed attack that could exploit the previous behavior, but where possible it is better to validate prior to decryption.
    • ๐Ÿ›  Fix CocoaPods

    ๐Ÿ— > See build details and artifacts at buddybuild:
    ๐Ÿ— > https://dashboard.buddybuild.com/apps/57ea731dbd45750100873fb1/build/57ea785c3dd53201003bef05

  • v5.0.0 Changes

    September 14, 2016
    • Rework for Swift 3
    • โฌ‡๏ธ Drops ObjC bridging. There are too many problems with the Swift compiler at this point to support this cleanly. ObjC code should use RNCryptor-ObjC.
    • ๐Ÿ‘ #159 Add WatchOS support to Podspec
    • ๐Ÿ‘ Better debugging output in case of unexpected cryptor failure
    • โž• Added Examples/KeyDerivation to explain how to manually derive keys
  • v4.1.0 Changes

    September 19, 2016

    ๐Ÿš€ For those remaining on Swift 2.3, the swift2 branch (4.x) will continue to support you. If you're on Swift 3, please see master and release 5.0.

  • v4.0.0 Changes

    October 20, 2015

    ๐Ÿ‘ RNCryptor 4 is a complete rewrite of RNCryptor for Swift 2 with full bridging support to Objective-C. It has a streamlined API, simpler installation, and improved internals. It continues to use the v3 data format and is fully interoperable with other RNCryptor implementations.

    ๐Ÿš€ For users desiring a fully Objective-C solution, v3 is still available. I don't currently plan to do significant new work on v3, but will consider it if there is strong interest. Going forward, I expect most OS X and iOS projects to be able to accept a mix of ObjC and Swift code. Objective-C continues to be a fully supported language in RNCryptor 4.

  • v4.0.0-beta.1 Changes

    October 04, 2015

    ๐Ÿ‘ RNCryptor 4 is a complete rewrite of RNCryptor for Swift 2 with full bridging support to Objective-C. It has a streamlined API, simpler installation, and improved internals. It continues to use the v3 data format and is fully interoperable with other RNCryptor implementations.

    ๐Ÿš€ For users desiring a fully Objective-C solution, v3 is still available. I don't currently plan to do significant new work on v3, but will consider it if there is strong interest. Going forward, I expect most OS X and iOS projects to be able to accept a mix of ObjC and Swift code. Objective-C continues to be a fully supported language in RNCryptor 4.

    ๐Ÿš€ I plan to convert this to a final release in a week or so if no major issues are discovered.

  • v3.0.1 Changes

    September 17, 2015

    ๐Ÿšš CocoaPods was including private headers. Removed.

  • v3.0.0 Changes

    September 16, 2015

    ๐Ÿ‘€ RNCryptor v3 has one backward-incompatible change: OpenSSL support has been removed. OpenSSL encryption is not a secure format, and supporting it over-complicates RNCryptor. For those needing OpenSSL compatibility see rnapier/RNOpenSSLCryptor.

    โœ… RNCryptor now cleanly integrates with Swift as a framework. The recommended way to do this is with Carthage, but CocoaPods is also tested and works.

    ๐Ÿš€ A native Swift 2 version of RNCryptor is now in alpha and should be available around the time Xcode 7 is released.

    ๐Ÿ“š Most of the rest of the changes in RNCryptor v3 are documentation and testing related. There are a few minor improvements in robustness (most are better defensive coding and do not solve actual bugs).

    Going forward, I will be using Semantic Versioning. Previous versions of RNCryptor have not done this.