Don't know if this is too late but I submitted a fairly recent port to
the group, don't know why they didn't pick it up.
This is R10B-3, the current release is R10B-7, maybe I'll pick that up
and do it in a little while. This port is WAY better then what is in
the tree and I'm sure it is way more secure as the one in the tree is
YEARS and revisions old.
A Port of R10B-3 that will compile and install on OpenBSD -current
(3.7) is available for general
download at :
http://www.snortdroid.com/DroidOS/erlang_otp_R10B-3_port.tgz
This port is several revisions past what is currently in the OpenBSD
/usr/ports tree.
This port has only been changed to allow it to properly build under
OpenBSD current (3.7)
IT HAS NOT been audited with regards to security. In particular there
are numerous uses
of sprintf and vsprintf in the code. As a consequence, be very
careful using Erlang in situations
where the security of the system could be compromised by un guarded
input.
I am offering this to the community so that people who use Erlang have
a modern version to
run on OpenBSD. I am currently working on a port of R10B-4 which will
be more in alignment
with the security standards that OpenBSD is known for. Until that
release, ( a few weeks out) please use
this version as a "beta", and realize that there are a lot of
potential security holes. I don't know if this will
become the "official" Erlang port for OpenBSD. I think the OpenBSD
would like the security issues cleaned
up a bit. And I'm hoping they will be considering my port of R10B-4
for potential inclusion into their ports
tree.
cheers,
Rick Pettit wrote:
On Wed, Jun 15, 2005 at 05:18:01PM +0200, Jonathan Schleifer wrote:
Hi!
The Erlang port is broken on x86. erl simply segfaults. Running gdb
returns this:
Program received signal SIGSEGV, Segmentation fault.
0x0585dd36 in vsprintf () from /usr/lib/libc.so.37.0
If someone could debug that further or mark the port broken?
Unfortunately, the port is so old it is next to useless. I suggest you grab the
source from http://www.erlang.org and build/install by hand.
You will have to patch one file, though:
otp_src_R10B-5/lib/os_mon/c_src/memsup.c
the patch is:
98d97
< #include <vm/vm_param.h>
and once written to memsup.c.patch can be applied with:
prompt> patch otp_src_R10B-5/lib/os_mon/c_src/memsup.c memsup.c.patch
Another thing I had to do was to run configure like so (to get SSL):
prompt> ./configure --with-ssl=/usr/include/openssl
before running make. The problem you will then encounter during the build has
to do with autotools confusion as to where the openssl command is found.
Let the build fail in certs examples under ssl, then replace the value of
OPENSSL_CMD in otp_src_R10B-5/lib/ssl/examples/certs/i386-unknown-openbsd3.7
with the following:
OPENSSL_CMD = /usr/sbin/openssl
Save the file and rerun 'gmake' from the top-level otp_src_R10B-5 and you
should be ok (minus J-Interface which I don't bother with on OpenBSD).
I should add that I am running a recent OpenBSD 3.7 snapshot, though this
procedure has worked since the days of R9C-0 on OpenBSD 3.6.
Let me know if you still have problems. I have meant to work on the port for
the longest time, but I have been too busy (and too lame) to bother.
HTH/HAND,
-Rick
