Last modified: 2011-04-11 01:40:59 UTC
IP addresses and ranges that have been account-creation blocked should not allow logged-in users to register new accounts. I've determined that a recent group of sockpuppet accounts I blocked (using checkuser) were registered from a range I had account-creation blocked. Apparently, the vandal had one sockpuppet account already (let's call it A), and used that account to register others - A registers for B, B registers for C, C registers for D, etc. All registrations were done using IP addressesI had already blocked.
Done in r32800.
(In reply to comment #1) > Done in r32800. > Gah, wrong bug.
ACB should be /real/ ACB rather than the current method of blocking account creation for anons-only. CUs can't be expected to be perfect, and this makes their job much easier. ACB on an IP or range needs to stop new accounts from being created, full stop. This is a loophole that requires perfection from CUs to close, and that's not cool; a software change is in order.
Sounds helpful. I support.
Fixed in r41150
*** Bug 14698 has been marked as a duplicate of this bug. ***
Please note that this bug causes me, an account creator at ACC, to not be able to create accounts when logged in even though the block on my shared IP that I sometimes edit from is anon. only.
Is your account in the IP block exempt group?
Now it is.
