|
[cip-core] RFC: Process to decide supported package list
Hello Lin-san, Yes we would. We may add more packages in near future discussions, but at least the following packages should be added into the list. openssl sudo *acl, pam and shadow have already list
Hello Lin-san, Yes we would. We may add more packages in near future discussions, but at least the following packages should be added into the list. openssl sudo *acl, pam and shadow have already list
|
By
Kento Yoshida
· #2125
·
|
|
[cip-core] Package Proposal #1 (Security packages)
Hello Kazu and CIP Core working group members, From Renesas, agree with this proposal. Best regards, Kent
Hello Kazu and CIP Core working group members, From Renesas, agree with this proposal. Best regards, Kent
|
By
Kento Yoshida
· #4087
·
|
|
[cip-core] Package Proposal #1 (Security packages)
Thank you for your feedback, Jan. We agree that systemd-timesyncd is sufficient for users who need only SNTP client functionality. The reason we want to add Chrony to our core packages is to support v
Thank you for your feedback, Jan. We agree that systemd-timesyncd is sufficient for users who need only SNTP client functionality. The reason we want to add Chrony to our core packages is to support v
|
By
Kento Yoshida
· #4101
·
|
|
[cip-core] Update PDP to 3.0 (was: RE: [cip-core] Package Proposal #1 (Security packages))
Hi, Sure. Now, the security working group is re-checking the proposed packages and their dependency. Actually, our original proposal consisted of a non-well-maintained package. In addition, as Jan men
Hi, Sure. Now, the security working group is re-checking the proposed packages and their dependency. Actually, our original proposal consisted of a non-well-maintained package. In addition, as Jan men
|
By
Kento Yoshida
· #4144
·
|
|
[cip-core] Update PDP to 3.0 (was: RE: [cip-core] Package Proposal #1 (Security packages))
It's convenience for us. Thank you. The security working group will have a bi-weekly meeting tomorrow, and we'll decide the packages that are proposed as the proposal of this time. I'll create the pro
It's convenience for us. Thank you. The security working group will have a bi-weekly meeting tomorrow, and we'll decide the packages that are proposed as the proposal of this time. I'll create the pro
|
By
Kento Yoshida
· #4155
·
|
|
RESUME REQUEST: [cip-core] Package Proposal #1 (Security packages)
Hello, I would like to resume our proposal from security working group. As you know, Kazu has modified the script to generate a proposal and posted the minimum base system proposal, and then I created
Hello, I would like to resume our proposal from security working group. As you know, Kazu has modified the script to generate a proposal and posted the minimum base system proposal, and then I created
|
By
Kento Yoshida
· #4187
·
|
|
RESUME REQUEST: [cip-core] Package Proposal #1 (Security packages)
Hello and thank you for your comment, Punit,
Hello and thank you for your comment, Punit,
|
By
Kento Yoshida
· #4204
·
|
|
RESUME REQUEST: [cip-core] Package Proposal #1 (Security packages)
Hello reviews, Thank you for your supporting against our proposal. I'd like to share you the description sheet for our proposal of security packages. Please consider my attachment and the following no
Hello reviews, Thank you for your supporting against our proposal. I'd like to share you the description sheet for our proposal of security packages. Please consider my attachment and the following no
|
By
Kento Yoshida
· #4351
·
|
|
Package Proposal #1 (Security packages), rev03
Hello CIP core group members, I'd formally like to propose to add security packages as revision 3. I've already the description sheet before, but I'll share all files for this review again in this mai
Hello CIP core group members, I'd formally like to propose to add security packages as revision 3. I've already the description sheet before, but I'll share all files for this review again in this mai
|
By
Kento Yoshida
· #4361
·
|
|
Package Proposal #1 (Security packages), rev03
Thank you for your comments, Punit. I'll reply to your queries, see the followings. We considered and decided to adopt only sudo binary. As the result, sudo source code includes both sudo and sudo-lda
Thank you for your comments, Punit. I'll reply to your queries, see the followings. We considered and decided to adopt only sudo binary. As the result, sudo source code includes both sudo and sudo-lda
|
By
Kento Yoshida
· #4492
·
|
|
Test case for the security pacakges tied to requirements of IEC 62443-4-2
Hi, As the last IRC meeting, I'll share a draft of test cases for security packages. Noted that this draft is still under review and improvement. In addition, it finally will be revised during validat
Hi, As the last IRC meeting, I'll share a draft of test cases for security packages. Noted that this draft is still under review and improvement. In addition, it finally will be revised during validat
|
By
Kento Yoshida
· #4543
·
|
|
Python 3.x vs 2.7
Hi CIP core group, The security package proposal is suspended now, but I'd like to discuss about the python version which is suitable to maintain. We selected "duplicity" for the requirement of system
Hi CIP core group, The security package proposal is suspended now, but I'd like to discuss about the python version which is suitable to maintain. We selected "duplicity" for the requirement of system
|
By
Kento Yoshida
· #4547
·
|
|
Python 3.x vs 2.7
Thank you for your feedback, Iwamatsu-san.
Thank you for your feedback, Iwamatsu-san.
|
By
Kento Yoshida
· #4550
·
|
|
Python 3.x vs 2.7
Hi,
By
Kento Yoshida
· #4558
·
|
|
[cip-security] [cip-dev] Python 3.x vs 2.7
Hi, I'll share you the functional requirements for system backup: 1. Regular periodic backup 2. Differential archives backup (to be light not to affect normal operation) 3. Encrypting/Decrypting the b
Hi, I'll share you the functional requirements for system backup: 1. Regular periodic backup 2. Differential archives backup (to be light not to affect normal operation) 3. Encrypting/Decrypting the b
|
By
Kento Yoshida
· #4583
·
|
|
Kindly review for kernel config changes
Hi, The security working group need to use "nftables", and it requires to add the below kernel configs to work. Before merging to the master branch of "isar-cip-core", would you kindly review to add t
Hi, The security working group need to use "nftables", and it requires to add the below kernel configs to work. Before merging to the master branch of "isar-cip-core", would you kindly review to add t
|
By
Kento Yoshida
· #4943
·
|
|
Kindly review for kernel config changes
I see. Thank you, Daniel. But, I'm wondering why conf/machine/qemu-amd64.conf doesn't define USE_CIP_KERNEL_CONFIG = "1". Do you have any information for this, Dinesh or Venkata? I think we should rec
I see. Thank you, Daniel. But, I'm wondering why conf/machine/qemu-amd64.conf doesn't define USE_CIP_KERNEL_CONFIG = "1". Do you have any information for this, Dinesh or Venkata? I think we should rec
|
By
Kento Yoshida
· #4949
·
|
|
CIP IRC weekly meeting today
Hi Kudo-san and all, I'll be absent today. And, I'll report here as an alternative to attendance. Both minor updates were once reported, but since they are protracted, I will summarize again here. Maj
Hi Kudo-san and all, I'll be absent today. And, I'll report here as an alternative to attendance. Both minor updates were once reported, but since they are protracted, I will summarize again here. Maj
|
By
Kento Yoshida
· #5505
·
|
|
CIP IRC weekly meeting today
Hi Kudo-san, I'll be absent today due to conflict the schedule. There is no major update from Security working group. One thing, we plan to issue tickets about action lists to meet the certification r
Hi Kudo-san, I'll be absent today due to conflict the schedule. There is no major update from Security working group. One thing, we plan to issue tickets about action lists to meet the certification r
|
By
Kento Yoshida
· #6126
·
|
|
CIP IRC weekly meeting today
Hello Kudo-san, I cannot attend IRC weekly meeting today due to schedule conflict. Sorry for my absence and there is no major update from SWG. Best regards, Kent
Hello Kudo-san, I cannot attend IRC weekly meeting today due to schedule conflict. Sorry for my absence and there is no major update from SWG. Best regards, Kent
|
By
Kento Yoshida
· #6196
·
|