Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for manpage 'portsnap(8)'

This is an experimental report containing PRs for manpage 'portsnap(8)' as of Thu Apr 17 07:38:44 2014 UTC. See notes.


PRs for manpage 'portsnap(8)':
SSubmittedTrackerResp.Description
o2014/04/10bin/188432cpercivaportsnap(8): MITM attacks against portsnap mirrors (pmirror.sh)
o2014/04/10bin/188430cpercivaFreeze attacks against portsnap(8)
o2014/04/10bin/188428cpercivaMITM attacks against portsnap(8)
o2014/02/06bin/186510cperciva[PATCH] Latest BIND port triggers problem in portsnap(8)
o2014/02/03bin/186398cpercivafreebsd-update(8) and portsnap(8) don't work with proxies that require authentication
o2014/01/01bin/185385cpercivaportsnap(8): portsnap fetch can't fetch file
o2013/04/02bin/177573cpercivaportsnap(8): Ports collection don't update when using portsnap
o2012/11/19bin/173725cpercivaportsnap(8) - fix entry validation
o2010/11/21bin/152446cpercivaportsnap(8) error
o2010/07/12bin/148528cperciva[patch] portsnap(8): add new command mode
o2009/05/09bin/134389cpercivaportsnap(8): phttpget opens a new connections for every file fetched via proxy
o2008/07/31bin/126131cpercivaportsnap(8) fetch error with HTTP_PROXY or HTTP_PROXY_AUTH
12 problems total.


Notes

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.