@@ -30,7 +30,8 @@ Config styles currently supported::
30
30
Json (see SecureJson) -- whole-data encryption only.
31
31
serialized dictionaries (see SecureConfig) -- whole-data encryption only.
32
32
33
- Please let the maintainer (@nthmost) know if you want to see another type supported.
33
+ If you'd like to see another type supported, please file a feature request on GitHub
34
+ at https://github.com/nthmost/python-secureconfig
34
35
35
36
Purpose
36
37
-------
@@ -47,9 +48,9 @@ for ConfigParser that allows us to keep 99% of the way we interact with
47
48
config files, and simply wraps the decryption step.
48
49
49
50
Of course, once you have decryption handled, you start to want simplified
50
- ways of encrypting as well.
51
+ ways of encrypting as well. That's why secureconfig supports writing new
52
+ config files.
51
53
52
- That's why secureconfig (as of 0.0.3) supports writing new config files.
53
54
See "basic usage" sections below to see how you can easily turn a plaintext
54
55
value or file into an encrypted value or file (depending on config style).
55
56
@@ -65,9 +66,8 @@ run. (Turn this off using paranoid=False, if you must.)
65
66
Finally, secureconfig contains a smattering of deployment utilities found in
66
67
secureconfig.utils. Feel free to suggest new ones.
67
68
68
- This library can be found at https://bitbucket.org/nthmost/python-secureconfig
69
-
70
69
Contributions and code/documentation critiques are warmly welcomed.
70
+ See the Contribution section below for information.
71
71
72
72
73
73
How secureconfig Works
@@ -137,17 +137,14 @@ The following requirements form the backbone of secureconfig::
137
137
cryptography
138
138
configparser
139
139
cffi
140
- six
141
140
pycparser
142
141
143
- If you have any problems installing these requirements, please let the
144
- maintainer of this package know at https://bitbucket .com/nthmost/python-secureconfig
142
+ If you have any problems installing these requirements, please let us know as a
143
+ github issue at https://github .com/nthmost/python-secureconfig
145
144
146
145
SecureConfigParser
147
146
------------------
148
147
149
- NEW SINCE 0.1.0:
150
-
151
148
SecureConfigParser is a subclass of the configparser module's ConfigParser class.
152
149
153
150
The difference is that, when instantiated via one of the standardized cryptkeeper
@@ -308,20 +305,20 @@ Given the above, SecureString cannot at this time be implicity trusted as
308
305
"secure", since so much depends upon how it's used.
309
306
310
307
311
- Future
312
- ------
308
+ Contributions
309
+ -------------
313
310
314
- Planned features include::
311
+ The home for SecureConfig is on github:
312
+ https://github.com/nthmost/secureconfig
315
313
316
- - more automated-deployment-oriented utils
317
- - asymmetric key deployments (e.g. RSA public key encryption)
314
+ If you'd like to contribute, please make sure you run the tests (I normally use pytest)
315
+ found in the tests/ directory. I might merge fixes into master but I won't update pypi
316
+ with a new version unless ALL the tests pass.
318
317
318
+ If you want to contribute a novel feature, please file it as an issue in the github repo
319
+ so we can discuss it first!
319
320
320
- CONTACT
321
- -------
322
-
323
- Look for @nthmost on bitbucket if you're interested and would like to contribute!
324
321
Comments, critiques, and bug reports warmly welcomed. Pull requests encouraged.
325
322
326
- --Naomi Most, spring 2014.
323
+ --Naomi Most, 2014-2020 and onward .
327
324
0 commit comments