Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

PEP8.

  • Loading branch information...
commit 2a06db1bd1584497a3545f179d4f7e23c93af02d 1 parent e8d81e6
@ralphbean authored
Showing with 10 additions and 9 deletions.
  1. +10 −9 fedmsg/crypto.py
View
19 fedmsg/crypto.py
@@ -49,8 +49,8 @@
To accomplish message signing, fedmsg must be able to read certificates and a
private key on disk. For message validation, it only need be able to read the
-certificate. Exactly *which* certificates are used are determined by looking up
-the ``certname`` in the :term:`certnames` config dict.
+certificate. Exactly *which* certificates are used are determined by looking
+up the ``certname`` in the :term:`certnames` config dict.
We use a large number of certs for the deployment of fedmsg. We have one cert
per `service-host`. For example, if we have 3 fedmsg-enabled services and each
@@ -63,8 +63,8 @@
Furthermore, attempts are made at the sysadmin-level to ensure that
fedmsg-enabled services run as users that have exclusive read access to their
own keys. See the `Fedora Infrastructure SOP
-<http://infrastructure.fedoraproject.org/infra/docs/fedmsg-certs.txt>`_ for more
-information (including how to generate new certs/bring up new services).
+<http://infrastructure.fedoraproject.org/infra/docs/fedmsg-certs.txt>`_ for
+more information (including how to generate new certs/bring up new services).
Routing Policy
--------------
@@ -84,9 +84,10 @@
If the topic of a message does *not* appear in the :term:`routing_policy`, two
different courses of action are possible:
- - If :term:`routing_nitpicky` is set to ``False``, then the message is given
- the green light. Our routing policy doesn't have anything specific to say
- about messages of this topic and so who are we to deny it passage, right?
+ - If :term:`routing_nitpicky` is set to ``False``, then the message is
+ given the green light. Our routing policy doesn't have anything
+ specific to say about messages of this topic and so who are we to deny
+ it passage, right?
- If :term:`routing_nitpicky` is set to ``True``, then we deny the message
and mark it as invalid.
@@ -269,8 +270,8 @@ def fail(reason):
if message['topic'] in routing_policy:
# If so.. is the signer one of those permitted senders?
if signer in routing_policy[message['topic']]:
- # We are good. The signer of this message is explicitly whitelisted
- # to send on this topic in our config policy.
+ # We are good. The signer of this message is explicitly
+ # whitelisted to send on this topic in our config policy.
pass
else:
# We have a policy for this topic and $homeboy isn't on the list.
Please sign in to comment.
Something went wrong with that request. Please try again.