From: "minmin@plathome.co.jp" <minmin@plathome.co.jp>
To: masashi.kudo@cybertrust.co.jp, cip-dev@lists.cip-project.org
Cc: pavel@denx.de, nobuhiro1.iwamatsu@toshiba.co.jp, wens@csie.org,
jan.kiszka@siemens.com
Subject: Re: [cip-dev] [Feedback Requested] RE: Cip-kernel-sec Updates for Week of 2021-03-18
Date: Fri, 19 Mar 2021 15:55:31 +0900 [thread overview]
Message-ID: <bbaaff0c-aace-4c0d-2c48-00d93653416f@plathome.co.jp> (raw)
In-Reply-To: <TY2PR01MB4972E1E07AE85D162237E83CA0699@TY2PR01MB4972.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]
Hi, Kudo-san, CIP kernel members,
On 2021/03/18 18:33, masashi.kudo@cybertrust.co.jp wrote:
> - CVE-2020-35519 is relating to X.25.
> X.25 is enabled as follows, but we wonder whether X.25 is really used or not.
>> 4.4.y-cip/x86/plathome_obsvx1.config:CONFIG_X25=m
Oh!
This configuration, "plathome_obsvx1.config" is for the OpenBlocks IoT VX1. VX1 is the predecessor to VX2 and we do not currently support VX1. Also, VX2 has been the reference hardware for the CIP since the 4.19 kernel.
Therefore, I think "plathome_obsvx1.config" should be removed from the CIP kernel configuration.
By the way, VX1 has almost the same hardware configuration as VX2, so the kernel for VX2 will work as is.
Best Regards,
minmin
[-- Attachment #2: Type: text/plain, Size: 428 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6295): https://lists.cip-project.org/g/cip-dev/message/6295
Mute This Topic: https://lists.cip-project.org/mt/81425316/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/4520388/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2021-03-19 6:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 9:33 [cip-dev] [Feedback Requested] RE: Cip-kernel-sec Updates for Week of 2021-03-18 masashi.kudo
2021-03-19 6:55 ` minmin [this message]
2021-03-19 7:05 ` masashi.kudo
2021-04-08 2:00 ` Nobuhiro Iwamatsu
2021-03-19 8:05 ` Jan Kiszka
2021-03-19 8:47 ` masashi.kudo
2021-04-08 1:55 ` Nobuhiro Iwamatsu
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=bbaaff0c-aace-4c0d-2c48-00d93653416f@plathome.co.jp \
--to=minmin@plathome.co.jp \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
--cc=masashi.kudo@cybertrust.co.jp \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=pavel@denx.de \
--cc=wens@csie.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).