| *** rajm has joined #cip | 07:37 | |
| *** masashi910 has joined #cip | 08:01 | |
| *** samwilson_ has joined #cip | 08:33 | |
| *** hungtran has joined #cip | 08:51 | |
| *** kazu24 has joined #cip | 08:55 | |
| *** fujita has joined #cip | 08:55 | |
| *** pave1 has joined #cip | 08:59 | |
| masashi910 | #startmeeting CIP IRC weekly meeting | 09:00 |
|---|---|---|
| brlogger | Meeting started Thu Nov 5 09:00:01 2020 UTC and is due to finish in 60 minutes. The chair is masashi910. Information about MeetBot at http://wiki.debian.org/MeetBot. | 09:00 |
| brlogger | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 09:00 |
| brlogger | The meeting name has been set to 'cip_irc_weekly_meeting' | 09:00 |
| *** brlogger changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| masashi910 | #topic rollcall | 09:00 |
| *** brlogger changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| pave1 | hi | 09:00 |
| masashi910 | please say hi if you're around | 09:00 |
| kazu24 | hi | 09:00 |
| fujita | hi | 09:00 |
| masashi910 | Today Chris-san and Chen-Yu-san are not here. | 09:01 |
| yoshidak[m] | hi | 09:01 |
| masashi910 | Let's get started. | 09:01 |
| masashi910 | #topic AI review | 09:01 |
| *** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 09:01 | |
| masashi910 | 1. Combine root filesystem with kselftest binary - iwamatsu | 09:01 |
| masashi910 | Iwamatsu-san, are you around? | 09:01 |
| masashi910 | Let's come back when he joins. | 09:01 |
| masashi910 | 2. Check whether CVE-2019-0145, CVE-2019-0147, CVE-2019-0148 needs to be backported to 4.4 - Kernel Team | 09:01 |
| iwamatsu | hi | 09:02 |
| iwamatsu | about 1., no update | 09:02 |
| masashi910 | iwamatsu: Noted. Thanks. | 09:02 |
| masashi910 | Regarding CVE-2019-0145, CVE-2019-0147, CVE-2019-0148, at the last meeting we recognized that those descriptions are not clear, and it is difficult for us to move forward based on those information. | 09:03 |
| masashi910 | Are there any changes? | 09:04 |
| pave1 | Not really. I believe we should let Intel solve that out. | 09:05 |
| pave1 | The descriptions are not really clear, we do not have i40e boards for testing... | 09:05 |
| pave1 | ...and the patches we identified do not really look like fixing too serious stuff. | 09:05 |
| masashi910 | pave1: Sure. Then let's keep this AI open till Intel fixes them. | 09:06 |
| masashi910 | pave1: Thanks! | 09:06 |
| masashi910 | any other topics? | 09:06 |
| masashi910 | 3 | 09:06 |
| masashi910 | 2 | 09:06 |
| pave1 | masashi910: I'd suggest simply dropping it from our list. | 09:06 |
| pave1 | masashi910: Let the stable team handle this one, no need to track it here. | 09:07 |
| iwamatsu | +1 | 09:07 |
| masashi910 | pave1: OK. Thanks for your advice. I will notify this to cip-dev as well. | 09:08 |
| pave1 | Thanks. | 09:08 |
| masashi910 | pave1: Thanks! | 09:08 |
| masashi910 | any other topics? | 09:08 |
| masashi910 | 3 | 09:08 |
| masashi910 | 2 | 09:09 |
| masashi910 | 1 | 09:09 |
| masashi910 | #topic Kernel maintenance updates | 09:09 |
| *** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 09:09 | |
| pave1 | From the last irc meeting, review of 4.19.153 and 4.19.155 were major topics. | 09:09 |
| iwamatsu | I reviewed 4.4.141 and 242-rc | 09:10 |
| masashi910 | pave1, iwamatsu: Thanks for your works! | 09:10 |
| masashi910 | any other topics? | 09:10 |
| masashi910 | 3 | 09:11 |
| masashi910 | 2 | 09:11 |
| masashi910 | 1 | 09:11 |
| masashi910 | BTW Chen-Yu-san mentioned that he will report his status this evening. | 09:11 |
| masashi910 | #topic Kernel testing | 09:11 |
| *** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 09:11 | |
| masashi910 | According to Chris-san, he has no updates. | 09:11 |
| masashi910 | any other topics? | 09:11 |
| masashi910 | 3 | 09:12 |
| masashi910 | 2 | 09:12 |
| masashi910 | 1 | 09:12 |
| masashi910 | #topic CIP Security | 09:12 |
| *** brlogger changes topic to "CIP Security (Meeting topic: CIP IRC weekly meeting)" | 09:12 | |
| yoshidak[m] | hi | 09:12 |
| yoshidak[m] | The gap assessment review for IEC 62443-4-2, technical requirements are scheduled tomorrow. | 09:12 |
| yoshidak[m] | It expected to be completed tomorrow, then Exida will create the report in several weeks. | 09:12 |
| yoshidak[m] | And, we'll continue to summarize the process requirements to other teams as the result of the gap assessment for IEC 62443-4-1. | 09:12 |
| yoshidak[m] | We'll hold the internal meeting next Monday and discuss about it. | 09:13 |
| pave1 | yoshidak: Could we talk on irc after the meeting? | 09:13 |
| yoshidak[m] | masashi910: Sure | 09:13 |
| yoshidak[m] | That's the end from me today. | 09:13 |
| masashi910 | yoshidak[m]: Thanks for your works! | 09:13 |
| masashi910 | BTW are you planning to give a talk at OSSJ? | 09:13 |
| yoshidak[m] | No | 09:14 |
| masashi910 | I see. Thanks. | 09:14 |
| masashi910 | any other topics? | 09:14 |
| masashi910 | 3 | 09:14 |
| masashi910 | 2 | 09:14 |
| masashi910 | 1 | 09:14 |
| masashi910 | #topic AOB | 09:14 |
| *** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 09:14 | |
| masashi910 | Are there any business to discuss? | 09:14 |
| masashi910 | 3 | 09:15 |
| masashi910 | 2 | 09:15 |
| masashi910 | 1 | 09:15 |
| masashi910 | #endmeeting | 09:15 |
| brlogger | Meeting ended Thu Nov 5 09:15:31 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:15 |
| brlogger | Minutes: https://irclogs.baserock.org/meetings/cip/2020/11/cip.2020-11-05-09.00.html | 09:15 |
| brlogger | Minutes (text): https://irclogs.baserock.org/meetings/cip/2020/11/cip.2020-11-05-09.00.txt | 09:15 |
| brlogger | Log: https://irclogs.baserock.org/meetings/cip/2020/11/cip.2020-11-05-09.00.log.html | 09:15 |
| *** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 09:15 | |
| masashi910 | Thanks, Bye! | 09:15 |
| pave1 | bye! | 09:15 |
| iwamatsu | Thank you! | 09:16 |
| pave1 | yoshidak: Do we have some guidelines about the use cases? | 09:16 |
| *** kazu24 has quit IRC | 09:16 | |
| pave1 | yoshidak: Like: is it okay to run untrusted code on the CPU? | 09:16 |
| pave1 | yoshidak: Like: do we recommend running JIT interpetters with untrusted code? | 09:17 |
| pave1 | yoshidak: etc? | 09:17 |
| yoshidak[m] | We can create some guidelines for a generic use case, but there is nothing concrete at this time. | 09:19 |
| pave1 | yoshidak: It would be good. There are various security barriers in the system, and it would be good to know which ones we focus on. | 09:20 |
| yoshidak[m] | About untrusted code, the norm says that It should be completely eliminated, so I guess the norm doesn't extend to be run untrusted code. | 09:20 |
| yoshidak[m] | Agree. | 09:20 |
| pave1 | yoshidak: So stuff like web browsers is ruled out? | 09:20 |
| *** tpollard has joined #cip | 09:21 | |
| yoshidak[m] | The norm has requirements for mobile codes, so user should follow that requirement basically. | 09:21 |
| pave1 | yoshidak: I'm not sure what "mobile code" is. | 09:22 |
| yoshidak[m] | But, I guess it also depends on use case. So, at least we can only recommend to assess risks to use mobile codes. | 09:22 |
| yoshidak[m] | pave1: mobile code means the program automatically downloaded and run via the browsers and so on. | 09:24 |
| pave1 | yoshidak: aha, ok. | 09:25 |
| yoshidak[m] | <pave1 "yoshidak: So stuff like web brow"> I intended to answer this question, but was it correct? | 09:26 |
| pave1 | yoshidak: Would it make sense to have a document describing various security guarantees inside kernel, and our priorities w.r.t. them? | 09:27 |
| pave1 | yoshidak: Well, web browsers download javascript from the web, then run it locally; we can't avoid them on general purpose desktops, but I believe we should make it clear that such stuff should not be done in industrial settings. | 09:28 |
| yoshidak[m] | <pave1 "yoshidak: Would it make sense to"> It is very useful for the assessment. Of course, it will be included in our offers to kernel team. | 09:28 |
| pave1 | Ok. Thank you! | 09:29 |
| yoshidak[m] | pave1: That's right. As a minimum, the supplier must show the user a policy on how to handle them. | 09:30 |
| yoshidak[m] | But, it's a supplier's task, we don't have specific idea to deal with them as you know. | 09:31 |
| yoshidak[m] | pave1: You're welcome. Bye! | 09:32 |
| pave1 | Bye1 | 09:33 |
| pave1 | ! | 09:33 |
| *** eduardas has joined #cip | 10:02 | |
| *** hungtran has quit IRC | 10:02 | |
| *** fujita has quit IRC | 10:06 | |
| *** pave1 has quit IRC | 10:31 | |
| *** monstr has joined #cip | 10:36 | |
| *** masashi910 has quit IRC | 11:08 | |
| *** toscalix has joined #cip | 12:02 | |
| *** toscalix has quit IRC | 13:12 | |
| *** eduardas has quit IRC | 14:14 | |
| *** eduardas has joined #cip | 14:14 | |
| *** toscalix has joined #cip | 15:37 | |
| *** toscalix_ has joined #cip | 16:03 | |
| *** toscalix has quit IRC | 16:06 | |
| *** eduardas has quit IRC | 16:16 | |
| *** tpollard has quit IRC | 17:02 | |
| *** samwilson_ has quit IRC | 17:10 | |
| *** samwilson_ has joined #cip | 17:14 | |
| *** samwilson_ has quit IRC | 17:56 | |
| *** monstr has quit IRC | 18:04 | |
| *** samwilson_ has joined #cip | 20:05 | |
| *** toscalix_ has quit IRC | 20:17 | |
| *** samwilson_ has quit IRC | 21:13 | |
| *** rajm has quit IRC | 23:01 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!