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

Clarify security implications of sharing an access key #2323

Open
1 task done
dubov94 opened this issue Jan 13, 2025 · 2 comments
Open
1 task done

Clarify security implications of sharing an access key #2323

dubov94 opened this issue Jan 13, 2025 · 2 comments
Labels
documentation feature request New feature, we are tracking it

Comments

@dubov94
Copy link

dubov94 commented Jan 13, 2025

Is there an existing issue that is already proposing this?

  • I have searched the existing issues

Application

Outline Manager

What are you trying to do? What is your use case?

I'm interested in understanding the security implications of access keys being shared, either intentionally or unintentionally. This is crucial for designing secure key distribution mechanisms. There's a significant difference in risk between "a little extra, unaccounted-for traffic" and the claim made here: https://support.getoutline.org/s/article/multiuse-access-key, which states that "[s]omeone with your access key has access to all your internet traffic."

Consider a scenario where a chatbot within an app generates unique access keys for each user. If there's any reason to suspect that the app itself might not be trustworthy in keeping messages private, it would be safer to deliver the keys through a different, more secure channel.

This leads to the core question: what level of access does an access key holder truly possess?

Is your feature request related to a problem? Please describe it.

No response

Describe the solution you'd like.

I would appreciate a more comprehensive exploration of potential attack vectors related to access key sharing in the article.

Describe alternatives you've considered

No response

@dubov94 dubov94 added the feature request New feature, we are tracking it label Jan 13, 2025
@Fiyaas
Copy link

Fiyaas commented Jan 13, 2025

Is there an existing issue that is already proposing this?

  • I have searched the existing issues

Application

Outline Manager

What are you trying to do? What is your use case?

I'm interested in understanding the security implications of access keys being shared, either intentionally or unintentionally. This is crucial for designing secure key distribution mechanisms. There's a significant difference in risk between "a little extra, unaccounted-for traffic" and the claim made here: https://support.getoutline.org/s/article/multiuse-access-key, which states that "[s]omeone with your access key has access to all your internet traffic."

Consider a scenario where a chatbot within an app generates unique access keys for each user. If there's any reason to suspect that the app itself might not be trustworthy in keeping messages private, it would be safer to deliver the keys through a different, more secure channel.

This leads to the core question: what level of access does an access key holder truly possess?

Is your feature request related to a problem? Please describe it.

No response

Describe the solution you'd like.

I would appreciate a more comprehensive exploration of potential attack vectors related to access key sharing in the article.

Describe alternatives you've considered

No response

@sbruens
Copy link
Contributor

sbruens commented Jan 14, 2025

Thanks for filing this issue. I agree we could probably improve that help center article with more precise language and elaborate to avoid confusion about what is possible.

The access key holder has the ability to decrypt all traffic encrypted with that access key. So if a key is shared between 2 users, both users will be able to decrypt each other's traffic if they for example are on the same network and have access to each other's packets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation feature request New feature, we are tracking it
Projects
None yet
Development

No branches or pull requests

3 participants