Removal of deprecated authorized_keys handling

[artem-sidorenko]

Resolves #16

[coveralls]

Coverage remained the same at 100.0% when pulling 82a2a29 on artem-sidorenko:remove-deprecated-authorited-keys into d1f1bf1 on dev-sec:master.

[coveralls]

Coverage remained the same at 100.0% when pulling f1445dc on artem-sidorenko:remove-deprecated-authorited-keys into d1f1bf1 on dev-sec:master.

[coveralls]

Coverage remained the same at 100.0% when pulling 6775dbc on artem-sidorenko:remove-deprecated-authorited-keys into d1f1bf1 on dev-sec:master.

[coveralls]

Coverage remained the same at 100.0% when pulling 4cac0c0 on artem-sidorenko:remove-deprecated-authorited-keys into d1f1bf1 on dev-sec:master.

[coveralls]

Coverage remained the same at 100.0% when pulling 76bf9c5 on artem-sidorenko:remove-deprecated-authorited-keys into d1f1bf1 on dev-sec:master.

[atomic111]

@artem-sidorenko thanks for cleaning this. May be you should add a hint in the README.md for the users. how to handle the ssh-key deployment. What do you think?

[artem-sidorenko]

@atomic111 I added a short notice that user/key handling are out-of-scope. I do not want to recommend any solution for user/key management, as it completely depends on the environment and particular needs (e.g. some manage keys/users via chef/puppet, in other setups you will see LDAP or IPA or even AD)

[artem-sidorenko]

@atomic111 and the deprecation notice was > 2 years old. In case somebody used it in the past - there was enough time to thing about alternatives :-)

[coveralls]

Coverage remained the same at 100.0% when pulling a733ab2 on artem-sidorenko:remove-deprecated-authorited-keys into d1f1bf1 on dev-sec:master.

[atomic111]

great, thank you