<feed xmlns='http://www.w3.org/2005/Atom'>
<title>staging/ynezz/package/libs, branch master</title>
<subtitle>Staging tree of Petr Stetiar</subtitle>
<id>https://git.openwrt.org/openwrt/staging/ynezz/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/openwrt/staging/ynezz/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/'/>
<updated>2021-05-23T13:11:38Z</updated>
<entry>
<title>wolfssl: add support for OpenVPN</title>
<updated>2021-05-23T13:11:38Z</updated>
<author>
<name>Ivan Pavlov</name>
</author>
<published>2021-05-05T15:23:19Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=b1baa01f1463c7b2cf5d10f7a35ed5dff47f2ac6'/>
<id>urn:sha1:b1baa01f1463c7b2cf5d10f7a35ed5dff47f2ac6</id>
<content type='text'>
Support for wolfSSL has been upstreamed to the master OpenVPN branch
in f6dca235ae560597a0763f0c98fcc9130b80ccf4, so we can use wolfSSL
directly in OpenVPN. So no more needed differnt SSL engine for OpenVPN
in systems based on wolfSSL library
Compiled &amp;&amp; tested on ramips/mt7620, ramips/mt7621

Signed-off-by: Ivan Pavlov &lt;AuthorReflex@gmail.com&gt;
</content>
</entry>
<entry>
<title>wolfssl: always export wc_ecc_set_rng</title>
<updated>2021-05-21T13:43:57Z</updated>
<author>
<name>David Bauer</name>
</author>
<published>2021-05-05T23:48:04Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=ef9b103107aebd1a54f4360af3d9cf28d0544f13'/>
<id>urn:sha1:ef9b103107aebd1a54f4360af3d9cf28d0544f13</id>
<content type='text'>
Since commit 6467de5a8840 ("Randomize z ordinates in scalar
mult when timing resistant") wolfssl requires a RNG for an EC
key when the hardened built option is selected.

wc_ecc_set_rng is only available when built hardened, so there
is no safe way to install the RNG to the key regardless whether
or not wolfssl is compiled hardened.

Always export wc_ecc_set_rng so tools such as hostapd can install
RNG regardless of the built settings for wolfssl.

Signed-off-by: David Bauer &lt;mail@david-bauer.net&gt;
</content>
</entry>
<entry>
<title>libubox: update to the latest version</title>
<updated>2021-05-18T10:52:52Z</updated>
<author>
<name>Felix Fietkau</name>
</author>
<published>2021-05-17T15:58:52Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=04d21604fd72f337c8a0410d13b3d878914b7e7e'/>
<id>urn:sha1:04d21604fd72f337c8a0410d13b3d878914b7e7e</id>
<content type='text'>
870acee325fe tests: cram: test_base64: fix failing tests
4d8995e91d56 tests: cram: test_base64: really fix failing tests
551d75b5662c libubox: tests: add more blobmsg/json test cases
a0dbcf8b8f96 tests: add blob-buffer overflow test
b36a3a90098d blob: fix exceeding maximum buffer length
b8abed749423 utils.h: add fallthrough macro
b14c4688612c json_script: fix unannotated fall-through warning

Signed-off-by: Felix Fietkau &lt;nbd@nbd.name&gt;
</content>
</entry>
<entry>
<title>uclient: update to Git version 2021-05-14</title>
<updated>2021-05-14T21:40:42Z</updated>
<author>
<name>Baptiste Jonglez</name>
</author>
<published>2021-05-14T21:40:40Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=1ec6fc4dcba16045a6bfcc493bdbe892de1265a9'/>
<id>urn:sha1:1ec6fc4dcba16045a6bfcc493bdbe892de1265a9</id>
<content type='text'>
6a6011d uclient-http: set eof mark when content-length is 0
19571e4 tests: fix help usage test for uclient built with sanitizer
c5fc04b tests: fix help usage test

Signed-off-by: Baptiste Jonglez &lt;git@bitsofnetworks.org&gt;
</content>
</entry>
<entry>
<title>build: introduce $(MKHASH)</title>
<updated>2021-05-13T13:13:15Z</updated>
<author>
<name>Leonardo Mörlein</name>
</author>
<published>2021-05-09T20:28:15Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=b993b68b6ca8444b5227a0c18df4600b37ac565c'/>
<id>urn:sha1:b993b68b6ca8444b5227a0c18df4600b37ac565c</id>
<content type='text'>
Before this commit, it was assumed that mkhash is in the PATH. While
this was fine for the normal build workflow, this led to some issues if

    make TOPDIR="$(pwd)" -C "$pkgdir" compile

was called manually. In most of the cases, I just saw warnings like this:

    make: Entering directory '/home/.../package/gluon-status-page'
    bash: line 1: mkhash: command not found
    bash: line 1: mkhash: command not found
    bash: line 1: mkhash: command not found
    bash: line 1: mkhash: command not found
    bash: line 1: mkhash: command not found
    bash: line 1: mkhash: command not found
    bash: line 1: mkhash: command not found
    bash: line 1: mkhash: command not found
    [...]

While these were only warnings and the package still compiled sucessfully,
I also observed that some package even fail to build because of this.

After applying this commit, the variable $(MKHASH) is introduced. This
variable points to $(STAGING_DIR_HOST)/bin/mkhash, which is always the
correct path.

Signed-off-by: Leonardo Mörlein &lt;me@irrelefant.net&gt;
</content>
</entry>
<entry>
<title>libsemanage: fix pkgconfig paths</title>
<updated>2021-04-15T10:54:14Z</updated>
<author>
<name>Rosen Penev</name>
</author>
<published>2021-04-14T03:18:26Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=0ec8c793f5fbecac5c601625a10327bc694e33da'/>
<id>urn:sha1:0ec8c793f5fbecac5c601625a10327bc694e33da</id>
<content type='text'>
The pkgconfig file currently points to host paths.

Signed-off-by: Rosen Penev &lt;rosenp@gmail.com&gt;
</content>
</entry>
<entry>
<title>libcap: bump to 2.48</title>
<updated>2021-04-05T15:20:45Z</updated>
<author>
<name>Stijn Tintel</name>
</author>
<published>2021-03-11T23:08:25Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=0f7f4de6ba9ae4d97c03f36b37ba37251b32dc3e'/>
<id>urn:sha1:0f7f4de6ba9ae4d97c03f36b37ba37251b32dc3e</id>
<content type='text'>
Signed-off-by: Stijn Tintel &lt;stijn@linux-ipv6.be&gt;
Acked-by: Hauke Mehrtens &lt;hauke@hauke-m.de&gt;
</content>
</entry>
<entry>
<title>libcap: drop invalid copyright header</title>
<updated>2021-04-05T15:20:40Z</updated>
<author>
<name>Stijn Tintel</name>
</author>
<published>2021-03-11T23:03:43Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=dd91ba0d6266e7753de01b8a3d4f1cebc12b4225'/>
<id>urn:sha1:dd91ba0d6266e7753de01b8a3d4f1cebc12b4225</id>
<content type='text'>
Signed-off-by: Stijn Tintel &lt;stijn@linux-ipv6.be&gt;
Acked-by: Hauke Mehrtens &lt;hauke@hauke-m.de&gt;
</content>
</entry>
<entry>
<title>libcap: import from packages feed</title>
<updated>2021-04-05T15:20:29Z</updated>
<author>
<name>Stijn Tintel</name>
</author>
<published>2021-03-11T23:03:22Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=427acb71fc8574406a70d41a1f775c0354768cf5'/>
<id>urn:sha1:427acb71fc8574406a70d41a1f775c0354768cf5</id>
<content type='text'>
Having libcap in OpenWrt base allows us to enable libcap support in
other packages in base.

In lldpd, this would allow the monitor process to drop its privileges
instead of running as root, improving security. It will also allow us to
drop our patch to disable libcap.

Signed-off-by: Stijn Tintel &lt;stijn@linux-ipv6.be&gt;
Acked-by: Hauke Mehrtens &lt;hauke@hauke-m.de&gt;
</content>
</entry>
<entry>
<title>uclient: update to Git version 2021-04-03</title>
<updated>2021-04-03T17:06:09Z</updated>
<author>
<name>Hauke Mehrtens</name>
</author>
<published>2021-04-03T17:04:53Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=1371910b76f021486810b18f371b3dc528d952ea'/>
<id>urn:sha1:1371910b76f021486810b18f371b3dc528d952ea</id>
<content type='text'>
83efca2 tests: fix possibly longer start of HTTP server
64e00d6 uclient-fetch: document missing options

Signed-off-by: Hauke Mehrtens &lt;hauke@hauke-m.de&gt;
</content>
</entry>
</feed>
