[BACK]Return to report.html CVS log [TXT][DIR] Up to [local] / www / openssh
File: [local] / www / openssh / report.html (download) (as text)

Revision 1.48, Fri Mar 17 02:46:03 2023 UTC (14 months, 2 weeks ago) by djm
Branch: MAIN
CVS Tags: HEAD
Changes since 1.47: +1 -1 lines 

update link to bugs closed since last release in OpenSSH bugzilla

<!doctype html>
<html lang=en>
<meta charset=utf-8>

<title>OpenSSH: Problem Reports</title>
<meta name="description" content="OpenSSH Problem Reports">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" type="text/css" href="openbsd.css">
<link rel="canonical" href="https://www.openssh.com/report.html">

<h2 id=OpenBSD>
<a href="/">
<i>Open</i><b>SSH</b></a>
Problem Reports
</h2>
<hr>

<h3>Released versions problem reports</h3>

<p>
Before reporting bugs/problems with released OpenSSH versions,
go through this checklist:

<ol>
<li>Check for <a href="https://www.openbsd.org/errata.html">patches
	and notes regarding OpenSSH.</a>
<li>Find out if there is a newer version available for
<a href="openbsd.html">OpenBSD</a>
or for the <a href="portable.html">portable release</a>,
depending upon your platform.
<li>Check the list of <a
href="https://bugzilla.mindrot.org/buglist.cgi?product=Portable+OpenSSH&amp;bug_status=RESOLVED">
bugs fixed since the last release</a> and
<a
href="https://bugzilla.mindrot.org/showdependencytree.cgi?id=V_9_3">
known bugs reported since the last release</a>.
</ol>

<p>
If nothing looks like it addresses your problem, then use
<a href="https://bugzilla.mindrot.org">Bugzilla</a>
to submit a bug report (but see below for reporting security
bugs privately).

<p>
You can reach the OpenSSH developers by sending email to one of
the following addresses:

<ul>
<li><a href="mailto:openssh@openssh.com">openssh@openssh.com</a>.  This
	is a private list read only by the OpenSSH developers.<br>
	<b>Appropriate for:</b> reports of problems with OpenBSD's OpenSSH,
	reports of security problems in OpenSSH on any platform.<br>
	<b>Not appropriate for:</b> How-to queries, reports of problems on
	platforms other than OpenBSD or with third-party patches, general
	discussion.
<li><a href="mailto:openssh-unix-dev@mindrot.org">openssh-unix-dev@mindrot.org</a>
	This is a public list that requires subscription before posting.
	<!--and is open to posting from non-subscribed
	users.-->
	<br>
	<b>Appropriate for:</b> bug reports, how-to questions and discussion
	of OpenSSH on any platform (including OpenBSD).<br>
	<b>Not appropriate for:</b> reports of security problems,
	bug reports for binaries not supplied by the OpenSSH team (unless they
	can be reproduced with the vanilla OpenSSH distribution).
</ul>

<h3>Current version problem reports</h3>

<ol>
<li>Test the problem at least twice, with source updated a few days apart.
<li>Do not report source tree compilation problems, unless they persist.
	They are almost always your mistake or they are being worked on
	as you encounter them.
<li>Remember that the <a href="https://www.openbsd.org/anoncvs.html">AnonCVS</a>
	mirrors are updated behind the actual working source tree.
<li>Check for <a href="https://www.openbsd.org/plus.html">OpenSSH changes</a>
        to see if the problem has been addressed.
</ol>

<h3 id=bugtypes>Sending in bug reports</h3>

<p>
Try to pin-point the exact problem.  Never give vague instructions,
or detail vague problems like "it crashes."
Talk to others on IRC or use some
other forum such as the <a href="https://marc.info/?l=openssh-unix-dev&amp;r=1&amp;w=2">
mailing list archives</a>
to confirm that it is new, repeatable, etc., and make sure
it is not a local problem.

<p>
For an excellent overview of the art of reporting bugs, see Simon
Tatham's <a href="https://www.chiark.greenend.org.uk/~sgtatham/bugs.html">
How to Report Bugs Effectively</a>. Remember, the better the
information in your report, the better the chance that your problem
will be resolved.

<p>
New features are accepted, especially with code that implements
your suggested new feature.
If someone else writes code for your new feature, the chances are that
it will be misunderstood and created so that you will not recognize it.

<p>
Types of bug reports in order of desirability:

<ol>
<li>Repeatable problems with source fixes are the best.
<li>Repeatable problems that are not specific to your hardware/software
     layout.
<li>Repeatable problems specific to your software layout.
<li>Repeatable problems specific to your hardware layout.
</ol>