You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Enhancement] Add a configuration option to always send secure profile key to whitelisted servers (in other words, to always treat whitelisted servers as enforcing secure profile)
#184
Closed
akemin-dayo opened this issue
Sep 2, 2022
· 4 comments
It would be helpful to add an configuration option to always send the user's secure profile key to any whitelisted server — in other words, to always treat whitelisted servers as enforcing secure profile.
This would avoid an undesirable situation where a user must prevent NCR from being loaded by their modloader of choice in order to join a secure-profile-enforced server that NCR is failing to detect (perhaps due to a custom disconnect reason being sent by the server), as seen in #185.
The text was updated successfully, but these errors were encountered:
akemin-dayo
changed the title
[Enhancement] Add a configuration option to always send secure profile key to whitelisted servers (in other words, to always treat whitelisted servers as enforcing secure profile) / [Issue] NCR can sometimes fail to detect that a third-party server is enforcing secure profile
[Enhancement] Add a configuration option to always send secure profile key to whitelisted servers (in other words, to always treat whitelisted servers as enforcing secure profile)
Sep 2, 2022
It would be helpful to add an configuration option to always send the user's secure profile key to any whitelisted server — in other words, to always treat whitelisted servers as enforcing secure profile.
This would avoid an undesirable situation where a user must prevent NCR from being loaded by their modloader of choice in order to join a secure-profile-enforced server that NCR is failing to detect (perhaps due to a custom disconnect reason being sent by the server), as seen in #185.
The text was updated successfully, but these errors were encountered: