Skip to content

Unhandled and not logged _SecurityException in SecurityManager::init #5531

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

Closed
1 task done
Santti4go opened this issue Dec 30, 2024 · 2 comments
Closed
1 task done
Labels
ci-pending PR which CI is running

Comments

@Santti4go
Copy link
Contributor

Santti4go commented Dec 30, 2024

Is there an already existing issue for this?

  • I have searched the existing issues

Expected behavior

Be able to use an intermediate Certificate Authority as Permissions CA without issues.

Current behavior

Application is crashing when creating a participant and the error message does not show the real reason.

See the logging messages in the picture below.

image

I track the problem all the way to this throw false. That line of code would be followed by this catch block which doesn't handle any SecurityException that may have occurred.

I had a really hard time debugging another problem because of the issue above.
I believe just adding a logging message like I did on this PR would be enough. WDYT?

Steps to reproduce

Basically creating any participant that trigger the throw false mentioned above would end up on the catch.

I found this while debugging another issue that made the code end up there.
I'll open a second one with more details regarding the root cause as soon asap, either here or in the security tab if I believe it's needed. But since it's independent of this I decided to just open a PR with the least amount of changes.

Fast DDS version/commit

Using Fast-DDS 2.6.9. Same happens with 2.6.x and 2.6.8

Platform/Architecture

Ubuntu Focal 20.04 amd64

Transport layer

Default configuration, UDPv4 & SHM

@Santti4go Santti4go added the triage Issue pending classification label Dec 30, 2024
@EugenioCollado
Copy link
Contributor

Hi @Santti4go,

Thank you for reporting this issue and for creating a PR. We will take a look at it and take the corresponding actions.

@MiguelCompany
Copy link
Member

Fixed via #5530

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci-pending PR which CI is running
Projects
None yet
Development

No branches or pull requests

3 participants