hestia 0.1.0 → 0.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: ee2e639cd00c467444c76fed6a718f9df5670834
-  data.tar.gz: 9122b7533ed0358a108bd56be5333e420f8d54c2
+  metadata.gz: 10feace28dda56911b32013d3fb9b41c85e3b101
+  data.tar.gz: 4e8e5c002fe8102089b2c8f1745b96d2a235cde0
 SHA512:
-  metadata.gz: 0086cb17ecff3769ecbfdf4d682102f7bd42bf04e671c9307ad4e20202b7593e153627432378583beb46c12106e8ad272cd92073b4e50b8b7abd4d8d69deaa96
-  data.tar.gz: d569bf9fd318e862f31539bcec7306ee45bc84668f614cd171baaa5b9c78b0c7895663e2319aecf15f23b848ceac2387ee886dd8a54f8a8f4f0b606cf3638935
+  metadata.gz: 83cc7fd6f3d6ec36b8c14558254b9b35e2b9825e1fb12c2cbd97067139de47ab8c8722cb016232b5a61dc89e1306d0deeb9414246d548e8484a5082b5eb3a916
+  data.tar.gz: 0f252f5d0324503808dfd62da05af883b94bff63d7f4eeab79120e72dd3616fb919c326c4d24e17b479183f4f0e3a206a4ec4966790c8413bf635ef70f8ac32a

data/.travis.yml

@@ -7,3 +7,4 @@ rvm:
 gemfile:
   - Gemfile.rails3
   - Gemfile.rails41
+  - Gemfile.rails42

data/Gemfile.rails42

@@ -0,0 +1,6 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in hestia.gemspec
+gemspec
+
+gem "actionpack", "~> 4.2.0"

data/README.md

@@ -1,5 +1,9 @@
 # Hestia
 
+***
+
+[![Build Status](https://travis-ci.org/fac/hestia.svg?branch=master)](https://travis-ci.org/fac/hestia)
+
 Add support for deprecating/rotating the signed cookie secret token in rails. Out of the box if you change `config.secret_token` in rails, as soon as you deploy the change all your existing signed cookies are rendered invalid with lovely side effects such as all of your users being logged out. Thing is, it would be nice to rotate the secret token occasionally, without that side effect.
 
 Enter hestia! You can now change your `config.secret_token`, and move the old value to `config.deprecated_secret_token` to allow existing cookies to be read in as valid cookies, but all cookies being sent out of the app are signed using the new secret token value. After a while all your users that have been active since the change will have cookies signed by the new token, and you can remove the old token from `config.deprecated_secret_token`. Hey presto, you just changed your `config.secret_token` without logging anyone out or losing any existing cookies.
@@ -26,6 +30,16 @@ And then require the railtie during your application boot process somewhere:
 require "hestia/railtie"
 ```
 
+## Supported Rails Versions
+
+We currently support (& test against):
+
+* Rails 3.2
+* Rails 4.1
+* Rails 4.2
+
+Pull requests always welcome to support other versions!
+
 ## Usage
 
 ### Rails 3.2
@@ -47,9 +61,7 @@ You should already have `Rails.application.config.secret_token` set to a value (
 
 *You can also set `config.deprecated_secret_token` to an array of strings to allow incoming cookies to be valid when signed with any of the secrets.*
 
-### Rails 4
-
-We support Rails 4.1. Rails 4.0 & 4.2 are unsupported at this time. (Pull requests welcome!)
+### Rails 4.1, 4.2
 
 Following the instructions for Rails 3.2 should work, but make sure you haven't set `config.secret_key_base` to a value otherwise Rails will take over and upgrade your cookies from signed to encrypted ones.
 

data/Rakefile

@@ -8,6 +8,7 @@ end
 task(:default => :spec)
 
 namespace :spec do
+  desc "Run specs across all gemfiles"
   task :all do
     Dir["Gemfile*"].reject {|name| name[".lock"] }.each do |gemfile|
       sh "BUNDLE_GEMFILE=#{gemfile} bundle exec rake spec"

data/hestia.gemspec

@@ -21,7 +21,7 @@ Gem::Specification.new do |spec|
   spec.required_ruby_version = '>= 2.0'
 
   spec.add_runtime_dependency "rack"
-  spec.add_runtime_dependency "actionpack", ">= 3.2.21", "< 4.2.0"
+  spec.add_runtime_dependency "actionpack", ">= 3.2.21", "< 5.0.0"
 
   spec.add_development_dependency "bundler", "~> 1.7"
   spec.add_development_dependency "rake", "~> 10.0"

data/lib/hestia/signed_cookie_jar_extension/action_pack_4.rb

@@ -1,3 +1,5 @@
+require "active_support/message_encryptor"
+
 module Hestia
   module SignedCookieJarExtension
     module ActionPack4
@@ -29,8 +31,10 @@ module Hestia
           ActiveSupport::LegacyKeyGenerator.new(secret).generate_key(@options[:signed_cookie_salt])
         end
 
+        serializer = ActiveSupport::MessageEncryptor::NullSerializer
+
         # Finally, override @verifier with our own multi verifier containing all the secrets
-        @verifier = Hestia::MessageMultiVerifier.new(current_secret: active_secret, deprecated_secrets: deprecated_secrets, options: {serializer: ActionDispatch::Cookies::NullSerializer})
+        @verifier = Hestia::MessageMultiVerifier.new(current_secret: active_secret, deprecated_secrets: deprecated_secrets, options: {serializer: serializer})
       end
     end
   end

data/lib/hestia/version.rb

@@ -1,3 +1,3 @@
 module Hestia
-  VERSION = "0.1.0"
+  VERSION = "0.2.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: hestia
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.2.0
 platform: ruby
 authors:
 - Caius Durling
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-07-31 00:00:00.000000000 Z
+date: 2016-08-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rack
@@ -33,7 +33,7 @@ dependencies:
         version: 3.2.21
     - - "<"
       - !ruby/object:Gem::Version
-        version: 4.2.0
+        version: 5.0.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -43,7 +43,7 @@ dependencies:
         version: 3.2.21
     - - "<"
       - !ruby/object:Gem::Version
-        version: 4.2.0
+        version: 5.0.0
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement
@@ -99,6 +99,7 @@ files:
 - ".travis.yml"
 - Gemfile.rails3
 - Gemfile.rails41
+- Gemfile.rails42
 - LICENSE.txt
 - README.md
 - Rakefile
@@ -137,7 +138,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.2.3
+rubygems_version: 2.6.6
 signing_key: 
 specification_version: 4
 summary: Support for deprecating/rotating signed cookie secret tokens in rails