1. 28 4月, 2023 5 次提交
  2. 23 4月, 2023 1 次提交
  3. 18 4月, 2023 1 次提交
    • D
      ath79: create Aruba AP-105 APBoot compatible image · bf81a921
      David Bauer 提交于
      Alter the Aruba AP-105 image generation process so OpenWrt can be loaded
      with the vendor Aruba APBoot.
      
      This works by prepending the OpenWrt LZMA loader to the uImage and
      jumping directly to the loader. Aruba does not offer bootm on these
      boards.
      
      This approach keeps compatibility to devices which had their U-Boot
      replaced. Both bootloaders can boot the same image.
      
      The same modification is most likely also possible for the Aruba AP-175.
      
      With this patch, new installations do not require replacing the
      bootloader and can be performed from the serial console without opening
      the case.
      
      Installation
      ------------
      
      1. Attach to the serial console of the AP-105.
         Interrupt autoboot and change the U-Boot env.
      
         $ setenv apb_rb_openwrt "setenv ipaddr 192.168.1.1;
           setenv serverip 192.168.1.66;
           netget 0x84000000 ap105.bin; go 0x84000040"
         $ setenv apb_fb_openwrt "cp.b 0xbf040000 0x84000000 0x10000;
           go 0x84000040"
         $ setenv bootcmd "run apb_fb_openwrt"
         $ saveenv
      
      2. Load the OpenWrt initramfs image on the device using TFTP.
         Place the initramfs image as "ap105.bin" in the TFTP server
         root directory, connect it to the AP and make the server reachable
         at 192.168.1.66/24.
      
         $ run apb_rb_openwrt
      
      3. Once OpenWrt booted, transfer the sysupgrade image to the device
         using scp and use sysupgrade to install the firmware.
      Signed-off-by: NDavid Bauer <mail@david-bauer.net>
      (cherry picked from commit e11d00d4)
      bf81a921
  4. 17 4月, 2023 1 次提交
    • E
      openssl: fix CVE-2023-464 and CVE-2023-465 · b6cbab1a
      Eneas U de Queiroz 提交于
      Apply two patches fixing low-severity vulnerabilities related to
      certificate policies validation:
      
      - Excessive Resource Usage Verifying X.509 Policy Constraints
        (CVE-2023-0464)
        Severity: Low
        A security vulnerability has been identified in all supported versions
        of OpenSSL related to the verification of X.509 certificate chains
        that include policy constraints.  Attackers may be able to exploit
        this vulnerability by creating a malicious certificate chain that
        triggers exponential use of computational resources, leading to a
        denial-of-service (DoS) attack on affected systems.
        Policy processing is disabled by default but can be enabled by passing
        the `-policy' argument to the command line utilities or by calling the
        `X509_VERIFY_PARAM_set1_policies()' function.
      
      - Invalid certificate policies in leaf certificates are silently ignored
        (CVE-2023-0465)
        Severity: Low
        Applications that use a non-default option when verifying certificates
        may be vulnerable to an attack from a malicious CA to circumvent
        certain checks.
        Invalid certificate policies in leaf certificates are silently ignored
        by OpenSSL and other certificate policy checks are skipped for that
        certificate.  A malicious CA could use this to deliberately assert
        invalid certificate policies in order to circumvent policy checking on
        the certificate altogether.
        Policy processing is disabled by default but can be enabled by passing
        the `-policy' argument to the command line utilities or by calling the
        `X509_VERIFY_PARAM_set1_policies()' function.
      
      Note: OpenSSL also released a fix for low-severity security advisory
      CVE-2023-466.  It is not included here because the fix only changes the
      documentation, which is not built nor included in any OpenWrt package.
      
      Due to the low-severity of these issues, there will be not be an
      immediate new release of OpenSSL.
      Signed-off-by: NEneas U de Queiroz <cotequeiroz@gmail.com>
      b6cbab1a
  5. 15 4月, 2023 1 次提交
  6. 14 4月, 2023 1 次提交
  7. 10 4月, 2023 2 次提交
  8. 09 4月, 2023 3 次提交
    • P
      imagebuilder: allow to specific ROOTFS_PARTSIZE · 38ccc476
      Paul Spooren 提交于
      Setting this options modifies the rootfs size of created images. When
      installing a large number of packages it may become necessary to
      increase the size to have enough storage.
      
      This option is only useful for supported devices, i.e. with an attached
      SD Card or installed on a hard drive.
      Signed-off-by: NPaul Spooren <mail@aparcar.org>
      (cherry picked from commit 7b7edd25)
      38ccc476
    • D
      ramips: define remapping-range for DAP-X1860 · deafcf91
      David Bauer 提交于
      Prevent the BBT translation layer from remapping the UBI used for
      storing rootfs.
      
      Explicitly define the number of blocks reserved for remapping.
      Signed-off-by: NDavid Bauer <mail@david-bauer.net>
      (cherry picked from commit 076da59f)
      deafcf91
    • S
      ramips: add support for D-Link DAP-X1860 A1 · 711e45e1
      Sebastian Schaper 提交于
      The DAP-X1860 is a wall-plug AX1800 repeater.
      
      Specifications:
      - MT7621, 256 MiB RAM, 128 MiB SPI NAND
      - MT7915 + MT7975 2x2 802.11ax (DBDC)
      - Ethernet: 1 port 10/100/1000
      - LED RSSI bargraph (2x green, 1x red/orange), status
        and RSSI LEDs are incorrectly populated red/orange
        (should be red/green according to documentation)
      
      Installation:
      - Keep reset button pressed during plug-in
      - Web Recovery Updater is at 192.168.0.50
      - Upload factory.bin, confirm flashing
        (seems to work best with Chromium-based browsers)
      
      Revert to OEM firmware:
      - tar -xvf DAP-X1860_RevA_Firmware_101b94.bin
      - openssl enc -d -md md5 -aes-256-cbc -in FWImage.st2 \
        -out FWImage.st1 -k MB0dBx62oXJXDvt12lETWQ==
      - tar -xvf FWImage.st1
      - flash kernel_DAP-X1860.bin via Recovery
      Signed-off-by: NSebastian Schaper <openwrt@sebastianschaper.net>
      (cherry picked from commit 3c31f6b5)
      711e45e1
  9. 08 4月, 2023 1 次提交
  10. 03 4月, 2023 20 次提交
  11. 02 4月, 2023 4 次提交