react-native-zeroconf 0.15.2 → 0.16.0

package/android/src/main/jni/mdnsresponder/Makefile

@@ -1,41 +0,0 @@
-#
-# Top level makefile for Build & Integration.
-# 
-# This file is used to facilitate checking the mDNSResponder project
-# directly out of CVS and submitting to B&I at Apple.
-#
-# The various platform directories contain makefiles or projects
-# specific to that platform.
-#
-#    B&I builds must respect the following target:
-#         install:
-#         installsrc:
-#         installhdrs:
-#         clean:
-#
-
-include /Developer/Makefiles/pb_makefiles/platform.make
-
-MVERS = "mDNSResponder-320.10.80"
-
-DDNSWRITECONFIG = "$(DSTROOT)/Library/Application Support/Bonjour/ddnswriteconfig"
-
-installSome:
-	cd "$(SRCROOT)/mDNSMacOSX"; xcodebuild install     OBJROOT=$(OBJROOT) SYMROOT=$(SYMROOT) DSTROOT=$(DSTROOT) MVERS=$(MVERS) SDKROOT=$(SDKROOT) -target Build\ Some
-
-SystemLibraries:
-	cd "$(SRCROOT)/mDNSMacOSX"; xcodebuild install     OBJROOT=$(OBJROOT) SYMROOT=$(SYMROOT) DSTROOT=$(DSTROOT) MVERS=$(MVERS) SDKROOT=$(SDKROOT) -target SystemLibraries
-
-install:
-	cd "$(SRCROOT)/mDNSMacOSX"; xcodebuild install     OBJROOT=$(OBJROOT) SYMROOT=$(SYMROOT) DSTROOT=$(DSTROOT) MVERS=$(MVERS) SDKROOT=$(SDKROOT)
-	# Make sure ddnswriteconfig is owned by root:wheel, then make it setuid root executable
-	if test -e $(DDNSWRITECONFIG) ; then chown 0:80 $(DDNSWRITECONFIG) ; chmod 4555 $(DDNSWRITECONFIG) ; fi
-
-installsrc:
-	ditto . "$(SRCROOT)"
-
-installhdrs::
-	cd "$(SRCROOT)/mDNSMacOSX"; xcodebuild installhdrs OBJROOT=$(OBJROOT) SYMROOT=$(SYMROOT) DSTROOT=$(DSTROOT) MVERS=$(MVERS) SDKROOT=$(SDKROOT)  -target SystemLibraries
-
-clean::
-	echo clean

package/android/src/main/jni/mdnsresponder/PrivateDNS.txt

