From: wireless <wireless@tampabay.rr.com>
To: gentoo-embedded@lists.gentoo.org,
Yury German <BlueKnight@technologysecure.com>
Subject: Re: [gentoo-embedded] Re: Assistance with Stabilization Testing for Arm
Date: Wed, 21 May 2014 13:07:42 -0500 [thread overview]
Message-ID: <537CEB6E.4080408@tampabay.rr.com> (raw)
In-Reply-To: <537AB4A1.90907@gentoo.org>
On 05/19/14 20:49, Rick "Zero_Chaos" Farina wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 05/19/2014 07:53 PM, Yury German wrote:
>> Hello,
>>
>> I am currently part of the Security Team, and am undergoing the final approval for a
>> full time member of the security team. I am also interested in arm development (RPI in
>>particular (for now at least)). So I would like to offer my help in
helping test
>> stabilization for the ARM platform.
>> I currently have a number of PI’s which I use distcc against 30+ cores, I have
>> access to a number of computer systems (although currently Pi is the only
>> one I have for Arm).
Hello Yury,
This is Fantastic news. What I would suggest is to jump straight to the
cutting edge of ARM limited Technology and work on the 64 bit Arm
security issues, so you are 'ahead' of the big push in Arm64 deployment. [1]
www.linaro.org
Surely embedded-gentoo will deploy on Aarch64 [2]. If you master that,
you are going to become an extremely valuable player in the embedded arm
security space, imho. Perhaps you could even update the embedded gentoo
handbook and add a section for aarch64 (arm64) and security on the
gentoo-embedded arm releases. [3] Perhaps you would be interested in
the port of lilblue to arm64 ? [4] Below are a few links you may find
interesting. [5].
hth,
James
[1] http://www.linaro.org/news/linaro-forms-security-working-group/
[2]
http://armin762.wordpress.com/2014/04/06/new-aarch64arm64-stage3-available/
[3] https://www.gentoo.org/proj/en/base/embedded/handbook/
[4] https://wiki.gentoo.org/wiki/Project:Hardened_uClibc/Lilblue
[5]
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZkhrZ1VYUEg2LTlQZzR0RlhzM3c#gid=3
prev parent reply other threads:[~2014-05-21 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5A1B1875-D1E6-4858-BCB8-B9661763BA1A@technologysecure.com>
2014-05-20 1:49 ` [gentoo-embedded] Re: Assistance with Stabilization Testing for Arm Rick "Zero_Chaos" Farina
2014-05-21 18:07 ` wireless [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=537CEB6E.4080408@tampabay.rr.com \
--to=wireless@tampabay.rr.com \
--cc=BlueKnight@technologysecure.com \
--cc=gentoo-embedded@lists.gentoo.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