Skip to content
Snippets Groups Projects
  1. Jul 19, 2020
  2. Jul 07, 2020
  3. Jun 04, 2020
    • Chrissi^ (Chris Fiege)'s avatar
      openwrt: Store Kernel Debug-Info (#1971) · 1956696d
      Chrissi^ (Chris Fiege) authored
      
      This change stores a Kernel with Debug-Symbols for the current
      architecture in a new output directory '<outputdir>/debug'.
      This allows a developer or operator of a network to store the kernel
      along with the actual images. In case of a kernel oops the debug
      information can be used with the script
      'scripts/decode_stacktrace.sh' in the kernel source tree to get the
      names to the symbols of the stack trace.
      
      OpenWRT already provides the CONFIG_COLLECT_KERNEL_DEBUG -option that
      creates a kernel with debug-symbols in the OpenWRT output directory.
      This change enables this option and copies the generated kernel to the
      gluon output directory.
      
      Signed-off-by: default avatarChrissi^ <chris@tinyhost.de>
      1956696d
  4. Jun 03, 2020
  5. May 31, 2020
    • Sven Roederer's avatar
      docs/build: add a short summary for some scripts · 5e35fa1a
      Sven Roederer authored
      This summaries giving an overview of a scripts function and a short summary
      how it's doing this. Only the scripts are covered, that are used by the
      Freifunk-Berlin firmwarebuiler too.
      
      [Matthias Schiffer: slightly reworded some descriptions]
      5e35fa1a
  6. May 30, 2020
  7. May 29, 2020
  8. May 13, 2020
  9. May 12, 2020
  10. May 10, 2020
  11. May 09, 2020
  12. May 02, 2020
  13. Apr 29, 2020
  14. Apr 27, 2020
  15. Apr 26, 2020
  16. Apr 25, 2020
  17. Apr 24, 2020
  18. Apr 11, 2020
  19. Apr 09, 2020
  20. Apr 05, 2020
  21. Mar 31, 2020
  22. Mar 25, 2020
  23. Mar 23, 2020
    • Martin Weinelt's avatar
      Add gluon-mesh-wireless-sae package · 461d9040
      Martin Weinelt authored
      This package adds support for SAE on 802.11s mesh connections.
      
      Enabling this package will require all 802.11s mesh connections
      to be encrypted using the SAE key agreement scheme. The security
      of SAE relies upon the authentication through a shared secret.
      
      In the context of public mesh networks a shared secret is an
      obvious oxymoron. Still this functionality provides an improvement
      over unencrypted mesh connections in that it protects against a
      passive attacker who did not observe the key agreement. In addition
      Management Frame Protection (802.11w) gets automatically enabled on
      mesh interfaces to prevent protocol-level deauthentication attacks.
      
      If `wifi.mesh.sae` is enabled a shared secret will automatically be
      derived from the `prefix6` variable. This is as secure as it gets
      for a public mesh network.
      
      For *private* mesh networks `wifi.mesh.sae_passphrase` should be
      set to your shared secret.
      
      Fixes #1636
      461d9040
  24. Mar 19, 2020
  25. Mar 14, 2020
  26. Mar 09, 2020
Loading