vagrant-rekey-ssh 0.1.1 → 0.1.3

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    NTkyMzA1ZGQ2YjAwYzI5MDVlYjY0MmZmY2E4Y2FjMjU1NmZiZWMzMA==
+    ZjNkMTYxOTliZDNiN2ZlMDU0ZTBjNDIwZDM2ZTdjMDRjNzEzOWRjMQ==
   data.tar.gz: !binary |-
-    MzI0ZTllMWNjZjcwYjJhZmNkNDVhYThiN2Y4Nzg4NzViYjU0YjIxOQ==
+    NzFkMTljMTRhMmEwYzgyYjQ2YjMwYTI0Y2QzZDMxMmZmY2JjMTU1OQ==
 SHA512:
   metadata.gz: !binary |-
-    MWFkODA3MDJjOTNlOTE0NjgyMTFkYjc3YTVlZmM5YWI5YTg0Yjc0NDVjNGY1
-    ZDQ3MDFkMTFiNWNhYzk5NWJjZWU3Nzk5Y2RhMTM0YTBiYzA0YjNlNWE5Yjhh
-    NDc1YjFkNWQyNzJmODhjYzVlMjZkNTMyZGEwMzU4MmY4ZjllM2E=
+    MjlhMzQ2NzAzOWRhZjUzMGI1ZjM1MjMxNmNiYzRjODMwZTE1NDJlZmNlMmVl
+    ZDUyYmMwNGEwYWNmNmJkNjYxYzkyMGZhNGI1OGE1ZmZlNjFlN2JiZDM1MDhi
+    MDlmOTA2OWRmYTg3MWNkZGJmODI5M2UyM2EwZDBkZDk2ZTQ0ZDE=
   data.tar.gz: !binary |-
-    ZDhlZjdkYWRiYzcyNzFiZDlkZDA1MzQxOWVkMjIwNDhlMDE5YjVmMDNjNDU0
-    YjU3YzNiNDU0MTgzN2MxMmZkZmQyNmVkYzY4ZTE4ZDY2NDkyZjhhNDNlZDMy
-    MzA2YzFlOGJhNTFlNGIwYzgyMzMyMWZjY2UxYWVkMWRjNDQxOWY=
+    MTRjMDlhZTI0ZDExNTVkZDI1M2YzZTM2MTU4M2I5Yzk0Y2VlNmNhMGI1MThl
+    M2ZkM2U4Zjk5ODE1NDI2OTU4NzE0OWYyNDYyZjIxM2VlYTcxYjVmZWUwMmY5
+    NTI5YjEwYWNlZjNlZmMyYzBmZmQyMDU0NWEwYzMwNzZjMWRkZDk=

data/Gemfile

@@ -7,6 +7,6 @@ group :development do
   # We depend on Vagrant for development, but we don't add it as a
   # gem dependency because we expect to be installed within the
   # Vagrant environment itself using `vagrant plugin`.
-  gem "vagrant", :git => "https://github.com/mitchellh/vagrant.git", :tag => 'v1.3.5'
+#  gem "vagrant", :git => "https://github.com/mitchellh/vagrant.git"
 end
 

data/README.md

@@ -8,7 +8,7 @@ Rationale
 ---------
 
 All Vagrant boxes come with the same ssh key and passwords installed. This
-means anyone who can ssh into your VM, will be able to authenticate to it
+means anyone who can ssh into your VM will be able to authenticate to it
 if they try the vagrant default credentials. Additionally, vagrant boxes
 come with passwordless sudo privileges, so anyone able to SSH into your 
 box will be able to do whatever they want on it.
@@ -17,7 +17,7 @@ As of Vagrant 1.2.3, for the most part this doesn't matter, because you can
 only access the Vagrant VM from localhost (previous versions allowed access
 from any machine on your local network). However, this becomes *extremely*
 important if you are using a vagrant box that is on a bridged network. If
-your VM is on a bridged network, without other controls in place that means
+your VM is on a bridged network without other controls in place, that means
 *anyone* who has access to your local network can SSH into your VM and get
 root access on it. There are plenty of documented ways of breaking out of a
 VM, so this is clearly a problem that needs to be addressed.
@@ -28,12 +28,12 @@ Since that isn't currently the case, I've created this plugin to help.
 This solution
 -------------
 
-The first time that this plugin is ran, it generates a unique SSH key and
+The first time that this plugin is run, it generates a unique SSH key and
 stores it as `~/vagrant.d/less_insecure_private_key`. Whenever you run the
 `vagrant provision` command, this plugin will run a script to check the
 authorized keys for the vagrant user to determine if the insecure key
-public key is present. If it is present, it will replace the key with the
-public key for the generated public key.
+public key is present. If it is present, it will replace the insecure key
+with the public key for the generated key pair.
 
 Additionally, if the insecure public key is present, it will delete the
 passwords for root and vagrant, so that you cannot login using a password.

data/lib/vagrant-rekey-ssh/actions/ssh_info.rb

@@ -28,7 +28,11 @@ module VagrantPlugins
           if @machine.config.ssh.private_key_path.nil?
             
             if ::File.exists?(rekey_sentinel_file)
-              @machine.config.ssh.private_key_path = ssh_key_path
+              if Vagrant::VERSION < "1.4.0"
+                @machine.config.ssh.private_key_path = ssh_key_path
+              else
+                @machine.config.ssh.private_key_path = [ssh_key_path]
+              end
             end
             
             # Vagrant < 1.4 only supports a single ssh key, do this differently

data/lib/vagrant-rekey-ssh/version.rb

@@ -1,5 +1,5 @@
 module VagrantPlugins
   module RekeySSH
-    VERSION = "0.1.1"
+    VERSION = "0.1.3"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-rekey-ssh
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.1.3
 platform: ruby
 authors:
 - Dustin Spicuzza
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-12-09 00:00:00.000000000 Z
+date: 2013-12-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -80,7 +80,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.1.10
+rubygems_version: 2.1.5
 signing_key: 
 specification_version: 4
 summary: Automatically secure vagrant boxes with a randomly generated SSH key