cose-key 0.0.5 → 0.1.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
- SHA256:
3
- metadata.gz: 1f56eab404fb65f8a3f4d297b801cb956f1779fccec411fba7810836845d5d36
4
- data.tar.gz: c17c239339f1041a13efb11d7c0081fef694acb70601205894f3c8217d3905dd
2
+ SHA1:
3
+ metadata.gz: 208b5b41e44c40b240ed65dee956ee88d0717f05
4
+ data.tar.gz: 338147a53f90187024e6dff8430aaafe58961f27
5
5
  SHA512:
6
- metadata.gz: 5cc31c2e58359d89c5e4d002a3b428c4b5efed16eb86a0666829c1daca57fef4c9eb0a1b3c87555453571b9819aa6ee4570f89a4901fa708e1156ea55632e041
7
- data.tar.gz: 51bfd900cb76a957d1a52ba63ce27ba27c888d622c9e5b470a14e2dc1f21afdf03e26740362e5dd8e7ca10d3746b807c70a09fb7445c69657bbb55ac026c75bf
6
+ metadata.gz: 0b868731d73734f081d368473525ae25546c766617eb398b63efa37fe5c48399bfa869a22bc00a34255190b69439f19ccd0bf753cd6ee188691fb174205000b2
7
+ data.tar.gz: b844aac95c6e92ac9bffd1a67fa778ecf9a5a9b4d6522e55ea5ee5601375fa9625eb857471c7920c7fa79f69a746b32f65d44be4ddcd0092af0f13f2554e27ec
data/README.md CHANGED
@@ -1,8 +1,6 @@
1
1
  # COSE::Key
2
2
 
