Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Secure Socket Funneling 1.1.0 #17

Closed
wants to merge 3 commits into from
Closed

Secure Socket Funneling 1.1.0 #17

wants to merge 3 commits into from

Conversation

dgarske
Copy link
Contributor

@dgarske dgarske commented Aug 2, 2018

No description provided.

dgarske added 2 commits August 2, 2018 15:49
…ME_WOLF.md with build instructions. Minor change to get `ssf_client_server_cipher_suites_tests` test to pass.
@dgarske dgarske self-assigned this Aug 2, 2018
@dgarske dgarske requested a review from MJSPollard August 7, 2018 16:00
@dgarske dgarske assigned toddouska and unassigned dgarske Aug 7, 2018
MJSPollard
MJSPollard previously approved these changes Aug 9, 2018
Copy link
Contributor

@MJSPollard MJSPollard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All SSF unit tests passed when testing with wolfSSL/wolfssl#1739.
I opt for this to be merged into master.

@dgarske dgarske assigned ejohnstown and unassigned toddouska Jul 28, 2021
@ejohnstown ejohnstown self-requested a review July 28, 2021 23:19
@dgarske dgarske assigned dgarske and unassigned ejohnstown Apr 25, 2022

2. Execute the following commands from the wolfSSL root directory

$ `cd wolfssl`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Download where?

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`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


4. Download ASIO 1.65.0 WolfSSL modified

$ `scp asio_1_65_1.tar.gz ubuntu@204.48.22.68:~/ssfwolfbuild`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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" ../`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)

@dgarske
Copy link
Contributor Author

dgarske commented Aug 3, 2023

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

@dgarske
Copy link
Contributor Author

dgarske commented Aug 3, 2023

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.

@dgarske
Copy link
Contributor Author

dgarske commented Aug 3, 2023

Reopening

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants