summaryrefslogtreecommitdiff
path: root/spec/mixlib
diff options
context:
space:
mode:
authorJay Mundrawala <jdmundrawala@gmail.com>2015-12-16 16:07:04 -0600
committerJay Mundrawala <jdmundrawala@gmail.com>2015-12-16 16:07:04 -0600
commitab32d60ef2cdca5a8164d19bd4955055963a703b (patch)
tree8ea3b04a74d187c95da827fac47e2940298ddaf9 /spec/mixlib
parentc6fc90a433d1e93df6aeb3ae88450013b62a5c35 (diff)
downloadmixlib-authentication-ab32d60ef2cdca5a8164d19bd4955055963a703b.tar.gz
Make hashing functions backwards compatible with mixlib-authentication 1.3
I had assumed that those functions were only used internally to mixlib-authentication. It seems that oc-chef-pedant tests use these functions. This patch makes the function backwards compatible by defaulting to using SHA1 for the digester if one is not supplied
Diffstat (limited to 'spec/mixlib')
-rw-r--r--spec/mixlib/authentication/digester_spec.rb24
1 files changed, 24 insertions, 0 deletions
diff --git a/spec/mixlib/authentication/digester_spec.rb b/spec/mixlib/authentication/digester_spec.rb
new file mode 100644
index 0000000..747227d
--- /dev/null
+++ b/spec/mixlib/authentication/digester_spec.rb
@@ -0,0 +1,24 @@
+require 'mixlib/authentication/digester'
+
+describe Mixlib::Authentication::Digester do
+ context 'backcompat' do
+ # The digester API should really have been private,
+ # however oc-chef-pedant uses it.
+ let(:test_string) { 'hello' }
+ let(:test_string_checksum) { 'qvTGHdzF6KLavt4PO0gs2a6pQ00=' }
+
+ describe '#hash_file' do
+ it 'should default to use SHA1' do
+ expect(described_class.hash_file(StringIO.new(test_string))).to(
+ eq(test_string_checksum))
+ end
+ end
+
+ describe '#hash_string' do
+ it 'should default to use SHA1' do
+ expect(described_class.hash_string(test_string)).to(
+ eq(test_string_checksum))
+ end
+ end
+ end
+end