opensecret 0.0.7 → 0.0.8
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +7 -7
- data/Rakefile +5 -5
- data/lib/opensecret/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: e67c23773cbe174123307c2867d43bb87eadeb52
|
4
|
+
data.tar.gz: a609ac281671d31a31347f3b4b495624a0943627
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 5a4ad46b55c31d1ee53b712d16614a1bc037e5530ade7a3cee1d1f36ac7a810ab24acfd477a80f1ae8f61a0b304fcf6fb6a00a93138b9c92eee7ec1feec8a56a
|
7
|
+
data.tar.gz: d234147703779a54e450edd86dacb66dc47f2fa651d8ff310d4baf32813a3a7e3dd632d1da2abe917b090d552fafe0f9196edfb56c94188687dda0d29c633c8a
|
data/README.md
CHANGED
@@ -29,13 +29,13 @@ opensecret never accesses the cloud for anything - it is designed to operate on
|
|
29
29
|
|
30
30
|
You are done setting up opensecret with just 5 commands. *Simple* means less mistakes, less confusion and therefore more secure. Let's recap on the 5 configurations
|
31
31
|
|
32
|
-
- <tt
|
33
|
-
- <tt
|
34
|
-
- <tt
|
35
|
-
- <tt
|
36
|
-
- <tt
|
32
|
+
- <tt>**keydir**</tt> » best practise is a usb key drive with your **actual keys**
|
33
|
+
- <tt>**name**</tt> » single word lowercase and short - how your peers call you
|
34
|
+
- <tt>**email**</tt> » email address (validation scheduled for end of March 2018)
|
35
|
+
- <tt>**domain**</tt> » **joe@home** if single or a team like it-dept@ibm.com
|
36
|
+
- <tt>**store**</tt> » a Git project URL to hold your encrypted secret material
|
37
37
|
|
38
|
-
The
|
38
|
+
The opensecret init command
|
39
39
|
|
40
40
|
- creates a 8192 bit uncrackable private key
|
41
41
|
- collects a human password and creates a machine password
|
@@ -119,7 +119,7 @@ Any hijacker will need access to a great many things and be very precise with th
|
|
119
119
|
|
120
120
|
You can use opensecret alone or you can use it to share secrets with colleagues, friends and family, even machines.
|
121
121
|
|
122
|
-
Every domain is tied to backend storage which is accessible by you and others in your domain. You can use Git, S3, a networked filesystem or shared drive, a SSH accessible filesystem and soon, free storage from
|
122
|
+
Every domain is tied to backend storage which is accessible by you and others in your domain. You can use Git, S3, a networked filesystem or shared drive, a SSH accessible filesystem and soon, free storage from <tt>opensecret.io</tt>
|
123
123
|
|
124
124
|
|
125
125
|
|
data/Rakefile
CHANGED
@@ -1,6 +1,5 @@
|
|
1
1
|
require "bundler/gem_tasks"
|
2
2
|
require "rake/testtask"
|
3
|
-
require 'yard'
|
4
3
|
|
5
4
|
# -
|
6
5
|
# - This configuration allows us to run "rake test"
|
@@ -19,7 +18,8 @@ task :default => :test
|
|
19
18
|
# - This configuration allows us to run "rake yard"
|
20
19
|
# - to build documentation.
|
21
20
|
# -
|
22
|
-
|
23
|
-
|
24
|
-
t.
|
25
|
-
|
21
|
+
# ---> require 'yard'
|
22
|
+
# ---> YARD::Rake::YardocTask.new do |t|
|
23
|
+
# ---> t.files = ['lib/**/*.rb']
|
24
|
+
# ---> t.stats_options = ['--list-undoc']
|
25
|
+
# ---> end
|
data/lib/opensecret/version.rb
CHANGED
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: opensecret
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.0.
|
4
|
+
version: 0.0.8
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Apollo Akora
|
@@ -159,7 +159,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
159
159
|
version: '0'
|
160
160
|
requirements: []
|
161
161
|
rubyforge_project:
|
162
|
-
rubygems_version: 2.5.1
|
162
|
+
rubygems_version: 2.5.2.1
|
163
163
|
signing_key:
|
164
164
|
specification_version: 4
|
165
165
|
summary: opensecret locks and unlocks secrets in a simple, secure and intuitive way.
|