[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #15503 [Tor]: VIA PadLock suupport does not work.
#15503: VIA PadLock suupport does not work.
------------------------+--------------------------------
Reporter: toyboy | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Tor: 0.2.7.x-final
Component: Tor | Version: Tor: unspecified
Resolution: | Keywords: VIA PadLock, lorax
Actual Points: | Parent ID:
Points: |
------------------------+--------------------------------
Changes (by yawning):
* keywords: VIA PadLock => VIA PadLock, lorax
* priority: major => normal
Comment:
Replying to [comment:1 nickm]:
> I wonder whether that's the invocation from SSL, or the invocation from
aes.c in Tor? Tor's aes.c uses EVP_aes_128_ctr() by default, I think --
is that accelerated in your setup?
That's TLS. Disabling GCM to test if padlock is working is sort of
overkill, since we log which engines we're going to use. The issue here
is that the user is running "OpenSSL-1.0.1OhMyGodUpgradeNow", which does
not have EVP CTR support (Checking through the git tags, while the code to
support it has been in the master branch for a while, they've never
shipped it in a stable release.
If the underlying copy of OpenSSL supported it, we would use it.
{{{
#ifdef NID_aes_128_ctr
log_engine("AES-128-CTR",
ENGINE_get_cipher_engine(NID_aes_128_ctr));
#endif
}}}
So, there's no bug on our side here for AES. Since we don't use EVP based
SHA1 currently, acceleration will not happen for that either, even if it
happens to be available, which may be something we can fix, but I don't
see this being major.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/15503#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs