<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div>I just installed Ubuntu 8.04, and now I notice that "configure"<br>seems to fail on any package at all (for instance, in this case<br>it's Wireshark 1.0.2)<br><br>root@bongo:/usr/local/src/wireshark-1.0.2# ./configure <br>...<br>checking for gcc... gcc<br>checking for C compiler default output file name... <br>configure: error: C compiler cannot create executables<br>See `config.log' for more details.<br>root@bongo:/usr/local/src/wireshark-1.0.2# <br><br>The only error I see in 'config.log' is this:<br>gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)<br>configure:3123: $? = 0<br>configure:3130: gcc -V >&5<br>gcc: '-V' option must have argument<br>configure:3133: $? = 1<br>configure:3156: checking for C compiler default output file name<br>configure:3183: gcc conftest.c
>&5<br>/usr/bin/ld: crt1.o: No such file: No such file or directory<br>collect2: ld returned 1 exit status<br><br>Did something change regarding the v/V options with gcc in this <br>version? I don't reckon that 'configure' is something that I could<br>change (successfully) and I don't have any other systems to<br>compare previous versions. <br><br>Any and all suggestions welcome - Ed<br><br><br></div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">----- Original Message ----<br>From: Sean Wilkerson <sean@seanandheather.com><br>Cc: calug@unknownlamer.org<br>Sent: Thursday, August 14, 2008 11:13:19 AM<br>Subject: Re: [CALUG] My EeePC 1000 Review<br><br>
Dave,<br>Informative review, thanks. I am thinking about an EeePC in the next <br>few months and was deciding which to get. This helps.<br><br>*,<br><br>I think there is something else here that other responses missed:<br><br>> If you know your security, then you should know that by turning off <br>> Samba, Print sharing, NFS, you would have in effect turned off the so <br>> called bad services, which is what a Firewall does.<br><br>Why on earth are we equating the value of a firewall to closing <br>services? First, firewalls don't turn-off anything and this is VERY <br>important to remember (defense-in-depth anyone?).<br><br>Second, a firewall does a lot more for me than to ensure I remembered to <br>close and lock the door. I may just have tcp/22 (avail only from <br>specific sources) open, or maybe no port at all, but I still want <br>netfilter available in the kernel and iptables to manage it.<br><br>Here are a few
things that a FW might do other than mitigate the <br>exposure of services that the admin (or the distro vendor) forgot to close:<br>- Provide detailed logs on activity regarding closed ports<br>- Provide you a dynamic blocking platform (see fail2ban or fwsnort<br>- Provide TCPOPTS/IPOPTS set in incoming packets allowing for off-line <br>analysis to determine OS/platform and client which generated incoming <br>packets<br>- Hidden-door VPN or other open port (see fwknop)<br>- mangling of outbound packets (for good reason of course)<br>- Managing the net between your VMs YOUR way, not their's<br>- Take a look at Michael Rash's book "Linux Firewalls" <br><a href="http://www.cipherdyne.org/LinuxFirewalls/" target="_blank">http://www.cipherdyne.org/LinuxFirewalls/</a> if you want more ideas (So <br>worth the read)<br><br>I think this is a critical flaw. It would be no problem if <br>netfilter/iptables was available yet with no default config, but to
not <br>make it available at all is short-sighted.<br><br>That the platform's chief purpose is a non-primary computing system, <br>only accentuates the need for a firewall IMHO. A primary computing <br>system will typically be used in a consistent fashion (work system, home <br>system, etc.) but an Ultra-Portable Laptop can be used....anywhere quite <br>easily. <br><br><br>Sean<br><br>_______________________________________________<br>CALUG mailing list<br><a ymailto="mailto:CALUG@unknownlamer.org" href="mailto:CALUG@unknownlamer.org">CALUG@unknownlamer.org</a><br><a href="http://lists.unknownlamer.org/listinfo/calug" target="_blank">http://lists.unknownlamer.org/listinfo/calug</a><br></div></div></div><br>
</body></html>