Re: latest MySql?
On Tue, Jan 12, 2010 at 11:09 PM, Robert Huff roberth...@rcn.com wrote: MySql-6.* is no longer in the ports tree. Things depend on it. Is there information on what happened and what the alternatives are? PostgreSQL? :-) For now MySQL 6.x development has been ceased for now [1] and new development happens on 5.5 series. You may need to consult their website to get a more useful big picture stuff. http://dev.mysql.com/doc/refman/6.0/en/index.html Cheers, -- Xin LI delp...@delphij.net http://www.delphij.net ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: devel/boost-jam doesn't install tools/build/v2 files
2010/1/12 cpghost cpgh...@cordula.ws How about adding boost_build as an option to devel/boost-all? Nice idea. Since I'm gaining some experience with the Boost.Build this would be possible. The only remaining thing is to discuss this with the current maintainer of boost_build (it's not me). Alexander Churanov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Now OK (Re: cvs commit: ports/net/mDNSResponder Makefile)
net/mDNSResponder, which was previously failing is OK after this commit. Thanks for fixing it! A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- QAT - your friendly neighborhood Daemon, preparing a heck of an error trapping system: - HMC and EOI? - Halt, Melt and Catch fire or Execute Operator Immediately. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
INDEX build failed for 6.x
INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found Done. make_index: vboxgtk-0.5.0: no entry for /usr/ports/emulators/virtualbox Committers on the hook: beat bland dinoex jadawin matusita nemoliu wen Most recent CVS update was: U MOVED U UPDATING U audio/p5-Audio-Scan/Makefile U audio/p5-Audio-Scan/distinfo U databases/p5-DBIx-Class-FrozenColumns/Makefile U databases/p5-DBIx-Class-FrozenColumns/distinfo U devel/oniguruma5/Makefile U devel/oniguruma5/distinfo U devel/p5-Dir-Project/Makefile U devel/p5-Dir-Project/distinfo U dns/Makefile U dns/autotrust/Makefile U dns/autotrust/distinfo U dns/autotrust/pkg-descr U emulators/Makefile U emulators/virtualbox-ose/Makefile U emulators/virtualbox-ose/distinfo U emulators/virtualbox-ose/pkg-descr U emulators/virtualbox-ose/pkg-message U emulators/virtualbox-ose/pkg-plist U emulators/virtualbox-ose/files/patch-Config.kmk U emulators/virtualbox-ose/files/patch-configure U emulators/virtualbox-ose/files/patch-src-VBox-Additions-x11-VBoxClient-Makefile.kmk U emulators/virtualbox-ose/files/patch-src-VBox-Devices-Audio-audio.c U emulators/virtualbox-ose/files/patch-src-VBox-Devices-Makefile.kmk U emulators/virtualbox-ose/files/patch-src-VBox-Frontends-VBoxManage-VBoxInternalManage.cpp U emulators/virtualbox-ose/files/patch-src-VBox-Frontends-VBoxManage-VBoxManageHelp.cpp U emulators/virtualbox-ose/files/patch-src-VBox-Frontends-VBoxManage-VBoxManageModifyVM.cpp U emulators/virtualbox-ose/files/patch-src-VBox-HostDrivers-Makefile.kmk U emulators/virtualbox-ose/files/patch-src-VBox-HostDrivers-Support-SUPR3HardenedMain.cpp U emulators/virtualbox-ose/files/patch-src-VBox-Installer-Makefile.kmk U emulators/virtualbox-ose/files/patch-src-VBox-Main-AudioAdapterImpl.cpp U emulators/virtualbox-ose/files/patch-src-VBox-Main-ConsoleImpl.cpp U emulators/virtualbox-ose/files/patch-src-VBox-Main-ConsoleImpl2.cpp U emulators/virtualbox-ose/files/patch-src-VBox-Main-include-ConsoleImpl.h U emulators/virtualbox-ose/files/patch-src-VBox-Runtime-VBox-log-vbox.cpp U emulators/virtualbox-ose/files/patch-src-VBox-Runtime-r3-freebsd-rtProcInitExePath-freebsd.cpp U emulators/virtualbox-ose/files/patch-src-settings-vm-VBoxVMSettingsAudio.cpp U emulators/virtualbox-ose/files/pkg-install.in U emulators/virtualbox-ose-additions/Makefile U emulators/virtualbox-ose-additions/distinfo U emulators/virtualbox-ose-additions/pkg-descr U emulators/virtualbox-ose-additions/pkg-plist U emulators/virtualbox-ose-additions/files/patch-src-VBox-Additions-freebsd-Makefile.kmk U emulators/virtualbox-ose-additions/files/vboxguest.in U emulators/virtualbox-ose-kmod/Makefile U emulators/virtualbox-ose-kmod/distinfo U emulators/virtualbox-ose-kmod/pkg-descr U emulators/virtualbox-ose-kmod/pkg-plist U emulators/virtualbox-ose-kmod/files/patch-src-VBox-HostDrivers-VBoxNetAdp-freebsd-VBoxNetAdp-freebsd.c U emulators/virtualbox-ose-kmod/files/patch-src-VBox-HostDrivers-VBoxNetFlt-freebsd-VBoxNetFlt-freebsd.c U emulators/virtualbox-ose-kmod/files/patch-src-VBox-Runtime-r0drv-freebsd-spinlock-r0drv-freebsd.c U emulators/virtualbox-ose-kmod/files/vboxnet.in U japanese/dbskkd-cdb/Makefile U japanese/dbskkd-cdb/files/pkg-message.in U net/mDNSResponder/Makefile U sysutils/ldap-account-manager/Makefile U textproc/apache-solr/Makefile U textproc/apache-solr/distinfo U textproc/apache-solr/pkg-plist U www/p5-HTTP-Request-AsCGI/Makefile U www/p5-HTTP-Request-AsCGI/distinfo U www/phpmyfaq/Makefile U www/phpmyfaq/distinfo U www/phpmyfaq/pkg-plist U www/yabb/Makefile U www/yabb/distinfo U www/yabb/pkg-plist U www/yabb/files/checksum.sha256 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
net-mgmt/p0f -- FreeBSD 8 not recognised
Hi, 'p0f - passive os fingerprinting utility, version 2.0.8' does not recognize new FreeBSD version 8: UNKNOWN [65535:64:1:60:M1460,N,W3,S,T:.:?:?] Up info is broken too (but that has been always as far as I remember). BR, M. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
security/openssl BROKEN, DEPRECATED, and EXPIRED?
http://docs.freebsd.org/cgi/mid.cgi?201001121543.o0CFhqWv076278 What happened? I haven't been able to find any discussion about this on either freebsd-ports, freebsd-ports-bugs, or freebsd-security. There doesn't seem to be a PR, either. Am I just being overly sensitive or does this present a POLA problem? My ports tree is up to date, but OpenSSL can't be upgraded, and neither can anything that depends on it. If a port is going to be deprecated, isn't it common to recommend a replacement? If 0.9.8l_1 is so horribly broken, would it have been better to drop back to the 'last known good' version? I haven't had a problem with 0.9.8l, that I know of. -- John D. Trix Farrar, CCNA __\\|//__ Basement.NET t...@basement.net (` o-o ') http://www.basement.net/ ---ooO-(_)-Ooo-- GPG Key Fprint: 525F DBA7 1A62 E4C4 E642 DF95 384B B851 3CEF C10A pgpwi5ImAA97z.pgp Description: PGP signature
Re: security/openssl BROKEN, DEPRECATED, and EXPIRED?
Hi Trix, http://docs.freebsd.org/cgi/mid.cgi?201001121543.o0CFhqWv076278 What happened? I haven't been able to find any discussion about this on either freebsd-ports, freebsd-ports-bugs, or freebsd-security. There doesn't seem to be a PR, either. I'm also wondering and waiting for an answer... http://docs.freebsd.org/cgi/getmsg.cgi?fetch=199172+0+current/freebsd-ports ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: latest MySql?
On Wed, 13 Jan 2010 02:09:24 -0500 Robert Huff roberth...@rcn.com articulated: MySql-6.* is no longer in the ports tree. Things depend on it. Is there information on what happened and what the alternatives are? I have MySQL-6 installed. I have several applications that depend on it. What would be the recommended method to replace it with the latest stable release of MySQL? I see that 'portupgrade' offers quite a few options. Would one of them work? I really do not want to have to rebuild all of my applications that depend on MySQL-6 if possible. Thank you! -- Carmel carmel...@hotmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Wanting to test video4bsd on todays cvsup and build but can't compile the pwcbsd port.
On Tue, Jan 12, 2010 at 11:59:26AM -0600, eculp wrote: I am running todays current complete with cvsup, build and install kernel and userland. # uname -a FreeBSD ed.local.net.mx 9.0-CURRENT FreeBSD 9.0-CURRENT #420: Tue Jan 12 07:13:52 CST 2010 r...@ed.local.net.mx:/usr/obj/usr/src/sys/ENCONTACTO i386 When I try to build the pwcbsd port I get: # make === Building for pwcbsd-1.4.1_6 make -f Makefile.kld all Warning: Object directory not changed from original /usr/ports/multimedia/pwcbsd/work/pwcbsd cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c pwc.c pwc.c:576: error: conflicting types for 'pwc_mmap' pwc.c:47: error: previous declaration of 'pwc_mmap' was here *** Error code 1 Stop in /usr/ports/multimedia/pwcbsd/work/pwcbsd. *** Error code 1 Stop in /usr/ports/multimedia/pwcbsd/work/pwcbsd. *** Error code 1 Stop in /usr/ports/multimedia/pwcbsd. Any help or suggestions appreciated. ed Did you enable this in OPTIONS? Enable mmap support (MAY CRASH YOUR SYSTEM) pgpyAQrHQ8TvM.pgp Description: PGP signature
Re: latest MySql?
On Tue, Jan 12, 2010 at 11:09 PM, Robert Huff roberth...@rcn.com wrote: MySql-6.* is no longer in the ports tree. Things depend on it. Is there information on what happened and what the alternatives are? PostgreSQL? :-) Probably not worth the effort, given my limited knowledge of these things. For now MySQL 6.x development has been ceased for now [1] and new development happens on 5.5 series. You may need to consult their website to get a more useful big picture stuff. http://dev.mysql.com/doc/refman/6.0/en/index.html That's what I wanted to see, Thanks to everyone who replied. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
INDEX now builds successfully on 6.x
___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
patch for security/openssh-portable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Request.
Attached is a patch against security/openssh-portable Makefile to remove
FreeBSD version and openssl version from its version reply string.
This changes it from its default reply to: SSH-2.0-OpenSSH_5.2p1
I would rather leave a prober guessing rather than giving the information
he needs to analyze a large number of hosts quickly.
- --
Wed Jan 13 08:06:17 2010
jhell
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (FreeBSD)
iQEcBAEBAgAGBQJLTceJAAoJEJBXh4mJ2FR+nrMH/jzYBXWyUXueQFrGYJnovskV
uSDme/bxd+iwVlsAyGPNK8Ub8oQC9725ohh0a8N6rcotENODPJyXRh0c9Gz5Kr3D
81opHf+qE6Z0Awhb3FcNYf/jCve4TOj5MZpzdy1peZ6pwJXA8BM7YbrP1+OFlQRN
yu3HuNg/LQyx0Rk0kVzVISLInpdmndC/OBtCjLwBuGb0Np/WYshuNOr739jOodcL
Odqa94apkhZpm8yI5+P6tQdf/RMOpn/PgB0MidLt3hH2Ayxpm903Wrs9p4d6xzc8
i2tZR8crdHCwjO5TRHITWmc273XZychU24P8HIC06GP56pG8jClFR1XSqBCpZMY=
=fKHX
-END PGP SIGNATURE Makefile.orig 2009-12-30 15:14:04.646162156 -0500
+++ Makefile2009-12-30 15:15:36.939692199 -0500
@@ -229,11 +229,9 @@
-e 's|%%RC_SCRIPT_NAME%%|${RC_SCRIPT_NAME}|' ${WRKSRC}/sshd.8
@${REINPLACE_CMD} -E -e 's|SSH_VERSION|TMP_SSH_VERSION|' \
-e 's|.*SSH_RELEASE.*||' ${WRKSRC}/version.h
- @${ECHO_CMD} '#define FREEBSD_PORT_VERSION FreeBSD-${PKGNAME}'
\
+ @${ECHO_CMD} '#define SSH_VERSION TMP_SSH_VERSION SSH_PORTABLE'
\
${WRKSRC}/version.h
- @${ECHO_CMD} '#define SSH_VERSION TMP_SSH_VERSION SSH_PORTABLE
FREEBSD_PORT_VERSION' \
- ${WRKSRC}/version.h
- @${ECHO_CMD} '#define SSH_RELEASE TMP_SSH_VERSION SSH_PORTABLE
FREEBSD_PORT_VERSION' \
+ @${ECHO_CMD} '#define SSH_RELEASE TMP_SSH_VERSION SSH_PORTABLE'
\
${WRKSRC}/version.h
.if defined(WITH_HPN)
@${REINPLACE_CMD} -e 's|TMP_SSH_VERSION SSH_PORTABLE|TMP_SSH_VERSION
SSH_PORTABLE SSH_HPN|' \
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: patch for security/openssh-portable
Probably you want VersionAddendum option in sshd_config?
Wed, Jan 13, 2010 at 08:14 -0500 jhell:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Request.
Attached is a patch against security/openssh-portable Makefile to remove
FreeBSD version and openssl version from its version reply string.
This changes it from its default reply to: SSH-2.0-OpenSSH_5.2p1
I would rather leave a prober guessing rather than giving the information
he needs to analyze a large number of hosts quickly.
- --
Wed Jan 13 08:06:17 2010
jhell
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (FreeBSD)
iQEcBAEBAgAGBQJLTceJAAoJEJBXh4mJ2FR+nrMH/jzYBXWyUXueQFrGYJnovskV
uSDme/bxd+iwVlsAyGPNK8Ub8oQC9725ohh0a8N6rcotENODPJyXRh0c9Gz5Kr3D
81opHf+qE6Z0Awhb3FcNYf/jCve4TOj5MZpzdy1peZ6pwJXA8BM7YbrP1+OFlQRN
yu3HuNg/LQyx0Rk0kVzVISLInpdmndC/OBtCjLwBuGb0Np/WYshuNOr739jOodcL
Odqa94apkhZpm8yI5+P6tQdf/RMOpn/PgB0MidLt3hH2Ayxpm903Wrs9p4d6xzc8
i2tZR8crdHCwjO5TRHITWmc273XZychU24P8HIC06GP56pG8jClFR1XSqBCpZMY=
=fKHX
-END PGP SIGNATURE-
--- Makefile.orig 2009-12-30 15:14:04.646162156 -0500
+++ Makefile 2009-12-30 15:15:36.939692199 -0500
@@ -229,11 +229,9 @@
-e 's|%%RC_SCRIPT_NAME%%|${RC_SCRIPT_NAME}|' ${WRKSRC}/sshd.8
@${REINPLACE_CMD} -E -e 's|SSH_VERSION|TMP_SSH_VERSION|' \
-e 's|.*SSH_RELEASE.*||' ${WRKSRC}/version.h
- @${ECHO_CMD} '#define FREEBSD_PORT_VERSION FreeBSD-${PKGNAME}'
\
+ @${ECHO_CMD} '#define SSH_VERSION TMP_SSH_VERSION SSH_PORTABLE'
\
${WRKSRC}/version.h
- @${ECHO_CMD} '#define SSH_VERSION TMP_SSH_VERSION SSH_PORTABLE
FREEBSD_PORT_VERSION' \
- ${WRKSRC}/version.h
- @${ECHO_CMD} '#define SSH_RELEASE TMP_SSH_VERSION SSH_PORTABLE
FREEBSD_PORT_VERSION' \
+ @${ECHO_CMD} '#define SSH_RELEASE TMP_SSH_VERSION SSH_PORTABLE'
\
${WRKSRC}/version.h
.if defined(WITH_HPN)
@${REINPLACE_CMD} -e 's|TMP_SSH_VERSION SSH_PORTABLE|TMP_SSH_VERSION
SSH_PORTABLE SSH_HPN|' \
--
Cheers
Denis Barov
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: security/openssl BROKEN, DEPRECATED, and EXPIRED?
On Wednesday 13 Jan 2010 12:00:23 Trix Farrar wrote: What happened? I haven't been able to find any discussion about this on either freebsd-ports, freebsd-ports-bugs, or freebsd-security. There doesn't seem to be a PR, either. Am I just being overly sensitive or does this present a POLA problem? My ports tree is up to date, but OpenSSL can't be upgraded, and neither can anything that depends on it. If you have a look at the last commit for Mk/bsd.openssl.mk, you'll see the libcrypto versions have been bumped, too. 8.0-RELEASE has 0.9.8k in base, but this .mk looks for libcrypto.so.7 and the version conditional has been dropped (not that it would have made any difference set to 800105) so dropping back to the version in the base system is going to be no help either. Even HEAD is still on 0.9.8k (libcrypto.so.6). http://bit.ly/7h5PpU (CVSweb) I suspect that there's an update on its way, although that doesn't help the rest of us using ports in the meantime. For now, I'd personally recommend to use a date=2010.01.12.15.42.00 definition in your ports supfile until all of this shakes out. As for POLA, I can think of nothing more astonishing than finding that my systems cannot, under any circumstances, meet the requirements of bsd.openssl.mk, thus breaking nearly everything important. That sort of snuck up on me without warning... -- Matt Dawson MTD15-RIPE m...@chronos.org.uk signature.asc Description: This is a digitally signed message part.
Re: patch for security/openssh-portable
On Wed, 13 Jan 2010 08:29, dindin@ wrote:
Probably you want VersionAddendum option in sshd_config?
No.
To my understanding and my last tests VersionAddendum and is only a
Addendum or did not work which spurred me to patch up the Makefile in the
first place.
Thanks for the thought though but I did not miss that option.
Wed, Jan 13, 2010 at 08:14 -0500 jhell:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Request.
Attached is a patch against security/openssh-portable Makefile to remove
FreeBSD version and openssl version from its version reply string.
This changes it from its default reply to: SSH-2.0-OpenSSH_5.2p1
I would rather leave a prober guessing rather than giving the information
he needs to analyze a large number of hosts quickly.
- --
Wed Jan 13 08:06:17 2010
jhell
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (FreeBSD)
iQEcBAEBAgAGBQJLTceJAAoJEJBXh4mJ2FR+nrMH/jzYBXWyUXueQFrGYJnovskV
uSDme/bxd+iwVlsAyGPNK8Ub8oQC9725ohh0a8N6rcotENODPJyXRh0c9Gz5Kr3D
81opHf+qE6Z0Awhb3FcNYf/jCve4TOj5MZpzdy1peZ6pwJXA8BM7YbrP1+OFlQRN
yu3HuNg/LQyx0Rk0kVzVISLInpdmndC/OBtCjLwBuGb0Np/WYshuNOr739jOodcL
Odqa94apkhZpm8yI5+P6tQdf/RMOpn/PgB0MidLt3hH2Ayxpm903Wrs9p4d6xzc8
i2tZR8crdHCwjO5TRHITWmc273XZychU24P8HIC06GP56pG8jClFR1XSqBCpZMY=
=fKHX
-END PGP SIGNATURE-
--- Makefile.orig 2009-12-30 15:14:04.646162156 -0500
+++ Makefile2009-12-30 15:15:36.939692199 -0500
@@ -229,11 +229,9 @@
-e 's|%%RC_SCRIPT_NAME%%|${RC_SCRIPT_NAME}|' ${WRKSRC}/sshd.8
@${REINPLACE_CMD} -E -e 's|SSH_VERSION|TMP_SSH_VERSION|' \
-e 's|.*SSH_RELEASE.*||' ${WRKSRC}/version.h
- @${ECHO_CMD} '#define FREEBSD_PORT_VERSION FreeBSD-${PKGNAME}'
\
+ @${ECHO_CMD} '#define SSH_VERSION TMP_SSH_VERSION SSH_PORTABLE'
\
${WRKSRC}/version.h
- @${ECHO_CMD} '#define SSH_VERSION TMP_SSH_VERSION SSH_PORTABLE
FREEBSD_PORT_VERSION' \
- ${WRKSRC}/version.h
- @${ECHO_CMD} '#define SSH_RELEASE TMP_SSH_VERSION SSH_PORTABLE
FREEBSD_PORT_VERSION' \
+ @${ECHO_CMD} '#define SSH_RELEASE TMP_SSH_VERSION SSH_PORTABLE'
\
${WRKSRC}/version.h
.if defined(WITH_HPN)
@${REINPLACE_CMD} -e 's|TMP_SSH_VERSION SSH_PORTABLE|TMP_SSH_VERSION
SSH_PORTABLE SSH_HPN|' \
--
Wed Jan 13 08:38:24 2010
It may not be able to take your machine down, but it can fill up your
Internet Pipe.
jhell
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: patch for security/openssh-portable
On Wed, 13 Jan 2010 08:40, jhell@ wrote: On Wed, 13 Jan 2010 08:29, dindin@ wrote: Probably you want VersionAddendum option in sshd_config? No. To my understanding and my last tests VersionAddendum and is only a Addendum or did not work which spurred me to patch up the Makefile in the first place. Thanks for the thought though but I did not miss that option. This is the output of the add VersionAddendum in the current ports openssh centel# service openssh restart /usr/local/etc/ssh/sshd_config: line 13: Bad configuration option: VersionAdendum /usr/local/etc/ssh/sshd_config: terminating, 1 bad configuration options ? So like I was saying It does not work that way. -- Wed Jan 13 08:43:08 2010 jhell ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: patch for security/openssh-portable
Probably you want VersionAddendum option in sshd_config? No. To my understanding and my last tests VersionAddendum and is only a Addendum or did not work which spurred me to patch up the Makefile in the first place. I put VersionAddendum into sshd_config (with nothing trailing behind it), and it works as expected: telnet foo 22 Trying 192.168.0.1... Connected to foo Escape character is '^]'. SSH-2.0-OpenSSH_5.2p1 I'm using OpenSSH from base, but it should be the same with ports. -- Denny Lin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: security/openssl BROKEN, DEPRECATED, and EXPIRED?
On Wednesday 13 Jan 2010 13:34:29 I wrote: I suspect that there's an update on its way, although that doesn't help the rest of us using ports in the meantime. For now, I'd personally recommend to use a date=2010.01.12.15.42.00 definition in your ports supfile until all of this shakes out. And, just like magic, it's fixed with a commit at 13:30 UTC. Disregard the above. -- Matt Dawson MTD15-RIPE m...@chronos.org.uk signature.asc Description: This is a digitally signed message part.
Re: patch for security/openssh-portable
centel# service openssh restart /usr/local/etc/ssh/sshd_config: line 13: Bad configuration option: VersionAdendum /usr/local/etc/ssh/sshd_config: terminating, 1 bad configuration options ? So like I was saying It does not work that way. Looks like you have a typo. It should be VersionAddendum, not VersionAdendum (missing a d). -- Denny Lin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: patch for security/openssh-portable
On Wed, 13 Jan 2010 08:45:36 -0500 jhell jh...@dataix.net wrote: J centel# service openssh restart J /usr/local/etc/ssh/sshd_config: line 13: Bad configuration option: J VersionAdendum ^ VersionAddendum J /usr/local/etc/ssh/sshd_config: terminating, 1 bad configuration J options J J ? So like I was saying It does not work that way. J J -- J J Wed Jan 13 08:43:08 2010 J J jhell -- wbr, tiger ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: patch for security/openssh-portable
Il 01/13/10 14:45, jhell ha scritto: centel# service openssh restart /usr/local/etc/ssh/sshd_config: line 13: Bad configuration option: VersionAdendum /usr/local/etc/ssh/sshd_config: terminating, 1 bad configuration options ? So like I was saying It does not work that way. You spelt it incorrectly. Throw another d in. bye av. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: patch for security/openssh-portable
On Wed, 13 Jan 2010 08:45, jhell@ wrote: On Wed, 13 Jan 2010 08:40, jhell@ wrote: On Wed, 13 Jan 2010 08:29, dindin@ wrote: Probably you want VersionAddendum option in sshd_config? No. To my understanding and my last tests VersionAddendum and is only a Addendum or did not work which spurred me to patch up the Makefile in the first place. Thanks for the thought though but I did not miss that option. This is the output of the add VersionAddendum in the current ports openssh centel# service openssh restart /usr/local/etc/ssh/sshd_config: line 13: Bad configuration option: VersionAdendum /usr/local/etc/ssh/sshd_config: terminating, 1 bad configuration options ? So like I was saying It does not work that way. My apologies. I did use VersionAddendum with the correct spelling but I pasted my first try at this with the incorrect spelling. With the correct spelling it still gives the above output. -- Wed Jan 13 08:49:14 2010 It may not be able to take your machine down, but it can fill up your Internet Pipe. jhell ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Wanting to test video4bsd on todays cvsup and build but can't compile the pwcbsd port.
Quoting Lars Engels lars.eng...@0x20.net: On Tue, Jan 12, 2010 at 11:59:26AM -0600, eculp wrote: I am running todays current complete with cvsup, build and install kernel and userland. # uname -a FreeBSD ed.local.net.mx 9.0-CURRENT FreeBSD 9.0-CURRENT #420: Tue Jan 12 07:13:52 CST 2010 r...@ed.local.net.mx:/usr/obj/usr/src/sys/ENCONTACTO i386 When I try to build the pwcbsd port I get: # make === Building for pwcbsd-1.4.1_6 make -f Makefile.kld all Warning: Object directory not changed from original /usr/ports/multimedia/pwcbsd/work/pwcbsd cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c pwc.c pwc.c:576: error: conflicting types for 'pwc_mmap' pwc.c:47: error: previous declaration of 'pwc_mmap' was here *** Error code 1 Stop in /usr/ports/multimedia/pwcbsd/work/pwcbsd. *** Error code 1 Stop in /usr/ports/multimedia/pwcbsd/work/pwcbsd. *** Error code 1 Stop in /usr/ports/multimedia/pwcbsd. Any help or suggestions appreciated. ed Did you enable this in OPTIONS? Enable mmap support (MAY CRASH YOUR SYSTEM) Thanks Lars, but no the only thing that I have enabled is PROGRAMS build the programs, in fact I have done make rmconfig and confirmed multiple times. I had thought the same. It would seem that there is yet another pwc_mmap conflict:( The ifdif at 577 would seem to be causing the problem somehow but I don't understand it at all. Sorry. Thanks again Lars. ed ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: patch for security/openssh-portable
Denny Lin wrote: Probably you want VersionAddendum option in sshd_config? No. To my understanding and my last tests VersionAddendum and is only a Addendum or did not work which spurred me to patch up the Makefile in the first place. I put VersionAddendum into sshd_config (with nothing trailing behind it), and it works as expected: telnet foo 22 Trying 192.168.0.1... Connected to foo Escape character is '^]'. SSH-2.0-OpenSSH_5.2p1 I'm using OpenSSH from base, but it should be the same with ports. I am not sure, but I think VersionAddendum is option available only in base SSH, not in portable from ports. Miroslav Lachman ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: patch for security/openssh-portable
On Wed, 13 Jan 2010 09:03, 000.fbsd@ wrote: Denny Lin wrote: Probably you want VersionAddendum option in sshd_config? No. To my understanding and my last tests VersionAddendum and is only a Addendum or did not work which spurred me to patch up the Makefile in the first place. I put VersionAddendum into sshd_config (with nothing trailing behind it), and it works as expected: telnet foo 22 Trying 192.168.0.1... Connected to foo Escape character is '^]'. SSH-2.0-OpenSSH_5.2p1 I'm using OpenSSH from base, but it should be the same with ports. I am not sure, but I think VersionAddendum is option available only in base SSH, not in portable from ports. That's correct as far as I have seen so far. Personally I think that since openssh-portable is in ports why worry about a VersionAddendum at all and just patch it with the patch I submitted. Seems like a more secure option but that's only me. -- jhell ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: security/openssl BROKEN, DEPRECATED, and EXPIRED?
On Wed, Jan 13, 2010 at 05:26:59AM -0600, Trix Farrar wrote: What happened? I got an e-mail from maintainer din...@freebsd.org. There was, evidently, a breakage introduced when threading library linkage was removed (http://docs.freebsd.org/cgi/mid.cgi?201001051213.o05CDu49061700). This change has been patched and libversion bumped. The port is now at 0.9.8l_2 (http://docs.freebsd.org/cgi/mid.cgi?201001131330.o0DDURiS062782). -- John D. Trix Farrar, CCNA __\\|//__ Basement.NET t...@basement.net (` o-o ') http://www.basement.net/ ---ooO-(_)-Ooo-- GPG Key Fprint: 525F DBA7 1A62 E4C4 E642 DF95 384B B851 3CEF C10A pgpJLjphbFr3K.pgp Description: PGP signature
Re: security/openssl BROKEN, DEPRECATED, and EXPIRED?
Trix Farrar ha scritto: I got an e-mail from maintainer din...@freebsd.org. There was, evidently, a breakage introduced when threading library linkage was removed Nothing is evident here. The port was deprecated because of unfixed vulnerabilities and worked for most of you. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: latest MySql?
On Wed, 13 Jan 2010 02:09:24 -0500 Robert Huff roberth...@rcn.com articulated: MySql-6.* is no longer in the ports tree. Things depend on it. Is there information on what happened and what the alternatives are? I have MySQL-6 installed. I have several applications that depend on it. What would be the recommended method to replace it with the latest stable release of MySQL? I see that 'portupgrade' offers quite a few options. Would one of them work? I really do not want to have to rebuild all of my applications that depend on MySQL-6 if possible. Thank you! One of the disadvantages of being an earlier adopter and not waiting for the tribe to cross the canyon!! MySQL-6 was a development version which was not ready for production servers. Given the development issues I am not surprised it has been dropped for the time being. I think you may need to adapt any code that does not work on 5.5 to meet your needs. David ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: security/openssl BROKEN, DEPRECATED, and EXPIRED?
I'd like to echo some of the others regarding the recent changes in
security/openssl: since this port is used by a large number of
people, it would be better to announce major changes in advance, and
to test more carefully before committing.
The reverted deprecation leaves me a bit puzzled. What were the
problems that prompted the comment that the port had unfixed
vulnerabilities? If that meant that flawed renegotiation could be
enabled via run-time flags, and this was thought to be unacceptable,
why not patch the port to disable it, as in the base system openssl,
rather than suddenly attempting to remove the port? If it was
something else, what was it, and what, if anything, is going to be
done about it? Can we expect an update to 1.0.x, and the resurrection
of SCTP support, after the renegotiation problem is settled? Or is a
removal of the port still planned? If that is the case, what do those
who want to remove the port propose as a replacement?
I note that there are still a few obvious minor flaws after the most
recent commits, including what looks like an unintentional inversion
of the logic surrounding the SSE2 option. I'm attaching a suggested
patch.
Regards,
b.
--- old.Makefile2010-01-13 10:45:10.0 -0500
+++ Makefile2010-01-13 11:26:31.0 -0500
@@ -29,7 +29,8 @@
.error You have `USE_OPENSSL' variable defined either in environment or in
make(1) arguments. Please undefine and try again.
.endif
-OPTIONS= I386Use optimzed assembler for 80386 off \
+OPTIONS= I386Use optimized assembler for 80386 off \
+ OPENSSL_THREADS Build a multithreaded openssl off \
SSE2Use runtime SSE2 detection on \
ZLIBBuild with zlib compression on \
@@ -857,7 +858,7 @@
OPENSSL_BASE_SOPATH= ${OPENSSL_BASE_SONAME:H}
OPENSSL_SHLIBVER?= 7
-.if !defined(WITHOUT_SSE2)
+.if defined(WITHOUT_SSE2)
# disable runtime SSE2 detection
EXTRACONFIGURE+= no-sse2
.endif
@@ -900,11 +901,9 @@
.endif
do-configure:
-.if !defined(WITH_FIPS)
${RM} -rf ${WRKSRC}/fips
${RM} -f ${WRKSRC}/include/openssl/fips.h
${RM} -f ${WRKSRC}/include/openssl/fips_rand.h
-.endif
.if defined(WITH_OPENSSL_THREADS)
cd ${WRKSRC} \
${SETENV} CC=${CC} FREEBSDCC=${CC} CFLAGS=${CFLAGS}
PERL=${PERL} \
@@ -918,13 +917,6 @@
./config --prefix=${PREFIX} --openssldir=${OPENSSLDIR} \
-L${PREFIX}/lib ${EXTRACONFIGURE}
.endif
-.if defined(WITH_FIPS)
- @${REINPLACE_CMD} \
- -e 's|^MANDIR=.*$$|MANDIR=$$(MANPREFIX)/man|' \
- -e 's|lib/pkgconfig|libdata/pkgconfig|g' \
- -e 's|LIBVERSION=[^ ]* |LIBVERSION=$(OPENSSL_SHLIBVER) |' \
- ${WRKSRC}/Makefile
-.else
@${REINPLACE_CMD} \
-e 's|^MANDIR=.*$$|MANDIR=$$(MANPREFIX)/man|' \
-e 's|lib/pkgconfig|libdata/pkgconfig|g' \
@@ -949,8 +941,7 @@
-e 's|$$(FIPS_RNGVS)$$(EXE_EXT)||' \
-e 's|$$(FIPS_TEST_SUITE)$$(EXE_EXT)||' \
${WRKSRC}/test/Makefile
-.endif
- @(cd ${BUILD_WRKSRC}/${i} ${SETENV} ${MAKE_ENV} ${MAKE}
${MAKE_FLAGS} ${MAKEFILE} depend)
+ @(cd ${BUILD_WRKSRC} ${SETENV} ${MAKE_ENV} ${MAKE} ${MAKE_FLAGS}
${MAKEFILE} depend)
post-install:
.if !defined(NOSHARED)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: security/openssl BROKEN, DEPRECATED, and EXPIRED?
On 1/13/10, b. f. bf1...@googlemail.com wrote: I note that there are still a few obvious minor flaws after the most recent commits, including what looks like an unintentional inversion of the logic surrounding the SSE2 option. I'm attaching a suggested patch. In addition to the other changes, it seems that we should issue EXTRACONFIGURE+= no-threads when !defined(WITH_OPENSSL_THREADS). Also, I note that the krb5-related code seems to be disabled, because the necessary configure flags are not issued. Regards, b. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
rdiff-backup-1.2.8 python2.5.4 : OverflowError: signed integer is greater than maximum
I all. I run rdiff-backup on my backup server: - FreeBSD 8.0-RELEASE AMD64 - rdiff-backup-1.2.8,1 - python25-2.5.4_3 - be pro quad - 4G Ram I try to rdiff a folder on a nfs ro mounted volume to an other volume. I obtain this error : OverflowError: signed integer is greater than maximum I have the same problem as Brad Beyenhof see here : http://www.mail-archive.com/rdiff-backup-us...@nongnu.org/msg03794.html I know it's a know problem due to a bug in Python. And have to upgrad Python to 2.5.4 or 2.6.1. But I'm on python25-2.5.4_3 !!! and rdiff need python25 to run so I can't remove it for python26... What can I do to obtain my full backup ? Thanks -- Michel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
HEADS UP: utmp.h gone. All welcome utmpx.h.
Hello everyone, I just made various commits to FreeBSD HEAD to remove our old user accounting database interface (see utmp(5)) and replace it by the POSIX standardized utmpx interface (see getutxent(3)). This means we just got rid of some annoyances that are as old as the FreeBSD project itself: - Hostnames were originally restricted to 16 bytes, which is way too short for your average hostname generated by your ISP, but also for IPv6 addresses, which are at most 32 + 7 = 39 characters. - No support for login sessions not related to TTYs, like ppp(8), ftpd(8) sessions. - No support for multiple login sessions on one TTY, for example generated by login(1). I was not able to give us a smooth transition from utmp towards utmpx, simply because our utmp implementation offered almost no utility functions, which means all consumers modify the database files themselves. This means you should probably recompile any applications you're interested in that uses the user accounting database. I realize this may be quite uncomfortable, but we can't always win. [ This information is mainly for port maintainers: ] I've noticed there is some breakage in ports, but it shouldn't be too serious. I've seen cases where an application includes utmp.h, even though it doesn't use anything provided by that header. In other cases they used fields like UT_NAMESIZE to derive the maximum user name length supported by the system, which is clearly not what this definition was intended for. I've incremented __FreeBSD_version to 97 to identify the import of utmpx. In case a certain port breaks badly, let me know and I'm willing to take a look at it. Be sure to give it a try and report any issues. Thanks! -- Ed Schouten e...@80386.nl WWW: http://80386.nl/ pgpQip4OfOMJy.pgp Description: PGP signature
FreeBSD Port: sysutils/bubblemon-dockapp
Hi, I've just noticed that |sysutils/bubblemon-dockapp has stopped displaying correctly memory swap usage. This is most likely due to my upgrade from FreeBSD 6.4 to 8.0. Any idea how to fix it pls ? Cheers, M. | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: UIDs question
On Mon, Jan 11, 2010 at 12:39:41PM -0800, Jason thus spake: I was wondering if there is a way to have the port install the user using the native USERS or GROUPS directives in the do-install phase with the INSTALL macros, or if there is a more suggested, or conventional, way of doing this operation. Would you mind putting the files somewhere and showing us the error log? I am aware of one caveat at the moment, which is that you can't use users/groups created with USERS/GROUPS in pkg-plist. Every typical use case with directives contained in Makefile should be fine AFAIK. -- Florent Thoumie f...@freebsd.org FreeBSD Committer I've uploaded to pastebin, and hope this is enough to go on. Please let me know if it is not, and I will make the information needed available. http://freebsd.pastebin.com/m359b2c91 I will attach the text of the pastebin for convenience. I found that the local UIDs files was malformed, and once the formatting was fixed, it worked as it should. -jason ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: HEADS UP: utmp.h gone. All welcome utmpx.h.
On Wednesday 13 January 2010 20:42:54 Ed Schouten wrote: Hello everyone, I just made various commits to FreeBSD HEAD to remove our old user accounting database interface (see utmp(5)) and replace it by the POSIX standardized utmpx interface (see getutxent(3)). This means we just got rid of some annoyances that are as old as the FreeBSD project itself: - Hostnames were originally restricted to 16 bytes, which is way too short for your average hostname generated by your ISP, but also for IPv6 addresses, which are at most 32 + 7 = 39 characters. This is most welcome :-) - No support for login sessions not related to TTYs, like ppp(8), ftpd(8) sessions. - No support for multiple login sessions on one TTY, for example generated by login(1). I was not able to give us a smooth transition from utmp towards utmpx, simply because our utmp implementation offered almost no utility functions, which means all consumers modify the database files themselves. This means you should probably recompile any applications you're interested in that uses the user accounting database. I realize this may be quite uncomfortable, but we can't always win. [ This information is mainly for port maintainers: ] I've noticed there is some breakage in ports, but it shouldn't be too serious. I've seen cases where an application includes utmp.h, even though it doesn't use anything provided by that header. In other cases they used fields like UT_NAMESIZE to derive the maximum user name length supported by the system, which is clearly not what this definition was intended for. I've incremented __FreeBSD_version to 97 to identify the import of utmpx. In case a certain port breaks badly, let me know and I'm willing to take a look at it. Be sure to give it a try and report any issues. Thanks! From the commit logs I can tell it was a lot of work on something that many people wouldn't consider a very glamourous or spectacular piece of FreeBSD. So let me just say: Thanks! Cheers, Pieter de Goeje ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
