On 02/01/2011 07:11 PM, Adam Bishop wrote:
> OK, the issue is fixed in SAMBA 3.5.6.
Good to hear.
> It's a horrible, dirty fix, but to get 3.5.6 into 10.04 quickly:
>
> 0) Back up smb.conf
>
> 1) # aptitude purge samba winbind samba-common
>
> 2) add these 2 lines to /etc/apt/sources.lst
> deb
OK, the issue is fixed in SAMBA 3.5.6.
It's a horrible, dirty fix, but to get 3.5.6 into 10.04 quickly:
0) Back up smb.conf
1) # aptitude purge samba winbind samba-common
2) add these 2 lines to /etc/apt/sources.lst
deb http://gb.archive.ubuntu.com/ubuntu/ natty main restricted
deb-src http://g
Looks like you're right with the PEAP/SAMBA issue, seems to be a broken
SAMBA version.
Not sure how I'm going to solve this without an OS switch or compiling
from source - looking at the original thread, the password hash gained
from ntlm_auth needs to be hashed a second time?
Would simply patchi
On 02/01/2011 03:49 PM, Adam Bishop wrote:
> Encountering an odd issue with MSCHAPv2/PEAP
>
> I have 2 Radiator instances – one based on Debian 5, one on Ubuntu 10.04LTS.
> They share a config file (barring secrets), and the Debian one works fine.
> There is a difference in patch level – If I
Second trace as it exceeded the size limit:
Adam Bishop
--- Direct Trace 4 ---
Tue Feb 1 12:00:50 2011: DEBUG: Packet dump:
*** Received from 193.63.63.103 port 1814
Code: Access-Request
Identifier: 17
Authentic: (<26><187> <203><250>[<240><131>mS~<24><19>h<202>
Attributes:
User-Na
Encountering an odd issue with MSCHAPv2/PEAP
I have 2 Radiator instances – one based on Debian 5, one on Ubuntu 10.04LTS.
They share a config file (barring secrets), and the Debian one works fine.
There is a difference in patch level – If I remember correctly, the Debian
install is a few patc
