Skip to content

Conversation

@aarani
Copy link
Collaborator

@aarani aarani commented Apr 22, 2023

Upgrade to .NET 6 was necessary to be able
to use SocksV5 (which is what tor gives us)
as proxy for HttpClient.

@aarani aarani requested a review from knocte April 22, 2023 21:12
@aarani aarani force-pushed the testHSWithTorClient branch from cf6a445 to a4cb1fa Compare April 23, 2023 12:05
@knocte
Copy link
Member

knocte commented Apr 25, 2023

Is this .NETStandard2.0 compatible?

@aarani
Copy link
Collaborator Author

aarani commented Apr 25, 2023

Is this .NETStandard2.0 compatible?

NOnion itself is not touched, I only upgraded the test project.

@knocte
Copy link
Member

knocte commented Apr 25, 2023

This branch has conflicts that must be resolved

^

@aarani aarani force-pushed the testHSWithTorClient branch 16 times, most recently from faf99ab to 657c560 Compare April 25, 2023 19:09
This commit introduces a test to make sure our
hidden service hosts are accessible by official
tor client.

Testing only with NOnion's TorServiceClient can
cause mask problems because it shares lots of
code with TorServiceHost (especially crypto stuff)
and mistakes there can go unnoticed.

Upgrade to .NET 6 was necessary to be able
to use SocksV5 (which is what tor gives us)
as proxy for HttpClient.

Due to some problem with NUnit not writing test-by-test
output (whether it passed or failed), I had to upgrade
even furthur into .NET 7.

NUnit was also updated to latest version because it was
causing issue where some unrelated tests would fail in
.NET7 (maybe the Retry attributed wasn't working).
@aarani aarani force-pushed the testHSWithTorClient branch 2 times, most recently from 5088bfe to 35d51d2 Compare April 25, 2023 19:33
@aarani
Copy link
Collaborator Author

aarani commented Apr 25, 2023

This is done, I ran the tests multiple times +12 times, the flakiness is gone.

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.

2 participants