Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#48395 - Can't register on the Wiki

Attached to Project: Arch Linux
Opened by Emilio Cobos Álvarez (emiliocobos) - Wednesday, 02 March 2016, 00:30 GMT
Last edited by Jelle van der Waa (jelly) - Tuesday, 29 May 2018, 18:29 GMT
Task Type Bug Report
Category Web Sites
Status Assigned
Assigned To Pierre Schmitz (Pierre)
Giancarlo Razzolini (grazzolini)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 7
Private No

Details

Description:

Hi, I was trying to register the Wiki to add information about a difficult-to-debug SANE+CUPS conflict.

When I was trying to register, filling all the fields, but it keeps telling me that my answer is wrong.

The question was:

* What's the output of "pacman -V|base32|head -1"

Actually that command echoes on my system:

BIQC4LJNFYQCAIBAEAQCAIBAEAQCAIBAEAQCAICQMFRW2YLOEB3DKLRQFYYSALJANRUWEYLMOBWS

Output of "pacman -V":


.--. Pacman v5.0.1 - libalpm v10.0.1
/ _.-' .-. .-. .-. Copyright (C) 2006-2016 Pacman Development Team
\ '-. '-' '-' '-' Copyright (C) 2002-2006 Judd Vinet
'--'
This program may be freely redistributed under
the terms of the GNU General Public License.

Sorry if this is not the place to report something like this.
This task depends upon

Comment by Doug Newgard (Scimmia) - Wednesday, 02 March 2016, 00:35 GMT
Hasn't been updated for pacman 5.0.1, I would guess.

This is pretty fragile. Really bad when we have different versions of pacman in Core and Testing.
Comment by Stefano (senden9) - Saturday, 05 March 2016, 17:27 GMT
Pacman v5.0.1 and libalpm v10.0.1 are now also in "core". Please update the question or use a other one.
Comment by Alad Wenter (Alad) - Saturday, 17 June 2017, 23:43 GMT
Issue present again due to the pacman 5.0.2 update. The current string for registration is (exchanging 0.2 for 0.1 in the pacman -V output):

BIQC4LJNFYQCAIBAEAQCAIBAEAQCAIBAEAQCAICQMFRW2YLOEB3DKLRQFYYSALJANRUWEYLMOBWS

The correct string is:

BIQC4LJNFYQCAIBAEAQCAIBAEAQCAIBAEAQCAICQMFRW2YLOEB3DKLRQFYZCALJANRUWEYLMOBWS
Comment by Tinu Weber (ayekat) - Wednesday, 21 June 2017, 08:09 GMT
This is also a bit problematic if a user runs into an issue during an upgrade of pacman and would like to register here to ask a question, but they can't because the forum has already updated to the new version of pacman.

Same for people who use a live ISO with an older version of pacman (which may happen towards the end of a month).

And most importantly, this will lock out all people who haven't got a running Arch Linux system (live or installed).

--edit: Sorry, was talking out of my ***, this concerns the Wiki, not the BBS. Please ignore my comment.
Comment by Eduardo Villegas (ludenticus) - Monday, 26 June 2017, 14:47 GMT
@Alad -- That's the other way around

Correct string is BIQC4LJNFYQCAIBAEAQCAIBAEAQCAIBAEAQCAICQMFRW2YLOEB3DKLRQFYYSALJANRUWEYLMOBWS
Comment by Marcin Andrzejewski (mpan) - Sunday, 06 August 2017, 05:58 GMT
What’s the point of this feature?
- Blocking random bots from creating accounts: it works equally well to a request to enter any preset string.
- Blocking attackers intentionally assaulting the Wiki: doesn’t work, as the string is fixed.

Maybe it would be simpler to just remove it and replace with the equivalent solution? Like: “please enter the second word: ‘cat dog dragon’”? Does the same, simpler to maintain, no unintended side-effects on version changes. If one needs a question, that would be hard to solve for human solvers, it can be an output of any common *nix command.
Comment by Sibren Vasse (SibrenVasse) - Tuesday, 29 May 2018, 05:37 GMT
I encountered this issue just now. Currently Pacman v5.0.2 works.
Comment by Jelle van der Waa (jelly) - Tuesday, 29 May 2018, 18:22 GMT
Or we make it non-version depended! repo-elephant| base32|head -1
Comment by Giancarlo Razzolini (grazzolini) - Tuesday, 29 May 2018, 18:29 GMT
Can any of you test this now? The string was updated to reflect the new pacman version.
Comment by Doug Newgard (Scimmia) - Tuesday, 29 May 2018, 21:21 GMT
Changing the string is just kicking the can down the road. The question needs to be changed so that it doesn't depend on a version of pacman. The question the forums use makes a lot more sense.
Comment by Giancarlo Razzolini (grazzolini) - Wednesday, 30 May 2018, 02:34 GMT
@Scimmia

I agree with that. But I'm not the wiki maintainer, and I would want to have his take on this before starting to make changes to the wiki's code. Having said that, we can think of better captchas across the board.
Comment by Jelle van der Waa (jelly) - Wednesday, 30 May 2018, 07:01 GMT
FYI, the bbs uses date -u +%V$(uname)|sha1sum|sed 's/\W//g'
Comment by Giancarlo Razzolini (grazzolini) - Wednesday, 30 May 2018, 10:25 GMT
That would make us need to change the string every week, instead of just when pacman version changes. From what I checked of the FunnyQuestions module (yes, it's not even a captcha module), it doesn't support a function for checking things, but I might be wrong. I don't know what the best solution is, without using an external captcha system.
Comment by niknah (niknah) - Friday, 15 February 2019, 05:36 GMT
It was set to sha256sum today...
date -u +%V$(uname)|sha256sum|sed 's/\W//g'

but then it changed back, or maybe it's random.

Loading...