Renaming during Machine Authentication
Phil Mayers
p.mayers at imperial.ac.uk
Tue May 24 20:34:26 CEST 2011
On 05/24/2011 06:00 PM, Mark Jones wrote:
> Here is the latest debug with termination on Aruba turned off:
> FreeRADIUS Version 2.1.10, for host i686-pc-linux-gnu, built on Mar 23
> Sending Access-Challenge of id 152 to 10.152.0.100 port 32819
> EAP-Message =
> 0x010403fc1940a003020102020900a014abbd42e47192300d06092a864886f70d0101050500308193310b3009060355040613024652310f300d060355040813065261646975733112301006035504071309536f6d65776865726531153013060355040a130c4578616d706c6520496e632e3120301e06092a864886f70d010901161161646d696e406578616d706c652e636f6d312630240603550403131d4578616d706c6520436572746966696361746520417574686f72697479301e170d3131303231303136333231325a170d3132303231303136333231325a308193310b3009060355040613024652310f300d0603550408130652616469757331
> EAP-Message =
> 0x12301006035504071309536f6d65776865726531153013060355040a130c4578616d706c6520496e632e3120301e06092a864886f70d010901161161646d696e406578616d706c652e636f6d312630240603550403131d4578616d706c6520436572746966696361746520417574686f7269747930820122300d06092a864886f70d01010105000382010f003082010a0282010100aad4b906b8f15d9efa212c359bbae114566f2f9b0c75bf45ab4def0f4a617b3fe4e56795ecf32f378d128990b6317f25252528a101362bf9345a0a394dba35688e07e2eae969c4913c3796c1c224aced4e41e9d51f5335e6b9ec030da7c36217b48835b1df864ff9
> EAP-Message =
> 0xd82ada8cda0de980115896e4bd8ec5bab2a6b9111c109dafdb3e07d6ee4a5cebfa21f39e4efeb6a45e8a8cefc278ef3418aa2ccdb710ebe491eda4ed31df9156020958cddc21ce23a5749c9f06eeb098f3894184707af45719ff0d29350defa774ea4dbda2d0c61b7939abb1757a3ee271f1bb8d4b9868bc6289db9516b6a3d7fa5ad8abdbe57b5ce5359c9eb6a6169647d1310a53e40e930203010001a381fb3081f8301d0603551d0e0416041493331cbb1ef41d0e3c45f31449266f0c304c9b193081c80603551d230481c03081bd801493331cbb1ef41d0e3c45f31449266f0c304c9b19a18199a48196308193310b300906035504061302465231
> EAP-Message =
> 0x0f300d060355040813065261646975733112301006035504071309536f6d65776865726531153013060355040a130c4578616d706c6520496e632e3120301e06092a864886f70d010901161161646d696e406578616d706c652e636f6d312630240603550403131d4578616d706c6520436572746966696361746520417574686f72697479820900a014abbd42e47192300c0603551d13040530030101ff300d06092a864886f70d010105050003820101003cf11452f274ea06f722666622248542b6934b4f9aa2e919e20fb227801b1addbd2626d3570f8e4c20db411f132aa313a4e877f352772d0414b67207468978a5727bc5a22843f42390103f
> EAP-Message = 0x53c8cb22d3f8f1f7
> Message-Authenticator = 0x00000000000000000000000000000000
> State = 0x1ab6f10518b2e8e1468070e7a1c1e9d1
> Finished request 2.
Is this *really* the last thing it printed out? It didn't print
something about session expiry and a URL for you to look at?
Anyway - this is probably because the client doesn't know the CA cert.
You were previously terminating PEAP on the Aruba, so the cert was the
one belonging to Aruba. Now, it'll be the cert belonging to FreeRADIUS.
More information about the Freeradius-Users
mailing list