| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Modifies Ssl & SslContext.
This removes the errors like:
src/ssl/tests.rs:202:14: 202:27 error: the trait `core::kinds::Send` is not implemented for the type `*mut libc::types::common::c95::c_void`
src/ssl/tests.rs:202 let _t = Thread::spawn(move || {
^~~~~~~~~~~~~
src/ssl/tests.rs:202:14: 202:27 note: the type `*mut libc::types::common::c95::c_void` must implement `core::kinds::Send` because it appears within the type `ssl::Ssl`
We may want some locking around calls that do multiple operations on
the underlying Ssl and SslContext objects, but this lets us preserve
functionality for now.
|
| | |
|
| |
|
|
| |
This is breaking occaisionally but I can't repro it locally :(
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Closes #6
|
| | |
|
| | |
|
| |
|
|
|
| |
The use case here is to allow methods like `set_read_timeout` to be
called.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Allows calling SSL_accept() instead of SSL_connect() when creating an
SslStream.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
- Added cert loading
- Extracted X509 tests
|
| |
|
|
|
|
|
|
|
| |
`libcrypto` uses locks quite intensively even without SSL.
So they should be initialized before everything else to
function properly in multi-threaded apps in which SSL
operations are absent or delayed.
Finishes #79
|
| | |
|
| |
|
|
|
| |
Move common ffi initialization code to 'ffi::init()' and the initialization of error handling to a
a shared location.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Although wrapping was relatively easy it basically meant
that we depend on C compilation which becomes nightmare
as soon as multiple platforms are used. I’ve got a huge pain
once iOS was involved with 3 device archs and 2 simulator
arches to support, not mentioning different set of include
and lib flags.
So there are 2 different approaches:
- continue this way, maintaining all compilation issues like
like managing correct flags, providing correct paths and so
on. This way our Makefile will grow extremely fast and will
actually take more efforts to maintain.
- doing it pure Rust way. In this case we provide all the
macros expansions inside our wrappers and there should be
no other way to access raw data other than through those
wrappers. It might be fragile if OpenSSL internal data
structures will ever change, but I think (or hope) it is
pretty stable and wouldn’t change anytime soon.
This PR eliminates `BN_is_zero` at all from public API. It’s
functionality is implemented in `BigNum.is_zero` and should
be enough.
Additional notes:
1. I’ve moved BIGNUM into `bn` so it could access fields
directly and keep it as an opaque structure for everyone
else
2. I’ve kept empty Makefile as I hope to land `feature-matrix`
branch soon and I don’t like merging deleted/added file
conflicts.
|
| | |
|
| | |
|
| |\
| |
| | |
Fix #65: failing test case
|
| | | |
|
| |\ \
| | |
| | | |
Fixed incorrect EOF handling in MemBio, added error description
|
| | | |
| | |
| | |
| | | |
Actually, EOF wasn't handled at all and it caused `mem_bio.read_to_end()` to fail. Which in turn failed all `write_pem` implementations.
|
| |\ \ \
| |/ /
|/| | |
Using `Path`s instead of plain strings
|
| | |/
| |
| | |
Refs #45
|
| |/ |
|
| |
|
|
| |
cc #65
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Change error messages from numeric codes to human readable strings. This makes debugging failures much easier.
|
| | |
|
| |
|
|
|
| |
There is no need in wrapping function in option as there is no
sense in providing data without function.
|
| | |
|
| | |
|
| | |
|
| |
|
| |
Required quite a lot of refactoring
|
| | |
|
| |
|
|
|
|
|
| |
Unfortunately OS X comes with 0.9.8 bundled. There is a way to
install a recent version through homebrew, however it is
extremely hard to make it link agains brewed version without
tricking link version
|
| | |
|
| |\
| |
| | |
Allow to set cert/key pair
|
| | | |
|
| | | |
|
| |/ |
|