Bug 706803 - Impossible Captchas on FedoraProject.org when trying to become member.
Summary: Impossible Captchas on FedoraProject.org when trying to become member.
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: fedora-websites
Version: devel
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
Assignee: Fedora Websites Team
QA Contact: Karsten Wade
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-23 04:42 UTC by ewright2
Modified: 2013-03-11 16:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-11 16:07:38 UTC


Attachments (Terms of Use)
impossible captcha (4.12 KB, image/jpeg)
2011-05-23 04:43 UTC, ewright2
no flags Details

Description ewright2 2011-05-23 04:42:40 UTC
Description of problem:
Attached is the Captcha I am required to solve to become a member.  I've tried all the following possibilities, and none are right...

I should be able to hit a "get new captcha" button...


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Try to help out by becoming a BugZapper.
2. Fail at signing up for Fedora account.
  
Actual results:
no Fedora account


Expected results:
wanted Fedora account


Additional info:

Comment 1 ewright2 2011-05-23 04:43:19 UTC
Created attachment 500324 [details]
impossible captcha

Comment 2 ewright2 2011-05-23 04:46:39 UTC
HwtTX
HWtTX
CCHWtTX
CHWtTX
CHwTX

then a time out.

got a new Captcha, took 3 more tries, but it finally worked.

Comment 3 Toshio Ernie Kuratomi 2011-05-24 13:56:46 UTC
I agree, the captcha is not very good.  We have a new captcha that pingou wrote but we need to get it integrated into fas and push it to the servers.

Comment 4 Toshio Ernie Kuratomi 2013-03-11 16:07:38 UTC
Pingou's captcha has been available on the fas servers for quite a while now.  It prints an addition problem for the user to solve.  Closing.


Note You need to log in before you can comment on or make changes to this bug.