Add config argument to more password.Password invocations. The work done to allow password_pbkdf2_default_rounds to be overridden for testing requires that calls to password.Password include a config argument. This was needed because using the real value more than quadrupled testing runtime. However there are still a few places where config was not being set when Password was called. I think this fixes all of the ones that are called from a function that have access to a db.config object. The remaining ones all call Password(encrypted=x). This results in Password.unpack() being called. If x is not a propertly formatted password string ("{scheme}...", it calls encodePassword. It then should end up raising the ConfigNotSet exception. This is probably what we want as it means the shape of "x" is not correct. I don't understand why Password.unpack() attempts to encrypt the value of encrypted if it doesn't match the right form. According to codecov, this encryption branch is being used, so somewhere x is of the wrong form. Hmmm....

<!-- dollarId: issue.index,v 1.2 2001/07/29 04:07:37 richard Exp dollar-->

<tal:block metal:use-macro="templates/page/macros/icing">

<title metal:fill-slot="head_title" i18n:translate="" >
 About this Tracker
</title>
<tal:block metal:fill-slot="body_title" i18n:translate="">
  About this Tracker
</tal:block>

<div class="content" metal:fill-slot="content">

 <span tal:condition="not:python:request.user.hasRole('Admin')"
	tal:omit-tag="python:1" i18n:translate="">
    Please login with your username and password to find out about
    this tracker.
  </span>

  <div tal:condition="python:request.user.hasRole('Admin')"
       tal:omit-tag="python:1" i18n:translate="">
    <div tal:replace="structure python:utils.AboutPage(db)"></div>
  </div>
</div>

</tal:block>