Receptor Security
-
- KVRist
- 273 posts since 5 Oct, 2005 from In front of iLok's headquarters with a Molotov Cocktail!
I was curious about the security of a Receptor on my Intranet at home. I have a router and firewall on my Internet connection and I run checks and look at my log files. So, I think I'm fairly safe. Obviously, I can telnet, start a X-Windows session, browse the file system but what else is "open"? Is there a method for setting a password for Receptor Remote? Could someone browse to my Receptor drive and grab my files? Or delete them? Seems to me someone could get a hold of Receptor Remote, enter in my IP and connect (if I had static IPs or IP forwarding) to my Receptor.
Or is this paranoid? I have no idea what services are started when Muse's version of Linux boots. So, that's why I ask.
Thanks in advance.
Or is this paranoid? I have no idea what services are started when Muse's version of Linux boots. So, that's why I ask.
Thanks in advance.
Death to all dongles!
-
- MUSEician
- 682 posts since 20 Aug, 2004 from California
If you have a router and firewall, nobody can get into your Receptor, unless you let them.
Do a Google search for NAT (short for Network Address Translation). Sometimes it is called port forwarding. Check your router's manual. You should find how you can open specific ports on Receptor or any other computer on your LAN. Then, make sure no ports are forwarded to Receptor, which should be the case since you did not open them manually.
Do a Google search for NAT (short for Network Address Translation). Sometimes it is called port forwarding. Check your router's manual. You should find how you can open specific ports on Receptor or any other computer on your LAN. Then, make sure no ports are forwarded to Receptor, which should be the case since you did not open them manually.
Dan Timis
Software Developer
Muse Research, Inc.
Software Developer
Muse Research, Inc.
-
- KVRist
- Topic Starter
- 273 posts since 5 Oct, 2005 from In front of iLok's headquarters with a Molotov Cocktail!
Oops! Yeah, I meant port forwarding and not IP. Doh.DanTimis wrote:If you have a router and firewall, nobody can get into your Receptor, unless you let them.
Do a Google search for NAT (short for Network Address Translation). Sometimes it is called port forwarding. Check your router's manual. You should find how you can open specific ports on Receptor or any other computer on your LAN. Then, make sure no ports are forwarded to Receptor, which should be the case since you did not open them manually.
Okay, I'm covered. I don't have any port forwarding going on. It's buttoned up pretty tight.
Thanks.
Death to all dongles!
-
- MUSEician
- 682 posts since 20 Aug, 2004 from California
We debugged a few Receptors by logging in remotely. For that to happen, the customer has to forward the port on their router to Receptor, and tell us the IP of the router (it does not need to be fixed IP - whatever IP they have at the time). We even logged in a Receptor located in Australia. 
Dan Timis
Software Developer
Muse Research, Inc.
Software Developer
Muse Research, Inc.
-
- KVRist
- 77 posts since 25 Nov, 2005 from Stoke on Trent, UK
Dan,
Is it possible to password protect a Receptor so its sound library cannot be removed from over a network connection when installed in a public location. I have a client who needs the facility.
Thanks,
Al.
Is it possible to password protect a Receptor so its sound library cannot be removed from over a network connection when installed in a public location. I have a client who needs the facility.
Thanks,
Al.
Hey, hey.. it's a party.. I want to party too...... Please don't ask me about Mac's tonight.
www.grizzlymedia.co.uk
www.grizzlymedia.co.uk
