[OpenSSH]

How to report a Problem

Released versions problem reports.

Before reporting bugs/problems with released OpenSSH versions, go through this checklist:
  1. First check for patches and notes regarding OpenSSH.
  2. Next find out if there is a newer release available.

If nothing looks like it addresses your problem, then it may be time to read man sendbug before submitting a bug report.

You can reach the OpenSSH developers directly by sending email to openssh@openssh.com.

Current version problem reports.

  1. Test the problem at least twice, with source updated a few days apart.
  2. 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.
  3. Remember that the anoncvs servers are updated significantly behind the actual working source tree.
  4. Check for OpenSSH changes to see if the problem has been addressed.

Sending in bug reports.

Try to pin-point the exact problem. Never give vague instructions, or detail vague problems like "it crashes." Talk to others on IRC or some other forum to confirm that it is new, repeatable, etc. and make sure it is not a local problem.

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.

Types of bug reports in order of desirability:

  1. Repeatable problems with source fixes are the best.
  2. Repeatable problems that are not specific to your hardware/software layout.
  3. Repeatable problems specific to your software layout.
  4. Repeatable problems specific to your hardware layout.
OpenSSH www@openbsd.org
$OpenBSD: report.html,v 1.1 2000/05/05 17:13:35 provos Exp $