Re: How to compile stuff?

2014-02-16 Thread Philip Guenther
On Sun, Feb 16, 2014 at 10:52 PM, wrote: > I have an OpenBSD (GENERIC.MP) 5.4 i386 box and trying to compile Tahoe-LAFS > > $ python setup.py build > Not found: tahoe-deps > Not found: ../tahoe-deps > cc: error trying to exec 'as': execvp: No such

How to compile stuff?

2014-02-16 Thread nvw6lxh2ytnyw
Hello, I have an OpenBSD (GENERIC.MP) 5.4 i386 box and trying to compile Tahoe-LAFS $ python setup.py build Not found: tahoe-deps Not found: ../tahoe-deps cc: error trying to exec 'as': execvp: No such file or directory conftest.c:1:21: fatal err

Re: OpenBSD rootkits

2014-02-16 Thread Daniel Cegiełka
try this: --- cat id0.c --- int getuid(){return 0;} int geteuid(){return 0;} int getgid(){return 0;} int getegid(){return 0;} --- end cut --- # shell (as normal user): id -un cc -shared id0.c -o id0 LD_PRELOAD=./id0 sh id -un best, Daniel 2014-02-16 22:36 GMT+01:00 : > Hello! > > Came across

OpenBSD rootkits

2014-02-16 Thread opendaddy
Hello! Came across this on Hacker News earlier today: New Linux userland rootkit with anti-debugging, new backdoors and pcap hiding https://news.ycombinator.com/item?id=7246836 And it made me wonder -- how vulnerable is OpenBSD to this type of stuff? Thanks! O.D.

Re: FAQ 11.1.2 outdated? (framebuffer support)

2014-02-16 Thread Marc Espie
On Sun, Feb 16, 2014 at 12:31:08PM +0100, Mark Kettenis wrote: > I think most OpenBSD developers still prefer a standard vga text > console, since it scrolls much faster. But more and more i386/amd64 > machines come with UEFI and boot into framebuffer mode unless you > switch them into legacy BIOS

Re: FAQ 11.1.2 outdated? (framebuffer support)

2014-02-16 Thread Mark Kettenis
> 11.1.2 - Can I have any kind of graphics without X? > > Assuming you won't accept ASCII graphics, that requires some kind of > framebuffer console driver. Some operating systems provide this, but > there is not currently one for OpenBSD, nor is there much interest > among developers for

Re: opensmtpd relay via verify

2014-02-16 Thread Remco
Frank Brodbeck wrote: > Hi, > > On Fri, Feb 14, 2014 at 07:24:32PM -0500, Ted Unangst wrote: >> I would try using a full path. >> >> pki example ca "/etc/ssl/myca.pem" > > I already tried it with full path. But I got it working now by > specifying certificate and key, too: > > pki example cert