@@ -1,275 +0,0 @@
-Private DNS
-
-Summary
-
-Private DNS is an extension to standard Wide Area Bonjour that allows
-for secure, encrypted, and authorized communications. Private data sent
-from a client to a DNS server is encrypted using Transport Layer
-Security (TLS), ensuring that the data is hidden from prying eyes, and
-contains Transaction Signatures (TSIG), so the server can authorize the
-request. TSIGs are typically associated with Dynamic Updates; we are
-using them for standard and long-lived queries as well. Private DNS also
-protects Dynamic Updates from eavesdropping, by wrapping the update in a
-TLS communication channel if the server has been configured appropriately.
-
-Architectural Overview
-
-mDNSResponder has been modified to automatically issue a private query
-when necessary. After receiving an NXDOMAIN error, mDNSResponder checks
-in the system keychain to see if the user has a DNS query key (TSIG key)
-for the name in question, or for a parent of that name. If a suitable
-key is found, mDNSResponder looks up the zone data associated with the
-name of the question. After determining the correct name server,
-mDNSResponder looks up an additional SRV record "_dns-private._tcp". If
-it finds this record, mDNSResponder will re-issue the query privately.
-If either there is no _dns-private._tcp record, or there is no secret
-key, the call fails as it initially did, with an NXDOMAIN error.
-
-Once the secret key is found and the SRV record is looked up, mDNSResponder
-opens a TLS connection to the server on the port specified in the SRV
-record just looked up. After the connection succeeds, mDNSResponder
-can proceed to use that communication channel to make requests of
-the server. Every private packet must also have a TSIG record;
-the DNS server uses this TSIG record to allow access to its data.
-
-When setting up a long-lived query over TCP (with or without TLS)
-TCP's standard three-way handshake makes the full four-packet LLQ setup
-exchange described in <http://files.dns-sd.org/draft-sekar-dns-llq.txt>
-unnecessary. Instead, when connecting over TCP, the client simply sends
-a setup message and expects to receive ACK + Answers. The setup message
-sent is formatted as described in the LLQ document, however there is
-an additional TSIG' resource record added to the end of it. The TSIG
-resource records looks and acts exactly as it does in a secure update.
-So when the server receives an LLQ (or a standard query), it looks to
-see if the zone that is being referenced is public or private. If it's
-private, then it makes sure that the client is authorized to query that
-zone (by using the TSIG signature) and returns the appropriate data.
-When a zone is configured as private, the server will do this type of
-authorization checking for every query except those queries that are
-looking for SOA and NS records.
-
-Implementation Issues
-
-dnsextd
-
-dnsextd has been modified to behave much like a DNS firewall. The "real"
-DNS server is configured to listen on non-standard ports on the loopback
-interface. dnsextd then listens on the standard DNS ports (TCP/UDP port
-53) and intercepts all DNS traffic. It is responsible for determining
-what zone a DNS request is associated with, determining whether the
-client is allowed access to that zone, and returning the appropriate
-information back to the caller. If the packet is allowed access, dnsextd
-forwards the request to the "real" nameserver, and returns the result to
-the caller.
-
-It was tempting to use BIND9's facility for configuring TSIG enabled
-queries while doing this work. However after proceeding down that path,
-enough subtle interaction problems were found that it was not practical
-to pursue this direction, so instead dnsextd does all TSIG processing
-for queries itself. It does continue to use BIND9 for processing TSIG
-enabled dynamic updates, though one minor downside with this is that
-there are two configuration files (named.conf or dnsextd.conf) that have
-the same secret key information. That seems redundant and error-prone,
-and moving all TSIG processing for both queries and updates into dnsextd
-would fix this.
-
-All private LLQ operations are TSIG-enabled and sent over a secure
-encrypted TLS channel. To accommodate service providers who don't want
-to have to keep open a large number of TLS connections to a large number
-of client machines, the server has the option of dropping the TLS
-connection after initial LLQ setup and sending subsequent events and
-refreshes using unencrypted UDP packets. This results in less load on
-the server, at the cost of slightly lower security (LLQs can only be set
-up by an authorized client, but once set up, subsequent change event
-packets sent over unencrypted UDP could be observed by an eavesdropper).
-A potential solution to this deficiency might be in using DTLS, which is
-a protocol based on TLS that is capable of securing datagram traffic.
-More investigation needs to be done to see if DTLS is suitable for
-private DNS.
-
-It was necessary to relax one of the checks that dnsextd performs during
-processing of an LLQ refresh. Prior to these changes, dnsextd would
-verify that the refresh request came from the same entity that setup the
-LLQ by comparing both the IP Address and port number of the request
-packet with the IP Address and port number of the setup packet. Because
-of the preceding issue, a refresh request might be sent over two
-different sockets. While their IP addresses would be the same, their
-port numbers could potentially differ. This check has been modified to
-only check that the IP addresses match.
-
-When setting up a semi-private LLQ (where the request and initial answer
-set is sent over TLS/TCP, but subsequent change events are sent over
-unencrypted UDP), dnsextd uses the port number of the client's TCP
-socket to determine the UDP event port number. While this eliminates the
-need to pass the UDP event port number in the LLQ setup request
-(obviating a potential data mismatch error), I think it does more harm
-than good, for three reasons:
-
-1) We are relying that all the routers out there implement the Port
-   Mapping Protocol spec correctly.
-
-2) Upon setup every LLQ must NAT map two ports. Upon tear down every LLQ
-   must tear down two NAT mappings.
-
-3) Every LLQ opens up two sockets (TCP and UDP), rather than just the
-   one TCP socket.
-
-All of this just to avoid sending two bytes in the LLQ setup packet
-doesn't seem logical. The approach also necessitates creating an
-additional UDP socket for every private LLQ, port mapping both the TCP
-socket as well as the UDP socket, and moderately increasing the
-complexity and efficiency of the code. Because of this we plan to allow
-the LLQ setup packet to specify a different UDP port for change event
-packets. This will allow mDNSResponder to receive all UDP change event
-packets on a single UDP port, instead of a different one for each LLQ.
-
-Currently, dnsextd is buggy on multi-homed hosts. If it receives a
-packet on interface 2, it will reply on interface 1 causing an error in
-the client program.
-
-dnsextd doesn't fully process all of its option parameters.
-Specifically, it doesn't process the keywords: "listen-on",
-"nameserver", "private", and "llq". It defaults to expecting the "real"
-nameserver to be listening on 127.0.0.1:5030.
-
-
-mDNSResponder
-
-Currently, mDNSResponder attempts to issue private queries for all
-queries that initially result in an NXDOMAIN error. This behavior might
-be modified in future versions, however it seems patently incorrect to
-do this for reverse name lookups. The code that attempts to get the zone
-data associated with the name will never find the zone for a reverse
-name lookup, and so will issue a number of wasteful DNS queries.
-
-mDNSResponder doesn't handle SERV_FULL or STATIC return codes after
-setting up an LLQ over TCP. This isn't a terrible problem right now,
-because dnsextd doesn't ever return them, but this should be fixed so
-that mDNSResponder will work when talking to other servers that do
-return these error codes.
-
-
-Configuration:
-
-Sample named.conf:
-
-//
-// Include keys file
-//
-include "/etc/rndc.key";
-// Declares control channels to be used by the rndc utility.
-//
-// It is recommended that 127.0.0.1 be the only address used.
-// This also allows non-privileged users on the local host to manage
-// your name server.
-
-//
-// Default controls
-//
-controls
-	{
-	inet 127.0.0.1 port 54 allow { any; } keys { "rndc-key"; };
-	};
-
-options
-	{
-	directory "/var/named";
-	/*
-	 * If there is a firewall between you and nameservers you want
-	 * to talk to, you might need to uncomment the query-source
-	 * directive below. Previous versions of BIND always asked
-	 * questions using port 53, but BIND 8.1 uses an unprivileged
-	 * port by default.
-	 */
-	
-	forwarders
-			{
-			65.23.128.2;
-			65.23.128.3;
-			};
-	
-	listen-on port 5030 { 127.0.0.1; };
-	recursion true;
-	};
-
-// 
-// a caching only nameserver config
-// 
-zone "." IN
-	{
-	type hint;
-	file "named.ca";
-	};
-
-zone "localhost" IN
-	{
-	type master;
-	file "localhost.zone";
-	allow-update { none; };
-	};
-
-zone "0.0.127.in-addr.arpa" IN
-	{
-	type master;
-	file "named.local";
-	allow-update { none; };
-	};
-
-zone "hungrywolf.org." in
-	{
-	type master;
-	file "db.hungrywolf.org";
-	allow-update { key hungrywolf.org.; };
-	};
-
-zone "157.23.65.in-addr.arpa" IN
-	{
-	file "db.65.23.157";
-	type master;
-	};
-
-zone "100.255.17.in-addr.arpa" IN
-	{
-	file "db.17.255.100";
-	type master;
-	};
-
-zone "66.6.24.in-addr.arpa" IN
-	{
-	file "db.24.6.66";
-	type master;
-	};
-
-key hungrywolf.org.
-	{
-	algorithm hmac-md5;
-	secret "c8LWr16K6ju6KMO5zT6Tyg==";
-	};
-
-logging
-	{
-	category default { _default_log; };
-
-	channel _default_log
-		{
-		file "/Library/Logs/named.log";
-		severity info;
-		print-time yes;
-		};
-	};
-
-
-Sample dnsextd.conf:
-
-options { };
-
-key "hungrywolf.org."
-	{
-	secret "c8LWr16K6ju6KMO5zT6Tyg==";
-	};
-
-zone "hungrywolf.org."
-	{
-	type private;
-	allow-query { key hungrywolf.org.; };
-	};