3
- Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/cose/key`. To experiment with that code, run `bin/console` for an interactive prompt.
4
-
5
- TODO: Delete this and the text above, and describe your gem
3
+ COSE Key (RSA & EC) in Ruby
6
4
 
7
5
  ## Installation
8
6
 
@@ -22,17 +20,33 @@ Or install it yourself as:
22
20
 
23
21
  ## Usage
24
22
 
25
- TODO: Write usage instructions here
23
+ ```ruby
24
+ require 'cose/key'
25
+
26
+ cose_key_in_cbor = "\xA5\x01\x02\x03& \x01!X \x06\x0F\xBD\x82\xE5U\xC4\xDEl\f\x8F7?_O\xFB\xC1H\b8\x0E\xA4\xB7b\xA8\f\x89\xF5\xFBS\xC7u\"X \n\x19\x98\x15\xF2\x10\x99#\xBE[\xB6\xE7PCo\xC5h:\xD2$z\xD0\x03\xD5[\xD8su\x94$\x9A\xD9"
27
+
28
+ cose_key = COSE::Key.decode cose_key_in_cbor
29
+ # => COSE::Key::EC2 or COSE::Key::RSA
30
+
31
+ cose_key.to_key
32
+ # => OpenSSL::PKey::EC or OpenSSL::PKey::RSA
33
+
34
+ cose_key.alg_key
35
+ # => :RS256, :ES256 etc.
36
+
37
+ cose_key.digest
38
+ # => OpenSSL::Digest::SHA(1|256|384|512) instance per algorithm.
39
+ ```
26
40
 
27
41
  ## Development
28
42
 
29
43
  After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
30
44
 
31
- To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
45
+ To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `VERSION`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
32
46
 
33
47
  ## Contributing
34
48
 
35
- Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/cose-key. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
49
+ Bug reports and pull requests are welcome on GitHub at https://github.com/nov/cose-key. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
36
50
 
37
51
  ## License
38
52
 
data/VERSION CHANGED
@@ -1 +1 @@
1
- 0.0.5
1
+ 0.1.0
data/cose-key.gemspec CHANGED
@@ -9,7 +9,7 @@ Gem::Specification.new do |gem|
9
9
  gem.license = 'MIT'
10
10
  gem.files = `git ls-files`.split("\n")
11
11
  gem.test_files = `git ls-files -- {test,spec,features}/*`.split("\n")
12
- gem.executables = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }
12
+ gem.executables = `git ls-files -- exe/*`.split("\n").map{ |f| File.basename(f) }
13
13
  gem.require_paths = ['lib']
14
14
  gem.required_ruby_version = '>= 2.3'
15
15
  gem.add_runtime_dependency 'cbor'
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: cose-key
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.0.5
4
+ version: 0.1.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - nov matake
@@ -83,16 +83,13 @@ dependencies:
83
83
  description: COSE Key (RSA & EC) in Ruby
84
84
  email:
85
85
  - nov@matake.jp
86
- executables:
87
- - console
88
- - setup
86
+ executables: []
89
87
  extensions: []
90
88
  extra_rdoc_files: []
91
89
  files:
92
90
  - ".gitignore"
93
91
  - ".rspec"
94
92
  - ".travis.yml"
95
- - CODE_OF_CONDUCT.md
96
93
  - Gemfile
97
94
  - LICENSE.txt
98
95
  - README.md
@@ -126,7 +123,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
126
123
  version: '0'
127
124
  requirements: []
128
125
  rubyforge_project:
129
- rubygems_version: 2.7.6
126
+ rubygems_version: 2.6.11
130
127
  signing_key:
131
128
  specification_version: 4
132
129
  summary: COSE Key in Ruby
data/CODE_OF_CONDUCT.md DELETED
@@ -1,74 +0,0 @@
1
- # Contributor Covenant Code of Conduct
2
-
3
- ## Our Pledge
4
-
5
- In the interest of fostering an open and welcoming environment, we as
6
- contributors and maintainers pledge to making participation in our project and
7
- our community a harassment-free experience for everyone, regardless of age, body
8
- size, disability, ethnicity, gender identity and expression, level of experience,
9
- nationality, personal appearance, race, religion, or sexual identity and
10
- orientation.
11
-
12
- ## Our Standards
13
-
14
- Examples of behavior that contributes to creating a positive environment
15
- include:
16
-
17
- * Using welcoming and inclusive language
18
- * Being respectful of differing viewpoints and experiences
19
- * Gracefully accepting constructive criticism
20
- * Focusing on what is best for the community
21
- * Showing empathy towards other community members
22
-
23
- Examples of unacceptable behavior by participants include:
24
-
25
- * The use of sexualized language or imagery and unwelcome sexual attention or
26
- advances
27
- * Trolling, insulting/derogatory comments, and personal or political attacks
28
- * Public or private harassment
29
- * Publishing others' private information, such as a physical or electronic
30
- address, without explicit permission
31
- * Other conduct which could reasonably be considered inappropriate in a
32
- professional setting
33
-
34
- ## Our Responsibilities
35
-
36
- Project maintainers are responsible for clarifying the standards of acceptable
37
- behavior and are expected to take appropriate and fair corrective action in
38
- response to any instances of unacceptable behavior.
39
-
40
- Project maintainers have the right and responsibility to remove, edit, or
41
- reject comments, commits, code, wiki edits, issues, and other contributions
42
- that are not aligned to this Code of Conduct, or to ban temporarily or
43
- permanently any contributor for other behaviors that they deem inappropriate,
44
- threatening, offensive, or harmful.
45
-
46
- ## Scope
47
-
48
- This Code of Conduct applies both within project spaces and in public spaces
49
- when an individual is representing the project or its community. Examples of
50
- representing a project or community include using an official project e-mail
51
- address, posting via an official social media account, or acting as an appointed
52
- representative at an online or offline event. Representation of a project may be
53
- further defined and clarified by project maintainers.
54
-
55
- ## Enforcement
56
-
57
- Instances of abusive, harassing, or otherwise unacceptable behavior may be
58
- reported by contacting the project team at nov@matake.jp. All
59
- complaints will be reviewed and investigated and will result in a response that
60
- is deemed necessary and appropriate to the circumstances. The project team is
61
- obligated to maintain confidentiality with regard to the reporter of an incident.
62
- Further details of specific enforcement policies may be posted separately.
63
-
64
- Project maintainers who do not follow or enforce the Code of Conduct in good
65
- faith may face temporary or permanent repercussions as determined by other
66
- members of the project's leadership.
67
-
68
- ## Attribution
69
-
70
- This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71
- available at [http://contributor-covenant.org/version/1/4][version]
72
-
73
- [homepage]: http://contributor-covenant.org
74
- [version]: http://contributor-covenant.org/version/1/4/