TMF files for EapHost on Windows 10?
Stefan.Paetow at jisc.ac.uk
Mon Apr 4 19:38:44 CEST 2016
Do you still need PDBs? I think I can get debug versions of these (I have
MSDN subs for that).
Moonshot Industry & Research Liaison Coordinator
t: +44 (0)1235 822 125
xmpp: stefanp at jabber.dev.ja.net
Jisc is a registered charity (number 1149740) and a company limited by
guarantee which is registered in England under Company No. 5747339, VAT
No. GB 197 0632 86. Jisc¹s registered office is: One Castlepark, Tower
Hill, Bristol, BS2 0JA. T 0203 697 5800.
Jisc Collections and Janet Ltd. is a wholly owned Jisc subsidiary and a
company limited by guarantee which is registered in England under Company
No. number 2881024, VAT No. GB 197 0632 86. The registered office is:
Lumen House, Library Avenue, Harwell, Didcot, Oxfordshire, OX11 0SG. T
On 20/03/2016 11:40, "Freeradius-Devel on behalf of Arran Cudbard-Bell"
<freeradius-devel-bounces+stefan.paetow=jisc.ac.uk at lists.freeradius.org on
behalf of a.cudbardb at freeradius.org> wrote:
>Hoping this reaches a friendly Microsoft person, or someone with more
>experience dealing with Windows development practices than me...
>It seems on Windows 10, you can still trace the EapHost service, but the
>output you get ETL files with lots of unresolvable UUIDs, which really
>aren't much use.
>Apparently there are TMF (Trace Message Format) files, which you need to
>convert the ETL files to something useful.
>I've got the PDB (public symbol files) files from the symbols package for
>Windows 10 Retail, but apparently they have the TMF information stripped,
>so are useless.
>Continuing the investigation into broken PEAP in v3.1.x. Managed to get
>a hacky fix for MSCHAPv2 by not setting the length flag in the outer
>Still cannot get PEAP-TLS to work, it always hangs after the server
>presents its certificate. The only time I did get it to work, was
>completely disabling fragmentation on the outer/inner EAP methods.
>Disabling fragmentation on the inner method only doesn't help.
>Also confirmed this particular issue is present in v3.0.x. Has anyone
>ever got Windows 10, PEAP-TLS working correctly with any version of
>Arran Cudbard-Bell <a.cudbardb at freeradius.org>
>FreeRADIUS development team
>FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
More information about the Freeradius-Devel