|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
|
|
acl aclname myipHi, all
I'd like to use "acl aclname myip" on squid-3.1.0.14 like the following. acl testmyip myip 1.1.1.1/32 But, the following error occurred. 2009/10/16 14:03:21| aclParseAclLine: Invalid ACL type 'myip' I guess that src/AclReg.cc needs the following line. ACL::Prototype ACLMyIP::RegistryProtoype(&ACLMyIP::RegistryEntry_, "myip"); What do you think ? Sincerely, -- Mikio Kishi |
|
|
Re: acl aclname myipHi, all
> acl testmyip myip 1.1.1.1/32 > > But, the following error occurred. > > 2009/10/16 14:03:21| aclParseAclLine: Invalid ACL type 'myip' > > I guess that src/AclReg.cc needs the following line. > > ACL::Prototype ACLMyIP::RegistryProtoype(&ACLMyIP::RegistryEntry_, "myip"); How about the above ? Something wrong ? Please give me some advice... Sincerely, -- Mikio Kishi On Sun, Oct 18, 2009 at 3:52 AM, Mikio Kishi <mkishi@...> wrote: > Hi, all > > I'd like to use "acl aclname myip" on squid-3.1.0.14 like the following. > > acl testmyip myip 1.1.1.1/32 > > But, the following error occurred. > > 2009/10/16 14:03:21| aclParseAclLine: Invalid ACL type 'myip' > > I guess that src/AclReg.cc needs the following line. > > ACL::Prototype ACLMyIP::RegistryProtoype(&ACLMyIP::RegistryEntry_, "myip"); > > What do you think ? > > Sincerely, > > -- > Mikio Kishi > |
|
|
Re: acl aclname myipHi, Amos
squid-3.0.STABLE18 is OK. but squid-3.1.0.14 ... Could you fix that ? Sincerely, -- Mikio Kishi On Sun, Oct 18, 2009 at 3:52 AM, Mikio Kishi <mkishi@...> wrote: > Hi, all > > I'd like to use "acl aclname myip" on squid-3.1.0.14 like the following. > > acl testmyip myip 1.1.1.1/32 > > But, the following error occurred. > > 2009/10/16 14:03:21| aclParseAclLine: Invalid ACL type 'myip' > > I guess that src/AclReg.cc needs the following line. > > ACL::Prototype ACLMyIP::RegistryProtoype(&ACLMyIP::RegistryEntry_, "myip"); > > What do you think ? > > Sincerely, > > -- > Mikio Kishi > |
|
|
Re: Re: acl aclname myipMikio Kishi wrote:
> Hi, Amos > > squid-3.0.STABLE18 is OK. but squid-3.1.0.14 ... > Could you fix that ? > Ah sure. Thanks for the reminder. Applied to HEAD, should be added to 3.1 in a few days. Amos > Sincerely, > > -- > Mikio Kishi > > On Sun, Oct 18, 2009 at 3:52 AM, Mikio Kishi <mkishi@...> wrote: >> Hi, all >> >> I'd like to use "acl aclname myip" on squid-3.1.0.14 like the following. >> >> acl testmyip myip 1.1.1.1/32 >> >> But, the following error occurred. >> >> 2009/10/16 14:03:21| aclParseAclLine: Invalid ACL type 'myip' >> >> I guess that src/AclReg.cc needs the following line. >> >> ACL::Prototype ACLMyIP::RegistryProtoype(&ACLMyIP::RegistryEntry_, "myip"); >> >> What do you think ? >> >> Sincerely, >> >> -- >> Mikio Kishi >> -- Please be using Current Stable Squid 2.7.STABLE7 or 3.0.STABLE20 Current Beta Squid 3.1.0.14 |
|
|
Re: Re: acl aclname myipHi, Amos
> Ah sure. Thanks for the reminder. > Applied to HEAD, should be added to 3.1 in a few days. I'll be waiting ! And now, for something completely different, when would you release "3.1 STABLE" ? Do you have any plan ? Sincerely, -- Mikio Kishi On Tue, Nov 3, 2009 at 6:34 PM, Amos Jeffries <squid3@...> wrote: > Mikio Kishi wrote: >> >> Hi, Amos >> >> squid-3.0.STABLE18 is OK. but squid-3.1.0.14 ... >> Could you fix that ? >> > > Ah sure. Thanks for the reminder. > Applied to HEAD, should be added to 3.1 in a few days. > > Amos > >> Sincerely, >> >> -- >> Mikio Kishi >> >> On Sun, Oct 18, 2009 at 3:52 AM, Mikio Kishi <mkishi@...> wrote: >>> >>> Hi, all >>> >>> I'd like to use "acl aclname myip" on squid-3.1.0.14 like the following. >>> >>> acl testmyip myip 1.1.1.1/32 >>> >>> But, the following error occurred. >>> >>> 2009/10/16 14:03:21| aclParseAclLine: Invalid ACL type 'myip' >>> >>> I guess that src/AclReg.cc needs the following line. >>> >>> ACL::Prototype ACLMyIP::RegistryProtoype(&ACLMyIP::RegistryEntry_, >>> "myip"); >>> >>> What do you think ? >>> >>> Sincerely, >>> >>> -- >>> Mikio Kishi >>> > > > -- > Please be using > Current Stable Squid 2.7.STABLE7 or 3.0.STABLE20 > Current Beta Squid 3.1.0.14 > |
|
|
Re: Re: acl aclname myipMikio Kishi wrote:
> Hi, Amos > >> Ah sure. Thanks for the reminder. >> Applied to HEAD, should be added to 3.1 in a few days. > > I'll be waiting ! Ported. 'twill be in the next snapshot. > > And now, for something completely different, when would you release > "3.1 STABLE" ? > Do you have any plan ? No set timetable. We developers are all volunteers working largely unpaid on Squid in spare time. Which means we have to work towards a set of goals. Whenever those are met we can drop the beta tag. Right now it is entirely dependent on when the last critical blocker bugs can be diagnosed and fixed. As maintainer I have a rough goal in mind hoping to get it available on any OS around the end of the this year or early next year. 3.1 is usable and available _right now_ as packaged builds on... (full) FreeBSD, NetBSD and DragonFly. (experimental) Debian, Ubuntu and Gentoo. Build failures on OpenSolaris, SunOS and AIX being worked on. Some features on OpenBSD and MacOSX are broken, but is usable without those features AFAIK. Being worked on as well. (bit slowly since I'm having to work on them myself on OS I don't use daily...) Windows, MingW, Cygwin all need a fair chunk of developer time by someone with a Windows IDE. Guido struggles to keep up with the rest of us adding new stuff. Other OS? still seeking info. Runs well on all reported Linux derivatives is about all I'm certain of. Amos > > Sincerely, > > -- > Mikio Kishi > > > On Tue, Nov 3, 2009 at 6:34 PM, Amos Jeffries <squid3@...> wrote: >> Mikio Kishi wrote: >>> Hi, Amos >>> >>> squid-3.0.STABLE18 is OK. but squid-3.1.0.14 ... >>> Could you fix that ? >>> >> Ah sure. Thanks for the reminder. >> Applied to HEAD, should be added to 3.1 in a few days. >> >> Amos >> >>> Sincerely, >>> >>> -- >>> Mikio Kishi >>> >>> On Sun, Oct 18, 2009 at 3:52 AM, Mikio Kishi <mkishi@...> wrote: >>>> Hi, all >>>> >>>> I'd like to use "acl aclname myip" on squid-3.1.0.14 like the following. >>>> >>>> acl testmyip myip 1.1.1.1/32 >>>> >>>> But, the following error occurred. >>>> >>>> 2009/10/16 14:03:21| aclParseAclLine: Invalid ACL type 'myip' >>>> >>>> I guess that src/AclReg.cc needs the following line. >>>> >>>> ACL::Prototype ACLMyIP::RegistryProtoype(&ACLMyIP::RegistryEntry_, >>>> "myip"); >>>> >>>> What do you think ? >>>> >>>> Sincerely, >>>> >>>> -- >>>> Mikio Kishi >>>> >> >> -- >> Please be using >> Current Stable Squid 2.7.STABLE7 or 3.0.STABLE20 >> Current Beta Squid 3.1.0.14 >> -- Please be using Current Stable Squid 2.7.STABLE7 or 3.0.STABLE20 Current Beta Squid 3.1.0.14 |
|
|
FakeAuth windows build?Hi,
I am looking to provide an "invisible" challenge to users broswers to get their user/password details and authenticate that against LDAP. I notice that in the v3 (or 3.1?) build of Squid, the FakeAuth helper has an option to strip the domain from windows users, which should do what I want. However, there is currently no Windows build available with this option. Now, I don't want to put undue stress on anyone (because I appreciate you are (nearly?) all volunteers), so I don't mind, but I am wondering if anyone is able to either: a) be willing to compile and provide a windows executable of a versions of FakeAuth which has the -S (strip domain) option (assuming it will work with Squid 2.7 - I am willing to give it a go if no-one sees a reason why not) or b) give some guidelines how I can build/compile just the FakeAuth helper for windows (given I haven't done any decent C programming in over a decade, and even that was small-fry stuff...). Alternatively - any other options of providing an "invisible" challenge to users, which I can then authenticate against LDAP? Any help or advice appreciated! Regards, Dion |
|
|
Re: FakeAuth windows build?Dion Beauglehall wrote:
> Hi, > > I am looking to provide an "invisible" challenge to users broswers to get > their user/password details and authenticate that against LDAP. > > I notice that in the v3 (or 3.1?) build of Squid, the FakeAuth helper has an > option to strip the domain from windows users, which should do what I want. > However, there is currently no Windows build available with this option. > > Now, I don't want to put undue stress on anyone (because I appreciate you > are (nearly?) all volunteers), so I don't mind, but I am wondering if anyone > is able to either: > > a) be willing to compile and provide a windows executable of a versions of > FakeAuth which has the -S (strip domain) option (assuming it will work with > Squid 2.7 - I am willing to give it a go if no-one sees a reason why not) > > or > > b) give some guidelines how I can build/compile just the FakeAuth helper for > windows (given I haven't done any decent C programming in over a decade, and > even that was small-fry stuff...). All volunteers here. If you are able to spare a bit of coinage I woudl recommend throwing it towards Guido of Acme Consulting for a binary build. That will also go a small way towards helping the Windows port stay afloat. http://squid.acmeconsulting.it/ > > Alternatively - any other options of providing an "invisible" challenge to > users, which I can then authenticate against LDAP? There is no such thing as an invisible challenge. Squid makes all challenges in the same way. Whether the browser informs the user about requests for their login credentials is up to the browser. I very much doubt you will be able to get a good browser that passes unencrypted info on demand like that. If I understand your other emails LDAP is sending the username/password to Squid. NTLM only manages the silent way accepted because the username/password are not transferred. Also, Fake Auth is designed to accept a user that presses enter twice in the login box. Amos -- Please be using Current Stable Squid 2.7.STABLE7 or 3.0.STABLE20 Current Beta Squid 3.1.0.14 |
| Free embeddable forum powered by Nabble | Forum Help |