package/android/src/main/jni/mdnsresponder/android/caseMapping/Iphlpapi.h

@@ -1 +0,0 @@
-#include <iphlpapi.h>

package/android/src/main/jni/mdnsresponder/android/caseMapping/README

@@ -1,3 +0,0 @@
-Windows filesystems, and consequently Windows C include files, are
-case-insensitive. This folder provides alternately-cased versions of header
-files for cases where that becomes a problem.

package/android/src/main/jni/mdnsresponder/android/caseMapping/Resource.h

@@ -1 +0,0 @@
-#include <resource.h>

package/android/src/main/jni/mdnsresponder/android/caseMapping/Ws2tcpip.h

@@ -1 +0,0 @@
-#include <ws2tcpip.h>

package/android/src/main/jni/mdnsresponder/android/caseMapping/ipExport.h

@@ -1 +0,0 @@
-#include <ipexport.h>

package/android/src/main/jni/mdnsresponder/android/windows_firewall_dummy.c

@@ -1,10 +0,0 @@
-int mDNSIsFileAndPrintSharingEnabled(int *ignored) {
-  (void)ignored;
-  return 0;
-}
-
-int mDNSAddToFirewall(const char* ignored, const char* also_ignored) {
-  (void)ignored;
-  (void)also_ignored;
-  return 0;
-}

package/android/src/main/jni/mdnsresponder/mDNSCore/Implementer Notes.txt

@@ -1,66 +0,0 @@
-February 2002:
-
-The mDNSResponder code has a slight architectural change to improve
-efficiency.
-
-The mDNSResponder code previously called ScheduleNextTask() after every
-operation, to calculate the time at which it needed to be called back to
-perform its next timed operation. When the workload is light, and
-protocol operations are rare and far apart, this makes sense.
-
-However, on networks where there is a lot of mDNS traffic (or the CPU is
-slow), this leads to the following anomolous behaviour: mDNSResponder
-spends a lot of CPU time working out what to do next, when what it needs
-to do next should be obvious: Finish processing the big backlog of
-packets that have been received.
-
-To remedy this, mDNSResponder now only executes ScheduleNextTask() when
-there is no other obvious work waiting to be done. However, the
-mDNSResponder code does not have direct access to this knowledge. Only
-the platform layer below knows whether there are packets waiting to be
-processed. Only the client layer above knows whether it is in the
-process of performing a long sequence of back-to-back mDNS API calls.
-
-This means that the new architecture places an additional responsibility
-on the client layer and/or platform support layer. As long as they have
-immediate work to do, they should call the appropriate mDNSCore routines
-to accomplish that work. With each call, mDNSCore will do only what it
-immediately has to do to satisfy the call. Any optional work will be
-deferred. As soon as there is no more immediate work to do, the calling
-layer MUST call mDNS_Execute(). Failure to call mDNS_Execute() will lead
-to unreliable or incorrect operation.
-
-The value returned from mDNS_Execute() is the next time (in absolute
-platform time units) at which mDNS_Execute() MUST be called again to
-perform its next necessary operation (e.g. transmitting its next
-scheduled query packet, etc.) Note that the time returned is an absolute
-time, not the time *interval* between now and the next required call.
-For OS APIs that work in terms of intervals instead of absolute times,
-mDNSPlatformTimeNow() must be subtracted from the absolute time to get
-the interval between now and the next event.
-
-In a single-threaded application using a blocking select() call as its
-main synchronization point, this means that you should call
-mDNS_Execute() before calling select(), and the timeout value you pass
-to select() MUST NOT be larger than that indicated by the result
-returned from mDNS_Execute(). After the blocking select() call returns,
-you should do whatever work you have to do, and then, if mDNS packets
-were received, or mDNS API calls were made, be sure to call
-mDNS_Execute() again, and if necessary adjust your timeout value
-accordingly, before going back into the select() call.
-
-In an asynchronous or interrupt-driven application, there are three
-places that should call mDNS_Execute():
-
-1. After delivering received packets, the platform support layer should
-call mDNS_Execute(), and use the value returned to set the platform
-callback timer to fire at the indicated time.
-
-2. After making any mDNS API call or series of calls, the client layer
-should call mDNS_Execute(), and use the value returned to set the
-platform callback timer to fire at the indicated time.
-
-3. When the platform callback timer fires, it should call mDNS_Execute()
-(to allow mDNSCore to perform its necessary work) and then the timer
-routine use the result returned to reset itself to fire at the right
-time for the next scheduled event.

package/android/src/main/jni/mdnsresponder/mDNSPosix/Client.c

@@ -1,223 +0,0 @@
-/* -*- Mode: C; tab-width: 4 -*-
- *
- * Copyright (c) 2002-2004 Apple Computer, Inc. All rights reserved.
- *
- * Licensed under the Apache License, Version 2.0 (the "License");
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- * 
- *     http://www.apache.org/licenses/LICENSE-2.0
- * 
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-
-#include <assert.h>
-#include <signal.h>
-#include <stdio.h>
-#include <string.h>
-#include <unistd.h>
-#include <stdlib.h>
-
-#include "mDNSEmbeddedAPI.h"// Defines the interface to the mDNS core code
-#include "mDNSPosix.h"    // Defines the specific types needed to run mDNS on this platform
-#include "ExampleClientApp.h"
-
-// Globals
-static mDNS mDNSStorage;       // mDNS core uses this to store its globals
-static mDNS_PlatformSupport PlatformStorage;  // Stores this platform's globals
-#define RR_CACHE_SIZE 500
-static CacheEntity gRRCache[RR_CACHE_SIZE];
-
-mDNSexport const char ProgramName[] = "mDNSClientPosix";
-
-static const char *gProgramName = ProgramName;
-
-static void BrowseCallback(mDNS *const m, DNSQuestion *question, const ResourceRecord *const answer, QC_result AddRecord)
-    // A callback from the core mDNS code that indicates that we've received a 
-    // response to our query.  Note that this code runs on the main thread 
-    // (in fact, there is only one thread!), so we can safely printf the results.
-{
-    domainlabel name;
-    domainname  type;
-    domainname  domain;
-	char nameC  [MAX_DOMAIN_LABEL+1];			// Unescaped name: up to 63 bytes plus C-string terminating NULL.
-	char typeC  [MAX_ESCAPED_DOMAIN_NAME];
-	char domainC[MAX_ESCAPED_DOMAIN_NAME];
-    const char *state;
-
-	(void)m;		// Unused
-	(void)question;	// Unused
-
-    assert(answer->rrtype == kDNSType_PTR);
-
-    DeconstructServiceName(&answer->rdata->u.name, &name, &type, &domain);
-
-    ConvertDomainLabelToCString_unescaped(&name, nameC);
-    ConvertDomainNameToCString(&type, typeC);
-    ConvertDomainNameToCString(&domain, domainC);
-
-    // If the TTL has hit 0, the service is no longer available.
-    if (!AddRecord) {
-        state = "Lost ";
-    } else {
-        state = "Found";
-    }
-    fprintf(stderr, "*** %s name = '%s', type = '%s', domain = '%s'\n", state, nameC, typeC, domainC);
-}
-
-static mDNSBool CheckThatServiceTypeIsUsable(const char *serviceType, mDNSBool printExplanation)
-    // Checks that serviceType is a reasonable service type 
-    // label and, if it isn't and printExplanation is true, prints 
-    // an explanation of why not.
-{
-    mDNSBool result;
-    
-    result = mDNStrue;
-    if (result && strlen(serviceType) > 63) {
-        if (printExplanation) {
-            fprintf(stderr, 
-                    "%s: Service type specified by -t is too long (must be 63 characters or less)\n", 
-                    gProgramName);
-        }
-        result = mDNSfalse;
-    }
-    if (result && serviceType[0] == 0) {
-        if (printExplanation) {
-            fprintf(stderr, 
-                    "%s: Service type specified by -t can't be empty\n", 
-                    gProgramName);
-        }
-        result = mDNSfalse;
-    }
-    return result;
-}
-
-static const char kDefaultServiceType[] = "_afpovertcp._tcp";
-static const char kDefaultDomain[]      = "local.";
-
-static void PrintUsage()
-{
-    fprintf(stderr, 
-            "Usage: %s [-v level] [-t type] [-d domain]\n",
-            gProgramName);
-    fprintf(stderr, "          -v verbose mode, level is a number from 0 to 2\n");
-    fprintf(stderr, "             0 = no debugging info (default)\n");
-    fprintf(stderr, "             1 = standard debugging info\n");
-    fprintf(stderr, "             2 = intense debugging info\n");
-    fprintf(stderr, "          -t uses 'type' as the service type (default is '%s')\n", kDefaultServiceType);
-    fprintf(stderr, "          -d uses 'domain' as the domain to browse (default is '%s')\n", kDefaultDomain);
-}
-
-static const char *gServiceType      = kDefaultServiceType;
-static const char *gServiceDomain    = kDefaultDomain;
-
-static void ParseArguments(int argc, char **argv)
-    // Parses our command line arguments into the global variables 
-    // listed above.
-{
-    int ch;
-    
-    // Set gProgramName to the last path component of argv[0]
-    
-    gProgramName = strrchr(argv[0], '/');
-    if (gProgramName == NULL) {
-        gProgramName = argv[0];
-    } else {
-        gProgramName += 1;
-    }
-    
-    // Parse command line options using getopt.
-    
-    do {
-        ch = getopt(argc, argv, "v:t:d:");
-        if (ch != -1) {
-            switch (ch) {
-                case 'v':
-                    gMDNSPlatformPosixVerboseLevel = atoi(optarg);
-                    if (gMDNSPlatformPosixVerboseLevel < 0 || gMDNSPlatformPosixVerboseLevel > 2) {
-                        fprintf(stderr, 
-                                "%s: Verbose mode must be in the range 0..2\n", 
-                                gProgramName);
-                        exit(1);
-                    }
-                    break;
-                case 't':
-                    gServiceType = optarg;
-                    if ( ! CheckThatServiceTypeIsUsable(gServiceType, mDNStrue) ) {
-                        exit(1);
-                    }
-                    break;
-                case 'd':
-                    gServiceDomain = optarg;
-                    break;
-                case '?':
-                default:
-                    PrintUsage();
-                    exit(1);
-                    break;
-            }
-        }
-    } while (ch != -1);
-
-    // Check for any left over command line arguments.
-    
-    if (optind != argc) {
-        fprintf(stderr, "%s: Unexpected argument '%s'\n", gProgramName, argv[optind]);
-        exit(1);
-    }
-}
-
-int main(int argc, char **argv)
-    // The program's main entry point.  The program does a trivial 
-    // mDNS query, looking for all AFP servers in the local domain.
-{
-    int     result;
-    mStatus     status;
-    DNSQuestion question;
-    domainname  type;
-    domainname  domain;
-
-    // Parse our command line arguments.  This won't come back if there's an error.
-    ParseArguments(argc, argv);
-
-    // Initialise the mDNS core.
-	status = mDNS_Init(&mDNSStorage, &PlatformStorage,
-    	gRRCache, RR_CACHE_SIZE,
-    	mDNS_Init_DontAdvertiseLocalAddresses,
-    	mDNS_Init_NoInitCallback, mDNS_Init_NoInitCallbackContext);
-    if (status == mStatus_NoError) {
-    
-        // Construct and start the query.
-        
-        MakeDomainNameFromDNSNameString(&type, gServiceType);
-        MakeDomainNameFromDNSNameString(&domain, gServiceDomain);
-
-        status = mDNS_StartBrowse(&mDNSStorage, &question, &type, &domain, mDNSInterface_Any, mDNSfalse, BrowseCallback, NULL);
-    
-        // Run the platform main event loop until the user types ^C. 
-        // The BrowseCallback routine is responsible for printing 
-        // any results that we find.
-        
-        if (status == mStatus_NoError) {
-            fprintf(stderr, "Hit ^C when you're bored waiting for responses.\n");
-        	ExampleClientEventLoop(&mDNSStorage);
-            mDNS_StopQuery(&mDNSStorage, &question);
-			mDNS_Close(&mDNSStorage);
-        }
-    }
-    
-    if (status == mStatus_NoError) {
-        result = 0;
-    } else {
-        result = 2;
-    }
-    if ( (result != 0) || (gMDNSPlatformPosixVerboseLevel > 0) ) {
-        fprintf(stderr, "%s: Finished with status %d, result %d\n", gProgramName, (int)status, result);
-    }
-
-    return 0;
-}