[vlc] can't register in forum

[Guy Perkins]

Konstantin

Thanks

Yes the Forum Videolan 403 page is certainly a bit more useful.
This does seem to reinforce the need for either information for users to
self diagnose or some sort of removal request link that retrieves the
clientside info required. I'm not on IRC sorry (and won't be)
Re the IP address. I can access all the pages without issue with FF from
the same machines & also my Samsung Galaxy droid phone over the same IP.
So in this instance it does appear to be an IE8 client issue.
Makes me smile that the link http://www.flameeyes.eu/projects/modsec
experiences the same issue(Forbidden), even www.flameeyes.eu. :)
(Reminds me of the good time years ago when modem manufacturers shipped
without drivers & said, "well, just download them")

Thanks

(FYI - User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1;
Trident/4.0) IP Address: 92.29.67.219)

Guy

-----Original Message-----
From: vlc-bounces at videolan.org [mailto:vlc-bounces at videolan.org] On
Behalf Of Konstantin Pavlov
Sent: 01 November 2011 06:38
To: Mailing list for VLC media player users
Subject: Re: [vlc] can't register in forum


On Tue, Nov 01, 2011 at 12:57:22AM -0000, Guy Perkins wrote:
> Hi
> 
> >From what I know and can work out.
> Firtsly, it seems to be to do with the blacklist used.

Indeed.

> Secondly, There is no information from devs about the blacklist 
> service used to allow users to try and help sort it.

Yeah, this was really frustrating for our users to see a blank page with
weird error. I have fixed forum.videolan.org to show more meaningful
webpage when this happens ( http://forum.videolan.org/403.html ).

Unfortunately I found no way to provide information why the user was
blocked; so the only way to find that out is to come on IRC as suggested
and ask me or other admins for help. 

Most of the time the IP addresses of users are banned as DNS blacklist
services list those as spam bots or open proxies.

> Lastly, This is the bit that I won't nail my hat on, but rather, it's 
> based on what I have tried. (with a pointer from Remi). User 
> agent...But..Not user agent alone, as if you try to resolve by 
> stripping .net and other extensions from a legitimate IE8 string, to 
> leave a bare IE8 string. No cigar, same 403. Tested IE8 strings in FF,

> but will return 403 in FF, so cannot establish if string blanketley 
> rejected, or if is detected as browser behaving as different to agent 
> & so rejected.

I think there might be a bug in our security system, so the best way to
debug IE8 issue is to come on IRC and chat with me. I don't have a
windows machine to test myself, unfortunately.

> Really need some method of either having access to blacklist provider 
> to solve, or conduit/facility to provide info for Devs to forward to 
> provider to resolve.

Sure.  We're using http://www.flameeyes.eu/projects/modsec by the way.

> Well understood that Devs far too busy to mess about with this, but, 
> guys, us users hands are tied here. We are ***sing in the wind.
> 
> Just to clarify, I am happy and willing to pursue and put the effort 
> in, not only for myself, but for others too. So please do not see this

> as me wanting to add to devs workload. We are just frustrated and 
> would really like to resolve this.

Sure.

-- 
Konstantin Pavlov
VideoLAN team ______________________________________________________
vlc mailing list
To unsubscribe or modify your subscription options:
http://mailman.videolan.org/listinfo/vlc