similar to: Report of collision-generation with MD5

On Wednesday 29 October 2003 17:29, Ricardo wrote: > Excellent! > > With WinAmp 5 it works but after about 45seconds I get the same messages in > error.log > > [2003-10-29 08:38:33] DBUG format/format_generic_write_buf_to_client > Client had recoverable error -1 This should never happen. It looks like a bug present in some old versions (> 6 months old), are you sure a

I just finished up a port of Andy Polyakov's excellent dvd+rw-tools to FreeBSD, and he has incorporated the patches into his release: http://fy.chalmers.se/~appro/ http://fy.chalmers.se/~appro/linux/DVD+RW/ http://fy.chalmers.se/~appro/linux/DVD+RW/tools/ (version 5.8.4.4.4) These tools support DVD-R, DVD-RW, DVD+R, and DVD+RW format dvd burners, including the popular Sony

On Wednesday 29 October 2003 18:06, Ricardo wrote: > Hi Mike > > cat /usr/ports/audio/icecast2/distinfo > MD5 (icecast-2.0-alpha-2-20030811.tar.gz) = > fc1dc4173a81daa741cef14cadbf6ce1 > > cat /usr/ports/audio/ices/distinfo > MD5 (ices-2.0-Beta2-20030811.tar.gz) = 5ccf54d6961eba9ac914090dffb874cc > > Should I expect problems with these versions? Is the problem with

> I'm confused. Does the release tarball now match RELEASE_32/final or > not? If not, that's a problem for those of us who count on the > repository matching the actual release. > > At the very least they should match so we can check out the release at > some point in the future. They should match now -- With best regards, Anton Korobeynikov Faculty of Mathematics and

Hi all: I'm currently using NSD 1.2.4 on a FreeBSD host to serve a big domain. I've been looking for new versions of NSD (particularly NSD 2.0.2) on FreeBSD Ports but I haven't found it. Who should add this new version to Ports? Can I make something to include it? I don't have enough experience with FreeBSD and I feel a little bit lost. Best Regards -- Sebastian E. Castro

While the sizes now match the SHA256 checksum do not match the original compressed tarballs. /usr/ports/devel/llvm # sha256 /usr/ports/distfiles/llvm-3.2.src.tar.gz SHA256 (/usr/ports/distfiles/llvm-3.2.src.tar.gz) = 265109c71b4fab8dc12ced314955921695c1ef549719553b0bc1e325110e143e root at sex:/usr/ports/devel/llvm # ls -l /usr/ports/distfiles/llvm-3.2.src.tar.gz -rw-r--r-- 1 root wheel

On Tue, Jan 15, 2013 at 09:25:42AM +1100, Mark Andrews wrote: > > While the sizes now match the SHA256 checksum do not match the original > compressed tarballs. > > /usr/ports/devel/llvm # sha256 /usr/ports/distfiles/llvm-3.2.src.tar.gz > SHA256 (/usr/ports/distfiles/llvm-3.2.src.tar.gz) = 265109c71b4fab8dc12ced314955921695c1ef549719553b0bc1e325110e143e > root at

Anybody out there who's got any luck to make it work?

Hi everyone, Not sure if you've read http://www.win.tue.nl/hashclash/SoftIntCodeSign/ . should some kind of advisory be sent to advise people not to rely solely on MD5 checksums? Maybe an update to the man page is due ? : " MD5 has not yet (2001-09-03) been broken, but sufficient attacks have been made that its security is in some doubt. The attacks on MD5 are in the

We are pleased to release pigeonhole 0.5.11. You can download it from locations below: https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11.tar.gz https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy --- *

We are pleased to release pigeonhole 0.5.11. You can download it from locations below: https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11.tar.gz https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy --- *

On 10/08/2012 21:58, nut-upsuser-request at lists.alioth.debian.org wrote: >>> Arnaud Quette<aquette.dev<at> gmail.com> writes: >>>> 2012/6/3 Chris Rees<crees<at> freebsd.org>: >>>>> Hi all, >>>> Hi Chris, >>>> >>>>> After some research I've found that this device should run with the

Hi We have a number offices accommodating 4-6 people each hence it is very important for PBX to be fanless and silent. We have been looking at using IDE flash disks also called DOM. The performance tests we have done so far satisfy our requirements, however we are concerned with DOM durability. We have installed debian and vanilla asterisk on 1GB DOM. All seems to work fine at the moment however

I am receiving a list of name collisions when I launch R as seen below. I'm new to R and any suggestion or help with how I can go about getting rid of these collisions would be greatly appreciated. % R R version 2.5.1 (2007-06-27) Copyright (C) 2007 The R Foundation for Statistical Computing ISBN 3-900051-07-0 R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to

How 'bout PAM? /usr/ports/security/pam_ldap. If you have machines that can't do PAM, perhaps NIS is the way to go (assuming, of course, you're behind a firewall). You can store login information in LDAP like you want, then use a home-grown script to extract the information to a NIS map. Or, if you have a Solaris 8 machine lying around, you can cut out the middle step and use

FYI ----- Forwarded message from Kris Kennaway <kris@FreeBSD.org> ----- X-Original-To: kkenn@localhost Delivered-To: kkenn@localhost.obsecurity.org Delivered-To: kris@freebsd.org Delivered-To: ports-committers@freebsd.org From: Kris Kennaway <kris@FreeBSD.org> Date: Thu, 4 Dec 2003 06:45:06 -0800 (PST) To: ports-committers@FreeBSD.org, cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org

FYI Kris ----- Forwarded message from Kris Kennaway <kris@FreeBSD.org> ----- X-Original-To: kkenn@localhost Delivered-To: kkenn@localhost.obsecurity.org Delivered-To: kris@freebsd.org Delivered-To: ports-committers@freebsd.org From: Kris Kennaway <kris@FreeBSD.org> Date: Thu, 17 Apr 2003 14:45:03 -0700 (PDT) To: ports-committers@FreeBSD.org, cvs-ports@FreeBSD.org,

Hello, I have a problem with directories that contain more than 10000 entries (Ubuntu 8.04.1) or with more than 70000 entries (RHEL 5.2). If you use readdir(3) or readdir64(3) you get one entry twice, with same name and inode. Some analyzing showed that disabling dir_index solves this problem, but I think that this is a bug in the ext3 code, as no other file-system shows this behavior.

2015-11-13 13:52 GMT-03:00 Gordon Messmer <gordon.messmer at gmail.com>: > On 11/13/2015 03:22 AM, Sergio Belkin wrote: > >> I'm trying to create virtualized linux bridge >> > > Well, you can't do that by putting two interfaces on the same LAN. A > bridge should be used to connect two separate LANs. > >

Hello! On Sat, 7 Oct 2006, Jose Alonso Cardenas Marquez wrote: > Modified files: > multimedia/win32-codecs Makefile distinfo pkg-plist > Log: > - Add the REALPLAYER and QUICKTIME(off) OPTIONS. If QUICKTIME OPTION is off, > this port could install without problem of vulnerabilities. > - Bump PORTREVISION > - Other few modifications Thanks, that's great,