Hi Bastian,
I recently added openssl as a generic build dependency for OpenWrt as
part of the new package signing infrastructure thus I don't think using
openssl sha256 is problematic.
Can you give an example please where there is an openssl without sha256
support?
Thanks,
Steven
* Etienne Champetier etienne.champet...@free.fr [09.10.2013 09:09]:
I've read here
http://stackoverflow.com/questions/592620/check-if-a-program-exists-from-a-bash-script
that it's better to use command -v or hash instead of which
interesting, but
r38026 change the gpio initial node to pinctrl. I want to enable uartf for
HLK-RM04 device, so i add a uartf_pins: uartf node to the pinctrl node.
+ uartf_pins: uartf {
+ uartf {
+ ralink,group = uartf;
+ ralink,function = gpio uartf;
+ };
+ };
This node can enable uartf function of RT5350, but
* Steven Barth cy...@openwrt.org [09.10.2013 09:45]:
I recently added openssl as a generic build dependency for OpenWrt as
part of the new package signing infrastructure thus I don't think
using openssl sha256 is problematic.
it's not 'openssl' itself in my case, but the ability to handle
Hello,
I consider myself quite experienced with OpenWRT already, having
deployed a few devices, but sadly, I'm a totally development newbie -
so sorry if my question is maybe stupid. ;-)
I'd like to stick with OpenWRT stable for my deployments, to have the
same base system. The problem, however,
On 2013-10-09 9:48 AM, Bastian Bittorf wrote:
* Steven Barth cy...@openwrt.org [09.10.2013 09:45]:
I recently added openssl as a generic build dependency for OpenWrt as
part of the new package signing infrastructure thus I don't think
using openssl sha256 is problematic.
it's not 'openssl'
* Felix Fietkau n...@openwrt.org [09.10.2013 19:54]:
it's not 'openssl' itself in my case, but the ability to handle 'sha256':
I think we should probably just put a self-contained utility in tools/
and use that instead of relying on different kinds of host tools.
So selfcompiling a small tool
Le 9 oct. 2013 20:06, Bastian Bittorf bitt...@bluebottle.com a écrit :
* Felix Fietkau n...@openwrt.org [09.10.2013 19:54]:
it's not 'openssl' itself in my case, but the ability to handle
'sha256':
I think we should probably just put a self-contained utility in tools/
and use that instead
This board is pretty similar to ARV752DPW22.
Signed-off-by: Álvaro Fernández Rojas nolt...@gmail.com
---
diff --git
a/target/linux/lantiq/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
b/target/linux/lantiq/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
index 7ec8d6f..2d5e09d 100644
---
I believe this problem appeared on or about r36682, which coincides with a
hostapd update to AA. This suggests a regression in hostapd w/r/t/ to
beacon interval code.
I can confirm the same problem happens when attempting to specify
beacon_int on a single psk2-encrypted adhoc interface, not just
Right now i tested with DISTRIB_REVISION=r38305
Successfully initialized wpa_supplicant
Line 12: unknown network field 'beacon_interval'.
Line 33: failed to parse network block.
Failed to read or parse configuration '/var/run/wpa_supplicant-adhoc0.conf'.
enable_mac80211(radio0): Failed to set up
11 matches
Mail list logo
