Skip to content
Snippets Groups Projects
  1. May 21, 2017
    • Kevin Darbyshire-Bryant's avatar
      dropbear: bump to 2017.75 · 6e10fc74
      Kevin Darbyshire-Bryant authored
      - Security: Fix double-free in server TCP listener cleanup A double-free
      in the server could be triggered by an authenticated user if dropbear is
      running with -a (Allow connections to forwarded ports from any host)
      This could potentially allow arbitrary code execution as root by an
      authenticated user.  Affects versions 2013.56 to 2016.74. Thanks to Mark
      Shepard for reporting the crash.
      CVE-2017-9078 https://secure.ucc.asn.au/hg/dropbear/rev/c8114a48837c
      
      - Security: Fix information disclosure with ~/.ssh/authorized_keys
      symlink.  Dropbear parsed authorized_keys as root, even if it were a
      symlink.  The fix is to switch to user permissions when opening
      authorized_keys
      
      A user could symlink their ~/.ssh/authorized_keys to a root-owned file
      they couldn't normally read. If they managed to get that file to contain
      valid authorized_keys with command= options it might be possible to read
      other contents of that file.
      This information disclosure is to an already authenticated user.
      Thanks to Jann Horn of Google Project Zero for reporting this.
      CVE-2017-9079 https://secure.ucc.asn.au/hg/dropbear/rev/0d889b068123
      
      
      
      Refresh patches, rework 100-pubkey_path.patch to work with new
      authorized_keys validation.
      
      Signed-off-by: default avatarKevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
      6e10fc74
  2. May 18, 2017
  3. May 16, 2017
  4. May 15, 2017
    • Hans Dedecker's avatar
      odhcpd: update to git HEAD version · 6d7cb533
      Hans Dedecker authored
      
      93abe6f config: fix invalid hoplimit in RA message
      2ae08d1 config: fix invalid retranstime in RA message
      0005cb4 config: fix invalid reachabletime in RA message
      5683dd2 config: limit ra_mtu to 65535
      f8d40a5 router: fix interface mtu read error
      f8f4b87 config: limit ra_retranstime to 60000
      a2d8bf6 dhcpv4: display two hex digits per octet in syslog
      a9e9bc4 config: make RA retransTime configurable via uci
      2cb6b48 config: make RA reachableTime configurable via uci
      e4504db config: make RA curHopLimit configurable via uci
      9dd5316 config: make RA mtu configurable via UCI
      29cb2ff config: fix dhcpv4 server being started
      0ef74ec ndp.c: add switch/case fallthrough comments
      
      Signed-off-by: default avatarHans Dedecker <dedeckeh@gmail.com>
      6d7cb533
  5. May 13, 2017
  6. May 12, 2017
  7. May 10, 2017
  8. May 09, 2017
  9. May 04, 2017
  10. May 03, 2017
    • Nick Lowe's avatar
      hostapd: add legacy_rates option to disable 802.11b data rates. · ed62d91f
      Nick Lowe authored
      Setting legacy_rates to 0 disables 802.11b data rates.
      Setting legacy_rates to 1 enables 802.11b data rates. (Default)
      
      The basic_rate option and supported_rates option are filtered based on this.
      
      The rationale for the change, stronger now than in 2014, can be found in:
      
      https://mentor.ieee.org/802.11/dcn/14/11-14-0099-00-000m-renewing-2-4ghz-band.pptx
      
      
      
      The balance of equities between compatibility with b clients and the
      detriment to the 2.4 GHz ecosystem as a whole strongly favors disabling b
      rates by default.
      
      Signed-off-by: default avatarNick Lowe <nick.lowe@gmail.com>
      Signed-off-by: Felix Fietkau <nbd@nbd.name> [cleanup, defaults change]
      ed62d91f
    • Abhilash Tuse's avatar
      hostapd: fix reload frequency change patch · 41feba8c
      Abhilash Tuse authored
      
      When sta is configured, hostapd receives 'stop' and 'update' command from
      wpa_supplicant. In the update command, hostapd gets sta parameters with
      which it configures ap.
      
      Problem is, with the default wireless configuration:
      mode:11g freq:2.4GHz channel:1
      If sta is connected to 5GHz network, then ap does not work. Ideally with
      340-reload_freq_change.patch hostapd should reload the frequency changes
      and start ap in 5GHz, but ap becomes invisible in the network.
      
      This issue can be reproduced with following /etc/config/wireless:
      config wifi-device  radio0
              option type     mac80211
              option channel  1
              option hwmode   11g
              option path     'virtual/uccp420/uccwlan'
              option htmode   'none'
      
      config wifi-iface 'ap'
              option device 'radio0'
              option encryption 'none'
              option mode 'ap'
              option network 'ap'
              option ssid 'MyTestNet'
              option encryption none
      
      config wifi-iface 'sta'
             option device radio0
             option network sta
             option mode sta
             option ssid TestNet-5G
             option encryption psk2
             option key 12345
      
      This change updates current_mode structure based on configured hw_mode
      received from wpa_supplicant. Also prepare rates table after frequency
      selection.
      
      Signed-off-by: default avatarAbhilash Tuse <Abhilash.Tuse@imgtec.com>
      Signed-off-by: Felix Fietkau <nbd@nbd.name> [cleanup, patch refresh]
      41feba8c
  11. May 02, 2017
  12. Apr 28, 2017
  13. Apr 27, 2017
  14. Apr 26, 2017
  15. Apr 24, 2017
  16. Apr 17, 2017
  17. Apr 12, 2017
  18. Apr 08, 2017
  19. Apr 01, 2017
  20. Mar 29, 2017
  21. Mar 22, 2017
    • Martin Schiller's avatar
      openvpn: add extra respawn parameters · 06c49dbc
      Martin Schiller authored
      
      This change protects the openvpn instances to be marked as "in a crash
      loop" and thereby the connection retries will run infinitely.
      
      When the remote site of an openvpn connection goes down for some time
      (network failure etc.) the openvpn instance in an openwrt/lede device
      should not stop retrying to establish the connection.
      
      With the current limit of 5 retries, there is a user interaction
      required, which isn't really what you want when the device should
      simply do everything to keep the vpn connection up.
      
      Signed-off-by: default avatarMartin Schiller <ms@dev.tdt.de>
      06c49dbc
  22. Mar 21, 2017
    • Rafał Miłecki's avatar
      umdns: update to the version 2017-03-21 · 106ae11e
      Rafał Miłecki authored
      
      This includes following changes:
      480d7bc Fix sending unicast questions on cache expire
      a0403cd Keep source sockaddr for every cached DNS record
      1478293 Fix code freeing cached non-A(AAA) records too early
      9f1cc22 Fix replying to "QU" questions received on unicast interface
      943bedb Fix reading port of incoming packets
      c725494 Use MCAST_PORT define for port 5353
      ce7e9e9 Use one define for DNS-Based Service Discovery service name
      e1bacef Drop entries cached for interface we're going to delete
      496aeba Fix comment typo in cache_gc_timer
      f89986b Fix refreshing cached A(AAA) records that expire
      
      Previous updates made umdns work as expected on startup but there were
      still many bugs. They were mostly related to runtime - cache management
      and requests + responses. E.g. umdns was never able to send question on
      DNS record expire. It was also ignoring all incoming unicast questions.
      
      Since these issues are quite serious it makes sense to backport this
      update to the stable branch.
      
      Signed-off-by: default avatarRafał Miłecki <rafal@milecki.pl>
      106ae11e
  23. Mar 18, 2017
  24. Mar 14, 2017
  25. Mar 10, 2017
  26. Mar 09, 2017
    • Kevin Darbyshire-Bryant's avatar
      dnsmasq: do not forward rfc6761 excluded domains · 3a06dd60
      Kevin Darbyshire-Bryant authored
      
      RFC 6761 defines a number of top level domains should not be forwarded
      to the Internet's domain servers since they are not responsible for
      those domains.
      
      This change adds a list of domains that will be blocked when 'boguspriv'
      is used and augments that which is already blocked by dnsmasq's notion
      of 'local service' using '--bogus-priv' i.e. RFC 1918 private addresses
      and IPv6 prefixes as defined in RFC 6303.
      
      To make this configurable rather than hard coded in dnsmasq's init
      script, a new file /usr/share/dnsmasq/rfc6761.conf is conditionally
      included.
      
      The default file matches the RFC 6761 recommendation along with a few
      other top level domains that should not be forwarded to the Internet.
      
      Compile & run tested Archer C7 v2
      
      Signed-off-by: default avatarKevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
      3a06dd60
  27. Mar 07, 2017
  28. Mar 06, 2017
  29. Mar 05, 2017
  30. Mar 02, 2017
  31. Feb 25, 2017
Loading