- Home
- Download

- GitHub

- News
- Documentation

- FAQ
- Tutorial
- API reference
- Examples

- XML Digital Signature
- XML Encryption
- XML Canonicalization
- Reporting Bugs
- Mailing list
- Related
- Authors

## Reporting Bugs and Getting Help

Well, any big enough program has a bug. You simply don't know where exactly :) The best way to report a bug is to use the GitHub Issues Tracker.

Before writing bug reports or questions, do not hesitate to check the FAQ. If you are writing your own code based on the XMLSec library, then you should try to reproduce your problem with the xmlsec command-line utility first. And if it works just fine then you know whom to blame, don't you? :)

If you completed all the steps above and still think that you found something new, please provide as much information as possible. A good question or bug report MUST include the following:

- XMLSec version number (or the snapshot date).
- The platform/compiler you are using.
- The exact xmlsec utility command line.
- All the files mentioned in this command line.
- The xmlsec utility output.

I'll do my best to fix reported bugs or answer questions as soon as I can. And of course, any patches, bug fixes and improvements are always welcome!

Please note that the bug-tracking database is open to everyone. Any private or confidential information posted there becomes public. The authors of the XMLSec library assumes no responsibility for any damage caused by any information distributed using the XMLSec GitHub issues tracker, discussions, source code, or any other XMLSec-related tools.

Unfortunately, I don't know the author of this picture and I was not able to ask permission to publish it. If you are the author or know the author, I would appreciate a message on GitHub so I can request permission and add the author's name here.