The TLS reference tests run a connection against a reference implementation: OpenSSL o

cc./ <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url

I also added some of my findings to the wiki: <a href="https://github.com/cloudflare/g

Refactor golang tests using openssl about go HOT 4 CLOSED

cloudflare commented on July 28, 2024

Refactor golang tests using openssl

from go.

Comments (4)

claucece commented on July 28, 2024

cc./ @chris-wood

from go.

claucece commented on July 28, 2024

I also added some of my findings to the wiki: https://github.com/cloudflare/go/wiki/Starting-out#how-to-regenerate-the-tls-testdata

from go.

armfazh commented on July 28, 2024

one way to enforce OpenSSL runs from the build directory is by specifying the full path in openssl command.

$ ./Cofingure --prefix=/tmp/installOSSL
$ make 
$ make install

so you can verify that the openssl binary actually uses the recently-compiled libraries (and not the ones form file system) by specifying the LD_LIBRARYP_PATH environment variable.

$ LD_LIBRARY_PATH=/tmp/installOSSL/lib  ldd /tmp/installOSSL/bin/openssl
	linux-vdso.so.1 (0x00007ffed1faf000)
	libssl.so.3 => ./lib/libssl.so.3 (0x00007fab45329000)
	libcrypto.so.3 => ./lib/libcrypto.so.3 (0x00007fab44ce4000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fab44ac5000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fab446d4000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fab444d0000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fab458b7000)

from go.

claucece commented on July 28, 2024

I'll be checking this here: https://github.com/claucece/go-exp

from go.

Recommend Projects