Skip to content

Conversation

@DaneEveritt
Copy link
Member

Improves the security posture of things more by limiting the servers that a node can even communicate about with the Panel.

@DaneEveritt DaneEveritt added this to the v1.12.0 milestone Dec 27, 2025
@DaneEveritt DaneEveritt added the security This issue is related to security. This does not necessarily make it high priority. label Dec 27, 2025
@QuintenQVD0
Copy link
Contributor

Have you checked that transfers still work?

@DaneEveritt
Copy link
Member Author

@QuintenQVD0 are you able to test that for me, I don't have a good setup for that. So far as I can tell they should be fine since the logic checks that either the source/dest node making the request are associated with the transfer.


$server = $this->repository->getByUuid($uuid);
if (! $server->node->is($node)) {
throw new HttpForbiddenException('Requesting node does not have permission to access this server.');
Copy link
Contributor

@Boy132 Boy132 Jan 1, 2026

Choose a reason for hiding this comment

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

This will break transfers: the destination node will call this endpoint and then error because technically the server still belongs to the source node.

For reference: pelican-dev/panel#1680

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

security This issue is related to security. This does not necessarily make it high priority.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants