| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
Should not be a problem, but makes static analyzers happy.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
changes
|
|
|
|
| |
Fixes #229.
|
| |
|
|
|
|
|
|
|
|
|
| |
framework
A bug in the framework on Android Jelly Bean causes a SIGSEGV when the private
key object returned from KeyChain.getPrivateKey is garbage collected.
Leaking the global reference to that object prevents the garbage
collection and thereby the crash.
|
| |
|
|
|
|
|
| |
We don't have a proper kernel-net interface on Android yet, so the check
for a usable interface does not work there.
|
| |
|
| |
|
|
|
|
|
| |
This is required because private keys are provided by an OpenSSL engine
in Jelly Bean, which makes them inaccessible directly via getEncoding.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|