Comments (5)
Shouldn't the tunnel address be something easy to reproduce, for example, from the user email + box label (https://ferjm-gmail-com-home.foxlink.org)?
Think about the case where the user wants to install and use a new app. If we depend on the nupnp step to get the tunnel address, that means that the user needs to be in the same network as the box to start using this new app. Is that a limitation that we want to have?
from foxbox.
Like the idea of auto discoverable, but using the email we will be leaking user information, when later on we will open the box to 3rd parties.
from foxbox.
Email was just an example. We could use unique labels for boxes.
from foxbox.
Yes, only being able to request client pairing from the local network, or using a PIN from an already paired client, is a feature. Without that, you would get lots of spam requests.
I also thought maybe the tunnel address could already be advertised over nupnp, but this unnecessarily leaks extra information and also doesn't port well to QR codes. So I think the easiest way would be the client doing a GET
to the Box's API, to obtain the tunnel's public URL.
from foxbox.
We are adding the tunnel url to the registration server at fxbox/registration_server#11 so I guess this one is not needed anymore. Please, reopen it if I am wrong.
from foxbox.
Related Issues (20)
- Intermittent SSL linking failures on Mac OS X HOT 2
- Travis: Some components might not `cargo test` because dependencies are too recent HOT 4
- OpenZWave: Merge getter and setter maps
- Our env_logger configuration doesn't dispaly the location HOT 1
- HTTP API should leverage HTTP Cache (via Etag or Last-Modified-Since headers) HOT 4
- Add the ability to describe channels and services
- Taxonomy should offer a DELETE operation
- When channel setter is called with wrong arguments all possible setters are called HOT 10
- HTTP API should use HTTP Compression
- Use l10n on the UI
- `build.rs` doesn't spot wrong rustc version HOT 3
- Rename OpenClosed => IsOpen, OnOff => IsOn
- Thinkerbell rules should be delivered as JSON, not strings HOT 1
- Add a feature to turn on/off zwave support at build time. HOT 1
- API error response should be clearly distinguishable from the successful one
- Can't generate Let'sEncrypt certificates with outdated letsencrypt.sh script version (Ubuntu 16.04 LTS 64-bit) HOT 1
- Update readme
- Let users choose a friendly remote name.
- Fails to build on OSX HOT 1
- Fails to build on Debian 3.16.36-1+deb8u1 HOT 10
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from foxbox.