PRs for tag 'crypto'
This is an experimental report containing PRs for tag 'crypto' as of 5-25-2012. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.
This report is generated statically.
Please give feedback on this report to linimon@FreeBSD.org. Thanks.
PRs for tag 'crypto':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2009/03/03 | kern/132277 | net | [crypto] [ipsec] poor performance using cryptodevice for IPSEC |
| o | 2008/02/04 | kern/120270 | simon | [crypto] [patch] AES-192 and AES-256 support for HW-accellerators ie. Hifn 795x / and OpenSSL engine 0.9.8e to _default_ use Cryptodev |
| p | 2007/08/21 | kern/115695 | [crypto] When "device padlock" defined first ssh to machine gives "Disconnecting: Bad packet length". | |
| o | 2006/02/24 | bin/93776 | [crypto] [patch] SHA256_Update / SHA512_Update fail to ensure correct alignment | |
| o | 2004/04/27 | kern/66029 | secteam | [crypto] [patch] MD5 alignment problem on a TriMedia processor |
Bugs can be in one of several states:
- o - open
- A problem report has been submitted, no sanity checking performed.
- a - analyzed
- The problem is understood and a solution is being sought.
- f - feedback
- Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
- p - patched
- A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
- r - repocopy
- The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
- s - suspended
- The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
- c - closed
- A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.