<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 4/19/2022 1:47 PM, Ullfig, Roberto
Alfredo wrote:<br>
</div>
<blockquote type="cite"
cite="mid:PH7PR13MB5480C52790E65DA9EF9F9367B0F29@PH7PR13MB5480.namprd13.prod.outlook.com">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif;
font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
AuthFILE PEAP TLS Handshake error: result: -1, reason/error:
'SSL_ERROR_SSL', state: 'error', error:1408F10B:SSL
routines:SSL3_GET_RECORD:wrong version number<br>
</div>
[...]
<div style="font-family: Calibri, Arial, Helvetica, sans-serif;
font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Any idea why 1 out of 490 logins fail from an automated monitor?</div>
</blockquote>
<p>This reminds me of a bug I bumped into with one of the Perl
crypto modules (IO::Socket::SSL I think) which was triggered only
when the first byte of a buffer was "0", so it would happen
approximately once every 256 connections.</p>
<p>I'd check that your dependencies are up to date on both the
server and client side...<br>
</p>
<pre class="moz-signature" cols="72">--
%% Christopher A. Bongaarts %% <a class="moz-txt-link-abbreviated" href="mailto:cab@umn.edu">cab@umn.edu</a> %%
%% OIT - Identity Management %% <a class="moz-txt-link-freetext" href="http://umn.edu/~cab">http://umn.edu/~cab</a> %%
%% University of Minnesota %% +1 (612) 625-1809 %%
</pre>
</body>
</html>