cocoapods-keys 1.3.1 → 1.3.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/CHANGELOG.md +4 -0
- data/Gemfile.lock +1 -1
- data/README.md +2 -2
- data/lib/cocoapods_keys.rb +1 -1
- data/lib/name_whisperer.rb +4 -3
- data/lib/plugin.rb +2 -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: dfeb86756e80df052b99475db7380a3b4801d4fd
|
4
|
+
data.tar.gz: 3a7db4640787b9daf6cf98a3a7764759425ab908
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: e8d025668c6ce05268a8b908c4a0e8d737725f74ab1d7e5b8b1a94afac977c1fdcde767ea02c02c4a2b2f2a1b13dce964ae25d913437f7b76e596ca4694b5989
|
7
|
+
data.tar.gz: 6e403a3dac62f4b1f0e89a2bbf6659d740a8fe3ec202eb6929475db609f5ac87b83f3401a33f9cd080710dfc08dca6e1503e91d6d284a33456a0d26180ec2662
|
data/CHANGELOG.md
CHANGED
data/Gemfile.lock
CHANGED
data/README.md
CHANGED
@@ -14,9 +14,9 @@ Requires CocoaPods 0.36
|
|
14
14
|
|
15
15
|
## How it works
|
16
16
|
|
17
|
-
Key names are stored in
|
17
|
+
Key names are stored in `~/.cocoapods/keys/` and key values in the OS X keychain. When you run `pod install` or `pod update`, an Objective-C class is created with scrambled versions of the keys, making it difficult to just [dump](https://github.com/stefanesser/dumpdecrypted) the contents of the decrypted binary and extract the keys. At runtime, the keys are unscrambled for use in your app.
|
18
18
|
|
19
|
-
The generated Objective-C classes are stored in the `Pods/
|
19
|
+
The generated Objective-C classes are stored in the `Pods/CocoaPodsKeys` directory, so if you're checking in your [Pods folder](http://guides.cocoapods.org/using/using-cocoapods.html#should-i-ignore-the-pods-directory-in-source-control), just add `Pods/CocoaPodsKeys` to your `.gitignore` file. CocoaPods-Keys supports integration in Swift or Objective-C projects.
|
20
20
|
|
21
21
|
## Usage
|
22
22
|
|
data/lib/cocoapods_keys.rb
CHANGED
data/lib/name_whisperer.rb
CHANGED
@@ -20,17 +20,18 @@ module CocoaPodsKeys
|
|
20
20
|
end
|
21
21
|
|
22
22
|
def self.search_folders_for_xcodeproj
|
23
|
+
ui = Pod::UserInterface
|
23
24
|
xcodeprojects = Pathname.glob('**/*.xcodeproj')
|
24
25
|
if xcodeprojects.length == 1
|
25
26
|
Pathname(xcodeprojects.first).basename
|
26
27
|
else
|
27
28
|
error_message = (xcodeprojects.length > 1) ? 'found too many' : "couldn't find any"
|
28
|
-
|
29
|
+
ui.puts 'CocoaPods-Keys ' + error_message + ' Xcode projects. Please give a name for this project.'
|
29
30
|
|
30
31
|
answer = ''
|
31
32
|
loop do
|
32
|
-
|
33
|
-
answer =
|
33
|
+
ui.print ' > '
|
34
|
+
answer = ui.gets.strip
|
34
35
|
break if answer.length > 0
|
35
36
|
end
|
36
37
|
answer
|
data/lib/plugin.rb
CHANGED
@@ -11,7 +11,8 @@ module CocoaPodsKeys
|
|
11
11
|
|
12
12
|
PreInstaller.new(user_options).setup
|
13
13
|
|
14
|
-
|
14
|
+
installation_root = Pod::Config.instance.installation_root
|
15
|
+
keys_path = installation_root.+('Pods/CocoaPodsKeys/').relative_path_from(installation_root)
|
15
16
|
|
16
17
|
# move our podspec in to the Pods
|
17
18
|
mkdir_p keys_path
|
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: cocoapods-keys
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.3.
|
4
|
+
version: 1.3.2
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Orta Therox
|
@@ -9,7 +9,7 @@ authors:
|
|
9
9
|
autorequire:
|
10
10
|
bindir: bin
|
11
11
|
cert_chain: []
|
12
|
-
date: 2015-06-
|
12
|
+
date: 2015-06-25 00:00:00.000000000 Z
|
13
13
|
dependencies:
|
14
14
|
- !ruby/object:Gem::Dependency
|
15
15
|
name: osx_keychain
|