another issue I'm facing with Colubris-AVPair is...
i'm hardcoding the return-list attributes in the radius.cfg file. the
way HP WLAN controller works is, it may require some placeholders to
be coded and the placeholders that is understood by the HP WLAN
controller uses special characters like %,
Hi All,
thank you to Klara. We have now added these to the dictionary in the latest
patch set.
Cheers.
On Tuesday 01 March 2011 07:07:23 am Klara Mall wrote:
> Hi,
>
> On 02/28/2011 09:42 PM, Heikki Vatiainen wrote:
> > On 02/28/2011 06:31 AM, Jeffrey Lee wrote:
> >> Mon Feb 28 15:27:01 2011: E
Hi,
On 02/28/2011 09:42 PM, Heikki Vatiainen wrote:
> On 02/28/2011 06:31 AM, Jeffrey Lee wrote:
>
>> Mon Feb 28 15:27:01 2011: ERR: Attribute number 254 (vendor 8744) is not
>> defined
>> in your dictionary
>> Mon Feb 28 15:27:01 2011: ERR: Attribute number 251 (vendor 8744) is not
>> defined
On 02/28/2011 06:31 AM, Jeffrey Lee wrote:
> Mon Feb 28 15:27:01 2011: ERR: Attribute number 254 (vendor 8744) is not
> defined
> in your dictionary
> Mon Feb 28 15:27:01 2011: ERR: Attribute number 251 (vendor 8744) is not
> defined
> in your dictionary
> Mon Feb 28 15:27:01 2011: ERR: Attrib
On 02/25/2011 03:32 PM, Gerard Alcorlo Bofill wrote:
> the error I'm receiving by mail is:
>
>
> Your program
>
>/usr/local/bin/radiusd -config_file
> /etc/radiator/radiuscesca/radiuscesca.cfg -foreground
>
> exited unexpectedly with exit status 25,
> signal number 0 and dump indication 0.
hi,
the root CA could be added to the server bundlebut that wont help
as the root CA needs to be known and trusted by the client. in this case,
windows 7.
rather than supplying certs, it seems like microsoft is supplying them 'on
demand'
in some cases...to keep fresh versions around rather
If I remember correctly, there is no way to solve this without hitting
Group Policy or requiring manual user intervention.
The issue is that out of the box, Windows trusts no root certificates for
802.1x authentication, no matter who the root CA is.
If you want to encourage your users to not clic
I've had a lot of fun with some Windows clients not showing particular CAs
(AddTrust External CA Root, in my case) in the list of recognized
certification authorities within the Windows 802.1X supplicant
configuration.
What's really frustrating is that the client must know about that particular
CA,
Earlier in February, my colleague contacted the list concerning the use
of Thawte intermediate certificates.
He followed the instructions he received from Heikki, (see a copy of
Heikki's message below my signature) and that seemed to resolve the
issue. At least for Mac's, older versions of Wi
