Since version 2.0.0, bitbake machinery is installing a kernel image into the boot partion. However that kernel is not used for booting at all and it can be removed safely.
Signed-off-by: Kareem Zarka kareem.zarka@huawei.com
@zyga my patch that enables removing the kernel image from the boot partition got merged and therefore now it can be safely removed by passing the parameter to skip installing the image
https://git.openembedded.org/openembedded-core/commit/?id=d3599afe5f604ea5afd9411e114934dcb52b2d48
https://git.openembedded.org/openembedded-core/commit/?id=a99bc5ed8bf67f171be24c0e2220aae6cccf230e
Dear project committers,
I would like to bring to your attention that the security team at the Eclipse Foundation will soon be requiring that accounts with committer privileges on gitlab.eclipse.org activate 2FA access control.
The plans, along with details on the importance of this change, have been shared on the committers mailing list.
As included in the announcement, we are opening this ticket to inform you and track the activation of 2FA on accounts belonging to this projects’ members.
To keep in mind, starting on on the 30th of October you’ll likely see a banner each time you access GitLab reminding you to activate 2FA in your account.
The deadline is December the 4th, by which access to your account will be limited until you activate 2FA. It is highly recommended that you enroll in this process before the deadline.
GitLab offers instructions on every step of the process and we’re happy to answer any question you might have.
Thank you!
/cc @mbarbero
Detailed instructions are available. In a nutshell, visit gitlab.eclipse.org/-/profile/two_factor_auth and follow the on-screen instructions.
If the form asks you for a password in order to set up 2FA on your account, this is not your Eclipse account’s password. It is a known bug on Gitlab that some accounts are requested a “local” password despite having one in the Active Directory.
You should request a password reset and use that same password for this form. This process does not change your Eclipse account password.
No. GitLab supports two 2FA methods: Time-based One Time Password (TOTP) compatible with mobile apps like Google Authenticator or Authy, and several password managers such as Bitwarden or 1Password. WebAuthN, which necessitates a hardware token, typically a USB key (examples include Solo 2 key or Yubikey). These tokens are sometimes referred to as FIDO2 keys.
In the near future, 2FA will become mandatory for authentication on your accounts. Should you not have enrolled by the deadline we communicated to you, access to the platform will be restricted.
No, you’re all good.
We highly recommend the utilization of diverse secondary authentication methods. In the event that you misplace all your secondary authentication elements, recovery codes will be the only way to restore account access. By securely storing your recovery codes, you'll ensure the ability to regain access.
Note that the Eclipse IT team may be able to recover access to accounts with 2FA enabled if both the 2FA credentials and account recovery methods are lost. This will require extra identity verification and direct contact with security@eclipse-foundation.org or webmaster@eclipse-foundation.org.
Greetings commiters,
This comment is meant to remind you that there's only one week left until the enforcement takes place.
We can see that not all committers on this project have 2FA active yet.
I'd like to take the chance to offer help in any difficulties you face in this change.
closing issue: ohos-planning#31 (closed)
hw lab is being discontinued therefore removing unmaintained ci jobs: lava and hawkbit
Signed-off-by: Francesco Pham francesco.pham@huawei.com
Stefan Schmidt (9936330f) at 07 Nov 09:08
Merge branch 'ci/remove-lava' into 'kirkstone'
... and 2 more commits
hw lab is being discontinued therefore removing unmaintained ci jobs: lava and hawkbit
Signed-off-by: Francesco Pham francesco.pham@huawei.com
hw lab is being discontinued therefore removing unmaintained ci jobs: lava and hawkbit
Signed-off-by: Francesco Pham francesco.pham@huawei.com
hw lab is being discontinued therefore removing unmaintained ci jobs: lava and hawkbit
Signed-off-by: Francesco Pham francesco.pham@huawei.com
gitlab-ci-templates project path was moved, therefore replacing with the correct path. Fixing CI pipeline
Relate-to: ohos-planning#31
Signed-off-by: Francesco Pham francesco.pham@huawei.com
Francesco Pham (deb66d92) at 27 Oct 17:12
Merge branch 'kirkstone' into 'kirkstone'
... and 1 more commit
gitlab-ci-templates project path was moved, therefore replacing with the correct path. Fixing CI pipeline
Relate-to: ohos-planning#31
Signed-off-by: Francesco Pham francesco.pham@huawei.com
gitlab-ci-templates project path was moved, therefore replacing with the correct path. Fixing CI pipeline
Relate-to: ohos-planning#31
Signed-off-by: Francesco Pham francesco.pham@huawei.com
gitlab-ci-templates project path was moved, therefore replacing with the correct path. Fixing CI pipeline
Relate-to: ohos-planning#31
Signed-off-by: Francesco Pham francesco.pham@huawei.com
Dear project committers,
I would like to bring to your attention that the security team at the Eclipse Foundation will soon be requiring that accounts with committer privileges on gitlab.eclipse.org activate 2FA access control.
The plans, along with details on the importance of this change, have been shared on the committers mailing list.
As included in the announcement, we are opening this ticket to inform you and track the activation of 2FA on accounts belonging to this projects’ members.
To keep in mind, starting on on the 30th of October you’ll likely see a banner each time you access GitLab reminding you to activate 2FA in your account.
The deadline is December the 4th, by which access to your account will be limited until you activate 2FA. It is highly recommended that you enroll in this process before the deadline.
GitLab offers instructions on every step of the process and we’re happy to answer any question you might have.
Thank you!
/cc @mbarbero
Detailed instructions are available. In a nutshell, visit gitlab.eclipse.org/-/profile/two_factor_auth and follow the on-screen instructions.
If the form asks you for a password in order to set up 2FA on your account, this is not your Eclipse account’s password. It is a known bug on Gitlab that some accounts are requested a “local” password despite having one in the Active Directory.
You should request a password reset and use that same password for this form. This process does not change your Eclipse account password.
No. GitLab supports two 2FA methods: Time-based One Time Password (TOTP) compatible with mobile apps like Google Authenticator or Authy, and several password managers such as Bitwarden or 1Password. WebAuthN, which necessitates a hardware token, typically a USB key (examples include Solo 2 key or Yubikey). These tokens are sometimes referred to as FIDO2 keys.
In the near future, 2FA will become mandatory for authentication on your accounts. Should you not have enrolled by the deadline we communicated to you, access to the platform will be restricted.
No, you’re all good.
We highly recommend the utilization of diverse secondary authentication methods. In the event that you misplace all your secondary authentication elements, recovery codes will be the only way to restore account access. By securely storing your recovery codes, you'll ensure the ability to regain access.
Note that the Eclipse IT team may be able to recover access to accounts with 2FA enabled if both the 2FA credentials and account recovery methods are lost. This will require extra identity verification and direct contact with security@eclipse-foundation.org or webmaster@eclipse-foundation.org.
Monthly auditing and risk assessment activities on Goofy.
This issue is related and comprehend all audit activities performed during the December iteration.
Advance of the audit process can be seen here
All
License Compliance Auditor
Monthly auditing and risk assessment activities on Goofy.
This issue is related and comprehend all audit activities performed during the November iteration.
Advance of the audit process can be seen here
All
License Compliance Auditor
Monthly auditing and risk assessment activities on Goofy.
This issue is related and comprehend all audit activities performed during the October iteration.
Advance of the audit process can be seen here
All
License Compliance Auditor
Signed-off-by: Luca Favaretto luca.favaretto@kalpa.it