Skip to content
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

org.bouncycastle.tls.TlsFatalAlertReceived: access_denied(49) #1731

Open
yjb152 opened this issue Jul 3, 2024 · 1 comment
Open

org.bouncycastle.tls.TlsFatalAlertReceived: access_denied(49) #1731

yjb152 opened this issue Jul 3, 2024 · 1 comment

Comments

@yjb152
Copy link

yjb152 commented Jul 3, 2024

I am encountering this issue with bctls-jdk18on versions above 1.71, but the problem does not occur when using bctls-jdk18on:1.71. This issue happens on the Windows 11 terminal, but not on Apple devices such as iPhones or Macs. This problem has been troubling me for a long time, do you have any suggestions for troubleshooting?

idea

@peterdettman
Copy link
Collaborator

TlsFatalAlertReceived indicates an error from the peer, not a local error.

access_denied: A valid certificate or PSK was received, but when
access control was applied, the sender decided not to proceed with
negotiation.

So presumably you are connecting to a server and it is denying access based on the presented certificate. That makes it difficult to see how the BC version could be relevant, but perhaps the later versions of BC are negotiating a different TLS protocol (e.g. TLS 1.3) and the bug arises downstream of that.

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

No branches or pull requests

2 participants