-
Notifications
You must be signed in to change notification settings - Fork 128
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
Problem with oc_addons *not* ignoring a second collar #1038
Comments
thumbs up
|
my mini con project actualy thought of this issue its one of the things i had meintioned a long time ago that was a potential issue, security hole solution is to store the key of the collar after successfull connection and ignore all calls from any thing else, then you have to have a way to detect when the collar id changes on relog, a solution i have not done yet would be to have the collar and app to store a shared secret and use that when restablishing connection. |
What version of OpenCollar are you using? OC 8.2.3
What behavior did you expect?
What behavior did you see instead? As a collar designer wearing a collar, if you rez a collar to work on it, the oc_addon script will try to connect the rezzed collar as an addon. The message you receive as Collar Wearer is: [19:44] Collar for Prototype Set: Addon connected successfully: OpenCollar
What steps does someone need to take to reproduce the problem? Wear a collar, then rez a second collar nearby
The text was updated successfully, but these errors were encountered: