Skip to content

Commit e352b9e

Browse files
committed
docs: update Changelog.
1 parent 6fa6995 commit e352b9e

File tree

1 file changed

+7
-9
lines changed

1 file changed

+7
-9
lines changed

docs/changelog.rst

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -164,8 +164,8 @@ Core Library
164164
`closed` flag, preventing historical bugs where a double close could destroy
165165
descriptors belonging to unrelated streams.
166166

167-
* `#586 <https://github.com/dw/mitogen/issues/586>`_: fix import of the
168-
`__main__` module on later versions of Python 3 when running from the
167+
* `#586 <https://github.com/dw/mitogen/issues/586>`_: fix import of
168+
:mod:`__main__` on later versions of Python 3 when running from the
169169
interactive console.
170170

171171
* `#606 <https://github.com/dw/mitogen/issues/606>`_: fix example code on the
@@ -192,13 +192,11 @@ Core Library
192192

193193
* `5924af15 <https://github.com/dw/mitogen/commit/5924af15>`_: *[security]* the
194194
unidirectional routing mode, in which contexts may only communicate with
195-
their parents and never siblings (such that a program cannot be used as a
196-
bridge for air-gapped networks) was not inherited when a new child context
197-
was initiated directly from an existing child.
198-
199-
The bug did not effect the Ansible extension since the top-level controller
200-
process initiates any new context that could be used for routing. Only
201-
forked tasks are started directly from children.
195+
parents and never siblings (so a program cannot accidentally bridge
196+
air-gapped networks) was not inherited when a child context was initiated
197+
directly from an existing child. This did not effect the Ansible extension,
198+
since the controller initiates any new context used for routing, only forked
199+
tasks are initiated by children.
202200

203201

204202
Thanks!

0 commit comments

Comments
 (0)