Bump pycrypto from 2.6 to 2.6.1

[dependabot[bot]]

Bumps pycrypto from 2.6 to 2.6.1.

Changelog

Sourced from pycrypto's changelog.

2.6.1

• [CVE-2013-1445] Fix PRNG not correctly reseeded in some situations.

  In previous versions of PyCrypto, the Crypto.Random PRNG exhibits a race condition that may cause forked processes to generate identical sequences of 'random' numbers.

  This is a fairly obscure bug that will (hopefully) not affect many applications, but the failure scenario is pretty bad. Here is some sample code that illustrates the problem:

  from binascii import hexlify
  import multiprocessing, pprint, time
  import Crypto.Random
  def task_main(arg):
  a = Crypto.Random.get_random_bytes(8)
  time.sleep(0.1)
  b = Crypto.Random.get_random_bytes(8)
  rdy, ack = arg
  rdy.set()
  ack.wait()
  return "%s,%s" % (hexlify(a).decode(),
  hexlify(b).decode())
  n_procs = 4
  manager = multiprocessing.Manager()
  rdys = [manager.Event() for i in range(n_procs)]
  acks = [manager.Event() for i in range(n_procs)]
  Crypto.Random.get_random_bytes(1)
  pool = multiprocessing.Pool(processes=n_procs,
  initializer=Crypto.Random.atfork)
  res_async = pool.map_async(task_main, zip(rdys, acks))
  pool.close()
  [rdy.wait() for rdy in rdys]
  [ack.set() for ack in acks]
  res = res_async.get()
  pprint.pprint(sorted(res))
  pool.join()
  

  The output should be random, but it looked like this:

  ['c607803ae01aa8c0,2e4de6457a304b34',
   'c607803ae01aa8c0,af80d08942b4c987',
   'c607803ae01aa8c0,b0e4c0853de927c4',
   'c607803ae01aa8c0,f0362585b3fceba4']
  

  This release fixes the problem by resetting the rate-limiter when Crypto.Random.atfork() is invoked. It also adds some tests and a

... (truncated)

Commits

• 7fd528d Release v2.6.1
• b37ffc0 Update the ChangeLog
• fa06af7 Fortuna: Add comments for reseed_interval and min_pool_size to FortunaAccumul...
• 19dcf7b Random: Make Crypto.Random.atfork() set last_reseed=None (CVE-2013-1445)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/onejgordon/flow-dashboard/network/alerts).