3 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4 <title>XML Security Library: Reporting Bugs</title>
6 <body><table witdh="100%" valign="top"><tr valign="top">
7 <td valign="top" align="left" width="210">
8 <img src="images/logo.gif" alt="XML Security Library" border="0"><p></p>
10 <li><a href="index.html">Home</a></li>
11 <li><a href="download.html">Download</a></li>
12 <li><a href="news.html">News</a></li>
13 <li><a href="documentation.html">Documentation</a></li>
15 <li><a href="faq.html">FAQ</a></li>
16 <li><a href="api/xmlsec-notes.html">Tutorial</a></li>
17 <li><a href="api/xmlsec-reference.html">API reference</a></li>
18 <li><a href="api/xmlsec-examples.html">Examples</a></li>
20 <li><a href="xmldsig.html">XML Digital Signature</a></li>
21 <ul><li><a href="http://www.aleksey.com/xmlsec/xmldsig-verifier.html">Online Verifier</a></li></ul>
22 <li><a href="xmlenc.html">XML Encryption</a></li>
23 <li><a href="c14n.html">XML Canonicalization</a></li>
24 <li><a href="bugs.html">Reporting Bugs</a></li>
25 <li><a href="http://www.aleksey.com/pipermail/xmlsec">Mailing list</a></li>
26 <li><a href="related.html">Related</a></li>
27 <li><a href="authors.html">Authors</a></li>
32 <td><a href="http://xmlsoft.org/"><img src="images/libxml2-logo.png" alt="LibXML2" border="0"></a></td>
36 <td><a href="http://xmlsoft.org/XSLT"><img src="images/libxslt-logo.png" alt="LibXSLT" border="0"></a></td>
40 <td><a href="http://www.openssl.org/"><img src="images/openssl-logo.png" alt="OpenSSL" border="0"></a></td>
42 <!--Links - start--><!--Links - end-->
45 <td valign="top"><table width="100%" valign="top"><tr><td valign="top" align="left" id="xmlsecContent">
46 <div align="center"><h2>Reporting Bugs and Getting Help</h2></div>
48 Well, any big enough program has a bug. You simply don't know where
49 exactly :) The best way to report a bug is to use the
50 <a href="http://bugzilla.gnome.org/buglist.cgi?product=xmlsec">Gnome bug
51 tracking database</a>. Please, make sure to use the "xmlsec" module name.
52 There is also a mailing list
53 <a href="mailto:xmlsec@aleksey.com">xmlsec@aleksey.com</a> with
54 <a href="http://www.aleksey.com/pipermail/xmlsec">online
55 archive</a>. To subscribe to this list
56 please visit <a href="http://www.aleksey.com/mailman/listinfo/xmlsec">list info</a>
57 Web page and follow instructions.</p>
58 <p>Before writing bug reports or questions do not
59 hesitate to check <a href="faq.html">FAQ</a> and old postings in the
60 <a href="http://www.aleksey.com/pipermail/xmlsec">mailing
61 list</a>. By doing this you might get the answer much faster.
62 If you are writing your own code based on the XMLSec library then you should
63 try to reproduce your problem with <a href="xmlsec-man.html">xmlsec command
64 line utiliy</a> first. And if it works just fine then you know whom to blame,
67 <p>If you did all the steps above and you still think that you found something
68 new then send as much information as possible, please.
69 A good question or bug report <b>MUST</b> include the following:
72 <li>XMLSec version number (or the snapshot date).
74 <li>The platform/compiler you are using.
76 <li>The exact xmlsec utility command line.
78 <li>All the files mentioned in this command line.
80 <li>The xmlsec utility output.
83 <p>I'll do my best to fix reported bugs or answer questions as soon as I can.
84 And of course, any patches, bug fixes and improvements are always welcome!<br></p>
85 <p>Please note, that bug tracking database and mailing list are open to anyone.
86 Any private or confidential information posted there became public.
87 The author of XMLSec library assumes no responsibility for any damage caused
88 by any information distribution using XMLSec
89 <a href="http://www.aleksey.com/pipermail/xmlsec">mailing
90 list</a>, GNOME CVS or
91 <a href="http://bugzilla.gnome.org/buglist.cgi?product=xmlsec">Gnome bug
92 tracking database</a>.
97 <a href="http://www.google.com"><img src="images/bart.gif" alt="Ask google" border="0"></a>
99 <small>Unfortunatelly, I don't know the author of this picture and I was not
100 able to ask permissions to publish it. If you are the author or know
101 the author then I would appreciate if you
102 <a href="mailto:aleksey@aleksey.com">send me</a> a message so I can ask
103 permissions and put author's name here.</small>
104 </td></tr></table></td>