TracCaptcha is a Trac plugin to embed a captcha in the ticket page in addition to Trac’s regular permission checks so that spammers are kept out.
“It just works”: Installation and configuration is very simple, just install the egg and put two configuration options in your trac.ini. No database changes required.
Batteries included: The popular reCAPTCHA system is supported out of the box. Technically it’s a plugin - if you don’t like it you’re free to use any other plugin while still leverage the benefits from the general captcha infrastructure.
Does not annoy users: After the user entered the captcha once, he does not have to solve the captcha again for the same ticket when he just clicks ‘preview’. Also you can configure exempt certain users or groups (e.g. ‘all authenticated users’) from the captchas just by using Trac’s permission system.
Easy to extend: Protecting an additional page with a captcha is very simple. Implementing captchas for the ticket module took only 20 lines of code! Captchas for the DiscussionPlugin needed 21 lines of code!
Easy to write custom captchas: If you don’t like reCAPTCHA, you can still use the generic infrastructure with all its features: You implement the code to generate the captcha and validate the user’s input. TracCaptcha will take care of displaying your plugin in all supported pages!
Changelog
0.3.1 (30.03.2011)
add config option to omit noscript section for recaptcha to enforce Javascript support for users
0.3 (25.03.2011)
add more debug logging about CAPTCHA display and accepted/rejected solutions to identify better how spammers managed to file a spam ticket
0.2.2 (04.02.2011)
fix tests on current Trac trunk (0.13dev)
fix: TICKET_ADMIN looses other ticket-related permissions on Trac < 0.13 thanks to Anton V. for reporting
0.2.1 (10.11.2010)
fix “installation” as egg file in Trac plugins folder
0.2 (10.07.2010)
integration in 3rd party Trac plugins: TracDiscussionPlugin and AccountManager (registration only)
reCAPTCHA: select widget theme via trac.ini (requires simplejson for Python 2.3-2.5)
reCAPTCHA: display the widget in the user’s locale (if translation is provided by the reCAPTCHA service)
reCAPTCHA: use HTTPS to include script files if Trac page was served with HTTPS
reCAPTCHA: show link for reCAPTCHA signup if no keys configured
reCAPTCHA: use new Google URLs
0.1 (25.06.2010)
initial release
1 maintainer
Metadata
1 maintainer
Release files for TracCaptcha 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| TracCaptcha-0.3.1.tar.gz | 25.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| TracCaptcha-0.3.1-py2.7.egg | Legacy Egg format | - | - | Details |
Total release size: 92.9 kB
Release files / TracCaptcha-0.3.1.tar.gz
| Download URL | TracCaptcha-0.3.1.tar.gz |
|---|---|
| Size | 25.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2368d3893d2808115a7980889006bd0b04fa1f936e1bd1c8d7c581abc0ca1a52
|
|
BLAKE2b-256 checksum How to use checksums |
47d971df9ef998f56cfb2f85366443c871aa355a9417c13095e11084f0f1af96
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / TracCaptcha-0.3.1-py2.7.egg
| Download URL | TracCaptcha-0.3.1-py2.7.egg |
|---|---|
| Size | 67.1 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
d8a06748519340e4c6ceb7a3e0e4ed0b3cf67620d11c338b3bdc14a4b89cc6c8
|
|
BLAKE2b-256 checksum How to use checksums |
10bda9e54588dcc51e33462e0eb4d53686045683765a9d527e6bc54dec577ace
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for TracCaptcha 0.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
