PRs for manpage 'portsnap(8)'
This is an experimental report containing PRs for manpage 'portsnap(8)' as of Fri May 30 07:38:49 2014 UTC. See notes.
PRs for manpage 'portsnap(8)':
|o||2014/04/10||bin/188432||cperciva||portsnap(8): MITM attacks against portsnap mirrors (pmirror.sh)|
|o||2014/04/10||bin/188430||cperciva||Freeze attacks against portsnap(8)|
|o||2014/04/10||bin/188428||cperciva||MITM attacks against portsnap(8)|
|o||2014/02/03||bin/186398||cperciva||freebsd-update(8) and portsnap(8) don't work with proxies that require authentication|
|o||2014/01/01||bin/185385||cperciva||portsnap(8): portsnap fetch can't fetch file|
|o||2013/04/02||bin/177573||cperciva||portsnap(8): Ports collection don't update when using portsnap|
|o||2012/11/19||bin/173725||cperciva||portsnap(8) - fix entry validation|
|o||2010/07/12||bin/148528||cperciva||[patch] portsnap(8): add new command mode|
|o||2009/05/09||bin/134389||cperciva||portsnap(8): phttpget opens a new connections for every file fetched via proxy|
|o||2008/07/31||bin/126131||cperciva||portsnap(8) fetch error with HTTP_PROXY or HTTP_PROXY_AUTH|
GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.
Please give feedback on this report to linimon@FreeBSD.org. Thanks.
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.