Banning timeout fixed in 1.5.x?? Banning timeout fixed in 1.5.x??
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

Banning timeout fixed in 1.5.x??

Started by windyweather, March 16, 2009, 06:31:14 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

windyweather

Sorry to be such a bother, but I would like to have my question answered. I'm sure this is the wrong place to post it, but I don't see any place to post bug questions for the upcoming 1.5.x release. Surely there must be a place to ask whether a bug has been fixed in 1.5.x.

It is no help at all to deny a thread and lock it and not move it to the correct forum. Please move this to the correct forum so that the question can be answered.

Thank you so very much for your kind attention to this matter.

Sincerely and kind regards,
- w

Quote
Banning timeout fixed in 1.5.x??
« on: Yesterday at 10:29:16 PM »
   
Have we fixed this in 1.5.x??

http://forum.coppermine-gallery.net/index.php/topic,55464.0.html

I couldn't see it in the fixed list and couldn't post it in the dev board, so I assume you want it posted here.

Problem, to restate without the link, is that the banning timeout on failed login attempts does not work. It does not timeout in the time specified.

This is a royal pain for users that encounter it. Seems like you need to wait until tomorrow until you can try again.

Thanks,
- w
   68.186.4.191
Joachim Müller
Administrator
Coppermine addict
*****
Gender: Male
Germany Germany

Posts: 41895


aka "GauGau"


View Profile WWW Personal Message (Offline)
   
   
Re: Banning timeout fixed in 1.5.x??
« Reply #1 on: Today at 03:36:26 AM »
   
cpg1.5.x goes unsupported (as in "no support at all"). Regular users can't even access this board. Only privileged users can access this board, but you are not allowed to start threads like yours. Don't abuse your extra privileges that come with your group membership. Locking.

Nibbler

I already told you it's not fixed. Fixed bugs are tagged as 'FIXED' when they have been fixed.

Joachim Müller

aargh. Use the quote button if applicable. Respect board rules. We don't care if you need to know wether this has been fixed in cpg1.5.x already or not. Reason is: cpg1.5.x hasn't been released yet and goes unsupported. Unsupported means that you can't ask questions about it. Is that so hard to understand? Behaving so stubborn is just plain silly. If you decide to use cpg1.5.x before it has been released oficially, you have to live with the fact that it goes unsupported and that you're not allowed to post questions. If you need to find that out so badly, you could have downloaded cpg1.5.x, performed an install on a local testbed and figured out if this has already been fixed or not.
Spreading the same question over the entire site in various sub-boards is just board clutter - something we're not very fond of. You just lost your privileges due to your misbehaviour.