-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/31/2013 03:39 PM, James Cameron wrote:
> What would prevent a network intruder, or a malicious user of OLPC
> OS, from supplanting http://know.local ?
Well, it is no worse a problem than someone arp poisoning or handing
out fake dhcp replies. I
Looking into this a bit more, what I am seeing may be dependency specific.
If you are lucky enough to have a XO image that has extra items added,
nss-mdns may be present as a dependency. Otherwise it is not.
I could have sworn this worked at one point in this past though because I
have definitel
Thanks. I hit this yesterday.
We already have some mDNS support present for Sugar collaboration in a
network when a School Server is absent; we have the Avahi packages,
but as you rightly point out we don't have the name service switch
module for mDNS, and so a gethostbyname(3) doesn't look at th
Are you sure a change is required?
I just tried connecting using a randomly-grabbed 12.1.0 machine to a
network-connected printer (http://hp-model_id.local/) via HTTP and it
worked fine.
On Wed, Jul 31, 2013 at 6:20 PM, Braddock wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/31/2013 03:17 PM, Paul Fox wrote:
> Fedora and most Linux distros (not to mention Macs) support mDNS
> out of the box, yet for some reason it is turned off in OLPC OS.
> I believe all that is required is the addition of the nss-mdns
> package to
braddock wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dear OLPC Devel folks,
> Is it possible to enable mDNS name resolution in future builds of OLPC OS?
>
> Fedora and most Linux distros (not to mention Macs) support mDNS out
> of the box, yet for some reason it is turned
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear OLPC Devel folks,
Is it possible to enable mDNS name resolution in future builds of OLPC OS?
Fedora and most Linux distros (not to mention Macs) support mDNS out
of the box, yet for some reason it is turned off in OLPC OS. I
believe all that is
