VPN: Difference between revisions
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
==Requirements for a VPN plugin== | ==Requirements for a VPN plugin== | ||
* Security | * Security | ||
** | ** Encryption | ||
** Secure method of "pairing" houses | ** Secure method of "pairing" houses | ||
This could be done by sharing a public key with whomever you wish to pair with. User 1 would enter User 2's public key along with an optional message. User 2 would manually approve User 1 for pairing, and the cores would connect via VPN and automatically share security notifications and anything else set in a settings panel. | This could be done by sharing a public key with whomever you wish to pair with. User 1 would enter User 2's public key along with an optional message. User 2 would manually approve User 1 for pairing, and the cores would connect via VPN and automatically share security notifications and anything else set in a settings panel. | ||
* Options panel for data to share with "paired" cores | |||
==Wish List== | |||
Add what you would like VPN to make possible in LinuxMCE | |||
Revision as of 21:06, 5 December 2007
VPN (Virtual Private Networking) offers a lot of potential for connecting multiple cores (between houses, apartments, etc.). This would enable families and friends to share security cameras, call/intercom each other for free via Asterisk, pipe security notifications to every device at every connected residence, and possibly even share media (legality?)
Requirements for a VPN plugin
- Security
- Encryption
- Secure method of "pairing" houses
This could be done by sharing a public key with whomever you wish to pair with. User 1 would enter User 2's public key along with an optional message. User 2 would manually approve User 1 for pairing, and the cores would connect via VPN and automatically share security notifications and anything else set in a settings panel.
- Options panel for data to share with "paired" cores
Wish List
Add what you would like VPN to make possible in LinuxMCE