This updates the CyaSSL names to wolfSSL, and removes obsolete code to
support old versions of the library < v3.10.4.
Some #include statements were moved around, so that wolfssl/options.h is
loaded before any other wolfssl/openssl header.
Signed-off-by: Eneas U de Queiroz
diff --git a/CMakeList
WolfSSL added a wolfSSL_X509_check_host function to perform CN
validation in v3.10.4, depending on the build-time configure options:
--enable-nginx enables it for all supported versions;
--enable-opensslextra, since v3.14.2.
If the function is unavailable, then SSL_get_verify_result will be
called
Starting in v3.13.2, wolfSSL stores the BIO send and recv callbacks
in the SSL struct. When the SSL session is created, it inherits the
calls from the SSL_CTX, but they do not get updated when the SSL_CTX
callbacks are changed.
Currently, ustream-ssl sets the callbacks after the SSL session is
cr
ustream-ssl does not currently work with client apps. They fail to
connect immediately. uclient-fetch, for example, just show a
'Connection failed' message. This was due to a change in the SSL
session struct.
While making small changes to my first attempt, I realized my testing
was not complete
No, they've always just been sitting in a local source tree. Do you have
any specific packages in mind? I just created watch files for the
measurement-kit, python-cachetools, python-cryptodomex, python-pyrsistent,
tessdata and tesseract packages.
On Wed, Sep 18, 2019 at 7:31 AM Jan Pavlinec wrote
Remove 300-bn_mul.h-Use-optimized-MULADDC-code-only-on-ARM-6.patch,
the issue has been fixed upstream.
Signed-off-by: Magnus Kroken
---
package/libs/mbedtls/Makefile | 4 +-
package/libs/mbedtls/patches/200-config.patch | 46 +--
...optimized-MULADDC-code-only-on
Remove 300-bn_mul.h-Use-optimized-MULADDC-code-only-on-ARM-6.patch,
the issue has been fixed upstream.
Signed-off-by: Magnus Kroken
---
Runtime-tested on: ath79
package/libs/mbedtls/Makefile | 4 +-
package/libs/mbedtls/patches/200-config.patch | 46 +--
...opti
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of David Bauer
> Sent: Mittwoch, 18. September 2019 17:04
> To: Adrian Schmutzler
> Cc: openwrt-devel@lists.openwrt.org; 'Chuanhong Guo' ;
> 'Sebastian Kemper' ;
> 'Christian Lamp
Some ar9344-based devices are using ath9k_patch_fw_mac_crc, which
is meant to generate a checksum, for fixing their ath9k MAC
addresses.
However, those do not have a checksum field, and the calculated
checksum offset would be negative.
This patch will use ath9k_patch_fw_mac function for those devi
Hello Adrian,
On 9/18/19 4:54 PM, Adrian Schmutzler wrote:
> From a practical perspective, it does not matter which function is used,
> because the checksum is not evaluated. So one could use either
> ath10kcal_patch_mac or ath10kcal_patch_mac_crc in all cases and would get the
> same result (i
Hi,
that's interesting.
> BTW there's another misuse in ath10k-caldata: All ath10k eeproms have
> checksum fields and should use ath10k_patch_mac_crc, ath10k_patch_mac
> exists only because ath10k firmware doesn't verify it.
So, let me repeat this to check whether I understood it:
From a techni
On Wed, Sep 18, 2019 at 10:06 PM Chuanhong Guo wrote:
> That's indeed a misuse. ar9300 eeproms (which are used on ar9331 and
> later socs and ar938x pcie cards) have their macs at 0x4 and don't
Oops. Typo here. mac is at 0x2
> have a checksum field at all.
__
Hi!
On Wed, Sep 18, 2019 at 8:18 PM Adrian Schmutzler
wrote:
>
> Hi,
>
> I've encountered the following issue, for which I would like a second opinion.
>
> In ath79's 10-ath9k-eeprom, in addition to patching the firmware MAC address,
> some devices also need a checksum adjustment:
> https://gith
There are two identical files in the OpenWrt repo:
package/utils/otrx/src/otrx.c
tools/firmware-utils/src/otrx.c
I'd like to get rid of the later one and add HostBuild to the
package/utils/otrx/Makefile.
For that to work I need something like:
TARGET_BUILD_DEPENDS:=otrx/host
as targets require "o
Hi,
I've encountered the following issue, for which I would like a second opinion.
In ath79's 10-ath9k-eeprom, in addition to patching the firmware MAC address,
some devices also need a checksum adjustment:
https://github.com/openwrt/openwrt/blob/master/target/linux/ath79/base-files/etc/hotplug.
If chksum_offset is converted by $(($...)) at the beginning, the
check [ -n "$chksum_offset" ] will always return true, as the
conversion yields "0" for an empty argument, and [ -n "0" ] is
true.
With this patch, the variable is not converted before the check,
but only when it's used in dd.
No co
Hi,
is there any source of watch files for uscan where I can push missing
package watch files?
J.P.
Dne 16. 09. 19 v 0:03 Stephen Walker napsal(a):
> Branch: refs/heads/master
> Home: https://github.com/sdwalker/sdwalker.github.io
> Commit: 4b1ac0e52c1d0f0bac5b464e6a01d2bda1b97102
>
17 matches
Mail list logo
