Not logged in
Log in now
Create an account
Subscribe to LWN
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
PostgreSQL 9.3 beta: Federated databases and more
Having thought about how else it could "worl" for a while, the only two ways I can think of are:
The vendor purchasing a FQDN. getting a CA signed cert for that domain, put that cert in the firmware image, then either:
* pointing it to a RFC 1918 address (internal, eg. 192.168.1.1)
* configuring the device to engage in some sort of dns spoofing.
All of which.. seems bad.
Am I close?
Posted Jan 6, 2011 17:35 UTC (Thu) by adamgundy (subscriber, #5418)
Posted Jan 7, 2011 11:48 UTC (Fri) by james (subscriber, #1325)
I imagine few users actually bother setting up static IP addresses, and many of those that do still use the router for DNS resolving (you don't know when your ISP is going to change their setup).
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds