Hi,

On Sat, 13 Oct 2018 13:42:21 +0200
Gisle Vanem <gisle.va...@gmail.com> wrote:

> I've been running Tor successfully on my main
> PC for several years. Now, after trying Tor on another
> machine (only a slow Intel Atom CPU), I get lots of these
> error in the log:
>    Oct 12 07:40:02.000 [warn] Unhandled OpenSSL errors found at
> buffers_tls.c:69: Oct 12 07:40:02.000 [warn] TLS error: internal
> error (in SSL routines:tls13_hkdf_expand:---) Oct 12 07:40:02.000
> [warn] TLS error: internal error (in SSL
> routines:tls13_hkdf_expand:---)
> 
> The last is always duplicated. And these also appear after the:
>    Self-testing indicates your DirPort is reachable from the outside.
> Excellent. message.
> 
> Anybody recognize them and what the cause could be?
> 
> These also causes entries in my Windows event-log. Seems the
> OpenSSL function SSLfatal() does that via some BIO-log call.
> 
> 

i can't answer your questions but maybe you uncovered a regression.

commit 1992c761308538cffea64abecc9e45cbd47b1bda
Author: Nick Mathewson <ni...@torproject.org>
Date:   Sun Aug 12 16:04:12 2018 -0400

    Split tls modules and their tests into openssl and generic.

    Also, add a stubbed-out nss version of the modules.  The tests won't
    pass with NSS yet since the NSS modules don't do anything.

    This is a good patch to read with --color-moved.

https://gitweb.torproject.org/tor.git/commit/?id=1992c761308538cffea64abecc9e45cbd47b1bda

Please file a ticket to keep trac.

-- 
traumschule.org

gpg fingerprint:
9356 4DED 8546 8D9A C290  3605 12EE 7D70 7111 2056

/otr info
OTR: traumsch...@irc.indymedia.org fingerprint:
OTR: 35AACA83 4564616C B6EBEC66 56B6B2FC C8D572F1
OTR: traumsch...@irc.oftc.net fingerprint:
OTR: D1CCD207 B60C1866 56A975AE ACE090E9 45E90846
OTR: traumsch...@chat.freenode.net fingerprint:
OTR: 51BF8BB9 434840CC 24F264BC 76450C27 A6AADB12
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

Reply via email to