Re: ipfilter fails to compile WITHOUT_INET6

2017-06-23 Thread Mikhail T.
On 22.06.2017 21:20, Cy Schubert wrote: Can you try the attached patch please? Yes, replacing: -#ifdef AF_INET6 +#ifdef USE_INET6 lets the build succeed. Is it Ok to modify stuff under contrib/ though?.. -mi ___ freebsd-current@freebsd.org

Locking console with Ctrl-S hangs various processes (ttydcd)

2014-05-13 Thread Mikhail T.
Hello! A fellow FreeBSD user was recently confounded by a problem: various processes on his 10.0 system were hanging or otherwise misbehaving: su, certain daemons, syslogd. They were all hung in the "ttydcd"-state. Searching for that revealed only

Re: md2 on current and 10.

2014-01-08 Thread Mikhail T.
On 08.01.2014 20:05, Peter Wemm wrote: > The path of least resistance is to make a libmd2 port. It's the only way I > can see you getting to use it on 10.0. *I* don't really care. *I* don't use md2 myself. I became aware of the problem by accident -- because one of my ports was affected (tcl-trf).

Re: md2 on current and 10.

2014-01-08 Thread Mikhail T
On 08.01.2014 02:54, Peter Wemm wrote: >> > Could we, please, have MD2 resurrected before 10.0 is officially out? >> > Preferably in both -lmd and -lcrypto, but certainly in the former. Thank >> > you! Yours, > The time to bring this up was before the freeze for 10.0, a good 6+ > months ago. It is

Re: md2 on current and 10.

2014-01-07 Thread Mikhail T.
On 27.12.2013 10:50, Ulrich Spörlein wrote: >> In other words, /if you like your digest algorithm, you can keep it/. Yours, > Seconded. What should people use if some of their old data is using MD2 > for verification? How can they now easily check that their data (from > tape or whatever) still mat

Re: md2 on current and 10.

2013-12-25 Thread Mikhail T
On 20.12.2013 13:38, olli hauer wrote: > md2 was deprecated in 2009 by the openssl project > > http://cvs.openssl.org/chngview?cn=18381 > CVE-2009-2409 > > As fas as I know some Linux based projects have removed md2 from > openssl-0.9.x in 2009. So, when are we removing sum(1) and cksum(1) -- im

Re: md2 on current and 10.

2013-12-20 Thread Mikhail T.
Thinking more about the MD2, I'd say, FreeBSD should not have removed the algorithm. Although no longer deemed sufficiently secure, it is still in use and people using it on FreeBSD-8.x and 9.x today may wish to continue doing so after upgrading to 10.x In the old "Mechanism vs. Policy" debate <

Re: md2 on current and 10.

2013-12-20 Thread Mikhail T.
On 20.12.2013 12:52, olli hauer wrote: > Hm the config script tests for md2 and sha1 ... > What happens if md2 support is removed from the code? Yes, the md2 can be removed from the set of digests made available by the port -- that's not a problem. What I wanted to know, was why? Maybe, the header

md2 on current and 10.

2013-12-19 Thread Mikhail T.
It would appear, neither nor are any longer available on FreeBSD current and 10.x This breaks the devel/tcl-trf port, which I maintain... Could someone, please, comment? Should I patch-up the port to disable the functionality? Or?.. Thank you! -mi _

patch -p broken on HEAD?

2013-12-01 Thread Mikhail T.
On 30.11.2013 13:24, pkg-fall...@freebsd.org wrote: > ===> Applying FreeBSD patches for xmdiary-3.0.3_3 > removing the malloc.h includes > /bin/sh /usr/ports/deskutils/xmdiary/scripts/nomalloc > /wrkdirs/usr/ports/deskutils/xmdiary/work/xmdiary-3.0.3 2>&1 > /dev/zero > patch: option requires an a

Re: ports include /etc/src.conf? i.e. graphics/libfpx

2013-02-15 Thread Mikhail T.
15.02.2013 19:12, Ian Lepore ???(??): > The src.conf manpage is not in error. The intent is that src.conf > applies only to the building of the freebsd world and kernel, that is, > the source that's usually located under /usr/src. If settings from > src.conf are leaking into other builds, the

Re: ports include /etc/src.conf? i.e. graphics/libfpx

2013-02-15 Thread Mikhail T.
14.02.2013 09:34, Peter Pentchev ???(??): However, there is then the argument of "well, if you want to use the bsd.*.mk infrastructure, then why don't you just copy it into your project and include it from there - just like many, many projects do with, say, the sys/queue.h header, or parts

Re: ports include /etc/src.conf? i.e. graphics/libfpx

2013-02-14 Thread Mikhail T.
14.02.2013 08:55, Tom Evans написав(ла): > On Thu, Feb 14, 2013 at 1:12 PM, Mikhail T. wrote: >> > I may sound defensive here, but I'll still repeat, that "this singular >> > port" >> > (and I do, in fact, have other ones like it) started using bsd

Re: ports include /etc/src.conf? i.e. graphics/libfpx

2013-02-14 Thread Mikhail T.
14.02.2013 08:02, Tom Evans написав(ла): > I think src.conf is meant only to be included when building src. For > example, bsd.port.mk sets _WITHOUT_SRCCONF before including bsd.own.mk > (which is the makefile that includes src.conf). It's done this since > src.conf was added in 2006, so evidently

Re: Re: ports include /etc/src.conf? i.e. graphics/libfpx

2013-02-14 Thread Mikhail T.
13.02.2013 11:22, O. Hartmann написав(ла): >> > If this is taken literally then could it be said that ports that use >> > bsd.lib.mk are broken because they are using makefile includes from >> > the source tree? >> > >> > -Kimmo For one, the particular port (its Makefile.bsd) was created in 2001,