> On Sat, Jun 18, 2005 at 01:19:37PM +0200, [EMAIL PROTECTED] > wrote: >> Nobody cares for the ettercap port and nobody updates it. >> And I noticed today again that the port builds fine but that the >> software >> WONT run on i386/amd64... >> >> Nothings changed for nearly a year... >> But now ettercap wont even start and isn't even useable in the >> Console-Mode. > > ettercap-NG-0.7.* versions need a recent hype libpcap, and it's painful > to let them work with our libpcap (pcap_if_t type, etc..). > > -- > > Alexandre Anriot > [EMAIL PROTECTED]
Yes I know Alexandre.. But a NON-Working ettercap is also "useless". OpenBSD provide a high-secure OS but not even 1 tool to test a existing enviroment. And some tools provided by the ports (like ettercap) just suck or don't work at all... :-/ I think that's a littlebit crazy because I can't even set some strong PW rules easy.... I know that the OpenBSD-Developers don#t have time to "code" such a tool by themself but tcpdump is a good example how tools can be included into the OS and maintained by the developers. Btw: I think OpenBSD can be more then just a FW or just a "simple" FTPd... But today you'll need tools wich do some "special" jobs (e.g. for cracking my own WEP-Key just to get a clue how long it would need if somebody else (the bad guy) would try it). But I'm sure I get the same answers like the answer I got in the past. "XYZ isn't needed..." or "The implementation sucks because %any_company designed the &any_thing ugly" (e.g. ACPI..). I wont start a flame-war I just noticed that some things get include I mentioned 2 years ago (and I got some very bad mails just for my request..). Kind regards, Sebastian
