From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org
Cc: Sai <Sai.Sathujoda@toshiba-tsip.com>,
dinesh.kumar@toshiba-tsip.com, kazuhiro3.hayashi@toshiba.co.jp,
quirin.gylstorff@siemens.com,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [isar-cip-core][PATCH 5/5] security-customizations: Fix password hint
Date: Thu, 2 Mar 2023 21:30:54 +0100 [thread overview]
Message-ID: <caf09d788e1af7274774e8c65a8a0f41525080ba.1677789054.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1677789054.git.jan.kiszka@siemens.com>
From: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
recipes-core/security-customizations/files/postinst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-core/security-customizations/files/postinst b/recipes-core/security-customizations/files/postinst
index 4ff8ecf6..167bab1c 100644
--- a/recipes-core/security-customizations/files/postinst
+++ b/recipes-core/security-customizations/files/postinst
@@ -4,7 +4,7 @@
# Security Package configurations
#
-echo "CIP Core Security Image (login: root/root)" > /etc/issue
+echo "CIP Core Security Image (login: root/Cipsecurity@123)" > /etc/issue
HOSTNAME=demo
echo "$HOSTNAME" > /etc/hostname
--
2.35.3
prev parent reply other threads:[~2023-03-02 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 20:30 [isar-cip-core][PATCH 0/5] Enable feature combinations of test and security extensions Jan Kiszka
2023-03-02 20:30 ` [isar-cip-core][PATCH 1/5] swupdate: Avoid open-coding IMAGE_FULLNAME Jan Kiszka
2023-03-02 20:30 ` [isar-cip-core][PATCH 2/5] initramfs-*-hook: " Jan Kiszka
2023-03-02 20:30 ` [isar-cip-core][PATCH 3/5] start-qemu: Add support for booting test-extended images Jan Kiszka
2023-03-02 20:30 ` [isar-cip-core][PATCH 4/5] cip-core-image-security: Add support for SWUpdate Jan Kiszka
2023-03-02 20:30 ` Jan Kiszka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=caf09d788e1af7274774e8c65a8a0f41525080ba.1677789054.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Sai.Sathujoda@toshiba-tsip.com \
--cc=cip-dev@lists.cip-project.org \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=felix.moessbauer@siemens.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
--cc=quirin.gylstorff@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.