| 05aea14e16612262d4cefbc3cc8ec66a09abefbe |
|
29-Apr-2016 |
Kenny Root <kroot@google.com> |
SSLEngineTest: test multiple thread use
Use SSLEngine with multiple threads to make sure there are no issues.
(cherry picked from commit 58af60a00935641f4669afc358593456944644ec)
Bug: 28473706
Change-Id: Ica180edff10d03fdf5e31621a901ad5575a762f3
|
| 58af60a00935641f4669afc358593456944644ec |
|
29-Apr-2016 |
Kenny Root <kroot@google.com> |
SSLEngineTest: test multiple thread use
Use SSLEngine with multiple threads to make sure there are no issues.
Bug: 28473706
Change-Id: Ica180edff10d03fdf5e31621a901ad5575a762f3
|
| 7c4f30cf50079df52bc4572688c7c9eed129a4bb |
|
07-Apr-2015 |
Sergio Giro <sgiro@google.com> |
libcore: change SSLEngineTest to close SSLEngine instances
It was leaking resources allocated by SSLEngine's, pipes among others,
thus causing subsequent tests to fail with "too many open files"
errors. In OpenSSLEngineImpl, the resources are freed in the finalizer,
so there's no guarantee that resources as pipes will ever be freed
unless the engines are explicitly closed.
Change-Id: Ide90808a64278486a19bcdfcba628f623c62afc9
|
| 0f32b9d0a7dc862b2250c22e0c9407433eb50098 |
|
07-Jan-2015 |
Kenny Root <kroot@google.com> |
SSLEngineTest: position should be same as produced/consumed
The position of the buffer should match the number of bytes produced or
consumed. Make sure all the tests have this condition on the handshake.
(cherry picked from commit 946d9a0b59d1a615278ad52518fa588407dfebd2)
Bug: 18921387
Change-Id: I8d248b2ac189d801586510fb5aca2e3bd6701ffe
|
| 946d9a0b59d1a615278ad52518fa588407dfebd2 |
|
07-Jan-2015 |
Kenny Root <kroot@google.com> |
SSLEngineTest: position should be same as produced/consumed
The position of the buffer should match the number of bytes produced or
consumed. Make sure all the tests have this condition on the handshake.
Bug: 18921387
Change-Id: I8d248b2ac189d801586510fb5aca2e3bd6701ffe
|
| a368cef707903c2adc7868ba48a95ccdac5f7625 |
|
22-Apr-2014 |
Kenny Root <kroot@google.com> |
Fix SSLEngineTest for RI
The assymmetry between client and server with create sessions seems
strange. It seems like a bug in the RI, so make sure Android does the
right thing.
Change-Id: I7b7ab501bd1963757b7f067c6ace8230a19a3e53
|
| 727df1258e3b8386afea4778626c9ab16ef467d6 |
|
09-Apr-2014 |
Kenny Root <kroot@google.com> |
Update SSLEngineTest for OpenSSL
Our new OpenSSL-based SSLEngine supports all the new stuff and no longer
fails tests.
Change-Id: I7db8e5134ca36ebd963c7081cd7ba79d91b3e5e2
|
| 3ad1704dc8e4653f4ceaeb5d8315ddb28318a1bb |
|
02-Apr-2014 |
Kenny Root <kroot@google.com> |
Update SSLEngineTest for RI
The RI now supports TLSv1.2 with SSLEngine, so update all the
expectations for their tests. It also appears to disable "weak"
algorithms when you select TLSv1.2.
Change-Id: I564283bb4945d3b71bee0f89c93c6dd6e238b4f8
|
| 4557728efb66c455a52b7669a8eefef7a9e54854 |
|
11-Aug-2010 |
Jesse Wilson <jessewilson@google.com> |
Moving tests to be under the libcore.* package.
This is indended to make it easier to run on VMs that restrict the packages
from which application classes can be loaded. For example, on the RI you need
to use the bootclasspath to load these tests.
Change-Id: I52193f35c5fcca18b5a3e1d280505b1e29b388af
|