Asenchi | 6 Aug 2003 22:55

inet.h error?

Hello,

I am using OpenBSD 3.3 with a GENERIC kernel.  Today I decided to try 
popa3d as a POP3 solution.

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?

I have tried this both as user and root.

Thank you,

asenchi
(Continue reading)

jhernandez | 6 Aug 2003 22:50
Picon
Picon

Re: inet.h error?

I am using popa3d in my free BDS box and is working good. As far as I
remember I did not had to make changes to params.h nor to the makefile. I
will think that the error that you are facing is caused by the changes you
made to the files.

Jose Hernandez
Network Specialist
jhernandez@...
MCSE, MCSA
----- Original Message ----- 
From: "Asenchi" <asenchi@...>
To: <popa3d-users@...>
Sent: Wednesday, August 06, 2003 3:55 PM
Subject: inet.h error?

> Hello,
>
> I am using OpenBSD 3.3 with a GENERIC kernel.  Today I decided to try
> popa3d as a POP3 solution.
>
> 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
(Continue reading)

Solar Designer | 7 Aug 2003 01:28
Favicon

Re: inet.h error?

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?

> 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?
(Continue reading)

Michael Coulter | 7 Aug 2003 02:32
Picon

Re: inet.h error?

On Thu, Aug 07, 2003 at 03:28:57AM +0400, Solar Designer wrote:

> 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.

In the in-tree version of virtual.c are these two lines:

#define u_char unsigned char
#define u_int unsigned int

This is from sys/types.h

#if !defined(_POSIX_SOURCE) && !defined(_XOPEN_SOURCE)
typedef unsigned char   u_char;
typedef unsigned short  u_short;
typedef unsigned int    u_int;
typedef unsigned long   u_long;

typedef unsigned char   unchar;         /* Sys V compatibility */
typedef unsigned short  ushort;         /* Sys V compatibility */
typedef unsigned int    uint;           /* Sys V compatibility */
typedef unsigned long   ulong;          /* Sys V compatibility */
#endif

Adding the two defines to virtual.c from 0.6.3 and changing
from AUTH_SHADOW to AUTH_PASSWD is enough to get it compiled cleanly
(aside from the sprintf() lecturing)
(Continue reading)

Solar Designer | 7 Aug 2003 03:08
Favicon

Re: inet.h error?

On Thu, Aug 07, 2003 at 12:32:57AM +0000, Michael Coulter wrote:
> On Thu, Aug 07, 2003 at 03:28:57AM +0400, Solar Designer wrote:
> 
> > 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.
> 
> In the in-tree version of virtual.c are these two lines:
> 
> #define u_char unsigned char
> #define u_int unsigned int
> 
> This is from sys/types.h
> 
> #if !defined(_POSIX_SOURCE) && !defined(_XOPEN_SOURCE)
> typedef unsigned char   u_char;
> typedef unsigned short  u_short;
> typedef unsigned int    u_int;
> typedef unsigned long   u_long;
> 
> typedef unsigned char   unchar;         /* Sys V compatibility */
> typedef unsigned short  ushort;         /* Sys V compatibility */
> typedef unsigned int    uint;           /* Sys V compatibility */
> typedef unsigned long   ulong;          /* Sys V compatibility */
> #endif

Thanks.

(Continue reading)

Asenchi | 7 Aug 2003 07:37

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
(Continue reading)

Solar Designer | 8 Aug 2003 00:12
Favicon

Re: inet.h error?

On Thu, Aug 07, 2003 at 12:37:28AM -0500, Asenchi wrote:
> On Wednesday, Aug 6, 2003, at 18:28 US/East-Indiana, Solar Designer wrote:
> >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.

> >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.

You didn't need to unless you require a non-standard configuration.  I
don't know why the included popa3d didn't work for you.

> >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?

Yes, you did.  Thank you. :-)

--

-- 
/sd
(Continue reading)

Asenchi | 8 Aug 2003 17:37

Re: inet.h error?

>
> You didn't need to unless you require a non-standard configuration.  I
> don't know why the included popa3d didn't work for you.

Just a follow up, it is working wonderfully now.

Thanks.

Daniel | 12 Aug 2003 07:31

Built In SSL Support

Hi,

Are there any plans to progress popa3d with inbuilt support for SSL?

I don't want a stunnel solution, or an VPN type solution.
I'm looking for a simple secure solution that has inbuilt SSL support.

Plain text transmission of passwords seems a very old
concept, not to mention insecure. And most modern email
clients support (or should support) SSL.

OpenBSD ships with popa3d by default. It seems abit
strange to me that an o/s that boasts about it's security features,
ships a pop3 daemon that doesn't provide SSL support out of the box.

I recognise the security features of popa3d in regards to process execution
etc. but I think inbuilt support for SSL is also crucial.

hotdiggedydog (Daniel)
[ www.thebsdwindow.com ]
[ www.privatecage.com ]

Michael Coulter | 12 Aug 2003 19:13
Picon

Re: Built In SSL Support


On Tue, Aug 12, 2003 at 03:31:26PM +1000, Daniel wrote:

> I don't want a stunnel solution, or an VPN type solution.

Why not ? Using either of these solutions simplify the job of
popa3d considerably. Stunnel chroots and drops privileges. 
Popa3d employs privilege separation techniques, this means
a mininimum amount of code is run with privileges. This is
the way I want applications on my machines to run.

> etc. but I think inbuilt support for SSL is also crucial.

Crucial ? I've been running pop3 + ssl using stunnel for months
now on quite a few machines. It doesn't seem like I'm missing
anything crucial.


Gmane