Secure Socket Funneling 1.1.0#17
Secure Socket Funneling 1.1.0#17dgarske wants to merge 3 commits intowolfSSL:masterfrom dgarske:ssf_1.1
Conversation
…ME_WOLF.md with build instructions. Minor change to get `ssf_client_server_cipher_suites_tests` test to pass.
MJSPollard
left a comment
MJSPollard
left a comment
There was a problem hiding this comment.
All SSF unit tests passed when testing with wolfSSL/wolfssl#1739.
I opt for this to be merged into master.
|
|
||
| 2. Execute the following commands from the wolfSSL root directory | ||
|
|
||
| $ `cd wolfssl` |
There was a problem hiding this comment.
Above it says to start in the wolfSSL root directory. Do we want to change directory into the headers directory here?
| https://github.com/securesocketfunneling/ssf/releases | ||
| $ `wget https://github.com/securesocketfunneling/ssf/archive/1.1.0.tar.gz` | ||
| $ `tar -xzf 1.1.0.tar.gz` | ||
| Extracts to ssf-1.1.0 |
There was a problem hiding this comment.
Where are we downloading and extracting this to? Into the wolfSSL root directory? It's own directory parallel to wolfSSL? Somewhere else?
| $ `scp asio_1_65_1.tar.gz ubuntu@204.48.22.68:~/ssfwolfbuild` | ||
| $ `tar -xzf asio_1_65_1.tar.gz` | ||
|
|
||
| 5. Download boost 1_65_1 into third_party/boost |
| 5. Download boost 1_65_1 into third_party/boost | ||
|
|
||
| https://www.boost.org/users/history | ||
| $ `wget https://dl.bintray.com/boostorg/release/1.65.1/source/boost_1_65_1.tar.gz` |
There was a problem hiding this comment.
URL has changed. It is now found at https://boostorg.jfrog.io/artifactory/main/release/1.65.1/source/boost_1_65_1.tar.gz
|
|
||
| 4. Download ASIO 1.65.0 WolfSSL modified | ||
|
|
||
| $ `scp asio_1_65_1.tar.gz ubuntu@204.48.22.68:~/ssfwolfbuild` |
There was a problem hiding this comment.
When do we make ssfwolfbuild?
| $ `tar -xzf boost_1_65_1.tar.gz` | ||
| $ `cd boost_1_65_1` | ||
|
|
||
| Link boost to SSF from boost_1_65_1 directory |
There was a problem hiding this comment.
I had to guess where to do this. I did it from the ssf directory I got unarchiving the ssf sources above.
| $ `ln -s ../../../osp/asio_1_65_1 ./boost/asio` | ||
|
|
||
| Link boost to SSF from boost_1_65_1 directory | ||
| $ `cd ../ssf-1.1.0` |
There was a problem hiding this comment.
Again which directory? Where I installed everything, boost_1_65_1 wasn't at ../..
|
|
||
| $ `mkdir build` | ||
| $ `cd build` | ||
| $ `cmake -DCMAKE_BUILD_TYPE=Release -DWOLFSSL="/usr/local" ../` |
There was a problem hiding this comment.
CMake Error at cmake/external/ExternalPackageHelpers.cmake:246 (message):
[Boost] # Cannot determine Boost's source directory (NOTFOUND)
Call Stack (most recent call first):
cmake/external/ExternalPackageHelpers.cmake:818 (external_error)
cmake/external/ExternalPackageHelpers.cmake:929 (external_search_source_path)
cmake/external/boost/FindBoost.cmake:74 (externals_build)
cmake/external/boost/FindBoost.cmake:256 (boost_build_components)
CMakeLists.txt:193 (find_package)
|
Note: GitHub is not letting either Jacob or I reopen this PR so I'll just open a new one with a different branch name |
|
My fork was not tied upstream. Setup new proper fork. Attempting to re-open again based on that. Would like to use this PR to avoid loosing the comments. |
|
Reopening |
7 participants
No description provided.