On 17/10/2018 18:03, Alan Cudmore wrote:
Is the POSIX API preferred for RTEMS applications moving forward?
I would use standard APIs such as POSIX, C++11 or boost.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax
Is the POSIX API preferred for RTEMS applications moving forward?
Thanks,
Alan
On Wed, Oct 17, 2018 at 5:20 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 15/10/2018 14:23, Thawra Kadeed wrote:
> >
> > Thanks a lot Sebastian for referring me to the git master.
> >
> > Actua
On Tue, Oct 16, 2018 at 8:02 PM wrote:
> Hi, there seems to be a protocol issue with libssh that allows the bypass
> of credentials. I was wondering if there are any parts of RTEMS that use
> libssh?
>
> Instead of butchering the explanation of a protocol that I don’t know, see
> CVE-2018-10933.
On 17/10/2018 12:38, emanuel stiebler wrote:
On 2017-12-05 07:14, Sebastian Huber wrote:
Hello,
we don't have support for AArch64 in RTEMS, but you can run in 32-bit
mode on these processors. We don't work on AArch64 support at the
moment. It shouldn't be very difficult.
Would there be any big
On 2017-12-05 07:14, Sebastian Huber wrote:
> Hello,
>
> we don't have support for AArch64 in RTEMS, but you can run in 32-bit
> mode on these processors. We don't work on AArch64 support at the
> moment. It shouldn't be very difficult.
Would there be any bigger issues, to get the AArch64 Toolcha
On 15/10/2018 14:23, Thawra Kadeed wrote:
Thanks a lot Sebastian for referring me to the git master.
Actually, I cloned the current git master and I was looking for the
RTEMS kernel (source code) and I have found it in this path:
"rtems-master/cpukit/rtems"
I think this is the RTEMS library