Skip to content

env: enable tls on some nodes - #1405

Merged
roman-khimov merged 1 commit into
masterfrom
ezayats/tls
Aug 7, 2026
Merged

env: enable tls on some nodes#1405
roman-khimov merged 1 commit into
masterfrom
ezayats/tls

Conversation

@evgeniiz321

Copy link
Copy Markdown
Contributor

No description provided.

@evgeniiz321
evgeniiz321 marked this pull request as draft July 20, 2026 18:13
@evgeniiz321
evgeniiz321 marked this pull request as ready for review July 22, 2026 17:56

@roman-khimov roman-khimov left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I'm mostly interested in:

  • node functioning and registering its TLS port correctly in netmap
  • other nodes connecting to TLSed one (object on TLS node, GET via open)
  • TLSed node connecting to regular ones (object on open node, GET via TLS)
  • gateways connecting to TLSed node and doing the same accesses thing
  • registering TLS port in netmap and running with two really open ports, unregistered one being non-TLS, everything should work when going through any of these ports

@@ -0,0 +1,28 @@
-----BEGIN PRIVATE KEY-----

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Static key won't work for SN since nspcc-dev/neofs-node#4095, you need to extract the key from wallet with NeoGo (@532910 does this in production).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Updated.

Comment thread neofs-testlib/neofs_testlib/env/templates/ir.yaml Outdated
Comment thread pytest_tests/tests/conftest.py
@evgeniiz321
evgeniiz321 force-pushed the ezayats/tls branch 3 times, most recently from 0fbfc24 to b92a925 Compare July 27, 2026 15:31
@evgeniiz321
evgeniiz321 marked this pull request as draft July 27, 2026 15:32
@evgeniiz321
evgeniiz321 force-pushed the ezayats/tls branch 6 times, most recently from 266a143 to 1bfd4bf Compare July 28, 2026 22:06
@evgeniiz321

Copy link
Copy Markdown
Contributor Author

I'm mostly interested in:

  • node functioning and registering its TLS port correctly in netmap
  • other nodes connecting to TLSed one (object on TLS node, GET via open)
  • TLSed node connecting to regular ones (object on open node, GET via TLS)
  • gateways connecting to TLSed node and doing the same accesses thing
  • registering TLS port in netmap and running with two really open ports, unregistered one being non-TLS, everything should work when going through any of these ports

Added missing tests + enabled TLS for the most commonly used fixture throughout the tests.

@evgeniiz321
evgeniiz321 marked this pull request as ready for review July 28, 2026 22:10
Signed-off-by: Evgeniy Zayats <zayatsevgeniy@nspcc.io>

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[
x509.DNSName(self.domain),
x509.DNSName(f"*.{self.domain}"),
x509.IPAddress(ipaddress.ip_address("127.0.0.1")),

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Seems redundant.

Comment thread neofs-testlib/neofs_testlib/env/env.py
@roman-khimov
roman-khimov merged commit 8ad50df into master Aug 7, 2026
5 of 7 checks passed
@roman-khimov
roman-khimov deleted the ezayats/tls branch August 7, 2026 08:02
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.

3 participants