Bug #3477
closedThe DNS on mobile devices is not working properly
Description
Mobile devices are (normally) not registered on dns, we can not depend on hostname verification.
Those devices should use skipidentify (less secure)
Updated by Matthieu CERDA over 11 years ago
- Tracker changed from Enhancement to Bug
- Subject changed from [android] skipidentify for mobile devices to The DNS on mobile devices is not working properly
- Category set to Techniques
- Status changed from New to Pending technical review
- Assignee set to Nicolas CHARLES
- Priority changed from N/A to 1 (highest)
- Target version set to 2.6.0~rc1
This looks like a valid workaround, but I'm invoking NCH for another validation
Updated by Nicolas CHARLES over 11 years ago
- Status changed from Pending technical review to Discussion
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
Thank you Cedric, this is awesome. I've merged it
However, I don't know on which version to target this fix, as it is on the android branch
Jon, I'll need your help on this one
Updated by Matthieu CERDA over 11 years ago
- Target version changed from 2.6.0~rc1 to 2.6.0
Updated by Jonathan CLARKE over 11 years ago
- Target version changed from 2.6.0 to 2.6.1
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.6.1 to 2.6.2
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.6.2 to 2.6.3
Updated by Nicolas PERRON over 11 years ago
- Target version deleted (
2.6.3)
Nicolas CHARLES wrote:
Thank you Cedric, this is awesome. I've merged it
However, I don't know on which version to target this fix, as it is on the android branch
Jon, I'll need your help on this one
AS you said, you've merged it... but on a special branch for Android so it does not look to be related to a Rudder version.
For the moment, I will remove its targeted version
Jon, what's your opinion on it ?
Updated by Jonathan CLARKE over 11 years ago
- Status changed from Discussion to Pending technical review
I think that ideally, this option (use of skipidentify) should be configurable on a host-by-host (or at least group-by-group) basis. It's not because a machine is running Android that DNS is unreliable, it's because it's in the field. So if you have an Android in an office, this is wrong, and if you have a Linux box out in the field, we'd need it too. For now, this an acceptable workaround, though.
As for the target version, since this isn't included in any release until the special branch for Android is merged into a main branch, it concerns no versions.
Updated by Jonathan CLARKE over 11 years ago
- Status changed from Pending technical review to Released
Updated by Benoît PECCATTE almost 10 years ago
- Project changed from 24 to Rudder
- Category changed from Techniques to Techniques
Updated by Benoît PECCATTE about 9 years ago
- Target version set to Ideas (not version specific)