Re: [yocto] Cannot update dhcpcd receipe from v6.11.5 to v7.x.x
Awesome On Sat, Jan 12, 2019 at 6:00 PM Stefano Cappa wrote: > Fixed. After some tests I'll send the new recipe with a patch to update > dhcpcd. > > Il gio 10 gen 2019, 00:12 Stefano Cappa ha > scritto: > >> Which should be the right path instead of the hardcoded /usr/include? >> Is there a recommended way to fix it in a yocto recipe? >> >> >> Il giorno mer 9 gen 2019 alle ore 03:41 Khem Raj ha >> scritto: >> >>> On Tue, Jan 8, 2019 at 3:48 PM Stefano Cappa >>> wrote: >>> > >>> > Hi! >>> > I'm using Yocto THUD and I'm trying to update dhcpcd >>> (meta-openembedded/meta-networking) from 6.11.5 to 7.0.8 ( >>> https://roy.marples.name/downloads/dhcpcd/dhcpcd-7.0.8.tar.xz) only to >>> do some experiments, however I think that it's correct to migrate to the >>> new version. >>> > >>> > I modified the recipe to download version 7.0.8, but when it's >>> building it throws this error: >>> > >>> > ERROR: dhcpcd-7.0.8-r0 do_configure: configure failed >>> > ERROR: dhcpcd-7.0.8-r0 do_configure: Function failed: do_configure >>> (log file is located at >>> /home/ks89/git/poky/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/dhcpcd/7.0.8-r0/temp/log.do_configure.90966) >>> > ERROR: Logfile of failure stored in: >>> /home/ks89/git/poky/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/dhcpcd/7.0.8-r0/temp/log.do_configure.90966 >>> > Log data follows: >>> > | DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', >>> 'arm-32', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', >>> 'common'] >>> > | DEBUG: Executing shell function autotools_preconfigure >>> > | DEBUG: Shell function autotools_preconfigure finished >>> > | DEBUG: Executing python function autotools_aclocals >>> > | DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', >>> 'arm-32', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', >>> 'common'] >>> > | DEBUG: Python function autotools_aclocals finished >>> > | DEBUG: Executing shell function do_configure >>> > | NOTE: Running ./configure --build=x86_64-linux >>> --host=arm-poky-linux-gnueabi--target=arm-poky-linux-gnueabi >>> --prefix=/usr--exec_prefix=/usr--bindir=/usr/bin >>> --sbindir=/usr/sbin--libexecdir=/usr/libexec--datadir=/usr/share >>> --sysconfdir=/etc--sharedstatedir=/com--localstatedir=/var >>> --libdir=/usr/lib--includedir=/usr/include >>> --oldincludedir=/usr/include--infodir=/usr/share/info >>> --mandir=/usr/share/man--disable-silent-rules >>> --disable-dependency-tracking >>> --with-libtool-sysroot=/home/ks89/git/poky/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/dhcpcd/7.0.8-r0/recipe-sysroot >>> --enable-ipv4 --disable-static --enable-ipv6 --with-udev >>> > | configure args: --build=x86_64-linux --host=arm-poky-linux-gnueabi >>> --target=arm-poky-linux-gnueabi --prefix=/usr --exec_prefix=/usr >>> --bindir=/usr/bin --sbindir=/usr/sbin --libexecdir=/usr/libexec >>> --datadir=/usr/share --sysconfdir=/etc --sharedstatedir=/com >>> --localstatedir=/var --libdir=/usr/lib --includedir=/usr/include >>> --oldincludedir=/usr/include --infodir=/usr/share/info >>> --mandir=/usr/share/man --disable-silent-rules >>> --disable-dependency-tracking >>> --with-libtool-sysroot=/home/ks89/git/poky/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/dhcpcd/7.0.8-r0/recipe-sysroot >>> --enable-ipv4 --disable-static --enable-ipv6 --with-udev >>> > | ./configure: WARNING: unknown option --exec_prefix >>> > | ./configure: WARNING: unknown option --sharedstatedir >>> > | ./configure: WARNING: unknown option --oldincludedir >>> > | ./configure: WARNING: unknown option --with-libtool-sysroot >>> > | ./configure: WARNING: unknown option --with-udev >>> > | Deriving operating system from ... arm-poky-linux-gnueabi >>> > | Configuring dhcpcd for ... linux >>> > | Enabling INET support >>> > | Enabling ARP support >>> > | Enabling ARPing support >>> > | Enabling IPv4LL support >>> > | Enabling INET6 support >>> > | Enabling DHCPv6 support >>> > | Enabling Authentication >>> > | Using compiler .. arm-poky-linux-gnueabi-gcc -march=armv7ve -mthumb >>> -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a7 >>> >>> --sysroot=/home/ks89/git/poky/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/dhcpcd/7.0.8-r0/recipe-sysroot >>> > | arm-poky-linux-gnueabi-gcc -march=armv7ve -mthumb -mfpu=neon >>> -mfloat-abi=hard -mcpu=cortex-a7 >>> >>> --sysroot=/home/ks89/git/poky/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/dhcpcd/7.0.8-r0/recipe-sysroot >>> does not create executables >>> > | NOTE: The following config.log files may provide further information. >>> > | NOTE: >>> /home/ks89/git/poky/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/dhcpcd/7.0.8-r0/dhcpcd-7.0.8/config.log >>> > | ERROR: configure failed >>> > | WARNING: exit code 1 from a shell command. >>> > | ERROR: Function failed: do_configure (log file is located at >>>
Re: [yocto] Cannot update dhcpcd receipe from v6.11.5 to v7.x.x
Fixed. After some tests I'll send the new recipe with a patch to update dhcpcd. Il gio 10 gen 2019, 00:12 Stefano Cappa ha scritto: > Which should be the right path instead of the hardcoded /usr/include? > Is there a recommended way to fix it in a yocto recipe? > > > Il giorno mer 9 gen 2019 alle ore 03:41 Khem Raj ha > scritto: > >> On Tue, Jan 8, 2019 at 3:48 PM Stefano Cappa >> wrote: >> > >> > Hi! >> > I'm using Yocto THUD and I'm trying to update dhcpcd >> (meta-openembedded/meta-networking) from 6.11.5 to 7.0.8 ( >> https://roy.marples.name/downloads/dhcpcd/dhcpcd-7.0.8.tar.xz) only to >> do some experiments, however I think that it's correct to migrate to the >> new version. >> > >> > I modified the recipe to download version 7.0.8, but when it's building >> it throws this error: >> > >> > ERROR: dhcpcd-7.0.8-r0 do_configure: configure failed >> > ERROR: dhcpcd-7.0.8-r0 do_configure: Function failed: do_configure (log >> file is located at >> /home/ks89/git/poky/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/dhcpcd/7.0.8-r0/temp/log.do_configure.90966) >> > ERROR: Logfile of failure stored in: >> /home/ks89/git/poky/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/dhcpcd/7.0.8-r0/temp/log.do_configure.90966 >> > Log data follows: >> > | DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32', >> 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common'] >> > | DEBUG: Executing shell function autotools_preconfigure >> > | DEBUG: Shell function autotools_preconfigure finished >> > | DEBUG: Executing python function autotools_aclocals >> > | DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32', >> 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common'] >> > | DEBUG: Python function autotools_aclocals finished >> > | DEBUG: Executing shell function do_configure >> > | NOTE: Running ./configure --build=x86_64-linux >> --host=arm-poky-linux-gnueabi--target=arm-poky-linux-gnueabi >> --prefix=/usr--exec_prefix=/usr--bindir=/usr/bin >> --sbindir=/usr/sbin--libexecdir=/usr/libexec--datadir=/usr/share >> --sysconfdir=/etc--sharedstatedir=/com--localstatedir=/var >> --libdir=/usr/lib--includedir=/usr/include >> --oldincludedir=/usr/include--infodir=/usr/share/info >> --mandir=/usr/share/man--disable-silent-rules >> --disable-dependency-tracking >> --with-libtool-sysroot=/home/ks89/git/poky/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/dhcpcd/7.0.8-r0/recipe-sysroot >> --enable-ipv4 --disable-static --enable-ipv6 --with-udev >> > | configure args: --build=x86_64-linux --host=arm-poky-linux-gnueabi >> --target=arm-poky-linux-gnueabi --prefix=/usr --exec_prefix=/usr >> --bindir=/usr/bin --sbindir=/usr/sbin --libexecdir=/usr/libexec >> --datadir=/usr/share --sysconfdir=/etc --sharedstatedir=/com >> --localstatedir=/var --libdir=/usr/lib --includedir=/usr/include >> --oldincludedir=/usr/include --infodir=/usr/share/info >> --mandir=/usr/share/man --disable-silent-rules >> --disable-dependency-tracking >> --with-libtool-sysroot=/home/ks89/git/poky/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/dhcpcd/7.0.8-r0/recipe-sysroot >> --enable-ipv4 --disable-static --enable-ipv6 --with-udev >> > | ./configure: WARNING: unknown option --exec_prefix >> > | ./configure: WARNING: unknown option --sharedstatedir >> > | ./configure: WARNING: unknown option --oldincludedir >> > | ./configure: WARNING: unknown option --with-libtool-sysroot >> > | ./configure: WARNING: unknown option --with-udev >> > | Deriving operating system from ... arm-poky-linux-gnueabi >> > | Configuring dhcpcd for ... linux >> > | Enabling INET support >> > | Enabling ARP support >> > | Enabling ARPing support >> > | Enabling IPv4LL support >> > | Enabling INET6 support >> > | Enabling DHCPv6 support >> > | Enabling Authentication >> > | Using compiler .. arm-poky-linux-gnueabi-gcc -march=armv7ve -mthumb >> -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a7 >> >> --sysroot=/home/ks89/git/poky/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/dhcpcd/7.0.8-r0/recipe-sysroot >> > | arm-poky-linux-gnueabi-gcc -march=armv7ve -mthumb -mfpu=neon >> -mfloat-abi=hard -mcpu=cortex-a7 >> >> --sysroot=/home/ks89/git/poky/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/dhcpcd/7.0.8-r0/recipe-sysroot >> does not create executables >> > | NOTE: The following config.log files may provide further information. >> > | NOTE: >> /home/ks89/git/poky/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/dhcpcd/7.0.8-r0/dhcpcd-7.0.8/config.log >> > | ERROR: configure failed >> > | WARNING: exit code 1 from a shell command. >> > | ERROR: Function failed: do_configure (log file is located at >> /home/ks89/git/poky/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/dhcpcd/7.0.8-r0/temp/log.do_configure.90966) >> > >> > Also, the content of "config.log" is : >> >cc1: error: include location "/usr/include" is unsafe for >> cross-compilation
[linux-yocto] v4.18.x - stable updates comprising v4.18.24
Bruce, Yocto kernel folks: Here is the next 4.18.x stable update "extension" primarily created for the Yocto project, continuing from the previous v4.18.23 release. There are about 230 commits here, based on commits chosen from what was used in existing 4.19.12 to 4.19.14 (inclusive) stable releases. Things seem to remain "normal" -- with just basically one commit per each issue. No one subsystem or arch or CVE with lots of changes. I've put this 4.18.x queue through the usual testing; build testing on x86-64/32, ARM-64/32, PPC and MIPS, plus some static analysis and finally some sanity runtime tests on x86-64. I did the signed tag just as per the previously released versions. Please find a signed v4.18.24 tag using this key: http://pgp.mit.edu/pks/lookup?op=vindex=0xEBCE84042C07D1D6 in the repo in the kernel.org directory here: https://git.kernel.org/cgit/linux/kernel/git/paulg/linux-4.18.y.git/ git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-4.18.y.git for merge to standard/base in linux-yocto-4.18 and then out from there into the other base and BSP branches. For those who are interested, the evolution of the commits is here: https://git.kernel.org/cgit/linux/kernel/git/paulg/longterm-queue-4.18.git/ This repo isn't needed for anything; it just exists for transparency and so people can see the evolution of the raw commits that were originally selected to create this 4.18.x release. Paul. -- -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[yocto] [meta-security][PATCH] Upgrade scapy to 2.4.2
Signed-off-by: Scott Ellis
---
recipes-security/scapy/python-scapy.inc | 4 ++--
.../scapy/{python-scapy_2.4.0.bb => python-scapy_2.4.2.bb}| 0
.../scapy/{python3-scapy_2.4.0.bb => python3-scapy_2.4.2.bb} | 0
3 files changed, 2 insertions(+), 2 deletions(-)
rename recipes-security/scapy/{python-scapy_2.4.0.bb => python-scapy_2.4.2.bb}
(100%)
rename recipes-security/scapy/{python3-scapy_2.4.0.bb =>
python3-scapy_2.4.2.bb} (100%)
diff --git a/recipes-security/scapy/python-scapy.inc
b/recipes-security/scapy/python-scapy.inc
index 5abe7db..d5a70fe 100644
--- a/recipes-security/scapy/python-scapy.inc
+++ b/recipes-security/scapy/python-scapy.inc
@@ -5,8 +5,8 @@ LICENSE = "GPLv2"
LIC_FILES_CHKSUM =
"file://bin/scapy;beginline=9;endline=13;md5=1d5249872cc54cd4ca3d3879262d0c69"
-SRC_URI[md5sum] = "d7d3c4294f5a718e234775d38dbeb7ec"
-SRC_URI[sha256sum] =
"452f714f5c2eac6fd0a6146b1dbddfc24dd5f4103f3ed76227995a488cfb2b73"
+SRC_URI[md5sum] = "e6a03d8c924a6bbde1e86fc58bd2b9d6"
+SRC_URI[sha256sum] =
"1baa048936207ceb1a4281a0e1e3b4317667c754872a0bb4734c5213c468e86a"
inherit pypi ptest
diff --git a/recipes-security/scapy/python-scapy_2.4.0.bb
b/recipes-security/scapy/python-scapy_2.4.2.bb
similarity index 100%
rename from recipes-security/scapy/python-scapy_2.4.0.bb
rename to recipes-security/scapy/python-scapy_2.4.2.bb
diff --git a/recipes-security/scapy/python3-scapy_2.4.0.bb
b/recipes-security/scapy/python3-scapy_2.4.2.bb
similarity index 100%
rename from recipes-security/scapy/python3-scapy_2.4.0.bb
rename to recipes-security/scapy/python3-scapy_2.4.2.bb
--
2.17.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Setting up a password for the root user
For security it is best to disable console login for root and all users
altogether and use ssh with keys. If you are building many devices you
would want to provision each of them with unique keys.
:rjs
On Sat, Jan 12, 2019, 04:42 Stefano Cappa From a security point of view, Is it better to use "usermod -p `openssl
> passwd mypass` root; \" or with uppercase P "usermod -P mypass root; \" ?
>
>
> Il giorno sab 12 gen 2019 alle ore 04:38 Rudolf J Streif <
> rudolf.str...@ibeeto.com> ha scritto:
>
>> Alberto,
>>
>> The quotes around
>>
>> `openssl passwd ${ROOT_PASSWORD}`
>>
>> have to be backticks (`) not single quotes (').
>>
>> :rjs
>>
>> On 01/11/2019 07:41 AM, Alberto Spin wrote:
>>
>> Hello There,
>>
>>
>>
>> I’m trying to set a password for the root user of my distribution (based
>> rocko branch)
>>
>>
>>
>> I’ve added the following to my image recipe:
>>
>>
>>
>> inherit extrausers
>>
>>
>>
>> # set image root password
>>
>> ROOT_PASSWORD = "secret"
>>
>>
>>
>> EXTRA_USERS_PARAMS = "\
>>
>> usermod -p 'openssl passwd ${ROOT_PASSWORD}' root; \
>>
>> "
>>
>>
>>
>> Everything builds fine, but in my image I end up with a password in my
>> /etc/shadow file like this:
>>
>>
>>
>> openssl passwd secret
>>
>>
>>
>> so it seems like the openssl command has not been executed during the
>> build, but instead the literal command is now part of my password.
>>
>>
>>
>> Can anybody please explain what’s going on here, and how to fix this?
>>
>>
>>
>> Kind Regards,
>>
>>
>>
>> Alberto
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-mingw and cmake
CC'ing yocto@yoctoproject.org On Sat, Jan 12, 2019 at 1:02 PM Sinan Kaya wrote: > > Hi Joshua, > > I have this instruction to build cmake as part of the SDK. > > +# Add the CMake binary to the SDK > +TOOLCHAIN_HOST_TASK += "nativesdk-cmake" > + > > When I add this, windows SDK build is failing to compile. > > I'm using the sumo branch. Do you have any ideas? I believe that compiling cmake for mingw works on master, can you give that a try? Also, be aware that while it compiles, it may not actually work in the SDK depending on your use case. See https://lists.yoctoproject.org/pipermail/yocto/2018-November/043344.html for more details. > > Sinan -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [linux-yocto] [kernel-cache][PATCH] qemuriscv64: Initial support for 64-bit QEMU RISC-V
On 2019-01-11 6:40 p.m., Alistair Francis wrote: On Wed, Jan 9, 2019 at 9:34 AM Bruce Ashfield wrote: On 2019-01-09 12:21 p.m., Alistair Francis wrote: On Wed, Jan 9, 2019 at 9:18 AM Bruce Ashfield wrote: On 2019-01-09 12:16 p.m., Alistair Francis wrote: On Wed, Jan 9, 2019 at 8:34 AM Bruce Ashfield wrote: Looks fine to me. This is on the 4.19 and master branches of the kernel-cache. Thanks Bruce! I'll send SRCREV bumps for those kernel versions shortly. Do you mind if I do it? I have a patch ready now to bump the SHA and add qemuriscv64 as a supported machine. I have it queued with a number of other changes, so it needs to come along with that SRCREV bump. Ah, no worries then. Otherwise if you do can you add qemuriscv64 as compatible. I'd have to test it first before I could add that. What would be the steps to do that ? Is everything else in oe-core ? We would also need to add the qemuriscv64 machine in order to build it. The only thing we are missing after that is the bootloader, which isn't in oe-core. We are working on a improved boot flow for RISC-V so the current boot loader will probably never go into oe-core. Gotcha. I'm just tidying up the other changes. I do expect to have them out today. So the wait won't be too long! Any update on the SRCREV changes? I just sent them a few minutes ago! Bruce Alistair Bruce Alistair Bruce Alistair Cheers, Bruce On 2019-01-07 7:54 p.m., Alistair Francis wrote: Signed-off-by: Alistair Francis --- arch/riscv/riscv.cfg | 8 ++ arch/riscv/riscv.scc | 4 +++ bsp/qemuriscv64/qemuriscv64-standard.scc | 8 ++ bsp/qemuriscv64/qemuriscv64.cfg | 34 bsp/qemuriscv64/qemuriscv64.scc | 1 + 5 files changed, 55 insertions(+) create mode 100644 arch/riscv/riscv.cfg create mode 100644 arch/riscv/riscv.scc create mode 100644 bsp/qemuriscv64/qemuriscv64-standard.scc create mode 100644 bsp/qemuriscv64/qemuriscv64.cfg create mode 100644 bsp/qemuriscv64/qemuriscv64.scc diff --git a/arch/riscv/riscv.cfg b/arch/riscv/riscv.cfg new file mode 100644 index ..e19a967e --- /dev/null +++ b/arch/riscv/riscv.cfg @@ -0,0 +1,8 @@ + +CONFIG_RISCV=y +CONFIG_RISCV_ISA_C=y +CONFIG_RISCV_ISA_A=y + +CONFIG_RISCV_TIMER=y + +CONFIG_MMU=y diff --git a/arch/riscv/riscv.scc b/arch/riscv/riscv.scc new file mode 100644 index ..a792680a --- /dev/null +++ b/arch/riscv/riscv.scc @@ -0,0 +1,4 @@ +if [ "$KARCH" = "riscv" ]; then + kconf hardware riscv.cfg + include cfg/timer/hz_100.scc +fi diff --git a/bsp/qemuriscv64/qemuriscv64-standard.scc b/bsp/qemuriscv64/qemuriscv64-standard.scc new file mode 100644 index ..1725c4fa --- /dev/null +++ b/bsp/qemuriscv64/qemuriscv64-standard.scc @@ -0,0 +1,8 @@ +define KMACHINE qemuriscv64 +define KTYPE standard +define KARCH riscv64 + +include ktypes/standard/standard.scc + +include cfg/virtio.scc +include qemuriscv64.scc diff --git a/bsp/qemuriscv64/qemuriscv64.cfg b/bsp/qemuriscv64/qemuriscv64.cfg new file mode 100644 index ..3e51db56 --- /dev/null +++ b/bsp/qemuriscv64/qemuriscv64.cfg @@ -0,0 +1,34 @@ +# +# RISC-V 64-bit +# +CONFIG_ARCH_RV64I=y +CONFIG_64BIT=y + +# +# Platform type +# +CONFIG_MAXPHYSMEM_128GB=y +CONFIG_SMP=y +CONFIG_NR_CPUS=8 +CONFIG_TUNE_GENERIC=y + +# +# Bus support +# +CONFIG_PCI=y +CONFIG_PCI_ECAM=y +CONFIG_PCI_HOST_COMMON=y +CONFIG_PCI_HOST_GENERIC=y +CONFIG_PCIEPORTBUS=y + +# +# Non-8250 serial port support +# +CONFIG_HVC_DRIVER=y +CONFIG_HVC_RISCV_SBI=y +CONFIG_VIRTIO_CONSOLE=y + +# +# IRQ chip support +# +CONFIG_SIFIVE_PLIC=y diff --git a/bsp/qemuriscv64/qemuriscv64.scc b/bsp/qemuriscv64/qemuriscv64.scc new file mode 100644 index ..527a2878 --- /dev/null +++ b/bsp/qemuriscv64/qemuriscv64.scc @@ -0,0 +1 @@ +kconf hardware qemuriscv64.cfg -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [yocto] Setting up a password for the root user
>From a security point of view, Is it better to use "usermod -p `openssl
passwd mypass` root; \" or with uppercase P "usermod -P mypass root; \" ?
Il giorno sab 12 gen 2019 alle ore 04:38 Rudolf J Streif <
rudolf.str...@ibeeto.com> ha scritto:
> Alberto,
>
> The quotes around
>
> `openssl passwd ${ROOT_PASSWORD}`
>
> have to be backticks (`) not single quotes (').
>
> :rjs
>
> On 01/11/2019 07:41 AM, Alberto Spin wrote:
>
> Hello There,
>
>
>
> I’m trying to set a password for the root user of my distribution (based
> rocko branch)
>
>
>
> I’ve added the following to my image recipe:
>
>
>
> inherit extrausers
>
>
>
> # set image root password
>
> ROOT_PASSWORD = "secret"
>
>
>
> EXTRA_USERS_PARAMS = "\
>
> usermod -p 'openssl passwd ${ROOT_PASSWORD}' root; \
>
> "
>
>
>
> Everything builds fine, but in my image I end up with a password in my
> /etc/shadow file like this:
>
>
>
> openssl passwd secret
>
>
>
> so it seems like the openssl command has not been executed during the
> build, but instead the literal command is now part of my password.
>
>
>
> Can anybody please explain what’s going on here, and how to fix this?
>
>
>
> Kind Regards,
>
>
>
> Alberto
>
>
>
>
>
>
>
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
