Relatando problemas no Weblate¶
O rastreador de problemas do Weblate está hospedado no GitHub.
Feel welcome to report any issues you have or suggest improvements for Weblate there. There are various templates prepared to comfortably guide you through the issue report.
Se o que encontrou é um problema de segurança no Weblate, consulte a secção Informar problemas de segurança abaixo.
Se não tem certeza sobre o seu relatório de bug ou solicitação de recurso, pode tentar Discussões do Weblate.
Informar problemas de segurança¶
Weblate’s development team is strongly committed to responsible reporting and disclosure of security-related issues. We have adopted and follow policies that are geared toward delivering timely security updates to Weblate.
Most normal bugs in Weblate are reported to our public GitHub issues tracker, but due to the sensitive nature of security issues, we ask that they not be publicly reported in this fashion.
Instead, if you believe you’ve found something in Weblate that has security implications, please submit a description of the issue to security@weblate.org, GitHub, or using HackerOne.
A member of the security team will respond to you within 48 hours, and depending on what action is taken, you may get more follow-up emails.
Nota
Sending encrypted reports
If you want to send an encrypted email (optional), please use the public
key for michal@weblate.org with ID 3CB 1DF1 EF12 CF2A C0EE 5A32 9C27 B313
42B7 511D. This public key is available on the most commonly used key servers,
and from Keybase.
Dica
O Weblate depende de componentes de terceiros para muitas coisas. Caso encontre uma vulnerabilidade a afetar um desses componentes em geral, relate-o diretamente ao respectivo projeto.
Alguns deles são: