1. 06 Apr, 2010 1 commit
  2. 24 Mar, 2010 2 commits
  3. 23 Mar, 2010 1 commit
  4. 22 Mar, 2010 3 commits
  5. 18 Mar, 2010 4 commits
  6. 17 Mar, 2010 4 commits
  7. 16 Mar, 2010 4 commits
  8. 11 Mar, 2010 2 commits
  9. 10 Mar, 2010 1 commit
  10. 09 Mar, 2010 3 commits
  11. 08 Mar, 2010 2 commits
    • Jean-Baptiste Queru's avatar
      Add an empty CleanSpec.mk · 55cd975f
      Jean-Baptiste Queru authored
      Change-Id: Id233ea6f854253776f57e64196e262c5a057e654
      55cd975f
    • David 'Digit' Turner's avatar
      Fix spurious DNS lookups in the C library. · d378c68d
      David 'Digit' Turner authored
      The problem was that the 'defdname' field of res_state structure
      was not properly initialized in __res_vinit(). This field is used
      to store the default domain name, which is normally build from
      calling gethostname() (see line 549 of res_init.c).
      
      Unfortunately, in the typical Android case, gethostname() returns
      an error (the hostname is configured) and a random stack string is
      used later to build the DNS search list (see lines 556+ in res_init.c)
      
      For the sake of illustration, let's say the search list is set to
      a random value like 'xWLK'.
      
      The end result is that when trying to result an unknown domain name
      (e.g. 'www.ptn'), the query fails then the resolver tries to make a
      new query with the DNS search list path(s) appended (e.g. 'www.ptn.xWLK').
      
      The patch simply initializes 'defdname' to an empty string to avoid
      this when the net.dns.search system property is not set.
      
      Also contains whitespace/formatting fixes
      d378c68d
  12. 05 Mar, 2010 1 commit
  13. 04 Mar, 2010 1 commit
  14. 03 Mar, 2010 5 commits
  15. 02 Mar, 2010 3 commits
  16. 01 Mar, 2010 1 commit
  17. 24 Feb, 2010 2 commits
    • David Turner's avatar
      Merge "Implement support for RFC 3484 (address selection/sorting) in bionic. ... · 1f6f4939
      David Turner authored
      Merge "Implement support for RFC 3484 (address selection/sorting) in bionic.  (The Java changes required not to mess up the ordering from bionic will arrive in a later commit.) In particular, this will give us more correct behavior when on a 6to4 network, in that IPv4 will usually be preferred over 6to4."
      1f6f4939
    • Steinar H. Gunderson's avatar
      Implement support for RFC 3484 (address selection/sorting) in bionic. (The · 9ab75d4c
      Steinar H. Gunderson authored
      Java changes required not to mess up the ordering from bionic will arrive in a
      later commit.) In particular, this will give us more correct behavior when on a
      6to4 network, in that IPv4 will usually be preferred over 6to4.
      
      Most of RFC 3484 is implemented -- what's not is rule 3 (avoid deprecated
      addresses), 4 (prefer home addresses) and 7 (prefer native transport) as they
      require low-level access to the kernel routing table via netlink. (glibc also
      started out this way, and these rules are primarily useful in pretty obscure
      circumstances, so we should be fine for the time being.)
      
      Also, rule 9 (use longest matching prefix) has been modified so it does not try
      to sort IPv4 addresses; given current IPv4 addressing practice these rules are
      pretty much meaningless. Finally, I've added support for Teredo as a separate
      label, with slightly lower preference than 6to4. (Vista puts the preference
      below IPv4 by default. glibc puts the preference together with non-tunneled
      IPv6.)
      
      Note that this patch removes support for the "sortlist" directive in
      resolv.conf; I've never seen it in actual use, it's irrelevant for Android
      (since we don't use resolv.conf anyway), and it's not clear how it would be
      implemented alongside RFC 3484.
      9ab75d4c