Anyone has Owl image for Raspberry Pi?

Colleagues,

despite that ARM is not mentioned at
http://www.openwall.com/Owl/ARCHITECTURES.shtml, I recall someone in the
past reported some experiments with Owl on ARM.  I wonder now whether
anyone tried to bring Owl up on Raspberry Pi.  Actually, what I need is a
(tiny, and definitely console-only) OS for Raspberry Pi being used as a
controlling computer in applications such as smart house, and it seems to
me that Owl is natural choice.

So, if there are any results so far in this area, please point me on them; 
if there are none, I'm going to try to build Owl for Raspberry Pi myself,
and in this case I'd be pleased for any tips and advices.  I only would
like to confirm I will not repeat someone else's work doing that.

Please note I've got an image of Debian for Raspberry Pi which is already
up and running; however, I doubt whether it is wise to use the Raspberry Pi
board itself for building a whole distro :) (well, as a last resort I'd do
even that).

Thanks!

--
Croco

software raid with device busy status

Owl encrypted / and tcplay

Hi:

Is there a way to encrypt Owl / with aes-xts-plain64 which can be
remotely authenticated remotely for decryption (like using dropbear in
initrd or mandos server-client mechanism in debian using hooks)?

Also interested in tcplay, but would be nice to know to securely
integrated with Owl 3.0.

Thanks!

openvz kernel

Hi:

In Owl 3.0 there is 2.6.18-348.3.1.el5.028stab106.2 kernel and vzctl
is 3.0.23. This has some limitations like vswap (--ram and --swap
parameters) which is not available below 3.0.30
(http://wiki.openvz.org/Vswap).

Is it ideal to update to RHEL6 kernels from openvz? If yes, how is
that accomplished in Owl? Is there a specific way to do so?

Thanks!

Owl-current and 3.0-stable 2013/04/08 snapshot

Hi,

A few days ago, we've released new snapshots of Owl-current and Owl
3.0-stable, as usual including ISO images, OpenVZ container templates,
binary packages for i686 and x86_64, and full sources:

http://www.openwall.com/Owl/

The Linux kernel has been rebased on the latest from OpenVZ's
RHEL5-based branch (RHEL 5.9-based currently), thereby fixing a number
of vulnerabilities including the PTRACE_SETREGS vs. process death race
condition (CVE-2013-0871), which could allow for a local root compromise
and OpenVZ container escape.  (However, the risk probability might have
been low due to the race being difficult to win.)

GnuPG has been updated to 1.4.13, which fixes a memory corruption bug
(CVE-2012-6085).  The bug allowed an attacker to crash gpg(1) and
corrupt the public keyring database file.  Arbitrary code execution was
not possible because the attacker cannot control the corrupted data.
The corrupted data is stored in the keyring file, so the DoS effect is
persistent, but the keyring can be manually restored by recovering from
the pubring.gpg~ backup file (which is created by gpg(1) itself).

In Owl 3.0-stable, both of the above changes have been merged (although
the kernel has fewer features enabled than Owl-current's), and
additionally the earlier xinetd security update from Owl-current and
some glibc bugfixes have been merged.  Owl 3.0-stable's kernel is now
compressed with Zopfli (pigz -11) instead of gzip -9.

More detail is available in the change logs:

http://www.openwall.com/Owl/CHANGES-current.shtml
http://www.openwall.com/Owl/CHANGES-3.0-stable.shtml

There's one known regression in Owl-current as compared to 3.0-stable:
the strace program fails to work against 32-bit x86 program binaries.
Indeed, we're going to correct this.

This Owl-current update is a lot more conservative than what we've been
planning to have by this date.  Frankly, progress has been slow.  We did
prepare an experimental update of Owl to RHEL6'ish kernels, and it was
in fact committed, but in light of severe security issues discovered in
the Linux kernel we chose to temporarily revert the major update and to
provide the security fixes on top of a more stable system first.

Alexander

Manage network interfaces

/etc/inittab exisits, yet reports none!

Hi,

I installed Owl-3_0-stable version on a separate /boot usb stick and /
in a hdd. After installation, boot halts reporting 'INIT: no inittab
file found \n Enter run level:' I entered 3 and it errored back:
'INIT: no more processes left in this run level'.

I tried to boot live iso in rescue mode, but reported kernel panic. So
I booted again in safe mode from the live iso image. Checked
/etc/inittab in the installed /etc (I allocated a separate partition
for /etc) directory and the file /etc/inittab duly exists.

What could be the problem?

/zenny

virtualization in openwall

Zdrasdsviche!

Belated happy new year 2013 to all Owl team!

BTW, I would like to know whether anyone has experience with
virtualization like xen or kvm with xen in Owl?

The reason I am asking is because a Polish distro Qubes-OS claims it
is secured. And I could not find anything more secured than Owl. If
xen or kvm with qemu be integrated to Owl, how will it scale in terms
of performance and security?

Any inputs would be appreciated! Spacibo bolshoi!

/zenny

Re: Owl kickstart - Owl-current (VirtualBox Guest Additions)

Owl2 VirtualBox Guest additions

OWL development snapshots on an ALIX 2d2 board