Report to Sender
Incident Information:- Database: d:/lotus/domino/data/mail1.box Originator: [EMAIL PROTECTED] Recipients: [EMAIL PROTECTED] Subject:Information Date/Time: 03/05/2004 05:55:26 AM The file attachment part1.cmd you sent to the recipients listed above was infected with the W32/[EMAIL PROTECTED] virus and was successfully cleaned.
Re: compiling wget 1.9 with ssl
On Fri, 5 Mar 2004, Hrvoje Niksic wrote: > Maybe configure should try to detect running under Red Hat 9 and kludge in > the kerberos path for that broken system. I've done exactly this hack once already for curl. It doesn't have to be _that_ kludgy, since you can invoke "pkg-config" to query what link and compiler options to use when building with OpenSSL, and then it'll include the path to the kerberos' headers. Feel free to use snippets from this: dnl Detect the pkg-config tool, as it may have extra info about the dnl openssl installation we can use. I *believe* this is what we are dnl expected to do on really recent Redhat Linux hosts. AC_PATH_PROG( PKGCONFIG, pkg-config, no, $PATH:/usr/bin:/usr/local/bin) if test "$PKGCONFIG" != "no" ; then AC_MSG_CHECKING([for OpenSSL options using pkg-config]) $PKGCONFIG --exists openssl SSL_EXISTS=$? if test "$SSL_EXISTS" -eq "0"; then SSL_LIBS=`$PKGCONFIG --libs-only-l openssl 2>/dev/null` SSL_LDFLAGS=`$PKGCONFIG --libs-only-L openssl 2>/dev/null` SSL_CPPFLAGS=`$PKGCONFIG --cflags-only-I openssl 2>/dev/null` LIBS="$LIBS $SSL_LIBS" CPPFLAGS="$CPPFLAGS $SSL_CPPFLAGS" LDFLAGS="$LDFLAGS $SSL_LDFLAGS" AC_MSG_RESULT([yes]) else AC_MSG_RESULT([no]) fi fi -- -=- Daniel Stenberg -=- http://daniel.haxx.se -=- ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol
Re: compiling wget 1.9 with ssl
Jamie Zawinski <[EMAIL PROTECTED]> writes: > - that pulled in krb5-devel (good so far) > - then I had to do ./configure --with-ssl=/usr/kerberos > because it needs /usr/kerberos/include/krb5.h I had the same problem on Red Hat 9, and solved it the same way. I think that was actually a bug which they fixed, because after upgrading some packages, compiling Wget with SSL worked out of the box. If this is true, the problem should not occur in Fedora. Maybe configure should try to detect running under Red Hat 9 and kludge in the kerberos path for that broken system.
Re: Bug in wget: cannot request urls with double-slash in the query string
D Richard Felker III <[EMAIL PROTECTED]> writes: >> The request log shows that the slashes are apparently respected. > > I retried a test case and found the same thing -- the slashes were > respected. OK. > Then I remembered that I was using -i. Wget seems to work fine with > the url on the command line; the bug only happens when the url is > passed in with: > > cat < http://... > EOF But I cannot repeat that, either. As long as the consecutive slashes are in the query string, they're not stripped. > Using this method is necessary since it is the ONLY secure way I > know of to do a password-protected http request from a shell script. Yes, that is the best way to do it.
compiling wget 1.9 with ssl
It took me a while to figure out how to build wget 1.9 with SSL on my stock Red Hat 9 system: - install openssl-devel (this was fairly obvious) - that pulled in krb5-devel (good so far) - then I had to do ./configure --with-ssl=/usr/kerberos because it needs /usr/kerberos/include/krb5.h So, it'd be nice if the configure script considered /usr/kerberos/ to be a "standard" default -I path, since that seems to be where Red Hat puts things. -- Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/ [EMAIL PROTECTED] http://www.dnalounge.com/
