popa3d-users - Re: inet.h error?

Openwall Project		/home Owl JtR Pro crypt pam_passwdqc tcb phpass scanlogd popa3d msulogin / Linux BIND / advisories presentations / services donations / wordlists passwords / news community lists wiki CVSweb mirrors signatures
bringing security into open environments

Password Recovery Resources on the Net

[<prev] [next>] [<thread-prev] [thread-next>] [month] [year] [list]

Date: Thu, 7 Aug 2003 00:37:28 -0500
From: Asenchi <asenchi@...nchi.com>
To: popa3d-users@...ts.openwall.com
Subject: Re: inet.h error?

Hello,
On Wednesday, Aug 6, 2003, at 18:28 US/East-Indiana, Solar Designer 
wrote:

> Hi,
>
> On Wed, Aug 06, 2003 at 03:55:09PM -0500, Asenchi wrote:
>> I am using OpenBSD 3.3 with a GENERIC kernel.  Today I decided to try
>> popa3d as a POP3 solution.
>
> OK.
>
> You know that OpenBSD includes popa3d, right?  Did that version or the
> way it's built not satisfy you and why?
>
 From my understanding, a package still needed to be installed.  I don't 
know why this is my understanding, but... I think what happened was I 
couldn't get it to start up using the version in inetd.conf, so i 
decided to install it.

>> After I tar -zxvf the latest stable release (0.6.3) I make my changes
>> to params.h and the Makefile.  I then try to do a 'make' and get this
>> error:
>>
>> $ make
>> gcc -c -Wall -02 -fomit-frame-pointer virtual.c
>> In file included from virtual.c:25:
>> /usr/include/arpa/inet.h:89: syntax error before 'inet_nsap_addr'
>> /usr/include/arpa/inet.h:89: syntax error before 'u_char'
>> /usr/include/arpa/inet.h:89: warning: data definition has no type or
>> storage class
>> /usr/include/arpa/inet.h:90: syntax error before '*'
>> *** Error code 1
>>
>> Stop in /home/asenchi/popa3d/popa3d-0.6.3.
>> $
>>
>> I have looked at the code, but I am not very good at C so I didn't 
>> want
>> to touch it.  Do any of you have an idea what could be the problem?
>
> 1. You have enabled POP_VIRTUAL.  Do you really need it?  If not,
> disable it and you'll avoid this problem.

I don't.  Just some tweaking, probably should have checked this 
before...

> 2. There really appears to be a bug either in that header file or in
> the way I'm using it with the #define's (_XOPEN_SOURCE and so on).
> Camiel, -- if you're reading this, could you handle this report within
> the OpenBSD team as appropriate?  I'd appreciate being CC'd on any
> discussions, especially if there's anything to correct on my part.

If this is indeed a bug, hopefully it helps that i posted this, maybe I 
found something worthwhile?

>> I have tried this both as user and root.
>
> You shouldn't be building source code as root.  But this is not
> related to the problem you're seeing.

yeah I know.  I just wanted to make sure, so that I don't get a RTFM 
you DUMB ASS :)

> -- 
> /sd
>
>
asenchi