Re: FreeBSD Security Advisory FreeBSD-SA-15:10.openssl

2015-06-13 Thread Zoran Kolic
My bad. Posted prior reading everything carefully. Thanks all for correcting me. Zoran ___ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to

Re: FreeBSD Security Advisory FreeBSD-SA-15:10.openssl

2015-06-12 Thread Zoran Kolic
Do I read this advisory correctly: it does not affect 9.3? Zoran ___ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to

Re: Security SSH

2015-01-13 Thread Zoran Kolic
Can you point to that for the rest of us? I'd rather not wade in openbsd-misc The link original poster presented is the correct one. Openbsd tend to set some default values, which one might like or not. I would disable root login at first. Misc seems rough at moment. I found it very

Re: Security SSH

2015-01-12 Thread Zoran Kolic
In fact, you got answer on openbsd misc list. Zoran ___ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to freebsd-security-unsubscr...@freebsd.org

Re: FreeBSD Security Advisory FreeBSD-SA-14:30.unbound

2014-12-18 Thread Zoran Kolic
The first part of that statement is false. The dns/unbound port was fixed for CVE-2014-8602 on 9 December. Thus a valid work around is to disable local_unbound and use ports/dns/unbound. To ask explicitelly: this does not affect 9.3? I see no unbound nor local_unbound on stock install.

Re: FreeBSD Security Advisory FreeBSD-SA-14:30.unbound

2014-12-18 Thread Zoran Kolic
This is weird as I now get a thing that Directory's required to be removed ... and that directory is / will this be fixed as this is kinda scary seeing Directory couldn't be removed rmdir / or something it showed. I had a problem using freebsd-update to 9.3-p6. I had to use it twice to

Re: FreeBSD Security Advisory FreeBSD-SA-14:18.openssl

2014-09-16 Thread Zoran Kolic
Systems running a RELEASE version of FreeBSD on the i386 or amd64 platforms can be updated via the freebsd-update(8) utility: # freebsd-update fetch # freebsd-update install No need to recompile the kernel? Zoran ___

Re: FreeBSD Security Advisory FreeBSD-SA-14:19.tcp

2014-09-16 Thread Zoran Kolic
Sorry to make a mistake, regarding the subject!!! Systems running a RELEASE version of FreeBSD on the i386 or amd64 platforms can be updated via the freebsd-update(8) utility: # freebsd-update fetch # freebsd-update install This is the question, I was intended to ask, since the patch

Re: FreeBSD Security Advisory FreeBSD-SA-14:19.tcp

2014-09-16 Thread Zoran Kolic
The advisory solution offers 3 options... freebsd-update is the binary approach (option #3) that provides you a new updated generic kernel already compiled. If you aren't using a generic kernel or want to patch and recompile your own, then you would use the option #2. Hm! I use custom

Re: FreeBSD Security Advisory FreeBSD-SA-14:19.tcp

2014-09-16 Thread Zoran Kolic
Unfortunately, I don't think your custom kernel got the patch. I made a mess out of this patch, that is for sure. On laptop I previously used freebsd-update for openssl advisory. Now I followed your advice and used patch way. Recompiled a kernel and got p1. I expected p2. However. On desktop, I

Re: FreeBSD Security Advisory FreeBSD-SA-14:18.openssl

2014-09-10 Thread Zoran Kolic
$ freebsd-version -k # means: kernel 10.0-RELEASE-p7 $ freebsd-version -u # means: userland 10.0-RELEASE-p8 $ freebsd-version# no option means: userland 10.0-RELEASE-p8 I have no freebsd-version on 9.3. Something on 10 only? Uname has -K and -U, but it is not it. Best regards

Re: FreeBSD Security Advisory FreeBSD-SA-14:18.openssl

2014-09-09 Thread Zoran Kolic
I used freebsd-update way on 9.3 amd64. It took 14 patches and 1 second to do the job. Now, I cannot see any difference. Only using fetch again, it says No updates needed to update system to 9.3-RELEASE-p1. How could I see that p1? I did not recompiled the kernel, as it was not mentioned in

.rnd file after starting X

2013-10-19 Thread Zoran Kolic
After updating to 9.2 release and upgrading ports, I had to compile nvidia driver 319.32. Finally, have graphics up. One file shows out of the blue, when- ever I run startx, spite I remove it regurarly. The size is 1024. Man for rand mentions it. I cannot see what openssl has to do with X at the

torrent

2006-05-23 Thread Zoran Kolic
I'd like to know if someone has link to tutorial for managing ipfw for torrent usage. Client side, for start. Best regards Zoran ___ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security

ICMP 3.3

2006-01-11 Thread Zoran Kolic
Hi all! For a long time I see icmp 3.3 packets in my log, coming from 65.59.245.131. Cannot find what this address is in fact. Every day, on both i386 and amd64. I use ipfw and not a server at all. Comes even if I just look for mail in console. Does someone have similar item in log? One more

pgp status

2005-07-06 Thread Zoran Kolic
Dear all! I'd like to know if something changed for pgp263i on amd64. In ports, archs recommended are i386 and alpha. Has someone used gpg-idea port (with idea and rsa) to circum- vent pgp - gpg missmetch? Best regards Zoran ___