From owner-freebsd-current Sun Jul 16 0: 0:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from dfw-smtpout4.email.verio.net (dfw-smtpout4.email.verio.net [129.250.36.44]) by hub.freebsd.org (Postfix) with ESMTP id 37F1237B5DA for ; Sun, 16 Jul 2000 00:00:40 -0700 (PDT) (envelope-from gjohnson@gs.verio.net) Received: from [129.250.38.61] (helo=dfw-mmp1.email.verio.net) by dfw-smtpout4.email.verio.net with esmtp (Exim 3.12 #7) id 13DiPn-0005fP-00; Sun, 16 Jul 2000 07:00:39 +0000 Received: from [204.1.124.74] (helo=power) by dfw-mmp1.email.verio.net with smtp (Exim 3.15 #4) id 13DiPn-0005Hq-00; Sun, 16 Jul 2000 07:00:39 +0000 Message-ID: <000c01bfeef3$8c71b8f0$4a7c01cc@gs.verio.net> From: "Tony Johnson" To: "John Polstra" Cc: References: <00cf01bfed15$43ab2910$4a7c01cc@gs.verio.net> <200007152234.PAA05700@vashon.polstra.com> Subject: Re: rtld-elf Date: Sun, 16 Jul 2000 02:00:38 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry about the message format. Someone else complained before I had a chance to see how it was set. It should be set to plain text now. Sorry When I was using cvsup I was allowing cvsup to edit already placed source code. So on Friday Morning, I deleted all my cvs source code and cvsup all new copies from scratch. I did a make world and the compile finished successfully. I am using dual PPro-200 ----- Original Message ----- From: "John Polstra" To: Cc: Sent: Saturday, July 15, 2000 5:34 PM Subject: Re: rtld-elf > [Whew! Could you set your mail format to plain text next time? > That MimeCroSoft stuff is awfully hard to read on real computers.] > > In article <00cf01bfed15$43ab2910$4a7c01cc@gs.verio.net>, > Tony Johnson wrote: > > > > Hmmm.. I have been experiencing a problem when I installworld with = > > freebsd-5.0. The install breaks with rtld-elf when the install put the = > > new copy of ld-elf.s0.1 onto my system. Most f my prgrams signal 11 = > > until I put the old ne back. Is there smething I was supposed t do = > > befre this?? > > Yours is the only trouble report I've seen for the new version of the > dynamic linker. Please tell me exactly what kind of CPU your system > has in it. Also please send me the output from "dmesg". > > Thanks, > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 1: 7:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from smople.thehub.com.au (smople.thehub.com.au [203.143.240.10]) by hub.freebsd.org (Postfix) with ESMTP id C595337BD0E for ; Sun, 16 Jul 2000 01:07:25 -0700 (PDT) (envelope-from mckay@thehub.com.au) Received: from dungeon.home (ppp18.dyn248.pacific.net.au [203.143.248.18]) by smople.thehub.com.au (8.9.3/8.9.1) with ESMTP id SAA63540; Sun, 16 Jul 2000 18:07:16 +1000 (EST) Received: from dungeon.home (localhost [127.0.0.1]) by dungeon.home (8.9.3/8.9.3) with ESMTP id SAA21950; Sun, 16 Jul 2000 18:09:31 +1000 (EST) (envelope-from mckay) Message-Id: <200007160809.SAA21950@dungeon.home> To: "Rodney W. Grimes" Cc: mckay@thehub.com.au (Stephen McKay), freebsd-current@FreeBSD.ORG Subject: Re: dc driver and underruns (was: Strangeness with 4.0-S) References: <200007150016.RAA18115@gndrsh.dnsmgr.net> In-Reply-To: <200007150016.RAA18115@gndrsh.dnsmgr.net> from "Rodney W. Grimes" at "Fri, 14 Jul 2000 17:16:49 -0700" Date: Sun, 16 Jul 2000 18:09:31 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 14th July 2000, "Rodney W. Grimes" wrote: >> I suspect an interaction between the ATA driver and VIA chipsets, >> because other than the network, that's all that is operating when I see >> the underruns. And my Celeron with a ZX chipset is immune. > >I've seen them on just about everything, chipset doesn't seem to matter, >IDE or SCSI doesn't seem to matter. Well, maybe they are just a fact of life. But using just my vague knowledge of how PCI works, it doesn't look inevitable to me. So I see bugs. :-) >> Getting even more technical, it appears to me that the current driver >> instructs the 21143 to poll for transmit packets (ie a small DMA) >> every 80us even if there are none to be sent. I don't know what percentage >> of bus time this might be, or even how to calculate it (got some time Rod?) > >I'll have to look at that. If it is a simple 32 bit read every 80uS >thats something like .1515% of the PCI bandwidth, something that shouldn't >matter much. (I assumed a simple 4 cycle PCI operation). Just how big >is this DMA operation every 80uS? I believe it is just one 32 bit read. But I don't understand that aspect of the hardware very well yet. I also suspect that this polling adds to the latency, but again, I haven't got to the end of that either. Sometimes other things can distract you from even the most interesting technical matter. :-) Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 2: 4:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id F0B2637B58A for ; Sun, 16 Jul 2000 02:03:57 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id LAA01766 for ; Sun, 16 Jul 2000 11:05:11 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007160905.LAA01766@grimreaper.grondar.za> To: current@FreeBSD.ORG Subject: Re: **HEADS UP** if you used to cvsup the crypto repo from internat ! References: <200007152315.QAA06420@vashon.polstra.com> In-Reply-To: <200007152315.QAA06420@vashon.polstra.com> ; from John Polstra "Sat, 15 Jul 2000 16:15:24 MST." Date: Sun, 16 Jul 2000 11:05:11 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 5. If you are using CTM to receive the "*,v" files and then using > the "cvs" command to check out your source tree, then I don't know > whether you need to delete your ",v" files and replace them or not. You do need to delete your ,v files in this case (only for the crypto dirs). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 4:44:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from home.bsdclub.org (home.bsdclub.org [202.227.26.94]) by hub.freebsd.org (Postfix) with ESMTP id E554637B55C; Sun, 16 Jul 2000 04:44:18 -0700 (PDT) (envelope-from sada@bsdclub.org) Received: (from sada@localhost) by home.bsdclub.org (8.9.3/3.7W) id UAA95710; Sun, 16 Jul 2000 20:44:14 +0900 (JST) Date: Sun, 16 Jul 2000 20:44:14 +0900 (JST) Message-Id: <200007161144.UAA95710@home.bsdclub.org> To: current@FreeBSD.org Cc: cvs-all@FreeBSD.org, sada@bsdclub.org Subject: Re: cvs commit: src/bin/mv mv.c In-Reply-To: Your message of "Sat, 15 Jul 2000 07:59:02 -0700 (PDT)". <200007151459.HAA47427@freefall.freebsd.org> From: SADA Kenji Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Mailer: mnews [version 1.22] 1999-12/19(Sun) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200007151459.HAA47427@freefall.freebsd.org> sada@FreeBSD.org writes: >> sada 2000/07/15 07:59:02 PDT >> >> Modified files: >> bin/mv mv.c >> Log: >> To make inherit file flags when mv(1) moves file between directories >> on different file systems. >> >> PR: bin/12375 >> Submitted by: Takashi SHIRAI >> No response by: steve >> No problem with: building 5-current world >> >> Revision Changes Path >> 1.26 +3 -1 src/bin/mv/mv.c I'd like to MFC this in time for 4.1-R. Please present any objection if you have. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 5:15:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id C68D737BBC8 for ; Sun, 16 Jul 2000 05:15:40 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id OAA28320; Sun, 16 Jul 2000 14:15:19 +0200 (MET DST) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id OAA83120; Sun, 16 Jul 2000 14:13:19 +0200 (CEST) (envelope-from andreas) Date: Sun, 16 Jul 2000 14:13:18 +0200 From: Andreas Klemm To: Mark Murray Cc: Current Subject: missing idea.h, still conflicting defines WITH_IDEA and MAKE_IDEA Message-ID: <20000716141318.A80785@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.2i X-Operating-System: FreeBSD 5.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 23, 2000 at 08:36:32AM +0200, Mark Murray wrote: > > Building world failed on my machine... (with USA_RESIDENT=NO) > > Does IDEA stuff compiled by default? > I messed this up. Fix coming. Something seems to be wrong with the logic concerning IDEA stuff. I ask because I can't build the security/p5-Net-SSLeay port anymore which is for example needed for webmin. It fails because idea.h can't be found. evp.h needs idea.h which isn't present: /usr/include/openssl/evp.h:#include There are several knobs to play with. I finally defined WITH_IDEA=YES in /etc/make.conf and did a make includes, but actually idea.h doesn't show up. When digging around under the secure src hierarchie I noticed, that WITH_IDEA only triggers a make variable secure/Makefile.inc: .if !defined(WITH_IDEA) || ${WITH_IDEA} != YES CFLAGS+= -DNO_IDEA .endif But that is not sufficient, since secure/lib/libcrypto/Makefile only includes IDEA stuff, if MAKE_IDEA is defined && set to "YES". [...] if defined(MAKE_IDEA) && ${MAKE_IDEA} == YES .PATH: ${LCRYPTO_SRC}/idea .endif [...] # idea .if defined(MAKE_IDEA) && ${MAKE_IDEA} == YES SRCS+= i_ecb.c i_cbc.c i_cfb64.c i_ofb64.c i_skey.c .endif [...] .if defined(MAKE_IDEA) && ${MAKE_IDEA} == YES HDRS+= idea/idea.h .endif That's the reason, why idea.h is missing in /usr/include. Two possibilities to fix the problem: A) etc/defaults/make.conf: DMAKE_IDEA=YES secure/Makefile.inc: .if !defined(WITH_IDEA) || ${WITH_IDEA} != YES CFLAGS+= -DNO_IDEA .else CFLAGS+= -DMAKE_IDEA ^^^^^^^^^^^^^^^^^^^^ .endif B) change the whole "ifdef MAKE_IDEA" stuff in secure/lib/libcrypto/Makefile to "ifdef WITH_IDEA" -- Andreas Klemm http://people.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD New APSFILTER 542 and songs from our band - http://people.freebsd.org/~andreas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 7:57:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhost.netbenefit.co.uk (mailhost.netbenefit.co.uk [212.53.64.39]) by hub.freebsd.org (Postfix) with ESMTP id AFBB437BC8A for ; Sun, 16 Jul 2000 07:57:35 -0700 (PDT) (envelope-from pierre.dampure@alveley.org) Received: from userk134.uk.uudial.com ([194.69.100.218] helo=alveley.org) by mailhost.netbenefit.co.uk with esmtp (NetBenefit 1.5) id 13DprL-0003oC-00 for current@FreeBSD.ORG; Sun, 16 Jul 2000 15:57:35 +0100 Message-ID: <3971CD5E.414EC080@alveley.org> Date: Sun, 16 Jul 2000 15:57:34 +0100 From: "Dampure, Pierre Y." X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Weird top output Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With a recently (10:00 BST) cvsup'd and built world / kernel: last pid: 288; load averages: 0.05, 0.04, 0.01 up 0+00:03:27 15:53:02 32 processes: 1 running, 31 sleeping CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 282M Active, 17M Inact, 20M Wired, 108K Cache, 20M Buf, 181M Free Swap: 3072M Total, 3072M Free PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 288 dampurep 46 0 1876K 1184K CPU0 1 0:00 0.87% 0.44% top 238 root 2 0 171M 170M select 1 0:05 0.00% 0.00% XFree86 35 root 10 0 256M 256M mfsidl 1 0:01 0.00% 0.00% mount_mfs 254 dampurep 2 0 3780K 2916K select 0 0:01 0.00% 0.00% wmaker 137 root 2 0 2140K 1408K select 0 0:00 0.00% 0.00% sshd 265 dampurep 10 0 2312K 1456K nanslp 0 0:00 0.00% 0.00% wmCalClock 220 mysql 2 0 10928K 9952K poll 0 0:00 0.00% 0.00% mysqld 285 dampurep 2 0 3668K 2988K select 0 0:00 0.00% 0.00% xterm 266 dampurep 10 0 2052K 1244K nanslp 1 0:00 0.00% 0.00% wmmixer 222 root 18 0 2864K 1468K pause 0 0:00 0.00% 0.00% xdm 239 root 10 0 2988K 2304K wait 0 0:00 0.00% 0.00% xdm 101 root 2 0 916K 656K select 1 0:00 0.00% 0.00% syslogd 270 dampurep 2 0 3128K 2412K select 0 0:00 0.00% 0.00% xconsole 286 dampurep 10 0 1092K 944K wait 0 0:00 0.00% 0.00% bash 125 root 2 0 1040K 784K select 0 0:00 0.00% 0.00% inetd 205 root 10 0 628K 460K wait 0 0:00 0.00% 0.00% sh I'm somewhat surprised by the resident size of XFree86-4 and mfs... from memory, the resident size of mfs was around 30Mb up until today (no recollection as to what it was fro XFree86-4, though). FWIW, this is just after a reboot. PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 9:11:36 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 6577E37BE2B; Sun, 16 Jul 2000 09:11:34 -0700 (PDT) Date: Sun, 16 Jul 2000 09:11:34 -0700 From: "Andrey A. Chernov" To: imp@village.org Cc: current@freebsd.org Subject: HEADS UP, mtree defaults returns back to original Message-ID: <20000716091132.A29072@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is possible /usr/src/UPDATING entry: 20000716: mtree now NOT follows symlinks by default, old behaviour restored to be compatible with rest of *BSD camp. New -L option added to follow symlinks. This require manual mtree rebuilding before 'make world' -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 10:48:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id B0F2037B5F9; Sun, 16 Jul 2000 10:48:43 -0700 (PDT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id KAA33926; Sun, 16 Jul 2000 10:48:43 -0700 (PDT) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id KAA37326; Sun, 16 Jul 2000 10:48:43 -0700 (PDT) (envelope-from frank) From: Frank Mayhar Message-Id: <200007161748.KAA37326@realtime.exit.com> Subject: Will the urio dev make it to -stable? To: current@freebsd.org Date: Sun, 16 Jul 2000 10:48:43 -0700 (PDT) Cc: stable@freebsd.org Reply-To: frank@exit.com Organization: Exit Consulting X-Copyright0: Copyright 2000 Frank Mayhar. All Rights Reserved. X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only. X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ...any time soon? It's been in current since 3/16 so it would seem MFCable, but what do I know. Nick? (I run 4-stable and don't plan to run -current any time soon, _and_ I want to buy a Rio 500, but not if I can't hook it to FreeBSD.) Sent to both -current and -stable as both lists seem relevant. Please limit followups, though. -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://store.exit.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 10:59:48 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 7806137B533; Sun, 16 Jul 2000 10:59:45 -0700 (PDT) Date: Sun, 16 Jul 2000 10:59:45 -0700 From: "Andrey A. Chernov" To: markm@freebsd.org Cc: current@freebsd.org Subject: randomdev entropy gathering is really weak Message-ID: <20000716105943.A60072@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found that I always got the same fortune quote after reboot, over and over again. It means that /dev/random produce exact the same values after reboot. It means that machine timer or keyboard not used for enthropy gathering. Using keyboard alone not helps for automatic tasks because it can be even not present, so machine timer must be used at least after reboot stage i.e. in randomdev init procedure. Otherwise first random values are very predictable and subject for attack. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 11:15:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id D5C5537B6C8 for ; Sun, 16 Jul 2000 11:15:32 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id UAA27846 for current@FreeBSD.org; Sun, 16 Jul 2000 20:15:21 +0200 (MET DST) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id UAA29461 for current@FreeBSD.org; Sun, 16 Jul 2000 20:06:50 +0200 (CEST) (envelope-from andreas) Date: Sun, 16 Jul 2000 20:06:50 +0200 From: Andreas Klemm To: current@FreeBSD.org Subject: make or fetch problem: hitting ^C doesn't terminate fetch process Message-ID: <20000716200650.A25974@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.2i X-Operating-System: FreeBSD 5.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ! I'm using -current of yesterday and tcsh. When installing a FreeBSD port and I interrupt a "make all install clean" session, when make is in the "make fetch target", the fetch process isn't killed and continues to run alone although the "make" is terminated. Andreas /// -- Andreas Klemm http://people.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD New APSFILTER 542 and songs from our band - http://people.freebsd.org/~andreas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 11:15:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from blues.jpj.net (blues.jpj.net [204.97.17.146]) by hub.freebsd.org (Postfix) with ESMTP id 1EF0937C006; Sun, 16 Jul 2000 11:15:49 -0700 (PDT) (envelope-from trevor@jpj.net) Received: from localhost (trevor@localhost) by blues.jpj.net (right/backatcha) with ESMTP id e6GIFij06852; Sun, 16 Jul 2000 14:15:44 -0400 (EDT) Date: Sun, 16 Jul 2000 14:15:44 -0400 (EDT) From: Trevor Johnson To: "Andrey A. Chernov" Cc: markm@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <20000716105943.A60072@freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I found that I always got the same fortune quote after reboot, over and over > again. It means that /dev/random produce exact the same values after reboot. There were some special instructions for the new random device: 2) If you do not have the randomdev module loaded, ssh will fail in strange and creative ways (like RSA or DH not working for strange reasons). 3) It is not built by default (except as a kernel module), so you either need to add the "options RANDOMDEV" like to your kernel config, or load it at boot time in /dev/loader.conf 4) Make sure that you update your /etc area (mergemaster is your friend). The rndcontrol(8) utility is now OBE, and no longer of relevance. (<200006251035.MAA16350@grimreaper.grondar.za> from Mark Murray ) -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 11:20:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout1.silyn-tek.de (mout1.silyn-tek.de [194.25.165.69]) by hub.freebsd.org (Postfix) with ESMTP id 6FBB537B632 for ; Sun, 16 Jul 2000 11:20:12 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from [192.168.32.33] (helo=mx1.silyn-tek.de) by mout1.silyn-tek.de with esmtp (Exim 3.13 #1) id 13Dt1P-00045m-00; Sun, 16 Jul 2000 20:20:11 +0200 Received: from p3e9c1125.dip0.t-ipconnect.de ([62.156.17.37] helo=neutron.cichlids.com) by mx1.silyn-tek.de with esmtp (Exim 3.13 #1) id 13Dt1K-000683-00; Sun, 16 Jul 2000 20:20:06 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 3B6A2AB91; Sun, 16 Jul 2000 20:21:33 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 35BFD14A62; Sun, 16 Jul 2000 20:20:04 +0200 (CEST) Date: Sun, 16 Jul 2000 20:20:04 +0200 To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: Network install HOWTO available. Message-ID: <20000716202004.A474@cichlids.cichlids.com> Mail-Followup-To: Alfred Perlstein , current@FreeBSD.ORG References: <20000713031014.P25571@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000713031014.P25571@fw.wintelcom.net>; from bright@wintelcom.net on Thu, Jul 13, 2000 at 03:10:15AM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. From: alex@big.endian.de (Alexander Langer) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Alfred Perlstein (bright@wintelcom.net): > http://people.freebsd.org/~alfred/pxe/ Nice article! I think that's worth going into the handbook, after you reworked the things you talked about :) Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 11:25:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id EAB1137BB9E; Sun, 16 Jul 2000 11:25:32 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id UAA03911; Sun, 16 Jul 2000 20:26:44 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007161826.UAA03911@grimreaper.grondar.za> To: "Andrey A. Chernov" Cc: markm@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <20000716105943.A60072@freebsd.org> In-Reply-To: <20000716105943.A60072@freebsd.org> ; from "Andrey A. Chernov" "Sun, 16 Jul 2000 10:59:45 MST." Date: Sun, 16 Jul 2000 20:26:44 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I found that I always got the same fortune quote after reboot, over and over > again. It means that /dev/random produce exact the same values after reboot. > It means that machine timer or keyboard not used for enthropy gathering. > Using keyboard alone not helps for automatic tasks because it can be even not > present, so machine timer must be used at least after reboot stage i.e. in > randomdev init procedure. Otherwise first random values are very predictable > and subject for attack. Gotcha - fix coming; I need to stash some randomness at shutdown time, and use that to reseed the RNG at reboot time. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 11:31:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 2CE8A37BEA3 for ; Sun, 16 Jul 2000 11:31:28 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id OAA282728; Sun, 16 Jul 2000 14:31:20 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200007150409.AAA32685@whizzo.transsys.com> References: <200007142139.RAA88779@khavrinen.lcs.mit.edu> <200007150409.AAA32685@whizzo.transsys.com> Date: Sun, 16 Jul 2000 14:32:18 -0400 To: "Louis A. Mamakos" From: Garance A Drosihn Subject: Re: Request for comments: new `lpd' suite feature Cc: Garrett Wollman , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:09 AM -0400 7/15/00, Louis A. Mamakos wrote: >I almost hate to bring this up, but I think the unnamed-here >proposed replacement for our lpd allows you to set your PRINTER >environment variable to something like > > PRINTER=queuename@spooler.do.main > >louie For what it's worth, I think that feature is a little too helpful, and I would not want that ability on our (RPI) public unix workstations. I do want some capability to specify a hostname, but not a wide-open capability to specify any hostname. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 11:33:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 0C9C337B8D8 for ; Sun, 16 Jul 2000 11:33:31 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id OAA805262; Sun, 16 Jul 2000 14:28:29 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200007150425.VAA19195@ix.netcom.com> References: <200007142139.RAA88779@khavrinen.lcs.mit.edu> <200007150409.AAA32685@whizzo.transsys.com> <200007150425.VAA19195@ix.netcom.com> Date: Sun, 16 Jul 2000 14:29:28 -0400 To: "Thomas D. Dean" , current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Request for comments: new `lpd' suite feature Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:25 PM -0700 7/14/00, Thomas D. Dean wrote: >How would this work with printers on local networks? > >Say, a print server 192.168.1.73? > If you do not have a special DNS entry for that printer, then this new synthetic-printcap option would do nothing for you. In other words, you would continue doing your printcap file exactly the way you do it now. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 11:41:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 8D1D937BF29 for ; Sun, 16 Jul 2000 11:41:47 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id LAA23975; Sun, 16 Jul 2000 11:41:37 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200007161841.LAA23975@gndrsh.dnsmgr.net> Subject: Re: dc driver and underruns (was: Strangeness with 4.0-S) In-Reply-To: <200007160809.SAA21950@dungeon.home> from Stephen McKay at "Jul 16, 2000 06:09:31 pm" To: mckay@thehub.com.au (Stephen McKay) Date: Sun, 16 Jul 2000 11:41:37 -0700 (PDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Friday, 14th July 2000, "Rodney W. Grimes" wrote: > > >> I suspect an interaction between the ATA driver and VIA chipsets, > >> because other than the network, that's all that is operating when I see > >> the underruns. And my Celeron with a ZX chipset is immune. > > > >I've seen them on just about everything, chipset doesn't seem to matter, > >IDE or SCSI doesn't seem to matter. > > Well, maybe they are just a fact of life. But using just my vague knowledge > of how PCI works, it doesn't look inevitable to me. So I see bugs. :-) Yes, there are bugs, it's in the poor specification of the PCI bus, and in the even poorer implementation of PCI in hardware. To qoute from the PCI 2.0 spec, starting at the bottom of page 44, section 3.4.4.3 Latency Guidelines: In most PCI systems, typical access latency is both short (likely under 2us) and easily quantified. However, worst case latency (however rare) may not only be quite long, but in some cases quite difficult to predict. For example, latency to a standard expansion adapter (ISA/EISA/MC) through a bridge is often a function of adapter behavior, not PCI behavior. (This is especially problematic since some existing adapters are not compliant with latency parameters defined by the associated bus standard.) To compensate, masters that require guaranteed worst case access latency must provide adequate buffering for 30 microseconds. This implies a minimum of about 50 bytes of buffering for a 10Mbit/second LAN, and about 500 bytes for a 100Mbit/second LAN. (If the buffers are line organized [i.e., 16- or 32-bit aligned] to imporove PCI and target memory utilization, minimum buffer size likely increases.) In spite of worst case uncertainty, 30 microseconds should provide sufficient margin for realizable system designs. My calculations say that 30uS is long enough to transfer about 3960Bytes, now you see the problem??? I think the current driver behavior is near optimal, it backs down until it becomes latency proof (store and forward is latency proof). The only thing it might do better is deal with the fact that short term bus starvation should not effect long term performance, and as long as the underun events have a tolerable frequence it should not down grade to store and forward. Right now the code immediately steps the TXTHRESH every time we get an underrun, this should probably use a frequency counter and not do this unless we are seeing some untolerable rate of underruns. Especially when makeing the transition to store and forward. Ohh... and a finally note, DEC blew the chip design by only including a 160byte threshold point given that PCI 2.0 spec says it should have been 500bytes!! (Well, they blew it when the did the DC2114x enhancement to the the DC2104x chip by not increasing the fifo depth to compensate for the higher rate at which the fifo is emptied.) > > >> Getting even more technical, it appears to me that the current driver > >> instructs the 21143 to poll for transmit packets (ie a small DMA) > >> every 80us even if there are none to be sent. I don't know what percentage > >> of bus time this might be, or even how to calculate it (got some time Rod?) > > > >I'll have to look at that. If it is a simple 32 bit read every 80uS > >thats something like .1515% of the PCI bandwidth, something that shouldn't > >matter much. (I assumed a simple 4 cycle PCI operation). Just how big > >is this DMA operation every 80uS? > > I believe it is just one 32 bit read. But I don't understand that aspect > of the hardware very well yet. I also suspect that this polling adds > to the latency, but again, I haven't got to the end of that either. > Sometimes other things can distract you from even the most interesting > technical matter. :-) :-) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 11:48:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout2.silyn-tek.de (mout2.silyn-tek.de [194.25.165.70]) by hub.freebsd.org (Postfix) with ESMTP id D20D837B614 for ; Sun, 16 Jul 2000 11:48:47 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from [192.168.32.34] (helo=mx2.silyn-tek.de) by mout2.silyn-tek.de with esmtp (Exim 3.13 #1) id 13DtT5-0002Ai-00; Sun, 16 Jul 2000 20:48:47 +0200 Received: from p3e9c1125.dip0.t-ipconnect.de ([62.156.17.37] helo=neutron.cichlids.com) by mx2.silyn-tek.de with esmtp (Exim 3.13 #1) id 13DtT2-0001oX-00; Sun, 16 Jul 2000 20:48:44 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id B0AE4AB91; Sun, 16 Jul 2000 20:50:11 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 470B714A62; Sun, 16 Jul 2000 20:48:43 +0200 (CEST) Date: Sun, 16 Jul 2000 20:48:43 +0200 To: Andreas Klemm Cc: current@FreeBSD.ORG Subject: Re: make or fetch problem: hitting ^C doesn't terminate fetch process Message-ID: <20000716204843.A2185@cichlids.cichlids.com> Mail-Followup-To: Andreas Klemm , current@FreeBSD.ORG References: <20000716200650.A25974@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000716200650.A25974@titan.klemm.gtn.com>; from andreas@klemm.gtn.com on Sun, Jul 16, 2000 at 08:06:50PM +0200 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. From: alex@big.endian.de (Alexander Langer) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Also sprach Andreas Klemm (andreas@klemm.gtn.com): > I'm using -current of yesterday and tcsh. > When installing a FreeBSD port and I interrupt a "make all install clean" > session, when make is in the "make fetch target", the fetch process isn't > killed and continues to run alone although the "make" is terminated. This is correct - same here. Very annoying while updating ports :-( Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 12:26:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 5F17F37B71F; Sun, 16 Jul 2000 12:26:33 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 9F6E81C64; Sun, 16 Jul 2000 15:26:31 -0400 (EDT) Date: Sun, 16 Jul 2000 15:26:31 -0400 From: Bill Fumerola To: Mark Murray Cc: "Andrey A. Chernov" , markm@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak Message-ID: <20000716152631.G51462@jade.chc-chimes.com> References: <20000716105943.A60072@freebsd.org> <200007161826.UAA03911@grimreaper.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200007161826.UAA03911@grimreaper.grondar.za>; from mark@grondar.za on Sun, Jul 16, 2000 at 08:26:44PM +0200 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 16, 2000 at 08:26:44PM +0200, Mark Murray wrote: > Gotcha - fix coming; I need to stash some randomness at shutdown time, and > use that to reseed the RNG at reboot time. ... and for installations where ssh-keygen is run the first time the system boots? -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 12:41:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 6BED837B609 for ; Sun, 16 Jul 2000 12:41:31 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id VAA04096; Sun, 16 Jul 2000 21:42:29 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007161942.VAA04096@grimreaper.grondar.za> To: Bill Fumerola Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <20000716152631.G51462@jade.chc-chimes.com> In-Reply-To: <20000716152631.G51462@jade.chc-chimes.com> ; from Bill Fumerola "Sun, 16 Jul 2000 15:26:31 -0400." Date: Sun, 16 Jul 2000 21:42:29 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Jul 16, 2000 at 08:26:44PM +0200, Mark Murray wrote: > > > Gotcha - fix coming; I need to stash some randomness at shutdown time, and > > use that to reseed the RNG at reboot time. > > ... and for installations where ssh-keygen is run the first time > the system boots? The situation is _worse_; the entropy is minimal, and is _very_ attackable. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 12:55: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 42BBF37B6D6; Sun, 16 Jul 2000 12:55:02 -0700 (PDT) Date: Sun, 16 Jul 2000 12:55:02 -0700 From: "Andrey A. Chernov" To: Mark Murray Cc: Bill Fumerola , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak Message-ID: <20000716125502.B89979@freebsd.org> References: <20000716152631.G51462@jade.chc-chimes.com> <200007161942.VAA04096@grimreaper.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <200007161942.VAA04096@grimreaper.grondar.za>; from mark@grondar.za on Sun, Jul 16, 2000 at 09:42:29PM +0200 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 16, 2000 at 09:42:29PM +0200, Mark Murray wrote: > > On Sun, Jul 16, 2000 at 08:26:44PM +0200, Mark Murray wrote: > > > > > Gotcha - fix coming; I need to stash some randomness at shutdown time, and > > > use that to reseed the RNG at reboot time. > > > > ... and for installations where ssh-keygen is run the first time > > the system boots? > > The situation is _worse_; the entropy is minimal, and is _very_ attackable. What's wrong about timers for enthropy (I mean high resolution ones)? Really we need only few bytes of enthropy and can use them to seed RNG for the first time if no true randomness available. To be joking: MD5 of kernel module can help too :-) -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 12:58:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 41DA437B609 for ; Sun, 16 Jul 2000 12:58:30 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 7212 invoked from network); 16 Jul 2000 19:58:24 -0000 Received: from acs-24-154-24-131.zoominternet.net (HELO cvzoom.net) (24.154.24.131) by ns.cvzoom.net with SMTP; 16 Jul 2000 19:58:24 -0000 Message-ID: <397213E0.F732E3B6@cvzoom.net> Date: Sun, 16 Jul 2000 15:58:24 -0400 From: Donn Miller X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: "NO_MODULES" in /etc/make.conf broken? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Recently, when building a kernel (about 20 minutes as of this email), I set NO_MODULES= false in /etc/make.conf. The modules still weren't built with the kernel. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 13:21: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 47F1937B681; Sun, 16 Jul 2000 13:20:56 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id NAA03949; Sun, 16 Jul 2000 13:29:50 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007162029.NAA03949@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Andrey A. Chernov" Cc: markm@freebsd.org, current@freebsd.org Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Sun, 16 Jul 2000 10:59:45 PDT." <20000716105943.A60072@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 16 Jul 2000 13:29:50 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I found that I always got the same fortune quote after reboot, over and over > again. It means that /dev/random produce exact the same values after reboot. > It means that machine timer or keyboard not used for enthropy gathering. > Using keyboard alone not helps for automatic tasks because it can be even not > present, so machine timer must be used at least after reboot stage i.e. in > randomdev init procedure. Otherwise first random values are very predictable > and subject for attack. The problem is that the randomdev stuff should be a delete option, ie. it should be built as part of the kernel unless EXPLICITLY excluded, not the wrong way around as it is at the moment. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 13:47:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 392F137B5C5 for ; Sun, 16 Jul 2000 13:47:19 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id QAA27702; Sun, 16 Jul 2000 16:46:59 -0400 (EDT) Message-ID: <20000716164658.A25557@netmonger.net> Date: Sun, 16 Jul 2000 16:46:58 -0400 From: Christopher Masto To: Garance A Drosihn , "Louis A. Mamakos" Cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: Request for comments: new `lpd' suite feature References: <200007142139.RAA88779@khavrinen.lcs.mit.edu> <200007150409.AAA32685@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Garance A Drosihn on Sun, Jul 16, 2000 at 02:32:18PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 16, 2000 at 02:32:18PM -0400, Garance A Drosihn wrote: > At 12:09 AM -0400 7/15/00, Louis A. Mamakos wrote: > >I almost hate to bring this up, but I think the unnamed-here > >proposed replacement for our lpd allows you to set your PRINTER > >environment variable to something like > > > > PRINTER=queuename@spooler.do.main > > > >louie > > For what it's worth, I think that feature is a little too helpful, > and I would not want that ability on our (RPI) public unix > workstations. I do want some capability to specify a hostname, > but not a wide-open capability to specify any hostname. Huh? Security through ignorance? -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 14:31:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id B6D1C37B7F0 for ; Sun, 16 Jul 2000 14:31:44 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 4E8B4942; Sun, 16 Jul 2000 14:31:44 -0700 (PDT) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) with ESMTP id OAA02747; Sun, 16 Jul 2000 14:31:43 -0700 (PDT) Message-ID: <397229BF.12150F34@cup.hp.com> Date: Sun, 16 Jul 2000 14:31:43 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: "NO_MODULES" in /etc/make.conf broken? References: <397213E0.F732E3B6@cvzoom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Donn Miller wrote: > > Recently, when building a kernel (about 20 minutes as of this email), > I set > > NO_MODULES= false > > in /etc/make.conf. The modules still weren't built with the kernel. The value is normally unimportant, thus NO_MODULES=false == NO_MODULES=true == ... To enable modules, remove or comment out the NO_MODULES line. HTH, -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 15: 0:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 2C67237B7A8; Sun, 16 Jul 2000 15:00:45 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA86441; Sun, 16 Jul 2000 15:00:45 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 16 Jul 2000 15:00:44 -0700 (PDT) From: Kris Kennaway To: Mark Murray Cc: Bill Fumerola , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007161942.VAA04096@grimreaper.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 16 Jul 2000, Mark Murray wrote: > > On Sun, Jul 16, 2000 at 08:26:44PM +0200, Mark Murray wrote: > > > > > Gotcha - fix coming; I need to stash some randomness at shutdown time, and > > > use that to reseed the RNG at reboot time. > > > > ... and for installations where ssh-keygen is run the first time > > the system boots? > > The situation is _worse_; the entropy is minimal, and is _very_ attackable. ssh-keygen should just block until it gets enough - this is not acceptable behaviour if /dev/urandom is returning unseeded data. OpenSSL uses /dev/urandom at the moment - I just read a comment in md_rand.c that using /dev/random may block, which I didn't think was true. On the other hand, doing a dd if=/dev/random of=/dev/null gives me infinite "randomness" at 10MB/sec - have the semantics of /dev/random changed? Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 15: 4: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 1005237B8D6; Sun, 16 Jul 2000 15:04:03 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA86688; Sun, 16 Jul 2000 15:04:02 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 16 Jul 2000 15:04:02 -0700 (PDT) From: Kris Kennaway To: Andreas Klemm Cc: Mark Murray , Current Subject: Re: missing idea.h, still conflicting defines WITH_IDEA and MAKE_IDEA In-Reply-To: <20000716141318.A80785@titan.klemm.gtn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 16 Jul 2000, Andreas Klemm wrote: > Something seems to be wrong with the logic concerning IDEA stuff. > I ask because I can't build the security/p5-Net-SSLeay port anymore > which is for example needed for webmin. Compare r1.2 of /usr/src/crypto/openssl/crypto/evp/evp.h with r1.4. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 17: 0: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 25A2E37B643 for ; Sun, 16 Jul 2000 16:59:59 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id TAA00352; Sun, 16 Jul 2000 19:59:54 -0400 (EDT) (envelope-from wollman) Date: Sun, 16 Jul 2000 19:59:54 -0400 (EDT) From: Garrett Wollman Message-Id: <200007162359.TAA00352@khavrinen.lcs.mit.edu> To: "Rodney W. Grimes" Cc: freebsd-current@FreeBSD.ORG Subject: Re: dc driver and underruns (was: Strangeness with 4.0-S) In-Reply-To: <200007161841.LAA23975@gndrsh.dnsmgr.net> References: <200007160809.SAA21950@dungeon.home> <200007161841.LAA23975@gndrsh.dnsmgr.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Ohh... and a finally note, DEC blew the chip design by only including > a 160byte threshold point given that PCI 2.0 spec says it should have > been 500bytes!! It wouldn't be the first thing DEC had screwed up in the design of these NICs. On the other hand, Intel has owned the silicon for a couple of years now, which is more than enough time to unscrew it if they really wanted to. Clearly, they'd rather be selling 82559s.... -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 17:15:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 5B1FD37B644 for ; Sun, 16 Jul 2000 17:15:08 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id UAA00415; Sun, 16 Jul 2000 20:15:05 -0400 (EDT) (envelope-from wollman) Date: Sun, 16 Jul 2000 20:15:05 -0400 (EDT) From: Garrett Wollman Message-Id: <200007170015.UAA00415@khavrinen.lcs.mit.edu> To: Christopher Masto Cc: Garance A Drosihn , "Louis A. Mamakos" , Garrett Wollman , current@FreeBSD.ORG Subject: Re: Request for comments: new `lpd' suite feature In-Reply-To: <20000716164658.A25557@netmonger.net> References: <200007142139.RAA88779@khavrinen.lcs.mit.edu> <200007150409.AAA32685@whizzo.transsys.com> <20000716164658.A25557@netmonger.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Huh? Security through ignorance? Remember that `lpr' is setuid-root and uses a ``privileged'' port for its communications. Many sites may still be using trusted-host ``authentication'' internally, and LPRng's ``feature'' may enable a compromise of some such service. (Got enough scare quotes there?) -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 17:23:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id E47DF37B644 for ; Sun, 16 Jul 2000 17:23:10 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA15861; Sun, 16 Jul 2000 17:23:03 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id RAA08127; Sun, 16 Jul 2000 17:23:01 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sun, 16 Jul 2000 17:23:01 -0700 (PDT) Message-Id: <200007170023.RAA08127@vashon.polstra.com> To: gjohnson@gs.verio.net Subject: Re: rtld-elf In-Reply-To: <000c01bfeef3$8c71b8f0$4a7c01cc@gs.verio.net> References: <00cf01bfed15$43ab2910$4a7c01cc@gs.verio.net> <200007152234.PAA05700@vashon.polstra.com> <000c01bfeef3$8c71b8f0$4a7c01cc@gs.verio.net> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <000c01bfeef3$8c71b8f0$4a7c01cc@gs.verio.net>, Tony Johnson wrote: > So on Friday Morning, I deleted all my cvs source code and cvsup > all new copies from scratch. I did a make world and the compile > finished successfully. Whew, you had me worried for awhile there. Thanks for the follow-up. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 17:37:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 6A77B37B63D for ; Sun, 16 Jul 2000 17:37:20 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id RAA24682; Sun, 16 Jul 2000 17:37:01 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200007170037.RAA24682@gndrsh.dnsmgr.net> Subject: Re: dc driver and underruns (was: Strangeness with 4.0-S) In-Reply-To: <200007162359.TAA00352@khavrinen.lcs.mit.edu> from Garrett Wollman at "Jul 16, 2000 07:59:54 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Sun, 16 Jul 2000 17:37:00 -0700 (PDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > > Ohh... and a finally note, DEC blew the chip design by only including > > a 160byte threshold point given that PCI 2.0 spec says it should have > > been 500bytes!! > > It wouldn't be the first thing DEC had screwed up in the design of > these NICs. On the other hand, Intel has owned the silicon for a > couple of years now, which is more than enough time to unscrew it if > they really wanted to. Clearly, they'd rather be selling 82559s.... As far as I can tell the fxp driver doesn't even use the tx_fifo in the 825xxx chips :-) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 18:36: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 1EB9437B7B9 for ; Sun, 16 Jul 2000 18:36:01 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id SAA05503; Sun, 16 Jul 2000 18:44:33 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007170144.SAA05503@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Garrett Wollman Cc: "Rodney W. Grimes" , freebsd-current@FreeBSD.ORG Subject: Re: dc driver and underruns (was: Strangeness with 4.0-S) In-reply-to: Your message of "Sun, 16 Jul 2000 19:59:54 EDT." <200007162359.TAA00352@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 16 Jul 2000 18:44:32 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > > Ohh... and a finally note, DEC blew the chip design by only including > > a 160byte threshold point given that PCI 2.0 spec says it should have > > been 500bytes!! > > It wouldn't be the first thing DEC had screwed up in the design of > these NICs. On the other hand, Intel has owned the silicon for a > couple of years now, which is more than enough time to unscrew it if > they really wanted to. Clearly, they'd rather be selling 82559s.... You're going to barf when I tell you that the ethernet component in the new ICH2 (PIIX4 equivalent in the new low-cost 815 chipset) looks like an 82586... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 18:41:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 791C137B7C9 for ; Sun, 16 Jul 2000 18:41:09 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id SAA23924 for ; Sun, 16 Jul 2000 18:41:08 -0700 Date: Sun, 16 Jul 2000 18:41:08 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: mfs_badop... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG any reason that we should be seeing these now: mfs_badop[vop_getwritemount] mfs_badop[vop_getwritemount] = 45 mfs_badop[vop_getwritemount] mfs_badop[vop_getwritemount] = 45 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 19:28:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 1CBE337B6AB for ; Sun, 16 Jul 2000 19:28:43 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id TAA23537; Sun, 16 Jul 2000 19:14:30 -0700 (PDT) Message-Id: <200007170214.TAA23537@implode.root.com> To: "Rodney W. Grimes" Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), freebsd-current@FreeBSD.ORG Subject: Re: dc driver and underruns (was: Strangeness with 4.0-S) In-reply-to: Your message of "Sun, 16 Jul 2000 17:37:00 PDT." <200007170037.RAA24682@gndrsh.dnsmgr.net> From: David Greenman Reply-To: dg@root.com Date: Sun, 16 Jul 2000 19:14:30 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> < said: >> >> > Ohh... and a finally note, DEC blew the chip design by only including >> > a 160byte threshold point given that PCI 2.0 spec says it should have >> > been 500bytes!! >> >> It wouldn't be the first thing DEC had screwed up in the design of >> these NICs. On the other hand, Intel has owned the silicon for a >> couple of years now, which is more than enough time to unscrew it if >> they really wanted to. Clearly, they'd rather be selling 82559s.... > >As far as I can tell the fxp driver doesn't even use the tx_fifo in the >825xxx chips :-) The 82557-9 have a 2KB internal buffer for transmits. They don't start transmitting until a programmed threshold is reached - this is to insure that PCI bus latency doesn't result in the transmitter getting stalled. The fxp driver starts out with this threshold set at 512 bytes, but will increase it (512 bytes at a time) when a DMA underrun occurs. Of course once the threshold reached 1536, then an entire 1500 byte packet is DMA'd into the buffer before the transmit begins. There is buffering on the receive side as well, but I don't recall off hand how large that is (although I think it's 2KB as well). -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org Manufacturer of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 19:31:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 4446737B878 for ; Sun, 16 Jul 2000 19:31:26 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id WAA14779; Sun, 16 Jul 2000 22:31:11 -0400 (EDT) Message-ID: <20000716223110.A11344@netmonger.net> Date: Sun, 16 Jul 2000 22:31:10 -0400 From: Christopher Masto To: Garrett Wollman Cc: Garance A Drosihn , "Louis A. Mamakos" , current@FreeBSD.ORG Subject: Re: Request for comments: new `lpd' suite feature References: <200007142139.RAA88779@khavrinen.lcs.mit.edu> <200007150409.AAA32685@whizzo.transsys.com> <20000716164658.A25557@netmonger.net> <200007170015.UAA00415@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <200007170015.UAA00415@khavrinen.lcs.mit.edu>; from Garrett Wollman on Sun, Jul 16, 2000 at 08:15:05PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 16, 2000 at 08:15:05PM -0400, Garrett Wollman wrote: > < said: > > > Huh? Security through ignorance? > > Remember that `lpr' is setuid-root and uses a ``privileged'' port for > its communications. Many sites may still be using trusted-host > ``authentication'' internally, and LPRng's ``feature'' may enable a > compromise of some such service. (Got enough scare quotes there?) That is indeed something I failed to consider. I suppose it would be necessary to have some control over that feature in some environments. I just find it incredibly convenient to be able to install LPRng on a bunch of client machines and just rm /etc/printcap, set $PRINTER, and be done with it. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 21:30:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 470AB37BA2F; Sun, 16 Jul 2000 21:30:05 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 3.15 #1) id 13E2X1-000HVO-00; Mon, 17 Jul 2000 11:29:27 +0700 Date: Mon, 17 Jul 2000 11:29:27 +0700 (ALMST) From: Boris Popov To: Mike Smith Cc: "Andrey A. Chernov" , markm@freebsd.org, current@freebsd.org Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007162029.NAA03949@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 16 Jul 2000, Mike Smith wrote: > The problem is that the randomdev stuff should be a delete option, ie. it > should be built as part of the kernel unless EXPLICITLY excluded, not the > wrong way around as it is at the moment. Exactly, randomdev should be compiled-in by default. This way it will make much less problems than it does now. -- Boris Popov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 21:51:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id EB9F637BA6C for ; Sun, 16 Jul 2000 21:50:37 -0700 (PDT) (envelope-from clefevre%no-spam@citeweb.net) Received: (qmail 15401862 invoked from network); 17 Jul 2000 04:50:36 -0000 Received: from r224m65.cybercable.tm.fr (HELO gits.dyndns.org) ([195.132.224.65]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 17 Jul 2000 04:50:36 -0000 Received: (from root@localhost) by gits.dyndns.org (8.9.3/8.9.3) id GAA45817; Mon, 17 Jul 2000 06:50:32 +0200 (CEST) (envelope-from clefevre%no-spam@citeweb.net) Posted-Date: Mon, 17 Jul 2000 06:50:32 +0200 (CEST) To: Christopher Masto Cc: Garrett Wollman , Garance A Drosihn , "Louis A. Mamakos" , current@FreeBSD.ORG Subject: Re: Request for comments: new `lpd' suite feature References: <200007142139.RAA88779@khavrinen.lcs.mit.edu> <200007150409.AAA32685@whizzo.transsys.com> <20000716164658.A25557@netmonger.net> <200007170015.UAA00415@khavrinen.lcs.mit.edu> <20000716223110.A11344@netmonger.net> Reply-To: clefevre@citeweb.net X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C From: Cyrille Lefevre Date: 17 Jul 2000 06:50:31 +0200 In-Reply-To: Christopher Masto's message of "Sun, 16 Jul 2000 22:31:10 -0400" Message-ID: Lines: 24 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Canyonlands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christopher Masto writes: > On Sun, Jul 16, 2000 at 08:15:05PM -0400, Garrett Wollman wrote: > > < said: > > > > > Huh? Security through ignorance? > > > > Remember that `lpr' is setuid-root and uses a ``privileged'' port for > > its communications. Many sites may still be using trusted-host > > ``authentication'' internally, and LPRng's ``feature'' may enable a > > compromise of some such service. (Got enough scare quotes there?) > > That is indeed something I failed to consider. I suppose it would be > necessary to have some control over that feature in some environments. > I just find it incredibly convenient to be able to install LPRng on > a bunch of client machines and just rm /etc/printcap, set $PRINTER, > and be done with it. as I remeber me, the same thing is possible under newer Solaris boxes. Cyrille. -- home:mailto:clefevre%no-spam@citeweb.net Supprimer "%no-spam" pour me repondre. work:mailto:Cyrille.Lefevre%no-spam@edf.fr Remove "%no-spam" to answer me back. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 21:54:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from hawaii.rr.com (hnlmail2.hawaii.rr.com [24.25.227.35]) by hub.freebsd.org (Postfix) with ESMTP id 2C5DA37BA0C; Sun, 16 Jul 2000 21:54:44 -0700 (PDT) (envelope-from yukarimail@mcn.ne.jp) Received: from localhost ([24.31.88.158]) by hawaii.rr.com with Microsoft SMTPSVC(5.5.1877.447.44); Sun, 16 Jul 2000 18:49:07 -1000 X-Sender: yukarimail@mcn.ne.jp From: Yukari To: "hi" Date: Sun, 16 Jul 2000 18:47:13 -1000 Subject: ŽÐ‰ï•×‹­ MIME-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Message-ID: <008e70749041170HNLMAIL2@hawaii.rr.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ‚¨‚ß‚Å‚Æ‚¤I ‡Šij‚¢‚¾‚æ`B ‚È‚ñ‚ÆAu¶ƒGƒbƒ`v‚ªŒ©‚ê‚é‚æB ‚µ‚©‚àAƒ^ƒ_‚È‚Ì‚¾B ŽÐ‰ï•×‹­‚Ì‚½‚ß‚ÉŒ©‚Ä‚¿‚åB http://216.101.214.74/LoveLovePussyKing/index-namasex.html ‚»‚ꂶ‚áA‚Ü‚½‚Ë[B ‚ä‚©‚è To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 22: 8:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from rtp.tfd.com (rtp.tfd.com [198.79.53.206]) by hub.freebsd.org (Postfix) with ESMTP id 5781237B8B9 for ; Sun, 16 Jul 2000 22:08:47 -0700 (PDT) (envelope-from kent@lab1.tfd.com) Received: from lab1.tfd.com (lab1.tfd.com [10.9.200.31]) by rtp.tfd.com (8.9.3/8.9.3) with SMTP id BAA12239 for ; Mon, 17 Jul 2000 01:06:36 -0400 (EDT) Received: by lab1.tfd.com id AA23307 (5.67b/IDA-1.5 for current@freebsd.org); Mon, 17 Jul 2000 01:05:45 -0400 Date: Mon, 17 Jul 2000 01:05:45 -0400 From: Kent Hauser Message-Id: <200007170505.AA23307@lab1.tfd.com> To: current@freebsd.org Subject: FIXIT problems with /dev Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, I just did something foolhardy -- and yet instructive. Pls let me relate. As I had polluted my system with an unstable recent CURRENT, I decided to rebuild from a more stable CURRENT. I (eventually) choose "cvs co -D 2000.06.21.04.00". Works great. Given the difficulty in finding working version, I decided to build "install" and "fixit" CDs to assist my future return should I need it. (make release not supporting cvs -D options only a minor difficulty). I ran into problems when I when I (stupidly) went to clean up my /dev directory (which probably dates from 2.x). After I successfully booted from the fixit CD & exited into the shell, I mounted my root, cd'd into dev & rm'd -rf [a-z]*. The subsequent sh MAKEDEV all, et al, is the source of my comments. 1) The PATH statements in MAKEDEV are inappropriate for fixit CD. The PATH variable in MAKEDEV is overridden to either "MAKEDEVPATH" or /bin:/sbin. The appropriate binaries are under /mnt2 or /dist. MAKEDEVPATH should be set or this override should be enhanced. As it exists, MAKEDEV can't find things such as '[', 'expr', etc. 2) Not all of the groups mentioned in MAKEDEV are listed in the FIXIT /etc/groups. Thus "sh MAKEDEV all" fails. To rebuild my "/mnt/dev" I had to execute "cp /mnt/etc/group /etc". 3) MAKEDEV executes "/sbin/mknod" as part of it's "mknod" function. This fails under the FIXIT environment as "/sbin/mknod" doesn't exit. I had to execute "mv /sbin /sbin.x;ln -s dist/sbin /sbin" to get things pointing right. I suggest that the MAKEDEV "mknod" function be renamed & execute the mknod binary via the PATH. 4) I have a PCI UDMA66 controller, so my root disk appears as "ad4". I also have a W98 partition, so my real root disk is "ad4s2a". This is challanging to get under the FIXIT cd. I had to (under csh): sh -x MAKEDEV ad4s2{a,b,c,d,e,f,g,h} This seems excessive. Please don't interpret the above as a complaint. Just as the comments as someone who stupidly tried to rebuild "/dev" via a FIXIT cd. Regards, Kent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 23: 6:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 1BC3C37B523; Sun, 16 Jul 2000 23:06:37 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id IAA05866; Mon, 17 Jul 2000 08:07:43 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007170607.IAA05866@grimreaper.grondar.za> To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <20000716125502.B89979@freebsd.org> In-Reply-To: <20000716125502.B89979@freebsd.org> ; from "Andrey A. Chernov" "Sun, 16 Jul 2000 12:55:02 MST." Date: Mon, 17 Jul 2000 08:07:43 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The situation is _worse_; the entropy is minimal, and is _very_ attackable. > > What's wrong about timers for enthropy (I mean high resolution ones)? > Really we need only few bytes of enthropy and can use them to seed RNG for the > first time if no true randomness available. To be joking: MD5 of kernel module > can help too :-) getnanotime() is already extensively used; we just need to force the RNG to reseed once at the beginning. As soon as I'm happy that the code is panic-free, I'll commit it. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 23:10:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 4859C37B6A3; Sun, 16 Jul 2000 23:10:04 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id IAA05883; Mon, 17 Jul 2000 08:11:11 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007170611.IAA05883@grimreaper.grondar.za> To: Mike Smith Cc: current@freebsd.org Subject: Re: randomdev entropy gathering is really weak References: <200007162029.NAA03949@mass.osd.bsdi.com> In-Reply-To: <200007162029.NAA03949@mass.osd.bsdi.com> ; from Mike Smith "Sun, 16 Jul 2000 13:29:50 MST." Date: Mon, 17 Jul 2000 08:11:11 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem is that the randomdev stuff should be a delete option, ie. it > should be built as part of the kernel unless EXPLICITLY excluded, not the > wrong way around as it is at the moment. I agree. Any objections? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 23:14:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 7D1C637B788; Sun, 16 Jul 2000 23:14:45 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id IAA05906; Mon, 17 Jul 2000 08:15:53 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007170615.IAA05906@grimreaper.grondar.za> To: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: In-Reply-To: ; from Kris Kennaway "Sun, 16 Jul 2000 15:00:44 MST." Date: Mon, 17 Jul 2000 08:15:53 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ssh-keygen should just block until it gets enough - this is not acceptable > behaviour if /dev/urandom is returning unseeded data. OpenSSL uses > /dev/urandom at the moment - I just read a comment in md_rand.c that using > /dev/random may block, which I didn't think was true. > > On the other hand, doing a dd if=/dev/random of=/dev/null gives me > infinite "randomness" at 10MB/sec - have the semantics of /dev/random > changed? Yes; remember that what we have here is Yarrow algorithm; which is an algorithm for cryptographically secure PRNG - one whose internal state is unguessable, or if compromised folr some reason is self-recovering. "Infinite" randomness is possible with this algorithm. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 16 23:24:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id E171A37B6A8; Sun, 16 Jul 2000 23:24:35 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id IAA00674; Mon, 17 Jul 2000 08:24:18 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mark Murray Cc: "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Mon, 17 Jul 2000 08:07:43 +0200." <200007170607.IAA05866@grimreaper.grondar.za> Date: Mon, 17 Jul 2000 08:24:18 +0200 Message-ID: <672.963815058@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007170607.IAA05866@grimreaper.grondar.za>, Mark Murray writes: >getnanotime() is already extensively used; I looked at that use, but as far as I can tell, it is only used as a flag at this time, the bits returned by getnanotime() does not end up in the entropy pool ? I'm not dissatisfied about that btw, the output from getnanotime() is not very random at all, unless you dive into the timecounter code to find out what the parameters are. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 0: 5: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 2F3AF37B7B4; Mon, 17 Jul 2000 00:04:59 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id AAA45279; Mon, 17 Jul 2000 00:04:59 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 17 Jul 2000 00:04:58 -0700 (PDT) From: Kris Kennaway To: Mark Murray Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007170615.IAA05906@grimreaper.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Mark Murray wrote: > > On the other hand, doing a dd if=/dev/random of=/dev/null gives me > > infinite "randomness" at 10MB/sec - have the semantics of /dev/random > > changed? > > Yes; remember that what we have here is Yarrow algorithm; which is an > algorithm for cryptographically secure PRNG - one whose internal state > is unguessable, or if compromised folr some reason is self-recovering. > > "Infinite" randomness is possible with this algorithm. On the other hand, didn't you say that at system boot the RNG is essentially unseeded, so this is actually a liability because processes cannot be sure they're getting real randomness. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 1:41:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (markm.ops.uunet.co.za [196.31.2.167]) by hub.freebsd.org (Postfix) with ESMTP id 938C537B816; Mon, 17 Jul 2000 01:41:26 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id KAA00475; Mon, 17 Jul 2000 10:42:42 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007170842.KAA00475@grimreaper.grondar.za> To: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: In-Reply-To: ; from Kris Kennaway "Mon, 17 Jul 2000 00:04:58 MST." Date: Mon, 17 Jul 2000 10:42:42 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 17 Jul 2000, Mark Murray wrote: > > > > On the other hand, doing a dd if=/dev/random of=/dev/null gives me > > > infinite "randomness" at 10MB/sec - have the semantics of /dev/random > > > changed? > > > > Yes; remember that what we have here is Yarrow algorithm; which is an > > algorithm for cryptographically secure PRNG - one whose internal state > > is unguessable, or if compromised folr some reason is self-recovering. > > > > "Infinite" randomness is possible with this algorithm. > > On the other hand, didn't you say that at system boot the RNG is > essentially unseeded, so this is actually a liability because processes > cannot be sure they're getting real randomness. Until you type or move the mouse. I'm putting the rest of the harvesting calls in today. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 1:41:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (markm.ops.uunet.co.za [196.31.2.167]) by hub.freebsd.org (Postfix) with ESMTP id 8F41C37B816; Mon, 17 Jul 2000 01:41:38 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id KAA00459; Mon, 17 Jul 2000 10:41:00 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007170841.KAA00459@grimreaper.grondar.za> To: Poul-Henning Kamp Cc: Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <672.963815058@critter.freebsd.dk> In-Reply-To: <672.963815058@critter.freebsd.dk> ; from Poul-Henning Kamp "Mon, 17 Jul 2000 08:24:18 +0200." Date: Mon, 17 Jul 2000 10:40:59 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <200007170607.IAA05866@grimreaper.grondar.za>, Mark Murray writes: > > >getnanotime() is already extensively used; > > I looked at that use, but as far as I can tell, it is only used as a > flag at this time, the bits returned by getnanotime() does not end up > in the entropy pool ? Not true; struct entropy contains nanotime and the harvested entropy; _both_ are hashed in the reseed operation. > I'm not dissatisfied about that btw, the output from getnanotime() > is not very random at all, unless you dive into the timecounter > code to find out what the parameters are. I agree that it is not (very) random; however cclock jitter and keystroke timing can help thwart the bad guys... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 6:22:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id C488837B978; Mon, 17 Jul 2000 06:22:11 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id JAA04774; Mon, 17 Jul 2000 09:19:25 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200007171319.JAA04774@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mark Murray Cc: Poul-Henning Kamp , "Andrey A. Chernov" , current@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: randomdev entropy gathering is really weak References: <672.963815058@critter.freebsd.dk> <200007170841.KAA00459@grimreaper.grondar.za> In-reply-to: Your message of "Mon, 17 Jul 2000 10:40:59 +0200." <200007170841.KAA00459@grimreaper.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Jul 2000 09:19:25 -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In message <200007170607.IAA05866@grimreaper.grondar.za>, Mark Murray writes: > > > > >getnanotime() is already extensively used; > > > > I looked at that use, but as far as I can tell, it is only used as a > > flag at this time, the bits returned by getnanotime() does not end up > > in the entropy pool ? > > Not true; struct entropy contains nanotime and the harvested entropy; > _both_ are hashed in the reseed operation. > > > I'm not dissatisfied about that btw, the output from getnanotime() > > is not very random at all, unless you dive into the timecounter > > code to find out what the parameters are. > > I agree that it is not (very) random; however cclock jitter and keystroke > timing can help thwart the bad guys... But do please keep in mind that many of my FreeBSD platforms have neither keyboard or mouse. And for the ones that do, they tend not to get used until long after the system boots. It's essential that the randomness harvesting also be driven off of other events, such as network interface or storage system interrupts for these environments. In fact, it would be rather interesting to have a configuration flag which always forces something like an fsck on a file system in order to provide some entropy to the random device. Or some other user-exposed way of providing entropy. I might have some data on disk, or some network operations which can be performed to help seed the entropy pool. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 6:37:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 570D637B958; Mon, 17 Jul 2000 06:37:13 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id PAA02452; Mon, 17 Jul 2000 15:36:59 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Louis A. Mamakos" Cc: Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Mon, 17 Jul 2000 09:19:25 EDT." <200007171319.JAA04774@whizzo.transsys.com> Date: Mon, 17 Jul 2000 15:36:59 +0200 Message-ID: <2450.963841019@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007171319.JAA04774@whizzo.transsys.com>, "Louis A. Mamakos" writ es: >In fact, it would be rather interesting to have a configuration flag which >always forces something like an fsck on a file system in order to provide >some entropy to the random device. Or some other user-exposed way of >providing entropy. I might have some data on disk, or some network >operations which can be performed to help seed the entropy pool. What we really need is this: fetch -o http://entropy.freebsd.org/ > /dev/random with a bunch of volounteers providing random bits to people in need. I have thought about adding a entropy server to my array of weird servers in my lab. Something like a Geiger counter and a smokedetector could do wonders. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 6:49:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout2.silyn-tek.de (mout2.silyn-tek.de [194.25.165.70]) by hub.freebsd.org (Postfix) with ESMTP id AA49E37B64D; Mon, 17 Jul 2000 06:49:30 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from [192.168.32.34] (helo=mx2.silyn-tek.de) by mout2.silyn-tek.de with esmtp (Exim 3.13 #1) id 13EBDZ-0006FV-00; Mon, 17 Jul 2000 15:45:57 +0200 Received: from p3e9c116d.dip0.t-ipconnect.de ([62.156.17.109] helo=neutron.cichlids.com) by mx2.silyn-tek.de with esmtp (Exim 3.13 #1) id 13EBDU-0007mk-00; Mon, 17 Jul 2000 15:45:52 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 3AD9CAB91; Mon, 17 Jul 2000 15:47:21 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 18F1514A62; Mon, 17 Jul 2000 15:45:50 +0200 (CEST) Date: Mon, 17 Jul 2000 15:45:49 +0200 To: Poul-Henning Kamp Cc: "Louis A. Mamakos" , Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak Message-ID: <20000717154549.A18676@cichlids.cichlids.com> Mail-Followup-To: Poul-Henning Kamp , "Louis A. Mamakos" , Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG References: <200007171319.JAA04774@whizzo.transsys.com> <2450.963841019@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <2450.963841019@critter.freebsd.dk>; from phk@critter.freebsd.dk on Mon, Jul 17, 2000 at 03:36:59PM +0200 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. From: alex@big.endian.de (Alexander Langer) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Poul-Henning Kamp (phk@critter.freebsd.dk): > I have thought about adding a entropy server to my array of weird > servers in my lab. Something like a Geiger counter and a smokedetector > could do wonders. HA! Cool! Do that please! I mean, seriously. And an option to sysinstall, where you can enable this as you can with ntpdate :) Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 6:58: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 60AF037B64D; Mon, 17 Jul 2000 06:57:59 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id PAA02615; Mon, 17 Jul 2000 15:57:36 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: alex@big.endian.de (Alexander Langer) Cc: "Louis A. Mamakos" , Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Mon, 17 Jul 2000 15:45:49 +0200." <20000717154549.A18676@cichlids.cichlids.com> Date: Mon, 17 Jul 2000 15:57:36 +0200 Message-ID: <2613.963842256@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000717154549.A18676@cichlids.cichlids.com>, Alexander Langer writ es: >Thus spake Poul-Henning Kamp (phk@critter.freebsd.dk): > >> I have thought about adding a entropy server to my array of weird >> servers in my lab. Something like a Geiger counter and a smokedetector >> could do wonders. > >HA! Cool! > >Do that please! > >I mean, seriously. >And an option to sysinstall, where you can enable this as you can with >ntpdate :) DuH! NTP is the perfect way to gather entropy at bootup! Predicting the clock's offset from reality and the two way path to the server of choice is impossible, plus if people enable authentication later on the packets will be choke full of high-quality entropy. We need an enterprising soul to add an option (default on) to ntpdate to write the received packets in toto to /dev/random if it exists. If somebody does this, I will spear-head the effort of getting it into the ntpv4 sources (Hmm, don't I have a commit bit there already ? Can't remember...) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 7: 6:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout1.silyn-tek.de (mout1.silyn-tek.de [194.25.165.69]) by hub.freebsd.org (Postfix) with ESMTP id CB22237B538; Mon, 17 Jul 2000 07:06:05 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from [192.168.32.34] (helo=mx2.silyn-tek.de) by mout1.silyn-tek.de with esmtp (Exim 3.13 #1) id 13EBTD-0007yl-00; Mon, 17 Jul 2000 16:02:07 +0200 Received: from p3e9c116d.dip0.t-ipconnect.de ([62.156.17.109] helo=neutron.cichlids.com) by mx2.silyn-tek.de with esmtp (Exim 3.13 #1) id 13EBT8-00081A-00; Mon, 17 Jul 2000 16:02:03 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id A1BA8AB91; Mon, 17 Jul 2000 16:03:33 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 0835114A62; Mon, 17 Jul 2000 16:02:05 +0200 (CEST) Date: Mon, 17 Jul 2000 16:02:04 +0200 From: Alexander Langer To: Poul-Henning Kamp Cc: "Louis A. Mamakos" , Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak Message-ID: <20000717160204.A19571@cichlids.cichlids.com> Mail-Followup-To: Poul-Henning Kamp , "Louis A. Mamakos" , Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG References: <20000717154549.A18676@cichlids.cichlids.com> <2613.963842256@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <2613.963842256@critter.freebsd.dk>; from phk@critter.freebsd.dk on Mon, Jul 17, 2000 at 03:57:36PM +0200 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Poul-Henning Kamp (phk@critter.freebsd.dk): > We need an enterprising soul to add an option (default on) to > ntpdate to write the received packets in toto to /dev/random > if it exists. If noone else wants to do it, I could take a look at it. Little time, though. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 7:12: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from sohara.dyndns.org (pooh.elsevier.nl [145.36.13.27]) by hub.freebsd.org (Postfix) with ESMTP id 84C2837B682 for ; Mon, 17 Jul 2000 07:12:00 -0700 (PDT) (envelope-from steve@sohara.dyndns.org) Received: (from steve@localhost) by sohara.dyndns.org (8.9.3/8.9.3) id PAA11171; Mon, 17 Jul 2000 15:17:03 +0100 (IST) (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <2613.963842256@critter.freebsd.dk> Date: Mon, 17 Jul 2000 15:17:02 +0100 (IST) From: "Steve O'Hara-Smith" To: Poul-Henning Kamp Subject: Re: randomdev entropy gathering is really weak Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jul-00 Poul-Henning Kamp wrote: > NTP is the perfect way to gather entropy at bootup! Only if in reach of an NTP server ? -- Steve O'Hara-Smith http://sohara.webhop.net/ A Better Way To Focus The Sun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 7:15: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 3B41F37B9A9 for ; Mon, 17 Jul 2000 07:14:56 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id QAA02800; Mon, 17 Jul 2000 16:14:50 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Steve O'Hara-Smith" Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Mon, 17 Jul 2000 15:17:02 BST." Date: Mon, 17 Jul 2000 16:14:50 +0200 Message-ID: <2798.963843290@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , "Steve O'Hara-Smith" writes : > >On 17-Jul-00 Poul-Henning Kamp wrote: >> NTP is the perfect way to gather entropy at bootup! > > Only if in reach of an NTP server ? Obviously :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 7:19:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.2.163]) by hub.freebsd.org (Postfix) with ESMTP id 3E4EC37B798 for ; Mon, 17 Jul 2000 07:19:31 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.15 #1) id 13EBjY-0005l2-00; Mon, 17 Jul 2000 16:19:00 +0200 From: Sheldon Hearn To: Makoto MATSUSHITA Cc: current@FreeBSD.ORG Subject: Re: MFS complains that no vop_getwritemount operation(?) In-reply-to: Your message of "Sun, 16 Jul 2000 01:11:16 +0900." <20000716011116B.matusita@jp.FreeBSD.org> Date: Mon, 17 Jul 2000 16:19:00 +0200 Message-ID: <22135.963843540@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 16 Jul 2000 01:11:16 +0900, Makoto MATSUSHITA wrote: > Jul 16 00:48:32 martini /kernel: mfs_badop[vop_getwritemount] > Jul 16 00:48:32 martini /kernel: mfs_badop[vop_getwritemount] = 45 > > I'm using MFS as /tmp filesystem, and this message shows up if I > access to /tmp directory such as create a file/directory. > > Following patch seems to shut up my kernel, but I dunno it is the > right fix for this problem (I've got a hint from ../ufs/ufs_vnops.c). Have you sent your patch to Kirk McKusick ? > Does anyone can reproduce mfs_badop[vop_getwritemount] warnings ? Yes, I got them until I switched to a malloc(9)-backed md(4) device. They seemed harmless. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 7:21:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.2.163]) by hub.freebsd.org (Postfix) with ESMTP id 3D85637BA46 for ; Mon, 17 Jul 2000 07:20:54 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.15 #1) id 13EBkm-0005lk-00; Mon, 17 Jul 2000 16:20:16 +0200 From: Sheldon Hearn To: mjacob@feral.com Cc: current@FreeBSD.ORG Subject: Re: mfs_badop... In-reply-to: Your message of "Sun, 16 Jul 2000 18:41:08 MST." Date: Mon, 17 Jul 2000 16:20:16 +0200 Message-ID: <22179.963843616@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 16 Jul 2000 18:41:08 MST, Matthew Jacob wrote: > any reason that we should be seeing these now: > > mfs_badop[vop_getwritemount] > mfs_badop[vop_getwritemount] = 45 I suspect that these relate to the import of ffs snapshots. I've mailed Kirk, and someone else has posted a tentative patch to this list. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 7:43: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from castle.jp.freebsd.org (castle.jp.freebsd.org [210.226.20.15]) by hub.freebsd.org (Postfix) with ESMTP id 9E8E937B9CF for ; Mon, 17 Jul 2000 07:43:00 -0700 (PDT) (envelope-from matusita@jp.freebsd.org) Received: from localhost (localhost [127.0.0.1]) by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id XAA59526; Mon, 17 Jul 2000 23:42:47 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: current@FreeBSD.ORG In-Reply-To: <22135.963843540@axl.ops.uunet.co.za> References: <20000716011116B.matusita@jp.FreeBSD.org> <22135.963843540@axl.ops.uunet.co.za> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Molpe) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 11 From: Makoto MATSUSHITA To: sheldonh@uunet.co.za Subject: Re: MFS complains that no vop_getwritemount operation(?) Date: Mon, 17 Jul 2000 23:42:43 +0900 Message-Id: <20000717234243H.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sheldonh> Have you sent your patch to Kirk McKusick ? No, not yet. It seems that this change is incoroprated with FFS snapshots feature, but I cannot decide it's true or not; other filesystem are modified also (see commitlogs), but mfs is not changed... Anyway, I'll try to email later. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 7:54:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (markm.ops.uunet.co.za [196.31.2.167]) by hub.freebsd.org (Postfix) with ESMTP id B5A2037BA03 for ; Mon, 17 Jul 2000 07:54:01 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id QAA00856; Mon, 17 Jul 2000 16:54:55 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007171454.QAA00856@grimreaper.grondar.za> To: "Louis A. Mamakos" Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <200007171319.JAA04774@whizzo.transsys.com> In-Reply-To: <200007171319.JAA04774@whizzo.transsys.com> ; from "Louis A. Mamakos" "Mon, 17 Jul 2000 09:19:25 -0400." Date: Mon, 17 Jul 2000 16:54:54 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I agree that it is not (very) random; however cclock jitter and keystroke > > timing can help thwart the bad guys... > > But do please keep in mind that many of my FreeBSD platforms have neither > keyboard or mouse. And for the ones that do, they tend not to get used > until long after the system boots. It's essential that the randomness > harvesting also be driven off of other events, such as network interface > or storage system interrupts for these environments. Agreed. I have already committed a "persistent" entropy cache that reseeds the random device on reboot. > In fact, it would be rather interesting to have a configuration flag which > always forces something like an fsck on a file system in order to provide > some entropy to the random device. Or some other user-exposed way of > providing entropy. I might have some data on disk, or some network > operations which can be performed to help seed the entropy pool. I'm (er, phk is) looking at hooking namei() in some way. I'm also going to hook the networking stack. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 8: 1: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (markm.ops.uunet.co.za [196.31.2.167]) by hub.freebsd.org (Postfix) with ESMTP id AA7BE37B582 for ; Mon, 17 Jul 2000 08:00:49 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id QAA00888; Mon, 17 Jul 2000 16:59:50 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007171459.QAA00888@grimreaper.grondar.za> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <2450.963841019@critter.freebsd.dk> In-Reply-To: <2450.963841019@critter.freebsd.dk> ; from Poul-Henning Kamp "Mon, 17 Jul 2000 15:36:59 +0200." Date: Mon, 17 Jul 2000 16:59:50 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What we really need is this: > > fetch -o http://entropy.freebsd.org/ > /dev/random For this to work, you'll need to encrypt the traffic. fetch -o https://entropy.freebsd.org/ > /dev/random ^ If the world knows what they are, your bits aren't random enough. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 8:25:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (blizzard.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id C280137BA13 for ; Mon, 17 Jul 2000 08:25:10 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.106]) by blizzard.sabbo.net (8.9.1/8.9.3) with ESMTP id RAA27844; Mon, 17 Jul 2000 17:59:57 +0300 (EEST) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.9.3/8.9.3) with ESMTP id SAA17491; Mon, 17 Jul 2000 18:01:28 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <39731FC5.34D3074D@FreeBSD.org> Date: Mon, 17 Jul 2000 18:01:25 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.73 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Mark Murray Cc: "Louis A. Mamakos" , current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: <200007171319.JAA04774@whizzo.transsys.com> <200007171454.QAA00856@grimreaper.grondar.za> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > > > I agree that it is not (very) random; however cclock jitter and keystroke > > > timing can help thwart the bad guys... > > > > But do please keep in mind that many of my FreeBSD platforms have neither > > keyboard or mouse. And for the ones that do, they tend not to get used > > until long after the system boots. It's essential that the randomness > > harvesting also be driven off of other events, such as network interface > > or storage system interrupts for these environments. > > Agreed. I have already committed a "persistent" entropy cache that > reseeds the random device on reboot. > You may also want to extend /etc/crontab to periodically save entropy. This would help if something unexpected like halt(8) or panic(9) happened. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 8:27:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id F0BC837B9AB for ; Mon, 17 Jul 2000 08:27:00 -0700 (PDT) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id RAA91679; Mon, 17 Jul 2000 17:26:56 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id RAA60167; Mon, 17 Jul 2000 17:08:35 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Mon, 17 Jul 2000 17:08:35 +0200 (CEST) From: Leif Neland To: "Steve O'Hara-Smith" Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Steve O'Hara-Smith wrote: > > On 17-Jul-00 Poul-Henning Kamp wrote: > > NTP is the perfect way to gather entropy at bootup! > > Only if in reach of an NTP server ? > If you can't reach a NTP server, you are not connected to the internet. In that case you don't need to worry so much about security... Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 8:34:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from sohara.dyndns.org (pooh.elsevier.nl [145.36.13.27]) by hub.freebsd.org (Postfix) with ESMTP id BEDBA37BD71 for ; Mon, 17 Jul 2000 08:34:36 -0700 (PDT) (envelope-from steve@sohara.dyndns.org) Received: (from steve@localhost) by sohara.dyndns.org (8.9.3/8.9.3) id QAA11369; Mon, 17 Jul 2000 16:41:56 +0100 (IST) (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 17 Jul 2000 16:41:55 +0100 (IST) From: "Steve O'Hara-Smith" To: Leif Neland Subject: Re: randomdev entropy gathering is really weak Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jul-00 Leif Neland wrote: > If you can't reach a NTP server, you are not connected to the internet. In > that case you don't need to worry so much about security... Not clear. I might not be connected at boot time but could well become connected later. -- Steve O'Hara-Smith http://sohara.webhop.net/ A Better Way To Focus The Sun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 8:38:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.osd.bsdi.com (zippy.osd.bsdi.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id B36E737BA10 for ; Mon, 17 Jul 2000 08:38:55 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id IAA05843 for ; Mon, 17 Jul 2000 08:39:57 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: current@freebsd.org Subject: world breakage in -current (also breaks release) Date: Mon, 17 Jul 2000 08:39:57 -0700 Message-ID: <5840.963848397@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cd /usr/src; make -f Makefile.inc1 hierarchy cd /usr/src/etc; make distrib-dirs mtree -deLU -f /usr/src/etc/mtree/BSD.root.dist -p / mtree: illegal option -- L usage: mtree [-cdeinrUux] [-f spec] [-K key] [-k key] [-p path] [-s seed] [-X excludes] *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 8:39:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id 5040637BBA0 for ; Mon, 17 Jul 2000 08:39:16 -0700 (PDT) (envelope-from sam@inf.enst.fr) Received: from antinea.enst.fr (antinea.enst.fr [137.194.160.145]) by ada.eu.org (Postfix) with ESMTP id 925611909D; Mon, 17 Jul 2000 17:39:14 +0200 (CEST) Received: by antinea.enst.fr (Postfix, from userid 1000) id 3005A2C8; Mon, 17 Jul 2000 17:39:12 +0200 (CEST) To: current@freebsd.org Subject: New mtree needed for installation Mime-Version: 1.0 (generated by tm-edit 1.5) Content-Type: text/plain; charset=US-ASCII Date: 17 Jul 2000 17:39:12 +0200 Lines: 20 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Capitol Reef" From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-07-17-17-39-12+trackit+sam@inf.enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did a "make buildworld" then "make installworld", and: -------------------------------------------------------------- >>> Making hierarchy -------------------------------------------------------------- cd /usr/src; make -f Makefile.inc1 hierarchy cd /usr/src/etc; make distrib-dirs mtree -deLU -f /usr/src/etc/mtree/BSD.root.dist -p / mtree: illegal option -- L usage: mtree [-cdeinrUux] [-f spec] [-K key] [-k key] [-p path] [-s seed] [-X excludes] *** Error code 1 Of course, installing the new mtree first solves this, but it may be worth a note in UPDATING (or better, use the newly built mtree or do not require the use of the new -L option). Sam -- Samuel Tardieu -- sam@inf.enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 9:19:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 389A037B523 for ; Mon, 17 Jul 2000 09:19:04 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id SAA36126; Mon, 17 Jul 2000 18:18:40 +0200 (CEST) (envelope-from des@flood.ping.uio.no) To: current@freebsd.org Subject: ftpd 550 reply From: Dag-Erling Smorgrav Date: 17 Jul 2000 18:18:39 +0200 Message-ID: Lines: 7 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone else than me have trouble with ftpd reporting "550 not a plain file" instead of "550 no such file or directory" when the requested file does not exist? DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 9:31:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id E82C337B5CC; Mon, 17 Jul 2000 09:31:39 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id JAA33104; Mon, 17 Jul 2000 09:35:15 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200007171635.JAA33104@troutmask.apl.washington.edu> Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <39731FC5.34D3074D@FreeBSD.org> from Maxim Sobolev at "Jul 17, 2000 06:01:25 pm" To: Maxim Sobolev Date: Mon, 17 Jul 2000 09:35:15 -0700 (PDT) Cc: Mark Murray , "Louis A. Mamakos" , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev wrote: [Charset koi8-r unsupported, filtering to ASCII...] > Mark Murray wrote: > > > Agreed. I have already committed a "persistent" entropy cache that > > reseeds the random device on reboot. > > You may also want to extend /etc/crontab to periodically save entropy. > This would help if something unexpected like halt(8) or panic(9) happened. > I thought about a reseed daemon periodically saving entropy to, say, /var/log/entropy. But, a crontab entry would work just as well. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 9:37:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 265ED37BB5A for ; Mon, 17 Jul 2000 09:37:24 -0700 (PDT) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id MAA89246; Mon, 17 Jul 2000 12:37:21 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Mon, 17 Jul 2000 12:37:20 -0400 (EDT) From: "Brandon D. Valentine" To: "Steve O'Hara-Smith" Cc: Leif Neland , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Steve O'Hara-Smith wrote: > >On 17-Jul-00 Leif Neland wrote: >> If you can't reach a NTP server, you are not connected to the internet. In >> that case you don't need to worry so much about security... > > Not clear. I might not be connected at boot time but could well become >connected later. [Why do so few people manage the RFC compliant space in their .sig? i.e. "-- "] But by then you've already booted and other events have generated some entropy for the random device. You no longer need seeding. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 9:49:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix1.free.fr (postfix1.free.fr [212.27.32.21]) by hub.freebsd.org (Postfix) with ESMTP id 6F52337B589 for ; Mon, 17 Jul 2000 09:49:35 -0700 (PDT) (envelope-from jaco@titine.fr.eu.org) Received: from titine.fr.eu.org (toulouse-2-6-243.dial.proxad.net [213.228.6.243]) by postfix1.free.fr (Postfix) with ESMTP id DE0B52812D for ; Mon, 17 Jul 2000 18:49:29 +0200 (MEST) Received: by titine.fr.eu.org (Postfix, from userid 1000) id 06FFE14A96; Mon, 17 Jul 2000 18:48:22 +0200 (CEST) X-Attribution: Jaco To: current@FreeBSD.ORG Subject: Re: world breakage in -current (also breaks release) References: <5840.963848397@localhost> From: Eric Jacoboni Date: 17 Jul 2000 18:48:22 +0200 In-Reply-To: "Jordan K. Hubbard"'s message of "Mon, 17 Jul 2000 08:39:57 -0700" Message-ID: <8766q4ya7d.fsf@titine.fr.eu.org> Lines: 14 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Jordan" =3D=3D Jordan K Hubbard writes: Jordan> cd /usr/src; make -f Makefile.inc1 hierarchy Jordan> cd /usr/src/etc; make distrib-dirs Jordan> mtree -deLU -f /usr/src/etc/mtree/BSD.root.dist -p / Jordan> mtree: illegal option -- L Yep, same for me... I succeed in installing mtree _before_ making installworld. --=20 --------------------------------------------------------- =C9ric Jacoboni =AB No sport, cigars! =BB (W. Churchill) --------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 10: 2:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout2.silyn-tek.de (mout2.silyn-tek.de [194.25.165.70]) by hub.freebsd.org (Postfix) with ESMTP id 11A0837BA2B for ; Mon, 17 Jul 2000 10:02:55 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from [192.168.32.33] (helo=mx1.silyn-tek.de) by mout2.silyn-tek.de with esmtp (Exim 3.13 #1) id 13EEI9-0008Bf-00; Mon, 17 Jul 2000 19:02:53 +0200 Received: from p3e9c116d.dip0.t-ipconnect.de ([62.156.17.109] helo=neutron.cichlids.com) by mx1.silyn-tek.de with esmtp (Exim 3.13 #1) id 13EEI8-0005KR-00; Mon, 17 Jul 2000 19:02:52 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 9832BAB91; Mon, 17 Jul 2000 19:04:23 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 02B3C14A62; Mon, 17 Jul 2000 19:02:50 +0200 (CEST) Date: Mon, 17 Jul 2000 19:02:50 +0200 To: Leif Neland Cc: Steve O'Hara-Smith , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak Message-ID: <20000717190250.A26970@cichlids.cichlids.com> Mail-Followup-To: Leif Neland , Steve O'Hara-Smith , current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from leifn@neland.dk on Mon, Jul 17, 2000 at 05:08:35PM +0200 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. From: alex@big.endian.de (Alexander Langer) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Leif Neland (leifn@neland.dk): > If you can't reach a NTP server, you are not connected to the internet. In > that case you don't need to worry so much about security... That is wrong :) Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 10: 3:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 99D3637B558 for ; Mon, 17 Jul 2000 10:01:50 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.9.3/1.13) id TAA64412; Mon, 17 Jul 2000 19:59:00 +0300 (EEST) Date: Mon, 17 Jul 2000 19:59:00 +0300 From: Ruslan Ermilov To: Samuel Tardieu Cc: current@freebsd.org Subject: Re: New mtree needed for installation Message-ID: <20000717195900.A64235@sunbay.com> Mail-Followup-To: Samuel Tardieu , current@freebsd.org References: <2000-07-17-17-39-12+trackit+sam@inf.enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <2000-07-17-17-39-12+trackit+sam@inf.enst.fr>; from sam@inf.enst.fr on Mon, Jul 17, 2000 at 05:39:12PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 05:39:12PM +0200, Samuel Tardieu wrote: > I did a "make buildworld" then "make installworld", and: > > -------------------------------------------------------------- > >>> Making hierarchy > -------------------------------------------------------------- > cd /usr/src; make -f Makefile.inc1 hierarchy > cd /usr/src/etc; make distrib-dirs > mtree -deLU -f /usr/src/etc/mtree/BSD.root.dist -p / > mtree: illegal option -- L > usage: mtree [-cdeinrUux] [-f spec] [-K key] [-k key] [-p path] [-s seed] > [-X excludes] > *** Error code 1 > > Of course, installing the new mtree first solves this, but it may be > worth a note in UPDATING (or better, use the newly built mtree or do > not require the use of the new -L option). > It is a known problem, and Marcel Moolenaar has posted a patch to -committers for a review. -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 10: 4: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 6D3AC37BB8C for ; Mon, 17 Jul 2000 10:03:57 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.9.3/1.13) id UAA64642; Mon, 17 Jul 2000 20:03:40 +0300 (EEST) Date: Mon, 17 Jul 2000 20:03:40 +0300 From: Ruslan Ermilov To: Dag-Erling Smorgrav Cc: current@freebsd.org Subject: Re: ftpd 550 reply Message-ID: <20000717200340.B64235@sunbay.com> Mail-Followup-To: Dag-Erling Smorgrav , current@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from des@flood.ping.uio.no on Mon, Jul 17, 2000 at 06:18:39PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 06:18:39PM +0200, Dag-Erling Smorgrav wrote: > Does anyone else than me have trouble with ftpd reporting "550 not a > plain file" instead of "550 no such file or directory" when the > requested file does not exist? > This is on 4.1-RC (built from today's sources which equivalent to -CURRENT): Script started on Mon Jul 17 20:01:30 2000 Connected to localhost. 220 perl.sunbay.crimea.ua FTP server (Version 6.00LS) ready. Name (localhost:ru): 331 Password required for ru. Password: 230 User ru logged in. Remote system type is UNIX. Using binary mode to transfer files. ftp> get foo local: foo remote: foo 550 foo: No such file or directory. ftp> by 221 Goodbye. Script done on Mon Jul 17 20:01:38 2000 -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 10:10: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from dfw-smtpout3.email.verio.net (dfw-smtpout3.email.verio.net [129.250.36.43]) by hub.freebsd.org (Postfix) with ESMTP id DE8AE37BAEB for ; Mon, 17 Jul 2000 10:10:00 -0700 (PDT) (envelope-from gjohnson@gs.verio.net) Received: from [129.250.38.61] (helo=dfw-mmp1.email.verio.net) by dfw-smtpout3.email.verio.net with esmtp (Exim 3.12 #7) id 13EENs-000104-00 for current@freebsd.org; Mon, 17 Jul 2000 17:08:48 +0000 Received: from [204.1.124.74] (helo=power) by dfw-mmp1.email.verio.net with smtp (Exim 3.15 #4) id 13EENr-0007LV-00 for current@freebsd.org; Mon, 17 Jul 2000 17:08:47 +0000 Received: by localhost with Microsoft MAPI; Mon, 17 Jul 2000 12:08:46 -0500 Message-ID: <01BFEFE7.C21FC8D0.gjohnson@gs.verio.net> From: Tony Johnson To: "'current@freebsd.org'" Subject: nic cards Date: Mon, 17 Jul 2000 12:08:45 -0500 Organization: Expert Solutions, L.L.C. X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One thing that I just noticed on the python mailing list is a portable way of retrieving an ip addy. Why not start using eth0 (unfortunately as they do in Linuxland) eth1 ... For nic cards instead of fxp0 for an intel, etc... The fxp0 way is too hardware and implementation dependant. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 10:11:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by hub.freebsd.org (Postfix) with ESMTP id 4016837BA2B; Mon, 17 Jul 2000 10:11:29 -0700 (PDT) (envelope-from knu@idaemons.org) Received: from daemon.local.idaemons.org (203-165-77-17.sugnm1.kt.home.ne.jp [203.165.77.17]) by ms.tokyo.jcom.ne.jp (8.9.3/3.7W 04/27/00) with ESMTP id CAA01716; Tue, 18 Jul 2000 02:11:27 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id CAA46656; Tue, 18 Jul 2000 02:10:56 +0900 (JST) Date: Tue, 18 Jul 2000 02:10:55 +0900 Message-ID: <861z0sr8bk.wl@localhost.local.idaemons.org> From: "Akinori -Aki- MUSHA" To: des@FreeBSD.org Cc: current@FreeBSD.org Subject: fetch(1) bug? User-Agent: Wanderlust/1.1.2 (Raspberry Beret) EMIKO/1.13.12 (Euglena sociabilis) FLIM/1.13.2 (Kasanui) APEL/10.2 MULE XEmacs/21.1 (patch 10) (Capitol Reef) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 1BEF D9B2 BABD 25D7 659A FD08 89C2 F3BE E981 4E16 MIME-Version: 1.0 (generated by EMIKO 1.13.12 - "Euglena sociabilis") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I found a weird problem with your new fetch(1). Please try fetching the following file with both fetch and wget for comparison: http://www.hiei.kit.ac.jp/~hitomi/mutt/mutt/manual_ja-1.2i-0.tar.gz 1) Fetching the file with wget knu@archon[2]% uname -a ~ FreeBSD archon.local.idaemons.org 5.0-CURRENT FreeBSD 5.0-CURRENT #36: Sun Jul 16 21:17:50 JST 2000 root@archon.local.idaemons.org:/usr/src/sys/compile/ARCHON i386 knu@archon[2]% wget http://www.hiei.kit.ac.jp/~hitomi/mutt/manual_ja-1.2i-0.tar.gz --02:01:36-- http://www.hiei.kit.ac.jp:80/%7Ehitomi/mutt/manual_ja-1.2i-0.tar.gz => `manual_ja-1.2i-0.tar.gz.1' Connecting to www.hiei.kit.ac.jp:80... connected! HTTP request sent, awaiting response... 200 OK Length: 262,692 [application/x-gzip] 0K -> .......... .......... .......... .......... .......... [ 19%] 50K -> .......... .......... .......... .......... .......... [ 38%] 100K -> .......... .......... .......... .......... .......... [ 58%] 150K -> .......... .......... .......... .......... .......... [ 77%] 200K -> .......... .......... .......... .......... .......... [ 97%] 250K -> ...... [100%] 02:01:44 (33.20 KB/s) - `manual_ja-1.2i-0.tar.gz.1' saved [262692/262692] knu@archon[2]% ls -l manual_ja-1.2i-0.tar.gz ~ -rw-r--r-- 1 knu knu - 262692 Jul 6 09:06 manual_ja-1.2i-0.tar.gz knu@archon[2]% md5 manual_ja-1.2i-0.tar.gz ~ MD5 (manual_ja-1.2i-0.tar.gz) = 809121b8baa58906fba7422de9c2b236 knu@archon[2]% tar ztf manual_ja-1.2i-0.tar.gz ~ manual_ja.sgml manual_ja.tex manual_ja.txt manual_ja.html Seems fine. 2) Fetching the file with fetch knu@archon[2]% fetch -vv http://www.hiei.kit.ac.jp/~hitomi/mutt/manual_ja-1.2i-0.tar.gz looking up www.hiei.kit.ac.jp connecting to www.hiei.kit.ac.jp:80 requesting http://www.hiei.kit.ac.jp:80/~hitomi/mutt/manual_ja-1.2i-0.tar.gz looking up www.hiei.kit.ac.jp connecting to www.hiei.kit.ac.jp:80 requesting http://www.hiei.kit.ac.jp:80/~hitomi/mutt/manual_ja-1.2i-0.tar.gz Receiving manual_ja-1.2i-0.tar.gz: 262697 bytes 262697 bytes transferred in 7.7 seconds (33.16 kBps) knu@archon[2]% md5 manual_ja-1.2i-0.tar.gz ~ MD5 (manual_ja-1.2i-0.tar.gz) = 3b078418a5fdcc765d8bea0fed3ee6dd knu@archon[2]% ls -l manual_ja-1.2i-0.tar.gz ~ -rw-r--r-- 1 knu knu - 262697 Jul 6 09:06 manual_ja-1.2i-0.tar.gz knu@archon[2]% tar ztf manual_ja-1.2i-0.tar.gz ~ manual_ja.sgml manual_ja.tex manual_ja.txt manual_ja.html gzip: stdin: decompression OK, trailing garbage ignored tar: child returned status 2 Hmm, fetch(1) seems receiving extra 5 bytes of garbage. Have you got a clue? -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 10:26:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 7A16F37BA9F for ; Mon, 17 Jul 2000 10:26:43 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id KAA26568; Mon, 17 Jul 2000 10:25:21 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200007171725.KAA26568@gndrsh.dnsmgr.net> Subject: Re: dc driver and underruns (was: Strangeness with 4.0-S) In-Reply-To: <200007170214.TAA23537@implode.root.com> from David Greenman at "Jul 16, 2000 07:14:30 pm" To: dg@root.com Date: Mon, 17 Jul 2000 10:25:21 -0700 (PDT) Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... > >As far as I can tell the fxp driver doesn't even use the tx_fifo in the > >825xxx chips :-) > > The 82557-9 have a 2KB internal buffer for transmits. They don't start > transmitting until a programmed threshold is reached - this is to insure > that PCI bus latency doesn't result in the transmitter getting stalled. > The fxp driver starts out with this threshold set at 512 bytes, but will > increase it (512 bytes at a time) when a DMA underrun occurs. Of course > once the threshold reached 1536, then an entire 1500 byte packet is DMA'd > into the buffer before the transmit begins. Can you point me to the part of if_fxp.c that does this, as alls I can find about any form of fifo in the code are these references: Guardian# grep -i fifo *fxp* if_fxp.c: cbp->rx_fifo_limit = 8; /* rx fifo threshold (32 bytes) */ if_fxp.c: cbp->tx_fifo_limit = 0; /* tx fifo threshold (0 bytes) */ if_fxpreg.h: volatile u_int rx_fifo_limit:4, if_fxpreg.h: tx_fifo_limit:3, No place do I find anything that does any adjustments to these values :-(. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 10:32:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 4D82137B5EB; Mon, 17 Jul 2000 10:32:24 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id TAA00681; Mon, 17 Jul 2000 19:33:40 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007171733.TAA00681@grimreaper.grondar.za> To: Maxim Sobolev Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: <39731FC5.34D3074D@FreeBSD.org> In-Reply-To: <39731FC5.34D3074D@FreeBSD.org> ; from Maxim Sobolev "Mon, 17 Jul 2000 18:01:25 +0300." Date: Mon, 17 Jul 2000 19:33:40 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You may also want to extend /etc/crontab to periodically save entropy. This would > help if something unexpected like halt(8) or panic(9) happened. That is an idea I can use! :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 10:48:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id E22B037BAA4 for ; Mon, 17 Jul 2000 10:48:36 -0700 (PDT) (envelope-from chris@holly.calldei.com) Received: from holly.calldei.com ([208.191.149.190]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FXU00AMORUPQ5@mta4.rcsntx.swbell.net> for current@FreeBSD.ORG; Mon, 17 Jul 2000 12:42:26 -0500 (CDT) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id MAA50511; Mon, 17 Jul 2000 12:40:54 -0500 (CDT envelope-from chris) Date: Mon, 17 Jul 2000 12:40:53 -0500 From: Chris Costello Subject: Re: nic cards In-reply-to: <01BFEFE7.C21FC8D0.gjohnson@gs.verio.net> To: Tony Johnson Cc: "'current@freebsd.org'" Reply-To: chris@calldei.com Message-id: <20000717124053.D48019@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: <01BFEFE7.C21FC8D0.gjohnson@gs.verio.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, July 17, 2000, Tony Johnson wrote: > One thing that I just noticed on the python mailing list is a portable way > of retrieving an ip addy. Why not start using eth0 (unfortunately as they > do in Linuxland) eth1 ... For nic cards instead of fxp0 for an intel, > etc... > > The fxp0 way is too hardware and implementation dependant. ``eth0'' is no more portable than ``fxp0''. Just because Linux does it doesn't mean it's standard or portable. -- |Chris Costello |MIPS: Meaningless Indicator of Processor Speed. `------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 11: 2:59 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 0591737BE8B; Mon, 17 Jul 2000 11:02:56 -0700 (PDT) Date: Mon, 17 Jul 2000 11:02:55 -0700 From: "Andrey A. Chernov" To: Alexander Langer , markm@freebsd.org Cc: Leif Neland , Steve O'Hara-Smith , current@FreeBSD.ORG Subject: rc.shutdown hook is not a solution (was Re: randomdev entropy gathering is really weak) Message-ID: <20000717110255.A33448@freebsd.org> References: <20000717190250.A26970@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000717190250.A26970@cichlids.cichlids.com>; from alex@big.endian.de on Mon, Jul 17, 2000 at 07:02:50PM +0200 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 07:02:50PM +0200, Alexander Langer wrote: > Thus spake Leif Neland (leifn@neland.dk): > > > If you can't reach a NTP server, you are not connected to the internet. In > > that case you don't need to worry so much about security... > > That is wrong :) > The reason is not security only, the reason is buggy RNG. Imagine diskless keyboard-less and mouse-less slide-show machine with no rc.shutdown hooks since it comes with power up and goes down with power down. This machine will always start with same picture because RNG have not enough enthropy. In worst case we should relay only on processor registers always present, i.e. timers and so on. rc.shutdown hook not solve problem completely. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 11:30:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 886D337BC86 for ; Mon, 17 Jul 2000 11:30:16 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id LAA10683; Mon, 17 Jul 2000 11:39:08 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007171839.LAA10683@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tony Johnson Cc: "'current@freebsd.org'" Subject: Re: nic cards In-reply-to: Your message of "Mon, 17 Jul 2000 12:08:45 CDT." <01BFEFE7.C21FC8D0.gjohnson@gs.verio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Jul 2000 11:39:08 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > One thing that I just noticed on the python mailing list is a portable way > of retrieving an ip addy. Why not start using eth0 (unfortunately as they > do in Linuxland) eth1 ... For nic cards instead of fxp0 for an intel, > etc... > > The fxp0 way is too hardware and implementation dependant. 'ethX' is also too 'specific'. Use 'ifconfig -l' to get a list of network interfaces, at which point you don't care what they're called... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 11:58:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by hub.freebsd.org (Postfix) with ESMTP id E84A137BB42; Mon, 17 Jul 2000 11:58:45 -0700 (PDT) (envelope-from knu@idaemons.org) Received: from daemon.local.idaemons.org (203-165-77-17.sugnm1.kt.home.ne.jp [203.165.77.17]) by ms.tokyo.jcom.ne.jp (8.9.3/3.7W 04/27/00) with ESMTP id DAA13626; Tue, 18 Jul 2000 03:58:45 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id DAA48310; Tue, 18 Jul 2000 03:58:13 +0900 (JST) Date: Tue, 18 Jul 2000 03:58:12 +0900 Message-ID: <86ya30posb.wl@localhost.local.idaemons.org> From: "Akinori -Aki- MUSHA" To: des@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: fetch(1) bug? In-Reply-To: In your message of "Tue, 18 Jul 2000 02:10:55 +0900" <861z0sr8bk.wl@localhost.local.idaemons.org> References: <861z0sr8bk.wl@localhost.local.idaemons.org> User-Agent: Wanderlust/1.1.2 (Raspberry Beret) EMIKO/1.13.12 (Euglena sociabilis) FLIM/1.13.2 (Kasanui) APEL/10.2 MULE XEmacs/21.1 (patch 10) (Capitol Reef) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 1BEF D9B2 BABD 25D7 659A FD08 89C2 F3BE E981 4E16 MIME-Version: 1.0 (generated by EMIKO 1.13.12 - "Euglena sociabilis") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry, I seem to have supplied a wrong URL. Here's the correct one. http://www.hiei.kit.ac.jp/~hitomi/mutt/manual_ja-1.2i-0.tar.gz -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 12:22: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.bitmcnit.bryansk.su (bitmcnit.bryansk.ru [195.239.213.9]) by hub.freebsd.org (Postfix) with ESMTP id 1826C37B560 for ; Mon, 17 Jul 2000 12:21:46 -0700 (PDT) (envelope-from alex@kapran.bitmcnit.bryansk.su) Received: (from uucp@localhost) by server.bitmcnit.bryansk.su (8.9.3/8.9.3) with UUCP id WAA02235; Mon, 17 Jul 2000 22:58:30 +0400 Received: (from alex@localhost) by kapran.bitmcnit.bryansk.su (8.9.3/8.9.3) id UAA07876; Mon, 17 Jul 2000 20:41:58 +0400 (MSD) (envelope-from alex@kapran.bitmcnit.bryansk.su) X-Authentication-Warning: kapran.bitmcnit.bryansk.su: alex set sender to alex@kapran.bitmcnit.bryansk.su using -f Date: Mon, 17 Jul 2000 20:41:58 +0400 From: Alex Kapranoff To: Leif Neland Cc: current@freebsd.org Subject: Re: randomdev entropy gathering is really weak Message-ID: <20000717204157.A7583@kapran.bitmcnit.bryansk.su> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from leifn@neland.dk on Mon, Jul 17, 2000 at 05:08:35PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 05:08:35PM +0200, Leif Neland wrote: > On Mon, 17 Jul 2000, Steve O'Hara-Smith wrote: > > On 17-Jul-00 Poul-Henning Kamp wrote: > > > NTP is the perfect way to gather entropy at bootup! > > > > Only if in reach of an NTP server ? > > > If you can't reach a NTP server, you are not connected to the internet. In > that case you don't need to worry so much about security... Flawed logic. That's cryptography. It's about information protection. And you of course know that about 80% of computer crimes are commited by local cow orkers in a LAN environment behind a twenty five firewalls, proxies and the like. -- Alex Kapranoff, 2:50/383.20@fidonet, Voice: +7(0832)791845. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 12:50:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 9F7E737BAC4 for ; Mon, 17 Jul 2000 12:50:53 -0700 (PDT) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id PAA05990 for current@freebsd.org; Mon, 17 Jul 2000 15:50:52 -0400 (EDT) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200007171950.PAA05990@blackhelicopters.org> Subject: MS CHAP v2 in -current? To: current@freebsd.org Date: Mon, 17 Jul 2000 15:50:52 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ping... Does anyone know if ms chap v2 will be integrated into -current any time soon? I need it for pptpclient. If anyone has any patches they'd like public testing on, I'll volunteer. :) ==ml To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 12:56:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 9C19B37BB54; Mon, 17 Jul 2000 12:56:12 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id VAA01275; Mon, 17 Jul 2000 21:57:25 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007171957.VAA01275@grimreaper.grondar.za> To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG Subject: Re: rc.shutdown hook is not a solution (was Re: randomdev entropy gathering is really weak) References: <20000717110255.A33448@freebsd.org> In-Reply-To: <20000717110255.A33448@freebsd.org> ; from "Andrey A. Chernov" "Mon, 17 Jul 2000 11:02:55 MST." Date: Mon, 17 Jul 2000 21:57:25 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The reason is not security only, the reason is buggy RNG. Imagine diskless > keyboard-less and mouse-less slide-show machine with no rc.shutdown hooks > since it comes with power up and goes down with power down. This machine > will always start with same picture because RNG have not enough enthropy. In > worst case we should relay only on processor registers always present, i.e. > timers and so on. rc.shutdown hook not solve problem completely. Actually, it is only a faulty reseed mechanism. For the purposes of your argument above, the time-of-day would be an acceptable reseed to random(9). For cryptographic randomness, more noise is needed. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 13:14:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.2.163]) by hub.freebsd.org (Postfix) with ESMTP id 0B26137B817; Mon, 17 Jul 2000 13:14:15 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.15 #1) id 13EHHD-0007G2-00; Mon, 17 Jul 2000 22:14:07 +0200 From: Sheldon Hearn To: Mark Murray Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Mon, 17 Jul 2000 19:33:40 +0200." <200007171733.TAA00681@grimreaper.grondar.za> Date: Mon, 17 Jul 2000 22:14:07 +0200 Message-ID: <27901.963864847@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000 19:33:40 +0200, Mark Murray wrote: > That is an idea I can use! :-) See the recently fixed and documented crontab(5) @reboot, in fact. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 13:16:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 2CC6F37BB6F; Mon, 17 Jul 2000 13:16:44 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA52864; Mon, 17 Jul 2000 13:16:43 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 17 Jul 2000 13:16:43 -0700 (PDT) From: Kris Kennaway To: Mark Murray Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007171459.QAA00888@grimreaper.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Mark Murray wrote: > > What we really need is this: > > > > fetch -o http://entropy.freebsd.org/ > /dev/random > > For this to work, you'll need to encrypt the traffic. > > fetch -o https://entropy.freebsd.org/ > /dev/random > ^ > > If the world knows what they are, your bits aren't random enough. Plus you need to authenticate (and obviously trust) your entropy server and the data stream to make sure they're not actually someone else feeding you zeros. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 13:56:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 2F66737BD5E for ; Mon, 17 Jul 2000 13:56:50 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id WAA37671; Mon, 17 Jul 2000 22:56:44 +0200 (CEST) (envelope-from des@flood.ping.uio.no) To: Ruslan Ermilov Cc: current@freebsd.org Subject: Re: ftpd 550 reply References: <20000717200340.B64235@sunbay.com> From: Dag-Erling Smorgrav Date: 17 Jul 2000 22:56:44 +0200 In-Reply-To: Ruslan Ermilov's message of "Mon, 17 Jul 2000 20:03:40 +0300" Message-ID: Lines: 89 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ruslan Ermilov writes: > On Mon, Jul 17, 2000 at 06:18:39PM +0200, Dag-Erling Smorgrav wrote: > > Does anyone else than me have trouble with ftpd reporting "550 not a > > plain file" instead of "550 no such file or directory" when the > > requested file does not exist? > This is on 4.1-RC (built from today's sources which equivalent to > -CURRENT): > [doesn't have the bug] ---> ftp.ofug.org:21 <<< 220 flood.ping.uio.no FTP server (Version 6.00) ready. >>> USER ftp <<< 331 Guest login ok, send your email address as password. >>> PASS des@des.follo.net <<< 230- ******************************************************** <<< 230- * * <<< 230- * Welcome to flood.ping.uio.no! * <<< 230- * * <<< 230- * All transfers are logged. If you are not comfortable * <<< 230- * with that, please find another server. * <<< 230- * * <<< 230- * Please report any problems or irregularities to * <<< 230- * des@ping.uio.no. * <<< 230- * * <<< 230- ******************************************************** <<< 230 Guest login ok, access restrictions apply. >>> TYPE I <<< 200 Type set to I. >>> CWD /pub/FreeBSD/ports/distfiles <<< 250 CWD command successful. >>> SIZE shorten.tar.gz <<< 550 shorten.tar.gz: not a plain file. fetch: File unavailable (e.g., file not found, no access) ---> ftp.freebsd.org:21 <<< 220 sourcerer.freesoftware.com FTP server (Version DG-3.1.42 Thu Jul 6 14:10:01 PDT 2000) ready. >>> USER ftp <<< 331 Guest login ok, send your email address as password. >>> PASS des@des.follo.net <<< 230-Welcome to ftp.freesoftware.com - home FTP site for Walnut Creek CDROM. <<< 230-There are currently 744 users out of 5000 possible. <<< 230- <<< 230-Most of the files in this area are also available on CDROM. You can send <<< 230-email to info@wccdrom.com for more information or to order, or visit our Web <<< 230-site at http://www.wccdrom.com. For tech support about our products, please <<< 230-email support@wccdrom.com. You may also call our toll-free number: <<< 230-1-800-786-9907 or +1-925-674-0783. Please keep in mind that we only offer <<< 230-technical support for our CDROM products and not for the files on our <<< 230-FTP server. <<< 230- <<< 230-This server is a Xeon/550 with 4GB of memory & 400GB of RAID 5 storage. <<< 230-The operating system is FreeBSD. Should you wish to get your own copy of <<< 230-FreeBSD, see the pub/FreeBSD directory or visit http://www.freebsd.org <<< 230-for more information. FreeBSD on CDROM can be ordered using the WEB at <<< 230-http://www.wccdrom.com/titles/freebsd/freebsd.phtml or by sending email <<< 230-to orders@wccdrom.com. <<< 230- <<< 230-Gigabit colocation services provided by Lightning Internet. For more <<< 230-information, please visit http://www.lightning.net. <<< 230- <<< 230-Please send mail to ftp-bugs@ftp.freesoftware.com if you experience any <<< 230-problems. Please also let us know if there is something we don't have that <<< 230-you think we should! <<< 230- <<< 230 Guest login ok, access restrictions apply. >>> TYPE I <<< 200 Type set to I. >>> CWD /pub/FreeBSD/ports/distfiles <<< 250 CWD command successful. >>> SIZE shorten.tar.gz <<< 550 shorten.tar.gz: not a plain file. fetch: File unavailable (e.g., file not found, no access) ---> ftp.kiarchive.ru:21 <<< 220 kiarchive.relcom.ru FTP server (Version 6.00) ready. >>> USER ftp <<< 331 Guest login ok, send your email address as password. >>> PASS des@des.follo.net <<< 230 Guest login ok, access restrictions apply. >>> TYPE I <<< 200 Type set to I. >>> CWD /pub/misc/hardware/soundcard/gus <<< 250 CWD command successful. >>> SIZE timidity-0.2i.tar.gz <<< 550 timidity-0.2i.tar.gz: not a plain file. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 14:38:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 66D0337B524 for ; Mon, 17 Jul 2000 14:38:32 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id XAA37939; Mon, 17 Jul 2000 23:38:23 +0200 (CEST) (envelope-from des@flood.ping.uio.no) To: "Akinori -Aki- MUSHA" Cc: current@FreeBSD.org Subject: Re: fetch(1) bug? References: <861z0sr8bk.wl@localhost.local.idaemons.org> From: Dag-Erling Smorgrav Date: 17 Jul 2000 23:38:23 +0200 In-Reply-To: "Akinori -Aki- MUSHA"'s message of "Tue, 18 Jul 2000 02:10:55 +0900" Message-ID: Lines: 44 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Akinori -Aki- MUSHA" writes: > Hi, I found a weird problem with your new fetch(1). Actually, it's not as simple as I thought. It's a bug in the HTTP server that runs on www.hiei.kit.ac.jp, which triggers a misfeature of fetch(1), which causes it to fail to properly work around a second bug in the server. des@md5 ~% fetch http://www.hiei.kit.ac.jp:80/%7Ehitomi/mutt/manual_ja-1.2i-0.tar.gz ---> www.hiei.kit.ac.jp:80 >>> HEAD /%7Ehitomi/mutt/manual_ja-1.2i-0.tar.gz HTTP/1.1 >>> Host: www.hiei.kit.ac.jp:80 >>> User-Agent: fetch libfetch/2.0 >>> Connection: close >>> <<< HTTP/1.1 200 OK <<< Server: SWS-1.0 <<< Date: Mon, 17 Jul 2000 18:06:37 GMT <<< Content-Type: application/x-gzip <<< Last-Modified: Thu, 06 Jul 2000 00:06:51 GMT <<< Accept-Ranges: bytes <<< ---> www.hiei.kit.ac.jp:80 >>> GET /%7Ehitomi/mutt/manual_ja-1.2i-0.tar.gz HTTP/1.1 >>> Host: www.hiei.kit.ac.jp:80 >>> User-Agent: fetch libfetch/2.0 >>> Connection: close >>> <<< HTTP/1.1 200 OK <<< Server: SWS-1.0 <<< Date: Mon, 17 Jul 2000 18:06:39 GMT <<< Content-Type: application/x-gzip <<< Last-Modified: Thu, 06 Jul 2000 00:06:51 GMT <<< Accept-Ranges: bytes <<< Content-Length: 262692 <<< I've spent most of the night fixing this and am about to commit the last changes, so you should be able to cvsup and build working libfetch and fetch in an hour or two. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 14:49:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62]) by hub.freebsd.org (Postfix) with ESMTP id CDE2237B640 for ; Mon, 17 Jul 2000 14:49:02 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id OAA68848 for ; Mon, 17 Jul 2000 14:49:01 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Mon, 17 Jul 2000 14:49:01 -0700 (PDT) From: Doug Barton X-Sender: doug@dt052n3e.san.rr.com To: freebsd-current@freebsd.org Subject: No /boot/loader Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No response to this on -stable. The actual error message is: Disk error 0x1 (lba=0x7004c) No /boot/loader Also, on a whim I decided to try running /boot/loader. I got a message saying that there was a syntax error on line 4, that it was missing either a close paren or a close curly brace. It went by fast, and I couldn't reproduce it. A quick examination of the sources by my boot code inexpert eyes didn't reveal anything that looked relevant on any line 4's. Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? ---------- Forwarded message ---------- Date: Fri, 14 Jul 2000 20:30:48 -0700 (PDT) From: Doug Barton Subject: Re: CFT: boot patch for 4.x I'm having a problem that isn't related to your patch, but that I'm hoping you or someone can shed some light on. I installed 4-Stable from the 7/6 snapshot onto some shiny new machines, and when I reboot them I get an error: See above. then the boot: prompt comes up a couple of times, it finds the kerrnel and boots anyway. I found this odd because there clearly IS a /boot/loader, and I haven't changed anything in /boot at all. I did a make world today and installed a custom kernel, no joy. I'm also getting the dreaded top: nlist failed error. I have the following for adapters: ahc0: port 0x2000-0x20ff mem 0xf4100000-0xf4100fff irq 19 at d evice 12.0 on pci0 ahc0: aic7896/97 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: port 0x2400-0x24ff mem 0xf4101000-0xf4101fff irq 19 at d evice 12.1 on pci0 ahc1: aic7896/97 Wide Channel B, SCSI Id=7, 16/255 SCBs and this for disks: da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 8755MB (17930694 512 byte sectors: 255H 63S/T 1116C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 8755MB (17930694 512 byte sectors: 255H 63S/T 1116C) I did the install with dangerously dedicated disks, which I know John is not a big fan of, but on the IBM SCSI drives I have in the other machines I have no problems of this sort whatsoever. I suppose I could try the install again with a real partition table, I just hate to waste all that config time. :-/ Any help appreciated. Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 16:27:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from infidel.boolean.net (router.boolean.net [198.144.206.49]) by hub.freebsd.org (Postfix) with ESMTP id A831937B764; Mon, 17 Jul 2000 16:27:50 -0700 (PDT) (envelope-from Kurt@OpenLDAP.org) Received: from gypsy.OpenLDAP.org (gypsy.boolean.net [198.144.202.243]) by infidel.boolean.net (8.9.3/8.9.3) with ESMTP id XAA28570; Mon, 17 Jul 2000 23:27:18 GMT (envelope-from Kurt@OpenLDAP.org) Message-Id: <4.3.2.7.0.20000717161342.00b0c780@infidel.boolean.net> X-Sender: guru@infidel.boolean.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 17 Jul 2000 16:27:17 -0700 To: Sheldon Hearn From: "Kurt D. Zeilenga" Subject: Re: randomdev entropy gathering is really weak Cc: Mark Murray , Maxim Sobolev , current@FreeBSD.ORG In-Reply-To: <27901.963864847@axl.ops.uunet.co.za> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Note that there should be no need to cron the job. You only need to save one set of bits to be used as a seed for the next startup. And one set of bits SHOULD be as good as any other. I suggest you (at boot time): 1: open seed file for read unlink seed file use seed file + available entropy to seed algorithm close the seed file 2: open for seed file for write write X bytes for next time close file Note that even if you do cron step 2, I recommend highly you mix in whatever entropy you can gather at boot time into the initial seeding. This will ensure any reuse of the seed file (such as if you crash between steps 1 and 2) will result in different bit sequences. Regards, Kurt At 10:14 PM 7/17/00 +0200, Sheldon Hearn wrote: >On Mon, 17 Jul 2000 19:33:40 +0200, Mark Murray wrote: > >> That is an idea I can use! :-) > >See the recently fixed and documented crontab(5) @reboot, in fact. :-) > >Ciao, >Sheldon. > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 16:37: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id EDCB437B74F; Mon, 17 Jul 2000 16:37:01 -0700 (PDT) (envelope-from ggm@dstc.edu.au) Received: from dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155]) by piglet.dstc.edu.au (8.10.1/8.10.1) with ESMTP id e6HNaHb22147; Tue, 18 Jul 2000 09:36:17 +1000 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Kurt D. Zeilenga" Cc: Sheldon Hearn , Mark Murray , Maxim Sobolev , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: Message from "Kurt D. Zeilenga" of "Mon, 17 Jul 2000 16:27:17 MST." <4.3.2.7.0.20000717161342.00b0c780@infidel.boolean.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Jul 2000 09:36:23 +1000 Message-ID: <15477.963876983@dstc.edu.au> From: George Michaelson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG However much I love the idea of people coding in more randomness, I'd get a better fuzzy feeling if somebody with some cred in the crypto world was sitting in on this discussion and commenting on the ideas. Things like 'going out on the network and fetching some random bits via http' are so utterly bogus (open to attack, presume networks are there) that they kinda suggest this hasn't been well thought out. Likewise embedding a dependency on keyboard/mouse movements. IIRC There have been articles making it plain that week initial random settings propagate out like topsy: you can't add trustable randomness by taking skewed input sources. People like Bruce Schneier, Steve Bellovin, they are not unapproachable. Could somebody mail them for comments on whats considered acceptable sources of random bits? Please? -George -- George Michaelson | DSTC Pty Ltd Email: ggm@dstc.edu.au | University of Qld 4072 Phone: +61 7 3365 4310 | Australia Fax: +61 7 3365 4311 | http://www.dstc.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 18:11:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 2DA4937B771 for ; Mon, 17 Jul 2000 18:11:31 -0700 (PDT) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id DAA09444 for freebsd-current@FreeBSD.ORG; Tue, 18 Jul 2000 03:11:20 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id CAA72003 for ; Tue, 18 Jul 2000 02:14:49 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <005f01bff04d$3d39a800$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: Subject: cer/b7b/pfc -> pem Date: Tue, 18 Jul 2000 02:14:23 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Apropos pseudorandom, ssh etc; I hope this is not too off-topic, or can somebody point in the right direction: I have a Verisign personal certificate (Look me up at Verisign, as Leif Neland) This works nicely in Windows (Outlook Express), but I'd like to try using the same key with openssl to generate crypted (to myself) or signed messages. I can export the key as a .cer, .p7b or .pfx, but openssl seems to want it in .pem format. Am I totally confused, or is it possible to convert one of the above to .pem? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 18:28:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp-out1.bellatlantic.net (smtp-out1.bellatlantic.net [199.45.39.156]) by hub.freebsd.org (Postfix) with ESMTP id A126237B52D for ; Mon, 17 Jul 2000 18:28:48 -0700 (PDT) (envelope-from dberlin@redhat.com) Received: from dan2.cygnus.com (adsl-138-88-44-91.bellatlantic.net [138.88.44.91]) by smtp-out1.bellatlantic.net (8.9.1/8.9.1) with SMTP id VAA11698; Mon, 17 Jul 2000 21:28:38 -0400 (EDT) From: dberlin@redhat.com (Daniel Berlin+list.freebsd-current) To: "Leif Neland" Cc: Subject: Re: cer/b7b/pfc -> pem References: <005f01bff04d$3d39a800$0e00a8c0@neland.dk> Date: 17 Jul 2000 21:28:54 -0400 In-Reply-To: "Leif Neland"'s message of "Tue, 18 Jul 2000 02:14:23 +0200" Message-ID: Lines: 43 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Capitol Reef) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Leif Neland" writes: > Apropos pseudorandom, ssh etc; I hope this is not too off-topic, or can > somebody point in the right direction: > > I have a Verisign personal certificate (Look me up at Verisign, as Leif > Neland) > > This works nicely in Windows (Outlook Express), but I'd like to try using > the same key with openssl to generate crypted (to myself) or signed > messages. > > I can export the key as a .cer, .p7b or .pfx, but openssl seems to want it > in .pem format. > What does the p7b file look like? And the .cer file, and the .pfx file? Are any of them ascii, with a "BEGIN PKCS7" or "BEGIN CERTIFICATE" line? > Am I totally confused, or is it possible to convert one of the above to > .pem? > from crl2pkcs7's man page, in the notes section: The output file is a PKCS#7 signed data structure containing no signers and just certificates and an optional CRL. This utility can be used to send certificates and CAs to Netscape as part of the certificate enrollment process. This involves sending the DER encoded output as MIME type application/x-x509-user-cert. The PEM encoded form with the header and footer lines removed can be used to install user certificates and CAs in MSIE using the Xenroll control. > Leif > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 18:33:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 6988F37B633; Mon, 17 Jul 2000 18:33:16 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 335C34C; Mon, 17 Jul 2000 21:33:15 -0400 (AST) Message-ID: <3973B3DB.EAC14E82@vangelderen.org> Date: Mon, 17 Jul 2000 21:33:15 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Mon, 17 Jul 2000, Mark Murray wrote: > > > > On the other hand, doing a dd if=/dev/random of=/dev/null gives me > > > infinite "randomness" at 10MB/sec - have the semantics of /dev/random > > > changed? > > > > Yes; remember that what we have here is Yarrow algorithm; which is an > > algorithm for cryptographically secure PRNG - one whose internal state > > is unguessable, or if compromised folr some reason is self-recovering. > > > > "Infinite" randomness is possible with this algorithm. > > On the other hand, didn't you say that at system boot the RNG is > essentially unseeded, so this is actually a liability because processes > cannot be sure they're getting real randomness. /dev/random should block until it has seeded. If it does not it's a bug. /dev/random should *never* spit out non-random bytes. Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 18:36:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 94B8137B52D; Mon, 17 Jul 2000 18:36:34 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id CD0D14C; Mon, 17 Jul 2000 21:36:32 -0400 (AST) Message-ID: <3973B4A0.693373CA@vangelderen.org> Date: Mon, 17 Jul 2000 21:36:32 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: "Louis A. Mamakos" , Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <2450.963841019@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > In message <200007171319.JAA04774@whizzo.transsys.com>, "Louis A. Mamakos" writ > es: > > >In fact, it would be rather interesting to have a configuration flag which > >always forces something like an fsck on a file system in order to provide > >some entropy to the random device. Or some other user-exposed way of > >providing entropy. I might have some data on disk, or some network > >operations which can be performed to help seed the entropy pool. > > What we really need is this: > > fetch -o http://entropy.freebsd.org/ > /dev/random > > with a bunch of volounteers providing random bits to people in need. > > I have thought about adding a entropy server to my array of weird > servers in my lab. Something like a Geiger counter and a smokedetector > could do wonders. Right, and an attacker laughingly sniffing those bits. I think you forgot a ';-p' Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 18:44:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id BF46937B633; Mon, 17 Jul 2000 18:44:13 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 5C7834D; Mon, 17 Jul 2000 21:44:12 -0400 (AST) Message-ID: <3973B66C.D6BD5BFD@vangelderen.org> Date: Mon, 17 Jul 2000 21:44:12 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: Alexander Langer , "Louis A. Mamakos" , Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <2613.963842256@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > In message <20000717154549.A18676@cichlids.cichlids.com>, Alexander Langer writ > es: > >Thus spake Poul-Henning Kamp (phk@critter.freebsd.dk): > > > >> I have thought about adding a entropy server to my array of weird > >> servers in my lab. Something like a Geiger counter and a smokedetector > >> could do wonders. > > > >HA! Cool! > > > >Do that please! > > > >I mean, seriously. > >And an option to sysinstall, where you can enable this as you can with > >ntpdate :) > > DuH! > > NTP is the perfect way to gather entropy at bootup! > > Predicting the clock's offset from reality and the two way path to > the server of choice is impossible, plus if people enable authentication > later on the packets will be choke full of high-quality entropy. Please quantify 'impossible'. > We need an enterprising soul to add an option (default on) to > ntpdate to write the received packets in toto to /dev/random > if it exists. I think we first need to figure out the security implications. Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 18:48:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 8738C37B633; Mon, 17 Jul 2000 18:48:13 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id VAA00554; Mon, 17 Jul 2000 21:45:52 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200007180145.VAA00554@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Poul-Henning Kamp Cc: alex@big.endian.de (Alexander Langer), Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: randomdev entropy gathering is really weak References: <2613.963842256@critter.freebsd.dk> In-reply-to: Your message of "Mon, 17 Jul 2000 15:57:36 +0200." <2613.963842256@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Jul 2000 21:45:52 -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <20000717154549.A18676@cichlids.cichlids.com>, Alexander Langer writ > es: > >Thus spake Poul-Henning Kamp (phk@critter.freebsd.dk): > > > >> I have thought about adding a entropy server to my array of weird > >> servers in my lab. Something like a Geiger counter and a smokedetector > >> could do wonders. > > > >HA! Cool! > > > >Do that please! > > > >I mean, seriously. > >And an option to sysinstall, where you can enable this as you can with > >ntpdate :) > > DuH! > > NTP is the perfect way to gather entropy at bootup! > > Predicting the clock's offset from reality and the two way path to > the server of choice is impossible, plus if people enable authentication > later on the packets will be choke full of high-quality entropy. > > We need an enterprising soul to add an option (default on) to > ntpdate to write the received packets in toto to /dev/random > if it exists. > > If somebody does this, I will spear-head the effort of getting it > into the ntpv4 sources (Hmm, don't I have a commit bit there > already ? Can't remember...) Actually, you could really use this in ntpd(8), rather than just ntpdate. You could crank in the offset and delay samples for each packet received from an NTP peer; this will have the effect of adding into the entropy pool the "noise" in the latency of the path between you and each of your NTP peers. This varies over time with each sample, and in fact, NTP goes to considerable effort in it's sample filtering to exclude the noisy samples. We need to get that date before it's discarded and contribute it to the entropy cause. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 18:52:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 4CAA737B7D7 for ; Mon, 17 Jul 2000 18:52:38 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id VAA04807; Mon, 17 Jul 2000 21:52:22 -0400 (EDT) (envelope-from wollman) Date: Mon, 17 Jul 2000 21:52:22 -0400 (EDT) From: Garrett Wollman Message-Id: <200007180152.VAA04807@khavrinen.lcs.mit.edu> To: "Leif Neland" Cc: Subject: cer/b7b/pfc -> pem In-Reply-To: <005f01bff04d$3d39a800$0e00a8c0@neland.dk> References: <005f01bff04d$3d39a800$0e00a8c0@neland.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I can export the key as a .cer, .p7b or .pfx, but openssl seems to want it > in .pem format. Of course, you haven't really told us what the format of these things is, so it's difficult to say. The ``standard'' export format is something called PKCS#12. You can use `openssl pkcs12' with various options to extract the key and certificate from this sort of format. It will prompt you for the password you specified when exporting. If you export in any other format, it is highly unlikely to contain your private key, which is required to make use of the certificate. Those other formats are normally used when you want to distribute your public key to someone or as a part of something other than a mail message. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 19:57:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 7539D37B612 for ; Mon, 17 Jul 2000 19:57:28 -0700 (PDT) (envelope-from grog@wantadilla.lemis.com) Received: (from grog@localhost) by wantadilla.lemis.com (8.9.3/8.9.3) id MAA92780 for FreeBSD-current@FreeBSD.ORG; Tue, 18 Jul 2000 12:27:24 +0930 (CST) (envelope-from grog) Date: Tue, 18 Jul 2000 12:27:24 +0930 From: Greg Lehey To: FreeBSD current users Subject: Recent -CURRENT locks up keyboard Message-ID: <20000718122724.H77412@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just built a new world on one of my test boxes. The good news is that the Macronix Ethernet card that I have in it works fine (this is the one with the MX98715AEC-C chip with the small hash table). The bad news is that the keyboard is non-functional. This is a GENERIC kernel with nothing changed. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 21: 0:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (ftp.webmaster.com [209.10.218.74]) by hub.freebsd.org (Postfix) with ESMTP id DE25B37B957 for ; Mon, 17 Jul 2000 21:00:27 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Mon, 17 Jul 2000 20:59:57 -0700 From: "David Schwartz" To: "Jeroen C. van Gelderen" , "Poul-Henning Kamp" Cc: Subject: RE: randomdev entropy gathering is really weak Date: Mon, 17 Jul 2000 21:00:26 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <3973B66C.D6BD5BFD@vangelderen.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Predicting the clock's offset from reality and the two way path to > > the server of choice is impossible, plus if people enable authentication > > later on the packets will be choke full of high-quality entropy. > > Please quantify 'impossible'. Impossible as in cannot be done. The offset between, for example, the processor clock and the NIC clock is unpredictable. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 21:24:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id D08C737B7C0 for ; Mon, 17 Jul 2000 21:24:53 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id CF4C349; Tue, 18 Jul 2000 00:24:51 -0400 (AST) Message-ID: <3973DC13.E93F573A@vangelderen.org> Date: Tue, 18 Jul 2000 00:24:51 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: David Schwartz Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Schwartz wrote: > > > > Predicting the clock's offset from reality and the two way path to > > > the server of choice is impossible, plus if people enable authentication > > > later on the packets will be choke full of high-quality entropy. > > > > Please quantify 'impossible'. > > Impossible as in cannot be done. The offset between, for example, the > processor clock and the NIC clock is unpredictable. The EXACT offset is unpredictable. Unfortunately that's not what matters because an attacker can still guess. What does matter is the set of likely/possible offsets. That set may be small or may be large or may be biased. Can you tell me how large it *typically* is on your computer? My clock usually is within a few seconds from my NTP server. I guess -assuming microsecond resolution- that allows for a couple of million possibilities but no more. I can definately extract one or two bits of entropy from this, but can I do ten, twenty or even 30? [1] Can you generate a 1024-bit RSA key after processing 10 NTP packets? I don't think so. How many *do* you need? You need to quantify all this to make a good entropy estimate. Just implementing this functionality because 'predicting the clock's offset [...] is impossible' is pretty pointless. Cheers, Jeroen [1] And then, what's the effect of an attacker sniffing your LAN? What information would he have to make his guess more accurate? -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 21:54: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by hub.freebsd.org (Postfix) with ESMTP id 1FC6837B9A0 for ; Mon, 17 Jul 2000 21:54:01 -0700 (PDT) (envelope-from knu@idaemons.org) Received: from daemon.local.idaemons.org (203-165-77-17.sugnm1.kt.home.ne.jp [203.165.77.17]) by ms.tokyo.jcom.ne.jp (8.9.3/3.7W 04/27/00) with ESMTP id NAA00135; Tue, 18 Jul 2000 13:53:20 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id NAA91077; Tue, 18 Jul 2000 13:52:49 +0900 (JST) Date: Tue, 18 Jul 2000 13:52:47 +0900 Message-ID: <86u2do59b4.wl@localhost.local.idaemons.org> From: "Akinori -Aki- MUSHA" To: des@flood.ping.uio.no Cc: current@FreeBSD.org Subject: Re: fetch(1) bug? In-Reply-To: In your message of "17 Jul 2000 23:38:23 +0200" References: <861z0sr8bk.wl@localhost.local.idaemons.org> User-Agent: Wanderlust/1.1.2 (Raspberry Beret) EMIKO/1.13.12 (Euglena sociabilis) FLIM/1.13.2 (Kasanui) APEL/10.2 MULE XEmacs/21.1 (patch 10) (Capitol Reef) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 1BEF D9B2 BABD 25D7 659A FD08 89C2 F3BE E981 4E16 MIME-Version: 1.0 (generated by EMIKO 1.13.12 - "Euglena sociabilis") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 17 Jul 2000 23:38:23 +0200, DES wrote: > I've spent most of the night fixing this and am about to commit the > last changes, so you should be able to cvsup and build working > libfetch and fetch in an hour or two. Thanks! I could confirm that your changes fixed the problem, and am happy to see them MFC'd before 4.1-RELEASE. :) -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 22:18:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8B02C37B9AE; Mon, 17 Jul 2000 22:18:26 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA83912; Mon, 17 Jul 2000 23:18:23 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA68375; Mon, 17 Jul 2000 23:18:17 -0600 (MDT) Message-Id: <200007180518.XAA68375@harmony.village.org> To: "Andrey A. Chernov" Subject: Re: HEADS UP, mtree defaults returns back to original Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 16 Jul 2000 09:11:34 PDT." <20000716091132.A29072@freebsd.org> References: <20000716091132.A29072@freebsd.org> Date: Mon, 17 Jul 2000 23:18:17 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000716091132.A29072@freebsd.org> "Andrey A. Chernov" writes: : 20000716: : mtree now NOT follows symlinks by default, old behaviour restored to be : compatible with rest of *BSD camp. New -L option added to follow : symlinks. This require manual mtree rebuilding before 'make world' Is this still needed? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 22:37:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id B9DD537BA4D; Mon, 17 Jul 2000 22:37:11 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id HAA06767; Tue, 18 Jul 2000 07:36:46 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Jeroen C. van Gelderen" Cc: Alexander Langer , "Louis A. Mamakos" , Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Mon, 17 Jul 2000 21:44:12 EDT." <3973B66C.D6BD5BFD@vangelderen.org> Date: Tue, 18 Jul 2000 07:36:45 +0200 Message-ID: <6765.963898605@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3973B66C.D6BD5BFD@vangelderen.org>, "Jeroen C. van Gelderen" writes : >> Predicting the clock's offset from reality and the two way path to >> the server of choice is impossible, plus if people enable authentication >> later on the packets will be choke full of high-quality entropy. > >Please quantify 'impossible'. People have tried for 30+ years to predict what a quartz xtal will do next. Nobody expects any chance of success. Add to this the need to predict the difference between one or more NTP servers and your local qartz xtal and I think we can safely say "impossible". >I think we first need to figure out the security implications. I think the security implications of having no entropy are much worse than having entropy which a truly superhuman *maybe* could guess *some* of the bits in, are far worse. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 23: 3:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 64A8E37B9AE for ; Mon, 17 Jul 2000 23:03:38 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id IAA03329; Tue, 18 Jul 2000 08:04:37 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007180604.IAA03329@grimreaper.grondar.za> To: "Louis A. Mamakos" Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <200007180145.VAA00554@whizzo.transsys.com> In-Reply-To: <200007180145.VAA00554@whizzo.transsys.com> ; from "Louis A. Mamakos" "Mon, 17 Jul 2000 21:45:52 -0400." Date: Tue, 18 Jul 2000 08:04:37 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually, you could really use this in ntpd(8), rather than just ntpdate. > You could crank in the offset and delay samples for each packet > received from an NTP peer; this will have the effect of adding into > the entropy pool the "noise" in the latency of the path between you > and each of your NTP peers. This varies over time with each sample, > and in fact, NTP goes to considerable effort in it's sample filtering > to exclude the noisy samples. We need to get that date before it's > discarded and contribute it to the entropy cause. You forget; a snooper watching your (ether)net has access to nearly all of this information. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 23: 6: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 5AA7C37BA95 for ; Mon, 17 Jul 2000 23:06:03 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id IAA07085; Tue, 18 Jul 2000 08:05:51 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mark Murray Cc: "Louis A. Mamakos" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Tue, 18 Jul 2000 08:04:37 +0200." <200007180604.IAA03329@grimreaper.grondar.za> Date: Tue, 18 Jul 2000 08:05:51 +0200 Message-ID: <7083.963900351@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007180604.IAA03329@grimreaper.grondar.za>, Mark Murray writes: >> Actually, you could really use this in ntpd(8), rather than just ntpdate. >> You could crank in the offset and delay samples for each packet >> received from an NTP peer; this will have the effect of adding into >> the entropy pool the "noise" in the latency of the path between you >> and each of your NTP peers. This varies over time with each sample, >> and in fact, NTP goes to considerable effort in it's sample filtering >> to exclude the noisy samples. We need to get that date before it's >> discarded and contribute it to the entropy cause. > >You forget; a snooper watching your (ether)net has access to nearly >all of this information. No, he doesn't have access to the offset from the machines local clock. I ran a quick & dirty test here on some logfiles: that offset is very close to white noise. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 23:18:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 18F7537BA28 for ; Mon, 17 Jul 2000 23:18:54 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id IAA03375; Tue, 18 Jul 2000 08:17:57 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007180617.IAA03375@grimreaper.grondar.za> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <6765.963898605@critter.freebsd.dk> In-Reply-To: <6765.963898605@critter.freebsd.dk> ; from Poul-Henning Kamp "Tue, 18 Jul 2000 07:36:45 +0200." Date: Tue, 18 Jul 2000 08:17:57 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > People have tried for 30+ years to predict what a quartz xtal > will do next. Nobody expects any chance of success. Add to this > the need to predict the difference between one or more NTP servers > and your local qartz xtal and I think we can safely say "impossible". You can't predict this, but you can _measure_ it with a degree of accuracy. The attacker can use this accuracy to reduce the number of tries in his attack. > >I think we first need to figure out the security implications. > > I think the security implications of having no entropy are much > worse than having entropy which a truly superhuman *maybe* could > guess *some* of the bits in, are far worse. Yarrow addresses this problem; even if the attacker does manage to get the internal state, Yarrow will revover. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 23:25:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id E263E37BA4D for ; Mon, 17 Jul 2000 23:25:09 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id IAA07219; Tue, 18 Jul 2000 08:24:58 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Tue, 18 Jul 2000 08:17:57 +0200." <200007180617.IAA03375@grimreaper.grondar.za> Date: Tue, 18 Jul 2000 08:24:58 +0200 Message-ID: <7217.963901498@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007180617.IAA03375@grimreaper.grondar.za>, Mark Murray writes: >> People have tried for 30+ years to predict what a quartz xtal >> will do next. Nobody expects any chance of success. Add to this >> the need to predict the difference between one or more NTP servers >> and your local qartz xtal and I think we can safely say "impossible". > >You can't predict this, but you can _measure_ it with a degree of >accuracy. The attacker can use this accuracy to reduce the number >of tries in his attack. No he cannot. The NTP poll period is 64 seconds or longer and unless you have done something special about your hardware, he cannot predict all bits. If he could, ntp would have a longer poll period :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 23:25:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id B0DE137BA4D; Mon, 17 Jul 2000 23:25:28 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 2EA884D; Tue, 18 Jul 2000 02:25:27 -0400 (AST) Message-ID: <3973F857.1A59FCA@vangelderen.org> Date: Tue, 18 Jul 2000 02:25:27 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: Alexander Langer , "Louis A. Mamakos" , Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <6765.963898605@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > In message <3973B66C.D6BD5BFD@vangelderen.org>, "Jeroen C. van Gelderen" writes > : > > >> Predicting the clock's offset from reality and the two way path to > >> the server of choice is impossible, plus if people enable authentication > >> later on the packets will be choke full of high-quality entropy. > > > >Please quantify 'impossible'. > > People have tried for 30+ years to predict what a quartz xtal > will do next. Nobody expects any chance of success. Add to this > the need to predict the difference between one or more NTP servers > and your local qartz xtal and I think we can safely say "impossible". See my reply to David Schwartz. What kind of numbers are we talking about? > >I think we first need to figure out the security implications. > > I think the security implications of having no entropy are much > worse than having entropy which a truly superhuman *maybe* could > guess *some* of the bits in, are far worse. I agree, but to paraphrase: that's policy decision. Just quantify it so that people can be their own judge. Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 23:34:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 7EC9137BA4D; Mon, 17 Jul 2000 23:34:17 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id IAA07286; Tue, 18 Jul 2000 08:34:00 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Jeroen C. van Gelderen" Cc: Alexander Langer , "Louis A. Mamakos" , Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Tue, 18 Jul 2000 02:25:27 EDT." <3973F857.1A59FCA@vangelderen.org> Date: Tue, 18 Jul 2000 08:34:00 +0200 Message-ID: <7284.963902040@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3973F857.1A59FCA@vangelderen.org>, "Jeroen C. van Gelderen" writes: >> People have tried for 30+ years to predict what a quartz xtal >> will do next. Nobody expects any chance of success. Add to this >> the need to predict the difference between one or more NTP servers >> and your local qartz xtal and I think we can safely say "impossible". > >See my reply to David Schwartz. What kind of numbers are we >talking about? With microsecond timestamps, 64second ntp poll period we are talking about approx 10 bits of randomness in the received packet and about 3 bits of randomness in the clock difference. FreeBSD uses nanosecond timestamping (Actually could do nanoseconds with 32 bitfractions), but that only adds about 4 bits to the clock difference due to the clock frequency end interrupt hardware. >> >I think we first need to figure out the security implications. >> >> I think the security implications of having no entropy are much >> worse than having entropy which a truly superhuman *maybe* could >> guess *some* of the bits in, are far worse. > >I agree, but to paraphrase: that's policy decision. >Just quantify it so that people can be their own judge. No, it is not policy to try to get as many random bits as we can by default. It would be policy to *not* do so for some obscure principle of scientific purity. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 23:49:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.2.163]) by hub.freebsd.org (Postfix) with ESMTP id 5719D37BC07; Mon, 17 Jul 2000 23:49:12 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.15 #1) id 13ERBU-000BEJ-00; Tue, 18 Jul 2000 08:48:52 +0200 From: Sheldon Hearn To: "Kurt D. Zeilenga" Cc: Mark Murray , Maxim Sobolev , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Mon, 17 Jul 2000 16:27:17 MST." <4.3.2.7.0.20000717161342.00b0c780@infidel.boolean.net> Date: Tue, 18 Jul 2000 08:48:52 +0200 Message-ID: <43170.963902932@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000 16:27:17 MST, "Kurt D. Zeilenga" wrote: > Note that there should be no need to cron the job. You're right. My suggestion to use cron's @reboot was as stupid as they come. :-) Sorry, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 23:52: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id B8B0A37BBFC; Mon, 17 Jul 2000 23:52:02 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 3C97D4D; Tue, 18 Jul 2000 02:52:01 -0400 (AST) Message-ID: <3973FE91.BB1868DD@vangelderen.org> Date: Tue, 18 Jul 2000 02:52:01 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: Alexander Langer , "Louis A. Mamakos" , Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <7284.963902040@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > In message <3973F857.1A59FCA@vangelderen.org>, "Jeroen C. van Gelderen" writes: > > >> People have tried for 30+ years to predict what a quartz xtal > >> will do next. Nobody expects any chance of success. Add to this > >> the need to predict the difference between one or more NTP servers > >> and your local qartz xtal and I think we can safely say "impossible". > > > >See my reply to David Schwartz. What kind of numbers are we > >talking about? > > With microsecond timestamps, 64second ntp poll period we are talking > about approx 10 bits of randomness in the received packet and about > 3 bits of randomness in the clock difference. > > FreeBSD uses nanosecond timestamping (Actually could do nanoseconds > with 32 bitfractions), but that only adds about 4 bits to the clock > difference due to the clock frequency end interrupt hardware. Thanks! This is useful. > >> >I think we first need to figure out the security implications. > >> > >> I think the security implications of having no entropy are much > >> worse than having entropy which a truly superhuman *maybe* could > >> guess *some* of the bits in, are far worse. > > > >I agree, but to paraphrase: that's policy decision. > >Just quantify it so that people can be their own judge. > > No, it is not policy to try to get as many random bits as we can > by default. It would be policy to *not* do so for some obscure > principle of scientific purity. It's up to the user to decide what security level he needs. Both ought to be possible but having an insecure box ought to be an explicit decision. I think you will agree that there needs to be a decent security level by default. I.e. newly generated SSH host keys are sufficiently secure. Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 23:53: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id F343337BB50 for ; Mon, 17 Jul 2000 23:53:02 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id IAA04139; Tue, 18 Jul 2000 08:52:07 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007180652.IAA04139@grimreaper.grondar.za> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <7083.963900351@critter.freebsd.dk> In-Reply-To: <7083.963900351@critter.freebsd.dk> ; from Poul-Henning Kamp "Tue, 18 Jul 2000 08:05:51 +0200." Date: Tue, 18 Jul 2000 08:52:07 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No, he doesn't have access to the offset from the machines local clock. > > I ran a quick & dirty test here on some logfiles: that offset is > very close to white noise. With what amplitude? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 23:57:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 0444237B6B2 for ; Mon, 17 Jul 2000 23:57:08 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id IAA07471; Tue, 18 Jul 2000 08:56:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Tue, 18 Jul 2000 08:52:07 +0200." <200007180652.IAA04139@grimreaper.grondar.za> Date: Tue, 18 Jul 2000 08:56:57 +0200 Message-ID: <7469.963903417@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007180652.IAA04139@grimreaper.grondar.za>, Mark Murray writes: >> No, he doesn't have access to the offset from the machines local clock. >> >> I ran a quick & dirty test here on some logfiles: that offset is >> very close to white noise. > >With what amplitude? Depends on the termal environment of your xtal obviously :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 17 23:58:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 121CD37BB60; Mon, 17 Jul 2000 23:58:41 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id IAA07492; Tue, 18 Jul 2000 08:58:26 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Jeroen C. van Gelderen" Cc: Alexander Langer , "Louis A. Mamakos" , Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Tue, 18 Jul 2000 02:52:01 EDT." <3973FE91.BB1868DD@vangelderen.org> Date: Tue, 18 Jul 2000 08:58:26 +0200 Message-ID: <7490.963903506@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3973FE91.BB1868DD@vangelderen.org>, "Jeroen C. van Gelderen" writes >It's up to the user to decide what security level he needs. >Both ought to be possible but having an insecure box ought >to be an explicit decision. Principle of POLA: The box doesn't come up in a stupid configuration right after install. Principle of "tools, not politics": You can configure it stupidly if you want, you can also strengthen it beyond practical use if you want. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 0: 2:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout1.silyn-tek.de (mout1.silyn-tek.de [194.25.165.69]) by hub.freebsd.org (Postfix) with ESMTP id 0A58237B777; Tue, 18 Jul 2000 00:02:50 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from [192.168.32.34] (helo=mx2.silyn-tek.de) by mout1.silyn-tek.de with esmtp (Exim 3.13 #1) id 13EROs-0003zB-00; Tue, 18 Jul 2000 09:02:42 +0200 Received: from p3e9c114a.dip0.t-ipconnect.de ([62.156.17.74] helo=neutron.cichlids.com) by mx2.silyn-tek.de with esmtp (Exim 3.13 #1) id 13EROq-00053d-00; Tue, 18 Jul 2000 09:02:40 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 687ABAB91; Tue, 18 Jul 2000 09:04:12 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 0E42414A62; Tue, 18 Jul 2000 09:02:40 +0200 (CEST) Date: Tue, 18 Jul 2000 09:02:40 +0200 From: Alexander Langer To: "Louis A. Mamakos" Cc: Poul-Henning Kamp , Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak Message-ID: <20000718090240.A5383@cichlids.cichlids.com> Mail-Followup-To: "Louis A. Mamakos" , Poul-Henning Kamp , Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG References: <2613.963842256@critter.freebsd.dk> <200007180145.VAA00554@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200007180145.VAA00554@whizzo.transsys.com>; from louie@TransSys.COM on Mon, Jul 17, 2000 at 09:45:52PM -0400 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Louis A. Mamakos (louie@TransSys.COM): > Actually, you could really use this in ntpd(8), rather than just ntpdate. Hmm, as addition, I agree. However, I think more people use ntpdate than ntpd, and thus ntpdate is a good place :) Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 1:20:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 993F737B8A1 for ; Tue, 18 Jul 2000 01:20:49 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (qmail 767 invoked from network); 18 Jul 2000 08:20:46 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 18 Jul 2000 08:20:46 -0000 Date: Tue, 18 Jul 2000 18:20:40 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Kris Kennaway Cc: Mark Murray , Bill Fumerola , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 16 Jul 2000, Kris Kennaway wrote: > On the other hand, doing a dd if=/dev/random of=/dev/null gives me > infinite "randomness" at 10MB/sec - have the semantics of /dev/random > changed? Yes. /dev/random is now just an alias for /dev/urandom (or vice versa). You must have a fast machine to get 10MB/sec. I see the following speeds (using a better reading program than dd; dd gives up on EOF on the old /dev/random): old /dev/random on P5/133 5K/sec old /dev/urandom on P5/133 244K/sec old /dev/random on Celeron 366 overclocked to 5.5*95 25K/sec old /dev/urandom on Celeron 366 overclocked to 5.5*95 970K/sec new /dev/*random on Celeron 400 overclocked to 6.0*75 270K/sec Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 1:22:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (markm.ops.uunet.co.za [196.31.2.167]) by hub.freebsd.org (Postfix) with ESMTP id 017C737BB3C; Tue, 18 Jul 2000 01:22:09 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id IAA04177; Tue, 18 Jul 2000 08:58:12 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007180658.IAA04177@grimreaper.grondar.za> To: Poul-Henning Kamp Cc: "Jeroen C. van Gelderen" , Alexander Langer , "Louis A. Mamakos" , Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <7284.963902040@critter.freebsd.dk> In-Reply-To: <7284.963902040@critter.freebsd.dk> ; from Poul-Henning Kamp "Tue, 18 Jul 2000 08:34:00 +0200." Date: Tue, 18 Jul 2000 08:58:12 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > With microsecond timestamps, 64second ntp poll period we are talking > about approx 10 bits of randomness in the received packet and about > 3 bits of randomness in the clock difference. > > FreeBSD uses nanosecond timestamping (Actually could do nanoseconds > with 32 bitfractions), but that only adds about 4 bits to the clock > difference due to the clock frequency end interrupt hardware. So the attacker is down to 17 bits == 128k guesses. Now that is good entropy, but we need to know what the attacker can see inside the packet etc. How else can he reduce his keyspace? > No, it is not policy to try to get as many random bits as we can > by default. It would be policy to *not* do so for some obscure > principle of scientific purity. Pray explain? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 1:24:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 5BB2A37BC88; Tue, 18 Jul 2000 01:24:27 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id BAA51655; Tue, 18 Jul 2000 01:24:27 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 18 Jul 2000 01:24:27 -0700 (PDT) From: Kris Kennaway To: Bruce Evans Cc: Mark Murray , Bill Fumerola , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jul 2000, Bruce Evans wrote: > You must have a fast machine to get 10MB/sec. I see the following speeds > (using a better reading program than dd; dd gives up on EOF on the old > /dev/random): Oops, I misread the rate by 2 orders of magnitude. I get about 100K/sec on my PPro/233 :-) > old /dev/random on P5/133 5K/sec > old /dev/urandom on P5/133 244K/sec > old /dev/random on Celeron 366 overclocked to 5.5*95 25K/sec > old /dev/urandom on Celeron 366 overclocked to 5.5*95 970K/sec > new /dev/*random on Celeron 400 overclocked to 6.0*75 270K/sec Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 1:40:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by hub.freebsd.org (Postfix) with ESMTP id 2861537BC49 for ; Tue, 18 Jul 2000 01:40:09 -0700 (PDT) (envelope-from n_hibma@qubesoft.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by anchor-post-32.mail.demon.net with esmtp (Exim 2.12 #1) id 13ESv8-0007pP-0W; Tue, 18 Jul 2000 09:40:07 +0100 Received: from henny.webweaving.org (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id JAA42328; Tue, 18 Jul 2000 09:40:04 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id UAA05292; Mon, 17 Jul 2000 20:30:39 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Mon, 17 Jul 2000 20:30:38 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Mike Meyer Cc: Warner Losh , Bob Bishop , FreeBSD CURRENT Mailing List , USB BSD list Subject: Re: USB modems In-Reply-To: <14682.46457.71995.372686@guru.mired.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Right, I finally committed the driver you sent me. let me know if I've made a mistake and committed the wrong one. Mike, which Supra modem do you have? I've got a SupraMax 56K modem, SUP2920 and it gives me a rainforest worth of endpoints, not somethig that looks like a ACM CD Class device. Nick On Wed, 28 Jun 2000, Mike Meyer wrote: > Warner Losh writes: > > In message Bob Bishop writes: > > : Can anyone give a quick synopsis of the current status of support for USB > > : modems? TIA > > They aren't supported yet. There's at least one group that might be > > working on them. The value of supporting them is well known. Take > > care in your purcahse of a usb modem because some of them expect an > > isochronous audio stream... > > Nick (and I, for that matter) have a umodem.c that works, for some > definition of "works". It seems to work fine on USR USB modems. On the > Supra I bought (because it was easily available), it works for dialout > and makes PPP connections, but outgoing IP connections fail under an > indeterminate set of conditions. It's not clear where the problem is - > I'll be investigating it as soon as I once again have free time (a > couple of weeks). > > Nick has indicated he was going to try this version and commit it, but > it hasn't happened yet. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 1:54:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (markm.ops.uunet.co.za [196.31.2.167]) by hub.freebsd.org (Postfix) with ESMTP id 378E337B6DC for ; Tue, 18 Jul 2000 01:54:18 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id KAA00363; Tue, 18 Jul 2000 10:53:57 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007180853.KAA00363@grimreaper.grondar.za> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <7469.963903417@critter.freebsd.dk> In-Reply-To: <7469.963903417@critter.freebsd.dk> ; from Poul-Henning Kamp "Tue, 18 Jul 2000 08:56:57 +0200." Date: Tue, 18 Jul 2000 10:53:57 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> I ran a quick & dirty test here on some logfiles: that offset is > >> very close to white noise. > > > >With what amplitude? > > Depends on the termal environment of your xtal obviously :-) Help me here! :-) In your observed sample, what was the white noise amplitude? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 2: 4:50 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 17CE037BCBA; Tue, 18 Jul 2000 02:04:48 -0700 (PDT) Date: Tue, 18 Jul 2000 02:04:48 -0700 From: "Andrey A. Chernov" To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: HEADS UP, mtree defaults returns back to original Message-ID: <20000718020444.A50546@freebsd.org> References: <20000716091132.A29072@freebsd.org> <200007180518.XAA68375@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <200007180518.XAA68375@harmony.village.org>; from imp@village.org on Mon, Jul 17, 2000 at 11:18:17PM -0600 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 11:18:17PM -0600, Warner Losh wrote: > In message <20000716091132.A29072@freebsd.org> "Andrey A. Chernov" writes: > : 20000716: > : mtree now NOT follows symlinks by default, old behaviour restored to be > : compatible with rest of *BSD camp. New -L option added to follow > : symlinks. This require manual mtree rebuilding before 'make world' > > Is this still needed? The last sentence is not needed. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 2:44:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom0-123.telepath.com [216.14.0.123]) by hub.freebsd.org (Postfix) with SMTP id 1213A37B66D for ; Tue, 18 Jul 2000 02:44:02 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 80829 invoked by uid 100); 18 Jul 2000 09:43:14 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14708.9906.122604.993279@guru.mired.org> Date: Tue, 18 Jul 2000 04:43:14 -0500 (CDT) To: Nick Hibma Cc: Warner Losh , Bob Bishop , FreeBSD CURRENT Mailing List , USB BSD list Subject: Re: USB modems In-Reply-To: References: <14682.46457.71995.372686@guru.mired.org> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma writes: > Right, I finally committed the driver you sent me. let me know if I've > made a mistake and committed the wrong one. Well, the one you committed doesn't have the notification support I added, or the serial state bits that are in usbcdc.h. Do you need/want copies of the one I've been working on? Looks like umodem.c didn't make it into conf/files, either. > Mike, which Supra modem do you have? I've got a SupraMax 56K modem, > SUP2920 and it gives me a rainforest worth of endpoints, not somethig > that looks like a ACM CD Class device. It's a SupraExpress 56K USB. I believe the SupraMax 56K is documented as not being an ACM CD device. I've think I've set things up and cleared my plate enough that I can work on the problem I've been seeing. I'm also curious about is whether anyone else using USB modems for ppp is using userland ppp, or if they're all using kernel ppp. ; Tue, 18 Jul 2000 03:12:38 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id MAA08680; Tue, 18 Jul 2000 12:12:26 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Tue, 18 Jul 2000 10:53:57 +0200." <200007180853.KAA00363@grimreaper.grondar.za> Date: Tue, 18 Jul 2000 12:12:25 +0200 Message-ID: <8678.963915145@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007180853.KAA00363@grimreaper.grondar.za>, Mark Murray writes: >> >> I ran a quick & dirty test here on some logfiles: that offset is >> >> very close to white noise. >> > >> >With what amplitude? >> >> Depends on the termal environment of your xtal obviously :-) > >Help me here! :-) > >In your observed sample, what was the white noise amplitude? What do you mean by "amplitude" ? The frequency deviation ? The phase error ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 3:16: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 1974437B7DC; Tue, 18 Jul 2000 03:15:53 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 18 Jul 2000 11:15:34 +0100 (BST) Date: Tue, 18 Jul 2000 11:15:34 +0100 From: David Malone To: Kris Kennaway Cc: Mark Murray , Poul-Henning Kamp , current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak Message-ID: <20000718111534.A20086@walton.maths.tcd.ie> References: <200007171459.QAA00888@grimreaper.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.2i In-Reply-To: ; from kris@FreeBSD.org on Mon, Jul 17, 2000 at 01:16:43PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 01:16:43PM -0700, Kris Kennaway wrote: > On Mon, 17 Jul 2000, Mark Murray wrote: > > > What we really need is this: > > > > > > fetch -o http://entropy.freebsd.org/ > /dev/random > > > > For this to work, you'll need to encrypt the traffic. > > > > fetch -o https://entropy.freebsd.org/ > /dev/random > > ^ > > > > If the world knows what they are, your bits aren't random enough. > > Plus you need to authenticate (and obviously trust) your entropy server > and the data stream to make sure they're not actually someone else feeding > you zeros. I think there are other practical issues too. Unless the new libfetch fetch supports https this won't work. More to the point, I'd guess https needs a working /dev/random to set up the secure connection, but we're running fetch to set up /dev/random. How much entropy can we get from: (date; dmesg ; sysctl -X; vmstat -i ) > /dev/random Just playing it looks like you might get 4 so bits from the rtc and clk interupt count alone. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 4:15:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by hub.freebsd.org (Postfix) with ESMTP id CF15B37B56F for ; Tue, 18 Jul 2000 04:15:53 -0700 (PDT) (envelope-from n_hibma@qubesoft.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by anchor-post-31.mail.demon.net with esmtp (Exim 2.12 #1) id 13EVLq-000Br9-0V; Tue, 18 Jul 2000 12:15:50 +0100 Received: from henny.webweaving.org (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id MAA46529; Tue, 18 Jul 2000 12:15:49 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id LAA07353; Tue, 18 Jul 2000 11:43:09 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Tue, 18 Jul 2000 11:43:09 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Mike Meyer Cc: Warner Losh , Bob Bishop , FreeBSD CURRENT Mailing List , USB BSD list Subject: Re: USB modems In-Reply-To: <14708.9906.122604.993279@guru.mired.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, the one you committed doesn't have the notification support I > added, or the serial state bits that are in usbcdc.h. Do you need/want > copies of the one I've been working on? Yes, please. I must have them somewhere, but it might be a better idea to get your latest version. > Looks like umodem.c didn't make it into conf/files, either. Fixed (NOTES as well). Man pages, we will need those as well. Anyone? Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 6: 7:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (markm.ops.uunet.co.za [196.31.2.167]) by hub.freebsd.org (Postfix) with ESMTP id 69D0B37BDA2 for ; Tue, 18 Jul 2000 06:07:48 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id PAA00891; Tue, 18 Jul 2000 15:05:34 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007181305.PAA00891@grimreaper.grondar.za> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <8678.963915145@critter.freebsd.dk> In-Reply-To: <8678.963915145@critter.freebsd.dk> ; from Poul-Henning Kamp "Tue, 18 Jul 2000 12:12:25 +0200." Date: Tue, 18 Jul 2000 15:05:34 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Help me here! :-) > > > >In your observed sample, what was the white noise amplitude? > > What do you mean by "amplitude" ? The frequency deviation ? > The phase error ? The standard deviation of all the observation "amplitudes", measured in bits. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 7:37:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from spirit.jaded.net (shortbus.jaded.net [216.94.132.8]) by hub.freebsd.org (Postfix) with ESMTP id 64DA237BDCF for ; Tue, 18 Jul 2000 07:37:54 -0700 (PDT) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id KAA01240; Tue, 18 Jul 2000 10:37:29 -0400 (EDT) (envelope-from dan) Date: Tue, 18 Jul 2000 10:37:29 -0400 From: Dan Moschuk To: Mark Murray Cc: current@freebsd.org Subject: Re: randomdev entropy gathering is really weak Message-ID: <20000718103729.A1221@spirit.jaded.net> References: <20000716105943.A60072@freebsd.org> <200007161826.UAA03911@grimreaper.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007161826.UAA03911@grimreaper.grondar.za>; from mark@grondar.za on Sun, Jul 16, 2000 at 08:26:44PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | Gotcha - fix coming; I need to stash some randomness at shutdown time, and | use that to reseed the RNG at reboot time. What about saving the state of the RNG and re-reading it on bootup? That will allow Yarrow to continue right where it left off. :-) -Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 7:43: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from spirit.jaded.net (shortbus.jaded.net [216.94.132.8]) by hub.freebsd.org (Postfix) with ESMTP id 4DAF237BE49; Tue, 18 Jul 2000 07:43:03 -0700 (PDT) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id KAA01262; Tue, 18 Jul 2000 10:40:22 -0400 (EDT) (envelope-from dan) Date: Tue, 18 Jul 2000 10:40:22 -0400 From: Dan Moschuk To: Poul-Henning Kamp Cc: "Louis A. Mamakos" , Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak Message-ID: <20000718104022.B1221@spirit.jaded.net> References: <200007171319.JAA04774@whizzo.transsys.com> <2450.963841019@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <2450.963841019@critter.freebsd.dk>; from phk@critter.freebsd.dk on Mon, Jul 17, 2000 at 03:36:59PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | >In fact, it would be rather interesting to have a configuration flag which | >always forces something like an fsck on a file system in order to provide | >some entropy to the random device. Or some other user-exposed way of | >providing entropy. I might have some data on disk, or some network | >operations which can be performed to help seed the entropy pool. | | What we really need is this: | | fetch -o http://entropy.freebsd.org/ > /dev/random | | with a bunch of volounteers providing random bits to people in need. | | I have thought about adding a entropy server to my array of weird | servers in my lab. Something like a Geiger counter and a smokedetector | could do wonders. If you wanted to have some fun with this, you could do a rc5-like distributed client, feeding random bits to a server, and pulling down new bits every so often! -Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 7:44:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from spirit.jaded.net (shortbus.jaded.net [216.94.132.8]) by hub.freebsd.org (Postfix) with ESMTP id E819737BE58; Tue, 18 Jul 2000 07:44:24 -0700 (PDT) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id KAA01271; Tue, 18 Jul 2000 10:41:34 -0400 (EDT) (envelope-from dan) Date: Tue, 18 Jul 2000 10:41:34 -0400 From: Dan Moschuk To: Poul-Henning Kamp Cc: Alexander Langer , "Louis A. Mamakos" , Mark Murray , "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak Message-ID: <20000718104134.C1221@spirit.jaded.net> References: <20000717154549.A18676@cichlids.cichlids.com> <2613.963842256@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <2613.963842256@critter.freebsd.dk>; from phk@critter.freebsd.dk on Mon, Jul 17, 2000 at 03:57:36PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | DuH! | | NTP is the perfect way to gather entropy at bootup! | | Predicting the clock's offset from reality and the two way path to | the server of choice is impossible, plus if people enable authentication | later on the packets will be choke full of high-quality entropy. | | We need an enterprising soul to add an option (default on) to | ntpdate to write the received packets in toto to /dev/random | if it exists. | | If somebody does this, I will spear-head the effort of getting it | into the ntpv4 sources (Hmm, don't I have a commit bit there | already ? Can't remember...) Well, how many other OSs out there allow /dev/random to be written to? -Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 7:47:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from spirit.jaded.net (shortbus.jaded.net [216.94.132.8]) by hub.freebsd.org (Postfix) with ESMTP id 5EEC837BE58; Tue, 18 Jul 2000 07:47:44 -0700 (PDT) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id KAA01297; Tue, 18 Jul 2000 10:47:35 -0400 (EDT) (envelope-from dan) Date: Tue, 18 Jul 2000 10:47:35 -0400 From: Dan Moschuk To: David Malone Cc: Kris Kennaway , Mark Murray , Poul-Henning Kamp , current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak Message-ID: <20000718104735.D1221@spirit.jaded.net> References: <200007171459.QAA00888@grimreaper.grondar.za> <20000718111534.A20086@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000718111534.A20086@walton.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Tue, Jul 18, 2000 at 11:15:34AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | I think there are other practical issues too. Unless the new libfetch | fetch supports https this won't work. More to the point, I'd | guess https needs a working /dev/random to set up the secure | connection, but we're running fetch to set up /dev/random. | | How much entropy can we get from: | | (date; dmesg ; sysctl -X; vmstat -i ) > /dev/random | | Just playing it looks like you might get 4 so bits from the | rtc and clk interupt count alone. None. Any data that is publically available via userland should not be used for cryptography. -Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 8:31:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 0721D37BE98; Tue, 18 Jul 2000 08:31:21 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 18 Jul 2000 16:31:09 +0100 (BST) To: Dan Moschuk Cc: David Malone , Kris Kennaway , Mark Murray , Poul-Henning Kamp , current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Tue, 18 Jul 2000 10:47:35 EDT." <20000718104735.D1221@spirit.jaded.net> X-Request-Do: Date: Tue, 18 Jul 2000 16:30:57 +0100 From: David Malone Message-ID: <200007181631.aa20379@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > | (date; dmesg ; sysctl -X; vmstat -i ) > /dev/random > | > | Just playing it looks like you might get 4 so bits from the > | rtc and clk interupt count alone. > None. Any data that is publically available via userland should not be > used for cryptography. The data from sysctl -X and vmstat -i vary quite a lot with time and would be difficult to guess in their entrieity, even given the their values at some later date. While any piece of data from these commands isn't hard to guess, the idea is to take a few bits of each of them. I don't claim this produces hundreds of bits of entropy, but I'd expect it to produce ten or twenty bits, even if you are given the output of these from some stage shortly in the future. I note from Mark's comments that writing stuff to /dev/random doesn't change /dev/random's notion of how much entropy it has, but does reseed the generator - so what we're talking about here is the entropy of the seed - or how difficult to guess it is. He does mention a very similar way of reseeding to the above: (ps -gauxwww; netstat -an; dmesg; vmstat -c10 1) > /dev/random David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 8:44:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 15E3737BEDF for ; Tue, 18 Jul 2000 08:44:54 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id RAA10165; Tue, 18 Jul 2000 17:44:39 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Tue, 18 Jul 2000 15:05:34 +0200." <200007181305.PAA00891@grimreaper.grondar.za> Date: Tue, 18 Jul 2000 17:44:39 +0200 Message-ID: <10163.963935079@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007181305.PAA00891@grimreaper.grondar.za>, Mark Murray writes: >> >Help me here! :-) >> > >> >In your observed sample, what was the white noise amplitude? >> >> What do you mean by "amplitude" ? The frequency deviation ? >> The phase error ? > >The standard deviation of all the observation "amplitudes", measured >in bits. OK, then the answer is: "a couple of bits" -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 8:52:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from hurricane.columbus.rr.com (m5.columbus.rr.com [204.210.252.249]) by hub.freebsd.org (Postfix) with ESMTP id BC66637BEAD for ; Tue, 18 Jul 2000 08:52:11 -0700 (PDT) (envelope-from caa@columbus.rr.com) Received: from blizzard.columbus.rr.com ([204.210.252.252]) by hurricane.columbus.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-53939U80000L80000S0V35) with ESMTP id com; Tue, 18 Jul 2000 11:52:35 -0400 Received: from columbus.rr.com (dhcp9559163.columbus.rr.com [24.95.59.163]) by blizzard.columbus.rr.com (8.9.3/8.9.3) with ESMTP id LAA12256; Tue, 18 Jul 2000 11:51:13 -0400 (EDT) Received: (from caa@localhost) by columbus.rr.com (8.9.3/8.9.3) id LAA05179; Tue, 18 Jul 2000 11:52:58 GMT (envelope-from caa) Date: Tue, 18 Jul 2000 11:52:57 +0000 From: Charles Anderson To: usb-bsd@egroups.com Cc: Mike Meyer , Warner Losh , Bob Bishop , FreeBSD CURRENT Mailing List Subject: Re: [usb-bsd] Re: USB modems Message-ID: <20000718115257.A2474@midgard.dhs.org> References: <14708.9906.122604.993279@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from n_hibma@calcaphon.com on Tue, Jul 18, 2000 at 11:43:09AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Speaking of manpages, are there any out there for ugen(4), uhid(4) & ulpt(4) that are referenced in the usb(4) man page? -Charlie On Tue, Jul 18, 2000 at 11:43:09AM +0100, Nick Hibma wrote: > > Well, the one you committed doesn't have the notification support I > > added, or the serial state bits that are in usbcdc.h. Do you need/want > > copies of the one I've been working on? > > Yes, please. I must have them somewhere, but it might be a better idea > to get your latest version. > > > Looks like umodem.c didn't make it into conf/files, either. > > Fixed (NOTES as well). > > Man pages, we will need those as well. Anyone? > > Nick -- Charles Anderson caa@columbus.rr.com No quote, no nothin' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 9: 1:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id 16E0F37BE95; Tue, 18 Jul 2000 09:01:39 -0700 (PDT) (envelope-from netchild@leidinger.net) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout0.freenet.de with esmtp (Exim 3.15 #1) id 13EZoL-0002WY-00; Tue, 18 Jul 2000 18:01:33 +0200 Received: from a3347.pppool.de ([213.6.51.71] helo=Magelan.Leidinger.net) by mx3.freenet.de with esmtp (Exim 3.15 #1) id 13EZoK-0006r0-00; Tue, 18 Jul 2000 18:01:33 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id SAA02045; Tue, 18 Jul 2000 18:01:02 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200007181601.SAA02045@Magelan.Leidinger.net> Date: Tue, 18 Jul 2000 18:01:00 +0200 (CEST) From: Alexander Leidinger Subject: Re: randomdev entropy gathering is really weak To: mark@grondar.za Cc: current@FreeBSD.ORG, phk@freebsd.org In-Reply-To: <200007180604.IAA03329@grimreaper.grondar.za> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Jul, Mark Murray wrote: [using NTP to gather entropy] > You forget; a snooper watching your (ether)net has access to nearly > all of this information. I've only seen messages about getting ntp information over a network (so far), and I'm not familiar with crypto/entropy gathering/ntp, so forgive me if I ask a stupid question, but does everyone also think about those systems which have a more or less precise clock attached (e.g. GPS or atomic clocks which sync the system clock via nptd)? And what are the numbers for this solution (for those people which are interested in numbers to be their own judge)? Bye, Alexander. -- Reboot America. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 9: 6: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id E383037BE92 for ; Tue, 18 Jul 2000 09:05:57 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id SAA10398; Tue, 18 Jul 2000 18:05:43 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Alexander Leidinger Cc: mark@grondar.za, current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Tue, 18 Jul 2000 18:01:00 +0200." <200007181601.SAA02045@Magelan.Leidinger.net> Date: Tue, 18 Jul 2000 18:05:43 +0200 Message-ID: <10396.963936343@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007181601.SAA02045@Magelan.Leidinger.net>, Alexander Leidinger w rites: >On 18 Jul, Mark Murray wrote: > >[using NTP to gather entropy] >> You forget; a snooper watching your (ether)net has access to nearly >> all of this information. > >I've only seen messages about getting ntp information over a network (so >far), and I'm not familiar with crypto/entropy gathering/ntp, so forgive >me if I ask a stupid question, but does everyone also think about those >systems which have a more or less precise clock attached (e.g. GPS or >atomic clocks which sync the system clock via nptd)? The reason why ntp is interesting is that we compare the received data with our unpredictable local clock. It is the result of this comparison which is good entropy bits. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 9:34: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from flow.isolve.dk (flow.isolve.dk [195.249.214.175]) by hub.freebsd.org (Postfix) with ESMTP id 3235437B50C for ; Tue, 18 Jul 2000 09:34:03 -0700 (PDT) (envelope-from voland@flow.isolve.dk) Received: (from voland@localhost) by flow.isolve.dk (8.9.3/8.9.3) id SAA00348 for current@FreeBSD.ORG; Tue, 18 Jul 2000 18:33:30 +0200 (CEST) (envelope-from voland) Date: Tue, 18 Jul 2000 18:33:30 +0200 From: Vadim Belman To: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak Message-ID: <20000718183329.A333@flow.isolve.dk> Mail-Followup-To: current@FreeBSD.ORG References: <2798.963843290@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <2798.963843290@critter.freebsd.dk>; from phk@critter.freebsd.dk on Mon, Jul 17, 2000 at 04:14:50PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 04:14:50PM +0200, Poul-Henning Kamp wrote: > >> NTP is the perfect way to gather entropy at bootup! > > > > Only if in reach of an NTP server ? > > Obviously :-) And what if no network at all? -- /Voland Vadim Belman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 9:43:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id C6CCF37B50C for ; Tue, 18 Jul 2000 09:43:44 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id SAA10661; Tue, 18 Jul 2000 18:43:40 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Vadim Belman Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Tue, 18 Jul 2000 18:33:30 +0200." <20000718183329.A333@flow.isolve.dk> Date: Tue, 18 Jul 2000 18:43:40 +0200 Message-ID: <10659.963938620@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000718183329.A333@flow.isolve.dk>, Vadim Belman writes: >On Mon, Jul 17, 2000 at 04:14:50PM +0200, Poul-Henning Kamp wrote: > >> >> NTP is the perfect way to gather entropy at bootup! >> > >> > Only if in reach of an NTP server ? >> >> Obviously :-) > > And what if no network at all? Your need for random bits are quite a bit less urgent in that case. Remember: This is not about getting industry strength unbeatable crypto. If you want that, you buy a hardware solution. This is about making a FreeBSD machine as good as we can in the standard case. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 9:59:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from flow.isolve.dk (flow.isolve.dk [195.249.214.175]) by hub.freebsd.org (Postfix) with ESMTP id 7FE8D37B677 for ; Tue, 18 Jul 2000 09:59:09 -0700 (PDT) (envelope-from voland@flow.isolve.dk) Received: (from voland@localhost) by flow.isolve.dk (8.9.3/8.9.3) id SAA03645 for current@FreeBSD.ORG; Tue, 18 Jul 2000 18:58:41 +0200 (CEST) (envelope-from voland) Date: Tue, 18 Jul 2000 18:58:41 +0200 From: Vadim Belman To: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak Message-ID: <20000718185841.B333@flow.isolve.dk> Mail-Followup-To: current@FreeBSD.ORG References: <20000718183329.A333@flow.isolve.dk> <10659.963938620@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <10659.963938620@critter.freebsd.dk>; from phk@critter.freebsd.dk on Tue, Jul 18, 2000 at 06:43:40PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 06:43:40PM +0200, Poul-Henning Kamp wrote: > > And what if no network at all? > > Your need for random bits are quite a bit less urgent in that case. > > Remember: This is not about getting industry strength unbeatable > crypto. If you want that, you buy a hardware solution. > > This is about making a FreeBSD machine as good as we can in the > standard case. I mostly agree, but let's put it other way. A rare situation with a local network with no external connection, no NTP servers. Just a server(s) plus several clients. At least some of the clients are being treated as untrusted (consider public terminals) and server has some critical information on it. -- /Voland Vadim Belman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 10: 3:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id C60A237B6AC for ; Tue, 18 Jul 2000 10:03:40 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id TAA10793; Tue, 18 Jul 2000 19:03:37 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Vadim Belman Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Tue, 18 Jul 2000 18:58:41 +0200." <20000718185841.B333@flow.isolve.dk> Date: Tue, 18 Jul 2000 19:03:37 +0200 Message-ID: <10791.963939817@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000718185841.B333@flow.isolve.dk>, Vadim Belman writes: >> This is about making a FreeBSD machine as good as we can in the >> standard case. > > I mostly agree, but let's put it other way. A rare situation with a >local network with no external connection, no NTP servers. Just a server(s) >plus several clients. At least some of the clients are being treated as >untrusted (consider public terminals) and server has some critical >information on it. Nobody talked about relying on *only* NTP for entropy, quite the contrary in fact. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 10:11:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from flow.isolve.dk (flow.isolve.dk [195.249.214.175]) by hub.freebsd.org (Postfix) with ESMTP id C7DBC37B6AC for ; Tue, 18 Jul 2000 10:11:40 -0700 (PDT) (envelope-from voland@flow.isolve.dk) Received: (from voland@localhost) by flow.isolve.dk (8.9.3/8.9.3) id TAA03679 for current@FreeBSD.ORG; Tue, 18 Jul 2000 19:11:12 +0200 (CEST) (envelope-from voland) Date: Tue, 18 Jul 2000 19:11:12 +0200 From: Vadim Belman To: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak Message-ID: <20000718191112.C333@flow.isolve.dk> Mail-Followup-To: current@FreeBSD.ORG References: <20000718185841.B333@flow.isolve.dk> <10791.963939817@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <10791.963939817@critter.freebsd.dk>; from phk@critter.freebsd.dk on Tue, Jul 18, 2000 at 07:03:37PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 07:03:37PM +0200, Poul-Henning Kamp wrote: > > I mostly agree, but let's put it other way. A rare situation with a > >local network with no external connection, no NTP servers. Just a server(s) > >plus several clients. At least some of the clients are being treated as > >untrusted (consider public terminals) and server has some critical > >information on it. > > Nobody talked about relying on *only* NTP for entropy, quite the > contrary in fact. This I understand. 8) Ok, I've gotten the answer from the thread, somehow missed it before. -- /Voland Vadim Belman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 10:16:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 4C93937B6AC for ; Tue, 18 Jul 2000 10:16:51 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from bagabeedaboo.security.at12.de (dial-195-14-235-75.netcologne.de [195.14.235.75]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id TAA02602; Tue, 18 Jul 2000 19:16:48 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.2/8.10.2) with ESMTP id e6IHGg806023; Tue, 18 Jul 2000 19:16:42 +0200 (CEST) Date: Tue, 18 Jul 2000 19:16:42 +0200 (CEST) From: Paul Herman To: Poul-Henning Kamp Cc: Vadim Belman , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <10791.963939817@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jul 2000, Poul-Henning Kamp wrote: > In message <20000718185841.B333@flow.isolve.dk>, Vadim Belman writes: > > > I mostly agree, but let's put it other way. A rare situation with a > >local network with no external connection, no NTP servers. Just a server(s) > >plus several clients. At least some of the clients are being treated as > >untrusted (consider public terminals) and server has some critical > >information on it. > > Nobody talked about relying on *only* NTP for entropy, quite the > contrary in fact. Just to quickly jump in (and out) here, I recall a thread that went on for weeks in sci.crypt at the beginning of this year about the same thing. Before you all reinvent the wheel (and make this thread any longer), I would suggest sauntering on over to dejanews. For those who were patient enough to get past the usual banter, it was quite enlightening, indeed. They certainly have more of a clue about these things than I would ever hope to have. (Yes, they also talked about using NTP servers for gathering entropy.) -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 17:40:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id 7C5A637B64B for ; Tue, 18 Jul 2000 17:40:26 -0700 (PDT) (envelope-from ggm@dstc.edu.au) Received: from dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155]) by piglet.dstc.edu.au (8.10.1/8.10.1) with ESMTP id e6J0WBo23714; Wed, 19 Jul 2000 10:32:11 +1000 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Paul Herman Cc: Poul-Henning Kamp , Vadim Belman , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: Message from Paul Herman of "Tue, 18 Jul 2000 19:16:42 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Jul 2000 10:32:17 +1000 Message-ID: <16536.963966737@dstc.edu.au> From: George Michaelson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Where for instance do these ideas fit into the models proposed in draft-eastlake-randomness2-00.txt or the proceeding RFC? -George -- George Michaelson | DSTC Pty Ltd Email: ggm@dstc.edu.au | University of Qld 4072 Phone: +61 7 3365 4310 | Australia Fax: +61 7 3365 4311 | http://www.dstc.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 17:40:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id 9840F37B64B for ; Tue, 18 Jul 2000 17:40:38 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 25898 invoked from network); 19 Jul 2000 00:40:37 -0000 Received: from acs-24-154-24-131.zoominternet.net (24.154.24.131) by scully.zoominternet.net with SMTP; 19 Jul 2000 00:40:37 -0000 Date: Tue, 18 Jul 2000 20:40:37 -0400 (EDT) From: Donn Miller X-Sender: dmmiller@acs-24-154-24-131.zoominternet.net To: current@freebsd.org Subject: Lockups with recent PCM commits? Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-288401434-963967237=:5124" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-288401434-963967237=:5124 Content-Type: TEXT/PLAIN; charset=US-ASCII Try this (with a very recent kernel): cat /dev/audio It locks up my machine. Also, anything that accesses /dev/audio locks up my machine, such as mpg123. - Donn --0-288401434-963967237=:5124 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dmesg.out" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="dmesg.out" Q29weXJpZ2h0IChjKSAxOTkyLTIwMDAgVGhlIEZyZWVCU0QgUHJvamVjdC4N CkNvcHlyaWdodCAoYykgMTk3OSwgMTk4MCwgMTk4MywgMTk4NiwgMTk4OCwg MTk4OSwgMTk5MSwgMTk5MiwgMTk5MywgMTk5NA0KCVRoZSBSZWdlbnRzIG9m IHRoZSBVbml2ZXJzaXR5IG9mIENhbGlmb3JuaWEuIEFsbCByaWdodHMgcmVz ZXJ2ZWQuDQpGcmVlQlNEIDUuMC1DVVJSRU5UICMwOiBUdWUgSnVsIDE4IDE4 OjQ1OjM2IEVEVCAyMDAwDQogICAgZG1taWxsZXJAYWNzLTI0LTE1NC0yNC0x MzEuem9vbWludGVybmV0Lm5ldDovdXNyL3NyYy9zeXMvY29tcGlsZS9DVVNU T00NClRpbWVjb3VudGVyICJpODI1NCIgIGZyZXF1ZW5jeSAxMTkzMTgyIEh6 DQpDUFU6IFBlbnRpdW0vUDU1QyAoMTY2LjQ1LU1IeiA1ODYtY2xhc3MgQ1BV KQ0KICBPcmlnaW4gPSAiR2VudWluZUludGVsIiAgSWQgPSAweDU0MyAgU3Rl cHBpbmcgPSAzDQogIEZlYXR1cmVzPTB4ODAwMWJmPEZQVSxWTUUsREUsUFNF LFRTQyxNU1IsTUNFLENYOCxNTVg+DQpyZWFsIG1lbW9yeSAgPSA2MjkxNDU2 MCAoNjE0NDBLIGJ5dGVzKQ0KYXZhaWwgbWVtb3J5ID0gNTc0ODczNjAgKDU2 MTQwSyBieXRlcykNClByZWxvYWRlZCBlbGYga2VybmVsICJrZXJuZWwiIGF0 IDB4YzAzYmQwMDAuDQpQcmVsb2FkZWQgdXNlcmNvbmZpZ19zY3JpcHQgIi9i b290L2tlcm5lbC5jb25mIiBhdCAweGMwM2JkMDljLg0KSW50ZWwgUGVudGl1 bSBkZXRlY3RlZCwgaW5zdGFsbGluZyB3b3JrYXJvdW5kIGZvciBGMDBGIGJ1 Zw0Kc2VxMC02MzogTWlkaSBzZXF1ZW5jZXJzLg0KbWQwOiBNYWxsb2MgZGlz aw0KbnB4MDogPG1hdGggcHJvY2Vzc29yPiBvbiBtb3RoZXJib2FyZA0KbnB4 MDogSU5UIDE2IGludGVyZmFjZQ0KcGNpYjA6IDxIb3N0IHRvIFBDSSBicmlk Z2U+IG9uIG1vdGhlcmJvYXJkDQpwY2kwOiA8UENJIGJ1cz4gb24gcGNpYjAN CnBjaTA6IDxIb3N0IHRvIFBDSSBicmlkZ2UgKHZlbmRvcj0xMDM5IGRldmlj ZT01NTk3KT4gYXQgMC4wDQppc2FiMDogPFNpUyA4NWM1MDMgUENJLUlTQSBi cmlkZ2U+IGF0IGRldmljZSAxLjAgb24gcGNpMA0KaXNhMDogPElTQSBidXM+ IG9uIGlzYWIwDQphdGFwY2kwOiA8U2lTIDU1OTEgQVRBMzMgY29udHJvbGxl cj4gcG9ydCAweGQwMDAtMHhkMDBmLDB4ZDQwMC0weGQ0MDMsMHhkODAwLTB4 ZDgwNywweGUwMDAtMHhlMDAzLDB4ZTQwMC0weGU0MDcgaXJxIDExIGF0IGRl dmljZSAxLjEgb24gcGNpMA0KYXRhMDogYXQgMHgxZjAgaXJxIDE0IG9uIGF0 YXBjaTANCmF0YTE6IGF0IDB4MTcwIGlycSAxNSBvbiBhdGFwY2kwDQplZDA6 IDxORTIwMDAgUENJIEV0aGVybmV0IChSZWFsVGVrIDgwMjkpPiBwb3J0IDB4 YjgwMC0weGI4MWYgaXJxIDEwIGF0IGRldmljZSAxMC4wIG9uIHBjaTANCmVk MDogYWRkcmVzcyAwMDpjMDpkZjplZDowYjoxNywgdHlwZSBORTIwMDAgKDE2 IGJpdCkgDQpwY2kwOiA8U2lTIDU1OTcvOTggU1ZHQSBjb250cm9sbGVyPiBh dCAxOS4wIGlycSAxMQ0KdmdhMDogPEdlbmVyaWMgSVNBIFZHQT4gYXQgcG9y dCAweDNjMC0weDNkZiBpb21lbSAweGEwMDAwLTB4YmZmZmYgb24gaXNhMA0K c2MwOiA8U3lzdGVtIGNvbnNvbGU+IG9uIGlzYTANCnNjMDogVkdBIDwxNiB2 aXJ0dWFsIGNvbnNvbGVzLCBmbGFncz0weDIwMD4NCmZkYzA6IDxORUMgNzIw NjVCIG9yIGNsb25lPiBhdCBwb3J0IDB4M2YwLTB4M2Y1LDB4M2Y3IGlycSA2 IGRycSAyIG9uIGlzYTANCmZkYzA6IEZJRk8gZW5hYmxlZCwgOCBieXRlcyB0 aHJlc2hvbGQNCmZkMDogPDE0NDAtS0IgMy41IiBkcml2ZT4gb24gZmRjMCBk cml2ZSAwDQphdGtiZGMwOiA8S2V5Ym9hcmQgY29udHJvbGxlciAoaTgwNDIp PiBhdCBwb3J0IDB4NjAsMHg2NCBvbiBpc2EwDQphdGtiZDA6IDxBVCBLZXli b2FyZD4gZmxhZ3MgMHgxIGlycSAxIG9uIGF0a2JkYzANCmtiZDAgYXQgYXRr YmQwDQpzaW8yIGF0IHBvcnQgMHgzZTgtMHgzZWYgaXJxIDQgb24gaXNhMA0K c2lvMjogdHlwZSAxNjU1MEENCm1zZTA6IDxCdXMvSW5Qb3J0IE1vdXNlPiBh dCBwb3J0IDB4MjNjLTB4MjNmIGlycSAzIG9uIGlzYTANCm1wdTA6IHJlc2V0 IGZhaWxlZC4NCnBwYzA6IDxFQ1AgcGFyYWxsZWwgcHJpbnRlciBwb3J0PiBh dCBwb3J0IDB4Mzc4LTB4MzdmLDB4Nzc4LTB4NzdmIGlycSA3IGRycSAzIG9u IGlzYTANCnBwYzA6IFNNQy1saWtlIGNoaXBzZXQgKEVDUC9FUFAvUFMyL05J QkJMRSkgaW4gQ09NUEFUSUJMRSBtb2RlDQpwcGMwOiBGSUZPIHdpdGggMTYv MTYvMTYgYnl0ZXMgdGhyZXNob2xkDQpwcGkwOiA8UGFyYWxsZWwgSS9PPiBv biBwcGJ1czANCmxwdDA6IDxQcmludGVyPiBvbiBwcGJ1czANCmxwdDA6IElu dGVycnVwdC1kcml2ZW4gcG9ydA0KcGxpcDA6IDxQTElQIG5ldHdvcmsgaW50 ZXJmYWNlPiBvbiBwcGJ1czANCnVua25vd246IDxQTlAwNTAxPiBjYW4ndCBh c3NpZ24gcmVzb3VyY2VzDQp1bmtub3duOiA8UE5QMDUwMT4gY2FuJ3QgYXNz aWduIHJlc291cmNlcw0KdW5rbm93bjogPFBOUDA3MDA+IGNhbid0IGFzc2ln biByZXNvdXJjZXMNCnVua25vd246IDxQTlAwMzAzPiBjYW4ndCBhc3NpZ24g cmVzb3VyY2VzDQpzYmMxOiA8RVNTIEVTMTg2OD4gYXQgcG9ydCAweDIyMC0w eDIyZiwweDM4OC0weDM4YiwweDMzMC0weDMzMSBpcnEgNSBkcnEgMSwwIG9u IGlzYTANCnBjbTA6IDxFU1MgMTh4eCBEU1A+IG9uIHNiYzENCm1pZGkxOiA8 U0IgTWlkaSBJbnRlcmZhY2U+IG9uIHNiYzENCm1pZGkyOiA8U0IgT1BMIEZN IFN5bnRoZXNpemVyPiBvbiBzYmMxDQphZDA6IDMwOTNNQiA8RlVKSVRTVSBN UEIzMDMyQVRVPiBbNjcwNC8xNS82M10gYXQgYXRhMC1tYXN0ZXIgdXNpbmcg VURNQTMzDQphZDE6IDEwNDBNQiA8TTE2MTRUQT4gWzIxMTQvMTYvNjNdIGF0 IGF0YTAtc2xhdmUgdXNpbmcgV0RNQTINCmFjZDA6IENEUk9NIDxCQ0QtMjRY IDE5OTctMDYtMjc+IGF0IGF0YTEtbWFzdGVyIHVzaW5nIFdETUEyDQo= --0-288401434-963967237=:5124-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 21:10:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id EF3F337BCEC for ; Tue, 18 Jul 2000 21:10:16 -0700 (PDT) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id LAA67682; Wed, 19 Jul 2000 11:10:14 +0700 (NOVST) (envelope-from nnd) Date: Wed, 19 Jul 2000 11:10:14 +0700 (NOVST) Message-Id: <200007190410.LAA67682@wint.itfs.nsk.su> From: Nickolay Dudorov To: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/net ethernet.h X-Newsgroups: itfs.freebsd.cvs.all In-Reply-To: <200007182244.PAA33918@freefall.freebsd.org> User-Agent: tin/1.4.3-20000502 ("Marian") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <200007182244.PAA33918@freefall.freebsd.org> Archie Cobbs wrote: > archie 2000/07/18 15:44:52 PDT > > Modified files: > sys/net ethernet.h > Log: > Const'ify parameters to ethers(3) routines as appropriate. > > Revision Changes Path > 1.16 +6 -6 src/sys/net/ethernet.h This breaks 'buildworld' in the 'lib/libpcap'. The next patch seems to correct the error. N.Dudorov Index: contrib/libpcap/nametoaddr.c =================================================================== RCS file: /store/CVS/src/contrib/libpcap/nametoaddr.c,v retrieving revision 1.6 diff -b -u -r1.6 nametoaddr.c --- contrib/libpcap/nametoaddr.c 2000/01/30 00:43:34 1.6 +++ contrib/libpcap/nametoaddr.c 2000/07/19 04:02:27 @@ -366,7 +366,7 @@ } #else -#if !defined(sgi) && !defined(__NetBSD__) +#if !defined(sgi) && !defined(__NetBSD__) && !defined(__FreeBSD__) extern int ether_hostton(char *, struct ether_addr *); #endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 21:39: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from rtp.tfd.com (rtp.tfd.com [198.79.53.206]) by hub.freebsd.org (Postfix) with ESMTP id 5B0EB37BC88 for ; Tue, 18 Jul 2000 21:38:55 -0700 (PDT) (envelope-from kent@tfd.com) Received: from chapel-hill.tfd.com (chapel-hill.tfd.com [10.20.0.40]) by rtp.tfd.com (8.9.3/8.9.3) with ESMTP id AAA14099 for ; Wed, 19 Jul 2000 00:36:40 -0400 (EDT) Received: (from kent@localhost) by chapel-hill.tfd.com (8.9.3/8.9.3) id WAA00217 for current@freebsd.org; Tue, 18 Jul 2000 22:05:52 -0400 (EDT) (envelope-from kent) Date: Tue, 18 Jul 2000 22:05:52 -0400 (EDT) From: Kent Hauser Message-Id: <200007190205.WAA00217@chapel-hill.tfd.com> To: current@freebsd.org Subject: SBLive (value) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, I've again been trying to get my sound support working. The problem I have is the machine panic's (RAM parity error) whenever I (for instance) play an mp3. I have a SBLive Value card. The card works fine under W98. The EMU10K1 is recognized during the probe, but the "sbc" is not. I have pci/pcm/sbc enabled in the kernel. "cat /dev/sndstat" shows the emu10k1 ready and willing. Any thoughts? Thanks. Kent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 21:43:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id 0855C37BC88 for ; Tue, 18 Jul 2000 21:43:17 -0700 (PDT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id VAA57290; Tue, 18 Jul 2000 21:43:16 -0700 (PDT) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id VAA72036; Tue, 18 Jul 2000 21:43:15 -0700 (PDT) (envelope-from frank) From: Frank Mayhar Message-Id: <200007190443.VAA72036@realtime.exit.com> Subject: Re: SBLive (value) In-Reply-To: <200007190205.WAA00217@chapel-hill.tfd.com> from Kent Hauser at "Jul 18, 2000 10:05:52 pm" To: Kent Hauser Date: Tue, 18 Jul 2000 21:43:15 -0700 (PDT) Cc: current@FreeBSD.ORG Reply-To: frank@exit.com Organization: Exit Consulting X-Copyright0: Copyright 2000 Frank Mayhar. All Rights Reserved. X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only. X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kent Hauser wrote: > I've again been trying to get my sound support working. > The problem I have is the machine panic's (RAM parity error) > whenever I (for instance) play an mp3. This is a known problem with the SBLive and machines with ECC memory. So far no sign of a fix for it. Jordan, if you read this, please email me the address to send the memory stick. I'll contribute it to the cause. (I'll need a receipt, though. ;-) -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://store.exit.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 22: 5:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id B22CD37BD07 for ; Tue, 18 Jul 2000 22:05:29 -0700 (PDT) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id MAA01962; Wed, 19 Jul 2000 12:05:27 +0700 (NOVST) (envelope-from nnd) Date: Wed, 19 Jul 2000 12:05:27 +0700 (NOVST) Message-Id: <200007190505.MAA01962@wint.itfs.nsk.su> From: Nickolay Dudorov To: current@freebsd.org Subject: Re: cvs commit: src/sys/net ethernet.h X-Newsgroups: itfs.freebsd.current In-Reply-To: <200007190410.LAA67682@wint.itfs.nsk.su> User-Agent: tin/1.4.3-20000502 ("Marian") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is one more 'buildworld' problem - in 'src/usr.sbin/ipsend'. The (analogous) patch correct it: Index: contrib/ipfilter/iplang/iplang_y.y =================================================================== RCS file: /store/CVS/src/contrib/ipfilter/iplang/iplang_y.y,v retrieving revision 1.1.1.6 diff -b -u -r1.1.1.6 iplang_y.y --- contrib/ipfilter/iplang/iplang_y.y 2000/05/24 02:14:18 1.1.1.6 +++ contrib/ipfilter/iplang/iplang_y.y 2000/07/19 04:59:38 @@ -48,7 +48,7 @@ #include "ipf.h" #include "iplang.h" -#ifndef __NetBSD__ +#if !defined(__NetBSD__) && ! defined(__FreeBSD__) extern struct ether_addr *ether_aton __P((char *)); #endif > In <200007182244.PAA33918@freefall.freebsd.org> Archie Cobbs wrote: >> archie 2000/07/18 15:44:52 PDT >> >> Modified files: >> sys/net ethernet.h >> Log: >> Const'ify parameters to ethers(3) routines as appropriate. >> >> Revision Changes Path >> 1.16 +6 -6 src/sys/net/ethernet.h > > This breaks 'buildworld' in the 'lib/libpcap'. > > The next patch seems to correct the error. > > N.Dudorov > > Index: contrib/libpcap/nametoaddr.c > =================================================================== > RCS file: /store/CVS/src/contrib/libpcap/nametoaddr.c,v > retrieving revision 1.6 > diff -b -u -r1.6 nametoaddr.c > --- contrib/libpcap/nametoaddr.c 2000/01/30 00:43:34 1.6 > +++ contrib/libpcap/nametoaddr.c 2000/07/19 04:02:27 > @@ -366,7 +366,7 @@ > } > #else > > -#if !defined(sgi) && !defined(__NetBSD__) > +#if !defined(sgi) && !defined(__NetBSD__) && !defined(__FreeBSD__) > extern int ether_hostton(char *, struct ether_addr *); > #endif > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 18 22:46:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 5131C37BD4A for ; Tue, 18 Jul 2000 22:46:38 -0700 (PDT) (envelope-from leif@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id HAA80921; Wed, 19 Jul 2000 07:46:33 +0200 (CEST) (envelope-from leif@neland.dk) Received: from localhost (leif@localhost) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id HAA62299; Wed, 19 Jul 2000 07:46:20 +0200 (CEST) (envelope-from leif@neland.dk) Date: Wed, 19 Jul 2000 07:46:20 +0200 (CEST) From: Leif Neland To: "Daniel Berlin+list.freebsd-current" Cc: freebsd-current@FreeBSD.ORG Subject: Re: cer/b7b/pfc -> pem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17 Jul 2000, Daniel Berlin+list.freebsd-current wrote: > "Leif Neland" writes: > > > I have a Verisign personal certificate (Look me up at Verisign, as Leif > > Neland) > > > > This works nicely in Windows (Outlook Express), but I'd like to try using > > the same key with openssl to generate crypted (to myself) or signed > > messages. > > > > I can export the key as a .cer, .p7b or .pfx, but openssl seems to want it > > in .pem format. > > > > What does the p7b file look like? > > And the .cer file, and the .pfx file? > > Are any of them ascii, with a "BEGIN PKCS7" or "BEGIN CERTIFICATE" > line? > With crl2pcks7 I can convert the p7b and cer to a pem, which contain BEGIN PKCS7 , random characters, and END PKCS7 I can't use this to encrypt with, smime wants "BEGIN CERTIFICATE" Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 0:45:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 8B4E537BDBF for ; Wed, 19 Jul 2000 00:45:07 -0700 (PDT) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id OAA00261; Wed, 19 Jul 2000 14:45:02 +0700 (NOVST) (envelope-from nnd) Date: Wed, 19 Jul 2000 14:45:02 +0700 (NOVST) Message-Id: <200007190745.OAA00261@wint.itfs.nsk.su> From: Nickolay Dudorov To: current@freebsd.org Subject: Re: cvs commit: src/sys/net ethernet.h X-Newsgroups: itfs.freebsd.current In-Reply-To: <200007190505.MAA01962@wint.itfs.nsk.su> User-Agent: tin/1.4.3-20000502 ("Marian") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And (the last) one more patch to make 'buildworld' successfull: Index: usr.sbin/wlconfig/wlconfig.c =================================================================== RCS file: /store/CVS/src/usr.sbin/wlconfig/wlconfig.c,v retrieving revision 1.8 diff -b -u -r1.8 wlconfig.c --- usr.sbin/wlconfig/wlconfig.c 1999/08/28 01:20:39 1.8 +++ usr.sbin/wlconfig/wlconfig.c 2000/07/19 06:06:24 @@ -69,7 +69,6 @@ #include #include #include -extern struct ether_addr *ether_aton(char *a); #include #include In <200007190505.MAA01962@wint.itfs.nsk.su> Nickolay Dudorov wrote: > There is one more 'buildworld' problem - in > 'src/usr.sbin/ipsend'. The (analogous) patch correct it: > > Index: contrib/ipfilter/iplang/iplang_y.y > =================================================================== > RCS file: /store/CVS/src/contrib/ipfilter/iplang/iplang_y.y,v > retrieving revision 1.1.1.6 > diff -b -u -r1.1.1.6 iplang_y.y > --- contrib/ipfilter/iplang/iplang_y.y 2000/05/24 02:14:18 1.1.1.6 > +++ contrib/ipfilter/iplang/iplang_y.y 2000/07/19 04:59:38 > @@ -48,7 +48,7 @@ > #include "ipf.h" > #include "iplang.h" > > -#ifndef __NetBSD__ > +#if !defined(__NetBSD__) && ! defined(__FreeBSD__) > extern struct ether_addr *ether_aton __P((char *)); > #endif > >> In <200007182244.PAA33918@freefall.freebsd.org> Archie Cobbs wrote: >>> archie 2000/07/18 15:44:52 PDT >>> >>> Modified files: >>> sys/net ethernet.h >>> Log: >>> Const'ify parameters to ethers(3) routines as appropriate. >>> >>> Revision Changes Path >>> 1.16 +6 -6 src/sys/net/ethernet.h >> >> This breaks 'buildworld' in the 'lib/libpcap'. >> >> The next patch seems to correct the error. >> >> N.Dudorov >> >> Index: contrib/libpcap/nametoaddr.c >> =================================================================== >> RCS file: /store/CVS/src/contrib/libpcap/nametoaddr.c,v >> retrieving revision 1.6 >> diff -b -u -r1.6 nametoaddr.c >> --- contrib/libpcap/nametoaddr.c 2000/01/30 00:43:34 1.6 >> +++ contrib/libpcap/nametoaddr.c 2000/07/19 04:02:27 >> @@ -366,7 +366,7 @@ >> } >> #else >> >> -#if !defined(sgi) && !defined(__NetBSD__) >> +#if !defined(sgi) && !defined(__NetBSD__) && !defined(__FreeBSD__) >> extern int ether_hostton(char *, struct ether_addr *); >> #endif >> >> >> > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 5:43:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id 53D1F37B56A for ; Wed, 19 Jul 2000 05:43:34 -0700 (PDT) (envelope-from sam@inf.enst.fr) Received: from antinea.enst.fr (antinea.enst.fr [137.194.160.145]) by ada.eu.org (Postfix) with ESMTP id 5B81D19076; Wed, 19 Jul 2000 14:43:32 +0200 (CEST) Received: by antinea.enst.fr (Postfix, from userid 1000) id 78B65236; Wed, 19 Jul 2000 14:43:31 +0200 (CEST) To: current@freebsd.org Subject: world broken in libpcap Mime-Version: 1.0 (generated by tm-edit 1.5) Content-Type: text/plain; charset=US-ASCII Date: 19 Jul 2000 14:43:30 +0200 Lines: 10 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Capitol Reef" From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-07-19-14-43-31+trackit+sam@inf.enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cvsup'ed 1 hour ago cc -O -pipe -I. -Dyylval=pcap_lval -DHAVE_SYS_IOCCOM_H=1 -DHAVE_SYS_SOCKIO_H=1 -DHAVE_ETHER_HOSTTON=1 -DHAVE_STRERROR=1 -DHAVE_SOCKADDR_SA_LEN=1 -DLBL_ALIGN=1 -DINET6 -I/usr/src/lib/libpcap/../../contrib/libpcap -I/usr/src/lib/libpcap/../../contrib/libpcap/lbl -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libpcap/../../contrib/libpcap/nametoaddr.c -o nametoaddr.o /usr/src/lib/libpcap/../../contrib/libpcap/nametoaddr.c:370: conflicting types for `ether_hostton' /usr/obj/usr/src/i386/usr/include/net/ethernet.h:111: previous declaration of `ether_hostton' *** Error code 1 Stop in /usr/src/lib/libpcap. -- Samuel Tardieu -- sam@inf.enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 6: 7:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id 9C95F37BF51 for ; Wed, 19 Jul 2000 06:07:28 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.9.3/8.9.3) id JAA98111 for current@freebsd.org; Wed, 19 Jul 2000 09:08:41 -0400 (EDT) (envelope-from dufault) From: Peter Dufault Message-Id: <200007191308.JAA98111@hda.hda.com> Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <10396.963936343@critter.freebsd.dk> from Poul-Henning Kamp at "Jul 18, 2000 06:05:43 pm" To: current@freebsd.org Date: Wed, 19 Jul 2000 09:08:36 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The reason why ntp is interesting is that we compare the received data > with our unpredictable local clock. It is the result of this comparison > which is good entropy bits. Is the resolution of thermal sensors on many new motherboards and CPU high enough to get thermal randomness? Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 6: 7:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69]) by hub.freebsd.org (Postfix) with ESMTP id DD24137BDDC for ; Wed, 19 Jul 2000 06:07:25 -0700 (PDT) (envelope-from myevmenkin@att.com) Received: from njb140r1.ems.att.com ([135.65.202.58]) by kcmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id JAA14791; Wed, 19 Jul 2000 09:07:23 -0400 (EDT) Received: from njb140bh1.ems.att.com by njb140r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id JAA15374; Wed, 19 Jul 2000 09:06:14 -0400 (EDT) Received: by njb140bh1.ems.att.com with Internet Mail Service (5.5.2650.21) id <3352XVV9>; Wed, 19 Jul 2000 09:07:23 -0400 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'Archie Cobbs'" , Julian Elischer Cc: "'freebsd-current@freebsd.org'" Subject: RE: possible NETGRAPH/NG_ETHER bug Date: Wed, 19 Jul 2000 09:07:19 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [...] > From: Archie Cobbs [mailto:archie@whistle.com] > Julian Elischer writes: > > > i was working on integration of Ethernet TAP driver and NETGRAPH > > > and found strange thing. the problem is that NG_ETHER nodes do not > > > detach correctly when interface is gone. i was taking a very quick > > > look at it, and, it seems to me that we are missing one reference > > > to a node. i think it is ng_name_node/ng_unname pair. > > > > This is quite possible because until recently interfaces could never > > be removed. Therefore the act of removing a node was really > > just a case of RESETTING the node. It was not removed. > > Here's some more info that may be helpful. [...] the problem still exists :( i tried to collect some information that, i think, could be helpful. first, my system fly# uname -a FreeBSD fly.private.org 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Tue Jul 18 20:21:57 EST 2000 root@fly.private.org:/usr/src/sys/compile/FLY i386 now modules and interfaces fly# kldstat Id Refs Address Size Name 1 3 0xc0100000 1cd99c kernel 2 1 0xc0974000 4000 logo_saver.ko fly# ifconfig -a lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 now i will load if_tap module and create virtual interface fly# kldload -v ./if_tap.ko Loaded ./if_tap.ko, id=3 fly# cat /dev/tap0 ^C fly# ifconfig -a lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 tap0: flags=8802 mtu 1500 ether 00:bd:dd:25:00:00 now i will load ng_ether and check NETGRAPH nodes fly# kldload -v ng_ether Loaded ng_ether, id=4 fly# ngctl list There are 2 total nodes: Name: ngctl183 Type: socket ID: 00000002 Num hooks: 0 Name: tap0 Type: ether ID: 00000001 Num hooks: 0 fly# ngctl types There are 2 total types: Type name Number of living nodes --------- ---------------------- socket 1 ether 1 so far so good :) now i will unload if_tap module fly# kldunload if_tap fly# ifconfig -a lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 fly# cat /dev/tap0 cat: /dev/tap0: Device not configured ok, both device and interface are gone, what about NETGRAPH nodes fly# ngctl list There are 1 total nodes: Name: ngctl210 Type: socket ID: 00000004 Num hooks: 0 fly# ngctl types There are 2 total types: Type name Number of living nodes --------- ---------------------- socket 1 ether 1 fly# kldunload ng_ether kldunload: can't unload file: Device busy ooops :( there is still 1 ``ether'' node :( i did put some debug printf in ng_base and ng_ether. here is an output ng_ether_detach: start node->refs = 2 --- ng_ether_detach() ng_unref: node->refs = 3 --- ng_unfer(). ng_rmnode() it will add one extra reference ng_ether_detach: before final ng_unref() node->refs = 2 --- ng_ether_detach() just before last ng_unref() ng_unref: node->refs = 2 --- ng_unref() so i think that shows that last ng_unref() was called with node->refs equal to 2, and, i think, that is not correct :( again, here is one of the millions of possible patches that works for me :) *** ng_ether.c.old Tue Jul 18 21:17:54 2000 --- ng_ether.c Tue Jul 18 21:48:46 2000 *************** *** 293,298 **** --- 293,299 ---- bzero(priv, sizeof(*priv)); FREE(priv, M_NETGRAPH); node->private = NULL; + ng_unname(node); /* remove node name */ ng_unref(node); /* free node itself */ } if_tap module sources can be found at http://home.earthlink.net/~evmax/tap-fbsd5b1.tar.gz sorry for long letter :) hope that helps :) thanks, emax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 6:27:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from sohara.dyndns.org (pooh.elsevier.nl [145.36.13.27]) by hub.freebsd.org (Postfix) with ESMTP id 5D24A37BDC8 for ; Wed, 19 Jul 2000 06:27:53 -0700 (PDT) (envelope-from steve@sohara.dyndns.org) Received: (from steve@localhost) by sohara.dyndns.org (8.9.3/8.9.3) id OAA20720; Wed, 19 Jul 2000 14:34:48 +0100 (IST) (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200007191308.JAA98111@hda.hda.com> Date: Wed, 19 Jul 2000 14:34:48 +0100 (IST) From: "Steve O'Hara-Smith" To: Peter Dufault Subject: Re: randomdev entropy gathering is really weak Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Jul-00 Peter Dufault wrote: > Is the resolution of thermal sensors on many new motherboards and > CPU high enough to get thermal randomness? The voltage sensors have some noise too (maybe not enough). -- Steve O'Hara-Smith http://sohara.webhop.net/ A Better Way To Focus The Sun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 7:46:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id BCFDE37BFD2 for ; Wed, 19 Jul 2000 07:46:25 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (3543 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Wed, 19 Jul 2000 16:46:16 +0200 (CEST) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id 7FE52483D; Wed, 19 Jul 2000 16:46:14 +0200 (METDST) Subject: kernel compile failure without -O option To: freebsd-current@freebsd.org Date: Wed, 19 Jul 2000 16:46:14 +0200 (METDST) Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2831 Message-Id: <20000719144614.7FE52483D@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the process of tracing down the problem of the kernel panic when booting a kernel with pcvt enabled, i tried to compile a kernel without the -O option to gcc and got this compile failure (sources from 18.7.2000 9:00 MET): cc -c -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 -fomit-frame-pointer ../../i386/i386/atomic.c In file included from ../../i386/i386/atomic.c:47: machine/atomic.h: In function `atomic_set_char': machine/atomic.h:106: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_char': machine/atomic.h:107: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_char': machine/atomic.h:108: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_char': machine/atomic.h:109: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_set_short': machine/atomic.h:111: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_short': machine/atomic.h:112: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_short': machine/atomic.h:113: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_short': machine/atomic.h:114: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_set_int': machine/atomic.h:116: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_int': machine/atomic.h:117: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_int': machine/atomic.h:118: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_int': machine/atomic.h:119: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_set_long': machine/atomic.h:121: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_long': machine/atomic.h:122: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_long': machine/atomic.h:123: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_long': machine/atomic.h:124: inconsistent operand constraints in an `asm' *** Error code 1 hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 9: 5: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 2E45037BF28 for ; Wed, 19 Jul 2000 09:05:04 -0700 (PDT) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id SAA98873; Wed, 19 Jul 2000 18:04:56 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id SAA86168; Wed, 19 Jul 2000 18:04:25 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Wed, 19 Jul 2000 18:04:25 +0200 (CEST) From: Leif Neland To: "Steve O'Hara-Smith" Cc: Peter Dufault , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jul 2000, Steve O'Hara-Smith wrote: > > On 19-Jul-00 Peter Dufault wrote: > > Is the resolution of thermal sensors on many new motherboards and > > CPU high enough to get thermal randomness? > > The voltage sensors have some noise too (maybe not enough). > Fan speed too. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 9:17:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 478E237BFFA for ; Wed, 19 Jul 2000 09:17:54 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id JAA65795; Wed, 19 Jul 2000 09:17:19 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200007191617.JAA65795@bubba.whistle.com> Subject: Re: possible NETGRAPH/NG_ETHER bug In-Reply-To: from "Yevmenkin, Maksim N, CSCIO" at "Jul 19, 2000 09:07:19 am" To: "Yevmenkin, Maksim N, CSCIO" Date: Wed, 19 Jul 2000 09:17:19 -0700 (PDT) Cc: julian@elischer.org, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yevmenkin, Maksim N, CSCIO writes: > again, here is one of the millions of possible patches that works for me :) > > *** ng_ether.c.old Tue Jul 18 21:17:54 2000 > --- ng_ether.c Tue Jul 18 21:48:46 2000 > *************** > *** 293,298 **** > --- 293,299 ---- > bzero(priv, sizeof(*priv)); > FREE(priv, M_NETGRAPH); > node->private = NULL; > + ng_unname(node); /* remove node name */ > ng_unref(node); /* free node itself */ > } I think that is the right patch. Thanks! -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 10:34: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0D51837C13B for ; Wed, 19 Jul 2000 10:34:00 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA93028; Wed, 19 Jul 2000 11:33:56 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA82735; Wed, 19 Jul 2000 11:33:55 -0600 (MDT) Message-Id: <200007191733.LAA82735@harmony.village.org> To: Poul-Henning Kamp Subject: Re: randomdev entropy gathering is really weak Cc: Mark Murray , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 18 Jul 2000 08:56:57 +0200." <7469.963903417@critter.freebsd.dk> References: <7469.963903417@critter.freebsd.dk> Date: Wed, 19 Jul 2000 11:33:55 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <7469.963903417@critter.freebsd.dk> Poul-Henning Kamp writes: : In message <200007180652.IAA04139@grimreaper.grondar.za>, Mark Murray writes: : >> No, he doesn't have access to the offset from the machines local clock. : >> : >> I ran a quick & dirty test here on some logfiles: that offset is : >> very close to white noise. : > : >With what amplitude? : : Depends on the termal environment of your xtal obviously :-) Poul, what's the Allen Variance for the sample that you measured? That's going to be the quality of the two oscillators under measure. Here we see correleations on the order of 10e-15, but that's for really good cesium clocks :-). For PC hardware, these differences are going to be effectively random. Why? The quartz xtals in them are usually really really bad. They drift all over the place with temprature, humidity and all kinds of other factors. Even tiny changes in temperature can be measured in the resulting frequency change of the OSC. Temperature near the xtal can vary quite a bit due to the vagaries of PC hardware. The drift of your clock is going to be effectively random. Sure, you know that what range it will be in, but from moment to moment, you don't know what the silly thing will do. I'm not sure how many random bits we can harvest from these measurements, but they are a good source of at least a few bits. All the data I've looked at is for high precision clocks or at least temp controlled xtals, which have much smaller variations. Another good source would be if you had a Cesium clock and a GPS receiver. The delay due to atmospherics is another good source of random data. This varies +- 25ns and is highly locale dependent. One can measure this variance down to the nanosecond easily (giving about 5 bits of randomness) and with a lot of effort down to the pico second level, which would give you about 15 bits of randomness. When you are measuring the offset of two clocks that have been operating independently for a period of time, you'll find that the offset is effectively random. Since I think that ntp uses a one way time measurement, you will know the original time, the time on the remote, and maybe the approximate time that the packet returns. You can make low resolution estimates of the total delay and calculate an offset based on that. However, if the clocks are already close the delay almost always swamps the offset and your estimates of delay will be so far off that you'll not be able to estimate more than a few of the high order bits, if you are lucky. It certainly would be better than nothing and would be a decent source of randomness. It would be my expectation that if tests were run to measure this randomness and the crypto random tests were applied, we'd find a fairly good source. Warner Losh Timing Solutions http://www.timing.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 10:42:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 21A3937B689; Wed, 19 Jul 2000 10:42:39 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA93088; Wed, 19 Jul 2000 11:42:37 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA82840; Wed, 19 Jul 2000 11:42:35 -0600 (MDT) Message-Id: <200007191742.LAA82840@harmony.village.org> To: Alexander Leidinger Subject: Re: randomdev entropy gathering is really weak Cc: mark@grondar.za, current@FreeBSD.ORG, phk@FreeBSD.ORG In-reply-to: Your message of "Tue, 18 Jul 2000 18:01:00 +0200." <200007181601.SAA02045@Magelan.Leidinger.net> References: <200007181601.SAA02045@Magelan.Leidinger.net> Date: Wed, 19 Jul 2000 11:42:35 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007181601.SAA02045@Magelan.Leidinger.net> Alexander Leidinger writes: : systems which have a more or less precise clock attached (e.g. GPS or : atomic clocks which sync the system clock via nptd)? And what are the : numbers for this solution (for those people which are interested in : numbers to be their own judge)? I can tell you right now that the variation between GPS and a good cesium clock is on the order of +- 25ns. With nanosecond resolution, this gives you about 5 bits. The variation of the system clock when synchronized to the GPS receiver is on the order of +-10us as measured with a parallel port interrupt and a pps line from the gps receiver. The pps interrupt is measured using a fast interrupt (we hacked ppc to do fast interrupts for this), so the latency is fairly small and fairly constant. I don't have datasets that I can point people at, however. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 10:42:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from white.dogwood.com (white.dogwood.com [63.96.228.130]) by hub.freebsd.org (Postfix) with ESMTP id ABF3637B8C3 for ; Wed, 19 Jul 2000 10:42:45 -0700 (PDT) (envelope-from dave@dogwood.com) Received: (from dave@localhost) by white.dogwood.com (8.9.3/8.9.3) id KAA72740 for freebsd-current@freebsd.org; Wed, 19 Jul 2000 10:42:44 -0700 (PDT) (envelope-from dave) From: Dave Cornejo Message-Id: <200007191742.KAA72740@white.dogwood.com> Subject: fetch problem with fwtk To: freebsd-current@freebsd.org Date: Wed, 19 Jul 2000 10:42:44 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am using fwtk-2.1 on a firewall, and with the latest builds, fetch seems to have changed behaviors such that it no longer works with it. I have FTP_PROXY set to "red:9696" the difference in behavior seems that older versions of fetch would send a USER command like this: USER anonymous@ftp.freesoftware.com the latest fetch sends this: USER anonymous@ftp.freesoftware.com@21 which fwtk apparently interprets as username "anonymous@ftp.freesoftware.com" at IP address "0.0.0.21" What is incorrect here? Should FWTK understand this or is fetch wrong? dave -- Dave Cornejo @ Dogwood Media, Fremont, California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 10:46: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1819F37B8C3 for ; Wed, 19 Jul 2000 10:46:03 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA93117; Wed, 19 Jul 2000 11:46:01 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA82887; Wed, 19 Jul 2000 11:46:01 -0600 (MDT) Message-Id: <200007191746.LAA82887@harmony.village.org> To: Peter Dufault Subject: Re: randomdev entropy gathering is really weak Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 19 Jul 2000 09:08:36 EDT." <200007191308.JAA98111@hda.hda.com> References: <200007191308.JAA98111@hda.hda.com> Date: Wed, 19 Jul 2000 11:46:01 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007191308.JAA98111@hda.hda.com> Peter Dufault writes: : > The reason why ntp is interesting is that we compare the received data : > with our unpredictable local clock. It is the result of this comparison : > which is good entropy bits. : : Is the resolution of thermal sensors on many new motherboards and : CPU high enough to get thermal randomness? Yes. You'll also find that the voltage drifts as well. However, I doubt you'd be able to get more than 1 bit out of the voltage readings. The thermal readings, depending on their precision, would also yield several random bits. But this several may be only 3 or 4. The temperature varies based on work load and on the climate controls in place at the site. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 11:10:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (fw2.aub.dk [195.24.1.195]) by hub.freebsd.org (Postfix) with ESMTP id 3697D37B51B for ; Wed, 19 Jul 2000 11:10:39 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id UAA00948; Wed, 19 Jul 2000 20:09:49 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Wed, 19 Jul 2000 11:33:55 MDT." <200007191733.LAA82735@harmony.village.org> Date: Wed, 19 Jul 2000 20:09:48 +0200 Message-ID: <946.964030188@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007191733.LAA82735@harmony.village.org>, Warner Losh writes: >Another good source would be if you had a Cesium clock and a GPS >receiver. The delay due to atmospherics is another good source of >random data. This varies +- 25ns and is highly locale dependent. One >can measure this variance down to the nanosecond easily (giving about >5 bits of randomness) and with a lot of effort down to the pico second >level, which would give you about 15 bits of randomness. A geiger counter and a smoke-detector would be *so much* cheaper and give more bits per second :-) >It certainly would be better than nothing and would be a decent source >of randomness. It would be my expectation that if tests were run to >measure this randomness and the crypto random tests were applied, >we'd find a fairly good source. The trick here is to actually measure the quality of our entropy. I have asked Markm to provide us with some kernel option which can be used to get a copy of the entropy so we can study the quality off it. BTW: You have *no* idea how much I envy your access to high quality timing hardware :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 11:14:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 7E73937B51B for ; Wed, 19 Jul 2000 11:14:22 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id UAA00448; Wed, 19 Jul 2000 20:12:00 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007191812.UAA00448@grimreaper.grondar.za> To: Warner Losh Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <200007191733.LAA82735@harmony.village.org> In-Reply-To: <200007191733.LAA82735@harmony.village.org> ; from Warner Losh "Wed, 19 Jul 2000 11:33:55 CST." Date: Wed, 19 Jul 2000 20:11:59 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ A whole bunch of sane stuff removed ] > It certainly would be better than nothing and would be a decent source > of randomness. It would be my expectation that if tests were run to > measure this randomness and the crypto random tests were applied, > we'd find a fairly good source. The randomness is good, no doubt; I worry about how accessible that randomness is to an attacker? If the attacker is on your computer (he us a user, say), he might know a lot about the current frequency of your xtal. He can also get the same (remote) time offsets as you. What does that give him? Not much, but it could reduce the bits that he needs to guess. By how much? I don't know. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 11:22: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DDADE37BFC0 for ; Wed, 19 Jul 2000 11:21:56 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA93253; Wed, 19 Jul 2000 12:21:55 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA83214; Wed, 19 Jul 2000 12:21:55 -0600 (MDT) Message-Id: <200007191821.MAA83214@harmony.village.org> To: Poul-Henning Kamp Subject: Re: randomdev entropy gathering is really weak Cc: Mark Murray , current@FreeBSD.ORG In-reply-to: Your message of "Wed, 19 Jul 2000 20:09:48 +0200." <946.964030188@critter.freebsd.dk> References: <946.964030188@critter.freebsd.dk> Date: Wed, 19 Jul 2000 12:21:55 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <946.964030188@critter.freebsd.dk> Poul-Henning Kamp writes: : A geiger counter and a smoke-detector would be *so much* cheaper : and give more bits per second :-) Agreed. And a lot less hassle. A *LOT* less hassle. :-) : >It certainly would be better than nothing and would be a decent source : >of randomness. It would be my expectation that if tests were run to : >measure this randomness and the crypto random tests were applied, : >we'd find a fairly good source. : : The trick here is to actually measure the quality of our entropy. : I have asked Markm to provide us with some kernel option which can : be used to get a copy of the entropy so we can study the quality : off it. Yes. That's the hard part. that's one area where my knowledge is somewhat weak. : BTW: You have *no* idea how much I envy your access to high quality : timing hardware :-) Well, there are hidden benefits working here that I never knew :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 11:23:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0B0F437B5EE for ; Wed, 19 Jul 2000 11:23:21 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA93266; Wed, 19 Jul 2000 12:23:18 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA83239; Wed, 19 Jul 2000 12:23:18 -0600 (MDT) Message-Id: <200007191823.MAA83239@harmony.village.org> To: Mark Murray Subject: Re: randomdev entropy gathering is really weak Cc: Poul-Henning Kamp , current@FreeBSD.ORG In-reply-to: Your message of "Wed, 19 Jul 2000 20:11:59 +0200." <200007191812.UAA00448@grimreaper.grondar.za> References: <200007191812.UAA00448@grimreaper.grondar.za> <200007191733.LAA82735@harmony.village.org> Date: Wed, 19 Jul 2000 12:23:18 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007191812.UAA00448@grimreaper.grondar.za> Mark Murray writes: : The randomness is good, no doubt; I worry about how accessible that : randomness is to an attacker? That's a good thing to worry about. : If the attacker is on your computer (he us a user, say), he might know : a lot about the current frequency of your xtal. He can also get the same : (remote) time offsets as you. What does that give him? Not much, but it : could reduce the bits that he needs to guess. By how much? I don't : know. I don't know the answers to that either. Of course, if the attaker has root access to your machine, then you have bigtime problems with keeping the random bits secret anyway... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 11:25:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from reliant.nielsenmedia.com (reliant.nielsenmedia.com [205.129.32.15]) by hub.freebsd.org (Postfix) with ESMTP id 8CD8237BFDC for ; Wed, 19 Jul 2000 11:25:06 -0700 (PDT) (envelope-from David_W_Gray@tvratings.com) Received: from nmrusdunsxg0.nielsenmedia.com (nmrusdunsxg0.nielsenmedia.com [10.9.11.120]) by reliant.nielsenmedia.com (8.9.3/8.9.3) with ESMTP id OAA07707 for ; Wed, 19 Jul 2000 14:25:03 -0400 (EDT) Received: by nmrusdunsxg0.nielsenmedia.com with Internet Mail Service (5.5.2651.58) id <38BNS92V>; Wed, 19 Jul 2000 14:25:02 -0400 Message-ID: <01D4D419B1A4D111A30400805FE65B13070ABF5E@nmrusdunsx1.nielsenmedia.com> From: "Gray, David W." To: "'FreeBSD Current list'" Subject: make release? Date: Wed, 19 Jul 2000 14:25:01 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2651.58) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it just me, or is make release broken? I've been getting a bomb-out whilst making the boot crunch (in /bin/sh, I think. Its at home, I'm not.) I haven't seen anybody kvetching (I *do* read current...) Just to sanity check, I ran a 4.0 make release last night, that worked just fine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 11:56:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (fw2.aub.dk [195.24.1.195]) by hub.freebsd.org (Postfix) with ESMTP id C8BC837B5EE for ; Wed, 19 Jul 2000 11:56:40 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id UAA01161; Wed, 19 Jul 2000 20:56:13 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mark Murray Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-reply-to: Your message of "Wed, 19 Jul 2000 20:11:59 +0200." <200007191812.UAA00448@grimreaper.grondar.za> Date: Wed, 19 Jul 2000 20:56:13 +0200 Message-ID: <1159.964032973@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007191812.UAA00448@grimreaper.grondar.za>, Mark Murray writes: >[ A whole bunch of sane stuff removed ] > >> It certainly would be better than nothing and would be a decent source >> of randomness. It would be my expectation that if tests were run to >> measure this randomness and the crypto random tests were applied, >> we'd find a fairly good source. > >The randomness is good, no doubt; I worry about how accessible that >randomness is to an attacker? > >If the attacker is on your computer (he us a user, say), he might know >a lot about the current frequency of your xtal. He can also get the same >(remote) time offsets as you. What does that give him? Not much, but it >could reduce the bits that he needs to guess. By how much? I don't >know. Mark, this is one of the reasons why we need a way to measure the quality of our entropy, please???? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 12:29:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id 19CA237B95D for ; Wed, 19 Jul 2000 12:29:34 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.9.3/8.9.3) id PAA99620; Wed, 19 Jul 2000 15:30:42 -0400 (EDT) (envelope-from dufault) From: Peter Dufault Message-Id: <200007191930.PAA99620@hda.hda.com> Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007191746.LAA82887@harmony.village.org> from Warner Losh at "Jul 19, 2000 11:46:01 am" To: Warner Losh Date: Wed, 19 Jul 2000 15:30:37 -0400 (EDT) Cc: Peter Dufault , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <200007191308.JAA98111@hda.hda.com> Peter Dufault writes: > : > The reason why ntp is interesting is that we compare the received data > : > with our unpredictable local clock. It is the result of this comparison > : > which is good entropy bits. > : > : Is the resolution of thermal sensors on many new motherboards and > : CPU high enough to get thermal randomness? > > Yes. You'll also find that the voltage drifts as well. However, I > doubt you'd be able to get more than 1 bit out of the voltage > readings. The thermal readings, depending on their precision, would > also yield several random bits. But this several may be only 3 or 4. > The temperature varies based on work load and on the climate controls > in place at the site. I actually meant can you get real randomness, measuring the thermal noise in the on-chip temperature diode should be a good source of randomness. Except they are probably "kind" enough to fully filter it out. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 12:32:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 6E47D37B95D for ; Wed, 19 Jul 2000 12:32:16 -0700 (PDT) (envelope-from jhb@pike.osd.bsdi.com) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id MAA87685; Wed, 19 Jul 2000 12:32:03 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200007191932.MAA87685@pike.osd.bsdi.com> Subject: Re: make release? In-Reply-To: <01D4D419B1A4D111A30400805FE65B13070ABF5E@nmrusdunsx1.nielsenmedia.com> from "Gray, David W." at "Jul 19, 2000 02:25:01 pm" To: "Gray, David W." Date: Wed, 19 Jul 2000 12:32:03 -0700 (PDT) Cc: FreeBSD-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Charset iso-8859-1 unsupported, filtering to ASCII...] > Is it just me, or is make release broken? > > I've been getting a bomb-out whilst making the boot crunch (in /bin/sh, I > think. Its at home, I'm not.) I haven't seen anybody kvetching (I *do* read > current...) Just to sanity check, I ran a 4.0 make release last night, that > worked just fine. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Hmm, it built fine yesterday morning (July 18), but died this morning as follows: cc -O -pipe -I. -Dyylval=pcap_lval -DHAVE_SYS_IOCCOM_H=1 -DHAVE_SYS_SOCKIO_H=1 -DHAVE_ETHER_HOSTTON=1 -DHAVE_STRERROR=1 -DHAVE_SOCKADDR_SA_LEN=1 -DLBL_ALIGN=1 -DINET6 -I/usr/src/lib/libpcap/../../contrib/libpcap -I/usr/src/lib/libpcap/../ ../contrib/libpcap/lbl -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libpc ap/../../contrib/libpcap/nametoaddr.c -o nametoaddr.o /usr/src/lib/libpcap/../../contrib/libpcap/nametoaddr.c:370: conflicting types f or `ether_hostton' /usr/obj/usr/src/i386/usr/include/net/ethernet.h:111: previous declaration of `e ther_hostton' *** Error code 1 Stop in /usr/src/lib/libpcap. *** Error code 1 Stop in /usr/src/release. ---------------------------------------- release started at 00:30:00 on 07/19/00 release died at 02:30:39 on 07/19/00 ---------------------------------------- -- John Baldwin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 12:45:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from ywing.creative.net.au (ywing.creative.net.au [203.56.168.34]) by hub.freebsd.org (Postfix) with ESMTP id 4A88B37C018 for ; Wed, 19 Jul 2000 12:45:46 -0700 (PDT) (envelope-from adrian@ywing.creative.net.au) Received: (from adrian@localhost) by ywing.creative.net.au (8.9.3/8.9.3) id VAA45527; Wed, 19 Jul 2000 21:53:03 +0200 (CEST) (envelope-from adrian) Date: Wed, 19 Jul 2000 21:53:03 +0200 From: Adrian Chadd To: Tony Johnson Cc: "'current@freebsd.org'" Subject: Re: nic cards Message-ID: <20000719215303.A44512@ywing.creative.net.au> References: <01BFEFE7.C21FC8D0.gjohnson@gs.verio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <01BFEFE7.C21FC8D0.gjohnson@gs.verio.net>; from gjohnson@gs.verio.net on Mon, Jul 17, 2000 at 12:08:45PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000, Tony Johnson wrote: > One thing that I just noticed on the python mailing list is a portable way > of retrieving an ip addy. Why not start using eth0 (unfortunately as they > do in Linuxland) eth1 ... For nic cards instead of fxp0 for an intel, > etc... > > The fxp0 way is too hardware and implementation dependant. ifconfig -a ? Adrian -- Adrian Chadd Now 17-year-olds can't play a _video game_ because its called violent - and real violence is still called dinner. -- jamie@mccarthy.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 13:50:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from samxie.cl.msu.edu (samxie.cl.msu.edu [35.8.1.33]) by hub.freebsd.org (Postfix) with ESMTP id 19D4837BFBE for ; Wed, 19 Jul 2000 13:50:31 -0700 (PDT) (envelope-from sam@samxie.cl.msu.edu) Received: (from sam@localhost) by samxie.cl.msu.edu (8.9.3/8.9.3) id QAA39723 for freebsd-current@freebsd.org; Wed, 19 Jul 2000 16:51:33 -0400 (EDT) (envelope-from sam) Date: Wed, 19 Jul 2000 16:51:33 -0400 From: Sam Xie To: freebsd-current@freebsd.org Subject: trafshow doesn't work? Message-ID: <20000719165133.C511@samxie.cl.msu.edu> Mail-Followup-To: Sam Xie , freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i X-Operating-System: FreeBSD 5.0-CURRENT i386 WWW-Home-Page: http://samxie.cl.msu.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! There, My trafshow doesn't work. Whenever I tried to run trafshow, it gave me error message says, "trafshow: ÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐ: Device not configured" I check my Kernel configuration file, a line "device bpf 4 #Berkeley packet filter" is there and device drivers bpf0, bpf1, bpf2, and bpf3 are in /dev. I don't know whatelse I should configure. Can someone help me? My OS is FreeBSD 5.0-CURRENT #21. Thanks! Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 14: 6:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id D2F9D37B8DF; Wed, 19 Jul 2000 14:06:48 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA09984; Wed, 19 Jul 2000 14:06:48 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 19 Jul 2000 14:06:48 -0700 (PDT) From: Kris Kennaway To: Sam Xie Cc: freebsd-current@freebsd.org Subject: Re: trafshow doesn't work? In-Reply-To: <20000719165133.C511@samxie.cl.msu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jul 2000, Sam Xie wrote: > Hi! There, > My trafshow doesn't work. Whenever I tried to run trafshow, it gave = me > error message says, "trafshow: =D0=D0=D0=D0=D0=D0=D0=D0=D0=D0=D0=D0=D0=D0= =D0=D0: Device not configured" I check my Kernel configuration file, a line Fallout from the malloc.conf changes. tcpdump has the same bug. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 14: 7:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from nikias.cc.uoa.gr (nikias.cc.uoa.gr [195.134.68.10]) by hub.freebsd.org (Postfix) with ESMTP id 55DA337C07C for ; Wed, 19 Jul 2000 14:07:27 -0700 (PDT) (envelope-from eatha@cc.uoa.gr) Received: from localhost (eatha@localhost) by nikias.cc.uoa.gr (8.9.3/8.9.3) with SMTP id AAA13014 for ; Thu, 20 Jul 2000 00:07:23 +0300 (EET DST) Date: Thu, 20 Jul 2000 00:07:22 +0300 (EET DST) From: Elias Athanasopoulos Reply-To: Elias Athanasopoulos To: freebsd-current@freebsd.org Subject: Default Gateway problem. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have the following network: A (FreeBSD-CURRENT) - ethernet - B (Linux) - ppp - Internet 192.168.1.2 192.168.1.1 I have enabled IP Masq. in 'B' and set it as the default gateway for A, issuing the command below: [A] $ ifconfig add default 192.168.1.1 When the Internet connection is alive everything is ok. When no Internet connection exists I cannot make local telnets/ftps from FreeBSD to Linux, using hostnames instead of raw IP addresses. It seems that A (FreeBSD) tries to locate the nameservers specified in /etc/resolv.conf. My /etc/hosts: 192.168.1.1 B 192.168.1.2 A My /etc/host.conf: hosts bind Any hints? Regards, Elias -- Elias Athanasopoulos | I bet the human brain is | H.E.P & Apps. Lab. http://www.uoa.gr/~eatha | a kludge. -Marvin Minsky | University Of Athens To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 14:27: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4038537BE86 for ; Wed, 19 Jul 2000 14:26:56 -0700 (PDT) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id XAA08627; Wed, 19 Jul 2000 23:26:48 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id XAA61530; Wed, 19 Jul 2000 23:07:36 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Wed, 19 Jul 2000 23:07:36 +0200 (CEST) From: Leif Neland To: Sam Xie Cc: freebsd-current@FreeBSD.ORG Subject: Re: trafshow doesn't work? In-Reply-To: <20000719165133.C511@samxie.cl.msu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jul 2000, Sam Xie wrote: > Hi! There, > My trafshow doesn't work. Whenever I tried to run trafshow, it gave me > error message says, "trafshow: ÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐ: Device not configured" I check my Kernel configuration file, a line > "device bpf 4 #Berkeley packet filter" I get the same message when running arpwatch which also uses bpf. It still works, though. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 14:38:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id E308837BE45 for ; Wed, 19 Jul 2000 14:38:18 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e6JLcEH37821; Wed, 19 Jul 2000 14:38:14 -0700 (PDT) Date: Wed, 19 Jul 2000 14:38:14 -0700 (PDT) From: Doug White To: Elias Athanasopoulos Cc: freebsd-current@FreeBSD.ORG Subject: Re: Default Gateway problem. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 20 Jul 2000, Elias Athanasopoulos wrote: > > Hi, > > I have the following network: > > A (FreeBSD-CURRENT) - ethernet - B (Linux) - ppp - Internet > 192.168.1.2 192.168.1.1 > > I have enabled IP Masq. in 'B' and set it as the default gateway > for A, issuing the command below: > > [A] $ ifconfig add default 192.168.1.1 > Try 'route' instead of 'ifconfig' and you might have better luck. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 14:39:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id A430137C036 for ; Wed, 19 Jul 2000 14:39:37 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id XAA01094; Wed, 19 Jul 2000 23:37:47 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007192137.XAA01094@grimreaper.grondar.za> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <946.964030188@critter.freebsd.dk> In-Reply-To: <946.964030188@critter.freebsd.dk> ; from Poul-Henning Kamp "Wed, 19 Jul 2000 20:09:48 +0200." Date: Wed, 19 Jul 2000 23:37:46 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The trick here is to actually measure the quality of our entropy. > I have asked Markm to provide us with some kernel option which can > be used to get a copy of the entropy so we can study the quality > off it. I have something that is _very_ crude, and definitely not commitworthy, but it is up to the doing the job above. As soon as I've prettyfied it a bit, I'll give y'all some patches. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 14:41:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 64FB737C03F for ; Wed, 19 Jul 2000 14:41:37 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id XAA01113; Wed, 19 Jul 2000 23:41:25 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007192141.XAA01113@grimreaper.grondar.za> To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <200007191823.MAA83239@harmony.village.org> In-Reply-To: <200007191823.MAA83239@harmony.village.org> ; from Warner Losh "Wed, 19 Jul 2000 12:23:18 CST." Date: Wed, 19 Jul 2000 23:41:24 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : If the attacker is on your computer (he us a user, say), he might know > : a lot about the current frequency of your xtal. He can also get the same > : (remote) time offsets as you. What does that give him? Not much, but it > : could reduce the bits that he needs to guess. By how much? I don't > : know. > > I don't know the answers to that either. > > Of course, if the attaker has root access to your machine, then you > have bigtime problems with keeping the random bits secret anyway... My scenario assumed that the attacker/user was not root. Of course if he is root, he knows a bit more, but even a non-root attacker can make a statistical study of the local clock and some hand-rolled ntp code. (I'm not suggesting it is easy, just possible :-) ) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 14:44:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 3C69A37C0A7 for ; Wed, 19 Jul 2000 14:44:45 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id XAA01127; Wed, 19 Jul 2000 23:42:25 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007192142.XAA01127@grimreaper.grondar.za> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <1159.964032973@critter.freebsd.dk> In-Reply-To: <1159.964032973@critter.freebsd.dk> ; from Poul-Henning Kamp "Wed, 19 Jul 2000 20:56:13 +0200." Date: Wed, 19 Jul 2000 23:42:25 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >If the attacker is on your computer (he us a user, say), he might know > >a lot about the current frequency of your xtal. He can also get the same > >(remote) time offsets as you. What does that give him? Not much, but it > >could reduce the bits that he needs to guess. By how much? I don't > >know. > > Mark, this is one of the reasons why we need a way to measure the > quality of our entropy, please???? I understand 100%! That's why I'm doing it :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 14:58:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from nikias.cc.uoa.gr (nikias.cc.uoa.gr [195.134.68.10]) by hub.freebsd.org (Postfix) with ESMTP id 3D8D537C1B7 for ; Wed, 19 Jul 2000 14:58:44 -0700 (PDT) (envelope-from anteater@cc.uoa.gr) Received: from neutrino.particles.org (nikias.cc.uoa.gr [195.134.68.10]) by nikias.cc.uoa.gr (8.9.3/8.9.3) with ESMTP id AAA21151 for ; Thu, 20 Jul 2000 00:58:39 +0300 (EET DST) Received: (from anteater@localhost) by neutrino.particles.org (8.9.3/8.9.3) id BAA01166 for freebsd-current@freebsd.org; Thu, 20 Jul 2000 01:00:51 +0300 Date: Thu, 20 Jul 2000 01:00:51 +0300 From: Elias Athanasopoulos To: freebsd-current@freebsd.org Subject: Re: Default Gateway problem. Message-ID: <20000720010051.F799@neutrino> References: <20000720004803.E799@neutrino> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000720004803.E799@neutrino>; from eatha@cc.uoa.gr on Thu, Jul 20, 2000 at 12:48:03AM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 02:38:14PM -0700, Doug White wrote: > > > [A] $ ifconfig add default 192.168.1.1 > > > > Try 'route' instead of 'ifconfig' and you might have better luck. Oops! Sorry, it was a typo. :-( The command I used is 'route'. I have no problem with my routing table (which I can show you if you want). Regards, Elias -- Elias Athanasopoulos | I bet the human brain is | H.E.P & Apps. Lab. http://www.uoa.gr/~eatha | a kludge. -Marvin Minsky | University Of Athens To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 15:26:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3AA5237B985 for ; Wed, 19 Jul 2000 15:26:14 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e6JMQEx13581 for current@freebsd.org; Wed, 19 Jul 2000 15:26:14 -0700 (PDT) Date: Wed, 19 Jul 2000 15:26:13 -0700 From: Alfred Perlstein To: current@freebsd.org Subject: libexec/rtld-elf install broken? Message-ID: <20000719152613.Z13979@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> libexec/rtld-elf chflags noschg /usr/libexec/ld-elf.so.1 chflags noschg /usr/libexec/ld-elf.so.1.old cp -p /usr/libexec/ld-elf.so.1 /usr/libexec/ld-elf.so.1.old cp:No such file or directory *** Error code 1 Stop in /usr/src/libexec/rtld-elf. *** Error code 1 Stop in /usr/src/libexec. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 # ls -l /usr/libexec/ld-elf.so.1 /usr/libexec/ld-elf.so.1.old -r-xr-xr-x 1 root wheel 74512 Jul 19 15:13 /usr/libexec/ld-elf.so.1 -r-xr-xr-x 1 root wheel 74160 Jul 10 04:47 /usr/libexec/ld-elf.so.1.old boggles! -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 15:38:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id C7DB137B780 for ; Wed, 19 Jul 2000 15:38:09 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 0828C3EE9; Wed, 19 Jul 2000 15:38:09 -0700 (PDT) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) with ESMTP id PAA22588; Wed, 19 Jul 2000 15:38:08 -0700 (PDT) Message-ID: <39762DD0.C132BA6A@cup.hp.com> Date: Wed, 19 Jul 2000 15:38:08 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: libexec/rtld-elf install broken? References: <20000719152613.Z13979@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > ===> libexec/rtld-elf > chflags noschg /usr/libexec/ld-elf.so.1 > chflags noschg /usr/libexec/ld-elf.so.1.old > cp -p /usr/libexec/ld-elf.so.1 /usr/libexec/ld-elf.so.1.old > cp:No such file or directory > *** Error code 1 I think we need to copy 'cp' in installworld as well. I didn't catch it because it will probably only copy ld-elf.so if an existing version is present (I tested with an empty DESTDIR). I'll fix it. -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 15:59:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail4.svr.pol.co.uk (mail4.svr.pol.co.uk [195.92.193.211]) by hub.freebsd.org (Postfix) with ESMTP id 9E18D37B538 for ; Wed, 19 Jul 2000 15:59:45 -0700 (PDT) (envelope-from n_hibma@qubesoft.com) Received: from [195.92.67.23] (helo=mail18.svr.pol.co.uk) by mail4.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 13F2oX-0003Si-00 for current@freebsd.org; Wed, 19 Jul 2000 23:59:41 +0100 Received: from modem-244.imperator-angel.dialup.pol.co.uk ([62.137.32.244] helo=henny.webweaving.org) by mail18.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 13F2oW-0001Zw-00 for current@FreeBSD.ORG; Wed, 19 Jul 2000 23:59:41 +0100 Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id WAA09068 for ; Tue, 18 Jul 2000 22:43:29 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Tue, 18 Jul 2000 22:43:29 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: FreeBSD CURRENT Mailing List Subject: cvs commit: src/sys/dev/ppbus ppb_base.c (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could people try this out and see whether this solves any problems with detection of Zip drives? You might have to add flags=0x01 to ppc to use NIBBLE mode. If enough people respond I'll try and get this into 4.1-RC. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ ---------- Forwarded message ---------- Date: Tue, 18 Jul 2000 13:16:16 -0700 (PDT) From: Nick Hibma To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/dev/ppbus ppb_base.c n_hibma 2000/07/18 13:16:16 PDT Modified files: sys/dev/ppbus ppb_base.c Log: Fix the detection of parallel port Zip drives. Submitted by: j mckitrick Reviewed by: nsouchu Revision Changes Path 1.11 +6 -5 src/sys/dev/ppbus/ppb_base.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 16:23:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id 04AF437B67A for ; Wed, 19 Jul 2000 16:23:48 -0700 (PDT) (envelope-from jazepeda@pacbell.net) Received: from ppp-207-214-149-44.snrf01.pacbell.net ([207.214.149.44]) by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FXY00MEYWOM88@mta6.snfc21.pbi.net> for freebsd-current@FreeBSD.ORG; Wed, 19 Jul 2000 16:17:14 -0700 (PDT) Date: Wed, 19 Jul 2000 16:18:11 -0700 (PDT) From: Alex Zepeda Subject: Re: cer/b7b/pfc -> pem In-reply-to: <005f01bff04d$3d39a800$0e00a8c0@neland.dk> X-Sender: alex@zippy.pacbell.net To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jul 2000, Leif Neland wrote: > This works nicely in Windows (Outlook Express), but I'd like to try using > the same key with openssl to generate crypted (to myself) or signed > messages. > > I can export the key as a .cer, .p7b or .pfx, but openssl seems to want it > in .pem format. You need to export your private key (too). Without OE5, this is an option when you attempt to save a cert as a file. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 16:39:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id BAE2237B774 for ; Wed, 19 Jul 2000 16:39:55 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id QAA27911; Wed, 19 Jul 2000 16:48:45 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007192348.QAA27911@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Doug Barton Cc: freebsd-current@freebsd.org Subject: Re: No /boot/loader In-reply-to: Your message of "Mon, 17 Jul 2000 14:49:01 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Jul 2000 16:48:45 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No response to this on -stable. The actual error message is: > > Disk error 0x1 (lba=0x7004c) > No /boot/loader Disk geometry stuffup, or a 'real' disk error. > Also, on a whim I decided to try running /boot/loader. I got a It's not a FreeBSD executable (obviously enough), so you can't do this. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 17:28:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62]) by hub.freebsd.org (Postfix) with ESMTP id E755E37B8D3; Wed, 19 Jul 2000 17:28:31 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id RAA00539; Wed, 19 Jul 2000 17:28:26 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Wed, 19 Jul 2000 17:28:26 -0700 (PDT) From: Doug Barton X-Sender: doug@dt052n3e.san.rr.com To: Mike Smith Cc: freebsd-current@freebsd.org Subject: Re: No /boot/loader In-Reply-To: <200007192348.QAA27911@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jul 2000, Mike Smith wrote: > > No response to this on -stable. The actual error message is: > > > > Disk error 0x1 (lba=0x7004c) > > No /boot/loader > > Disk geometry stuffup, or a 'real' disk error. Well, I put my money on real disk error, but only because it vindicates my position that we shouldn't have switched to this new kind of disk in the first place. As for geometry, I tried both with and without "dangerously dedicated." My understanding was that if I used the dos partition entry method that we should be able to pick up the geometry correctly, but should I try the old dos fdisk trick as well? Also, would the adaptec setting to translate >1G be affecting this? It's on currently, which it is on all my other motherboards of similar vintage. Finally, the other thing that's confusing me is that the error message mentions "lba," which I thought was strictly an IDE thing. Just for grins I tried toggling LBA and CHS mode in the bios, but no joy. > > Also, on a whim I decided to try running /boot/loader. I got a > > It's not a FreeBSD executable (obviously enough), so you can't do this. Yeah... it was born out of frustration, since nothing else was working anyway. I was kind of surprised that it did anything at all, to be honest. Thanks for your response, Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 17:45: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 3405337B538 for ; Wed, 19 Jul 2000 17:44:57 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA09864; Wed, 19 Jul 2000 17:44:51 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id RAA15027; Wed, 19 Jul 2000 17:44:50 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 19 Jul 2000 17:44:50 -0700 (PDT) Message-Id: <200007200044.RAA15027@vashon.polstra.com> To: bright@wintelcom.net Subject: Re: libexec/rtld-elf install broken? In-Reply-To: <20000719152613.Z13979@fw.wintelcom.net> References: <20000719152613.Z13979@fw.wintelcom.net> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000719152613.Z13979@fw.wintelcom.net>, Alfred Perlstein wrote: > ===> libexec/rtld-elf > chflags noschg /usr/libexec/ld-elf.so.1 > chflags noschg /usr/libexec/ld-elf.so.1.old > cp -p /usr/libexec/ld-elf.so.1 /usr/libexec/ld-elf.so.1.old > cp:No such file or directory ^ | Why is the space missing that is supposed to be in this message? > # ls -l /usr/libexec/ld-elf.so.1 /usr/libexec/ld-elf.so.1.old > -r-xr-xr-x 1 root wheel 74512 Jul 19 15:13 /usr/libexec/ld-elf.so.1 > -r-xr-xr-x 1 root wheel 74160 Jul 10 04:47 /usr/libexec/ld-elf.so.1.old I can't figure out what is going on here. The whole set of commands in the Makefile is inside an ".if exists" block: beforeinstall: .if exists(${DESTDIR}${BINDIR}/${PROG}) -chflags noschg ${DESTDIR}${BINDIR}/${PROG} .if exists(${DESTDIR}${BINDIR}/${PROG}.old) -chflags noschg ${DESTDIR}${BINDIR}/${PROG}.old .endif cp -p ${DESTDIR}${BINDIR}/${PROG} ${DESTDIR}${BINDIR}/${PROG}.old .endif I added this to the Makefile 11 days ago, and haven't heard any other reports of problems. > boggles! Yep, I'm baffled too. Have you got a rogue "cp" program somewhere in your path? John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 17:48:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id C567637B588 for ; Wed, 19 Jul 2000 17:48:17 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e6K0mC318315; Wed, 19 Jul 2000 17:48:12 -0700 (PDT) Date: Wed, 19 Jul 2000 17:48:12 -0700 From: Alfred Perlstein To: John Polstra Cc: current@freebsd.org Subject: Re: libexec/rtld-elf install broken? Message-ID: <20000719174812.D13979@fw.wintelcom.net> References: <20000719152613.Z13979@fw.wintelcom.net> <200007200044.RAA15027@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200007200044.RAA15027@vashon.polstra.com>; from jdp@polstra.com on Wed, Jul 19, 2000 at 05:44:50PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * John Polstra [000719 17:45] wrote: > In article <20000719152613.Z13979@fw.wintelcom.net>, > Alfred Perlstein wrote: > > ===> libexec/rtld-elf > > chflags noschg /usr/libexec/ld-elf.so.1 > > chflags noschg /usr/libexec/ld-elf.so.1.old > > cp -p /usr/libexec/ld-elf.so.1 /usr/libexec/ld-elf.so.1.old > > cp:No such file or directory > ^ > | > Why is the space missing that is supposed to be in this message? > > I added this to the Makefile 11 days ago, and haven't heard any > other reports of problems. > > > boggles! > > Yep, I'm baffled too. Have you got a rogue "cp" program somewhere > in your path? I needed to add 'cp' to src/Makefile.inc1, Marcel explained it to me but I'm sorry I did, -current is terribly broken. I now have two machines in unusable state. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 17:49:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 52E0837C106; Wed, 19 Jul 2000 17:49:08 -0700 (PDT) (envelope-from jeremyp@pc0640.alcatel.com.au) Received: by border.alcanet.com.au id <115204>; Thu, 20 Jul 2000 10:48:48 +1000 Date: Wed, 19 Jul 2000 20:39:19 +1000 From: Peter Jeremy Subject: Re: dc driver and underruns (was: Strangeness with 4.0-S) In-reply-to: <20000714084639.B1926@freebie.demon.nl>; from wkb@freebie.demon.nl on Fri, Jul 14, 2000 at 08:46:40AM +0200 To: wilko@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Message-Id: <00Jul20.104848est.115204@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <200007131622.JAA12738@gndrsh.dnsmgr.net> <200007140251.MAA07785@dungeon.home> <20000714084639.B1926@freebie.demon.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 14, 2000 at 08:46:40AM +0200, Wilko Bulte wrote: >That theory is not correct, I have seen multiple Alpha machines reporting >buffer underruns as well. No ATA disk in sight there.. I get the same thing on AS4000/AS4100 machines running Tru64. I'm inclined to believe it's a design flaw in the chip. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 18:32:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id CC51437B684 for ; Wed, 19 Jul 2000 18:32:14 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id SAA10066; Wed, 19 Jul 2000 18:32:12 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000719174812.D13979@fw.wintelcom.net> Date: Wed, 19 Jul 2000 18:32:12 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Alfred Perlstein Subject: Re: libexec/rtld-elf install broken? Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > I needed to add 'cp' to src/Makefile.inc1, Marcel explained it to me Oh, so it was "cp" that wasn't found, I take it. We should change the message in make so it's more like what shells say ("command not found"). > but I'm sorry I did, -current is terribly broken. I now have two > machines in unusable state. Ugh. Sorry to hear that. Man, -current ain't what it used to be. But then it never was ... :-) John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 19:21:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id AECFD37B983 for ; Wed, 19 Jul 2000 19:21:29 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e6K2LRC20915; Wed, 19 Jul 2000 19:21:27 -0700 (PDT) Date: Wed, 19 Jul 2000 19:21:27 -0700 From: Alfred Perlstein To: John Polstra Cc: current@freebsd.org Subject: Re: libexec/rtld-elf install broken? Message-ID: <20000719192127.F13979@fw.wintelcom.net> References: <20000719174812.D13979@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from jdp@polstra.com on Wed, Jul 19, 2000 at 06:32:12PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * John Polstra [000719 18:32] wrote: > Alfred Perlstein wrote: > > > > I needed to add 'cp' to src/Makefile.inc1, Marcel explained it to me > > Oh, so it was "cp" that wasn't found, I take it. We should change > the message in make so it's more like what shells say ("command not > found"). > > > but I'm sorry I did, -current is terribly broken. I now have two > > machines in unusable state. > > Ugh. Sorry to hear that. Man, -current ain't what it used to be. > But then it never was ... :-) but.. but.. but... it _was_ working out so well.... ;( -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 19 19:31:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id CF2ED37B890 for ; Wed, 19 Jul 2000 19:31:14 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id TAA10301; Wed, 19 Jul 2000 19:31:13 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id TAA15177; Wed, 19 Jul 2000 19:31:12 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 19 Jul 2000 19:31:12 -0700 (PDT) Message-Id: <200007200231.TAA15177@vashon.polstra.com> To: hm@hcs.de Subject: Re: kernel compile failure without -O option In-Reply-To: <20000719144614.7FE52483D@hcswork.hcs.de> References: <20000719144614.7FE52483D@hcswork.hcs.de> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000719144614.7FE52483D@hcswork.hcs.de>, Hellmuth Michaelis wrote: > > In the process of tracing down the problem of the kernel panic when booting > a kernel with pcvt enabled, i tried to compile a kernel without the -O > option to gcc and got this compile failure (sources from 18.7.2000 9:00 MET): > > cc -c -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include > -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 > -fomit-frame-pointer ../../i386/i386/atomic.c > In file included from ../../i386/i386/atomic.c:47: > machine/atomic.h: In function `atomic_set_char': > machine/atomic.h:106: inconsistent operand constraints in an `asm' > machine/atomic.h: In function `atomic_clear_char': > machine/atomic.h:107: inconsistent operand constraints in an `asm' [...] I have seen that same problem recently in a slightly different context. After staring at the code for a very long time, I could only conclude that the problem was a bug in gcc. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 20 3:59:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout1.silyn-tek.de (mout1.silyn-tek.de [194.25.165.69]) by hub.freebsd.org (Postfix) with ESMTP id 42A2837BBA5 for ; Thu, 20 Jul 2000 03:59:40 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from [192.168.32.34] (helo=mx2.silyn-tek.de) by mout1.silyn-tek.de with esmtp (Exim 3.13 #1) id 13FE3H-0000p4-00 for current@freebsd.org; Thu, 20 Jul 2000 12:59:39 +0200 Received: from p3e9c115b.dip0.t-ipconnect.de ([62.156.17.91] helo=neutron.cichlids.com) by mx2.silyn-tek.de with esmtp (Exim 3.13 #1) id 13FE3E-0006eq-00 for current@freebsd.org; Thu, 20 Jul 2000 12:59:36 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 56E3BAB91 for ; Thu, 20 Jul 2000 13:01:18 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 2A37B14ABB; Thu, 20 Jul 2000 12:38:09 +0200 (CEST) Date: Thu, 20 Jul 2000 12:38:08 +0200 To: current@freebsd.org Subject: cross-building broken? Message-ID: <20000720123808.A78907@cichlids.cichlids.com> Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. From: alex@big.endian.de (Alexander Langer) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! root:/usr/src $ make MACHINE_ARCH=alpha buildworld .... -------------------------------------------------------------- >>> stage 4: building libraries -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/alpha COMPILER_PATH=/usr/obj/alpha/usr/src/i386/usr/libexec:/usr/obj/alpha/usr/src/i386/usr/bin LIBRARY_PATH=/usr/obj/alpha/usr/src/i386/usr/lib:/usr/obj/alpha/usr/src/i386/usr/lib OBJFORMAT_PATH=/usr/obj/alpha/usr/src/i386/usr/libexec PERL5LIB=/usr/obj/alpha/usr/src/i386/usr/libdata/perl/5.6.0 DESTDIR=/usr/obj/alpha/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/alpha/usr/src/i386/usr/sbin:/usr/obj/alpha/usr/src/i386/usr/bin:/usr/obj/alpha/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 -DNOHTML -DNOINFO -DNOMAN -DNOFSCHG libraries cd /usr/src/lib/csu/alpha; make depend; make all; make install sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 crt1.o /usr/obj/alpha/usr/src/i386/usr/lib/crt1.o sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 crtbegin.o /usr/obj/alpha/usr/src/i386/usr/lib/crtbegin.o sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 crtend.o /usr/obj/alpha/usr/src/i386/usr/lib/crtend.o sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 gcrt1.o /usr/obj/alpha/usr/src/i386/usr/lib/gcrt1.o sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 crtbegin.So /usr/obj/alpha/usr/src/i386/usr/lib/crtbeginS.o sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 crtend.So /usr/obj/alpha/usr/src/i386/usr/lib/crtendS.o cd /usr/src/lib/libmd; make depend; make all; make install cc -O -pipe -I/usr/src/lib/libmd -I/usr/obj/alpha/usr/src/i386/usr/include -c /usr/src/lib/libmd/md2c.c -o md2c.o /usr/src/lib/libmd/md2c.c: In function `MD2Final': /usr/src/lib/libmd/md2c.c:167: internal error--unrecognizable insn: (insn 26 24 28 (set (reg:DI 79) (and:DI (plus:DI (reg/v:DI 69) (const_int 586478694938416944 [0x823974408239730])) (const_int -8 [0xfffffffffffffff8]))) -1 (insn_list 4 (nil)) (nil)) *** Error code 1 Stop in /usr/src/lib/libmd. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. That is from FreeBSD cichlids.cichlids.com 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Jul 18 13:36:59 CEST 2000 alex@cichlids.cichlids.com:/usr/obj/usr/src/sys/cichlids i386 Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 20 8:46:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id D89C437BDA1; Thu, 20 Jul 2000 08:46:42 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e6KFkaV03018; Thu, 20 Jul 2000 08:46:36 -0700 (PDT) Date: Thu, 20 Jul 2000 08:46:36 -0700 (PDT) From: Doug White To: Doug Barton Cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: No /boot/loader In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jul 2000, Doug Barton wrote: > > Disk geometry stuffup, or a 'real' disk error. > > Well, I put my money on real disk error, but only because it > vindicates my position that we shouldn't have switched to this new kind of > disk in the first place. > > As for geometry, I tried both with and without "dangerously > dedicated." My understanding was that if I used the dos partition entry > method that we should be able to pick up the geometry correctly, but > should I try the old dos fdisk trick as well? Also, would the adaptec > setting to translate >1G be affecting this? It's on currently, which it is > on all my other motherboards of similar vintage. Your boot disk is now *required* (or will be very very soon) to have a proper slice table in -CURRENT; dedicated disks are deprecated in order to get a smarter boot0. Speaking of boot0 you might try using boot0cfg to force packet mode. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 20 9: 9:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 44C0B37B858 for ; Thu, 20 Jul 2000 09:09:33 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 592BC1F47; Thu, 20 Jul 2000 09:09:25 -0700 (PDT) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) with ESMTP id JAA23953; Thu, 20 Jul 2000 09:09:23 -0700 (PDT) Message-ID: <39772434.6EFCC1D1@cup.hp.com> Date: Thu, 20 Jul 2000 09:09:24 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Alexander Langer Cc: current@FreeBSD.ORG Subject: Re: cross-building broken? References: <20000720123808.A78907@cichlids.cichlids.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Langer wrote: > > cc -O -pipe -I/usr/src/lib/libmd > -I/usr/obj/alpha/usr/src/i386/usr/include -c /usr/src/lib/libmd/md2c.c > -o md2c.o > /usr/src/lib/libmd/md2c.c: In function `MD2Final': > /usr/src/lib/libmd/md2c.c:167: internal error--unrecognizable insn: > (insn 26 24 28 (set (reg:DI 79) > (and:DI (plus:DI (reg/v:DI 69) > (const_int 586478694938416944 [0x823974408239730])) > (const_int -8 [0xfffffffffffffff8]))) -1 (insn_list 4 > (nil)) > (nil)) This is a known problem; at least to me. We have this since the early days of cross-compiling. I have a patch on my side that worked with the previous gcc. I applied this patch with the new gcc and it still fails. I have to find the bug and send a patch to cygnus... If you're feeling lucky, you can download the patch I have on my webpage (http://people.freebsd.org/~marcel) and start from their. I suspect (or rather hope) it's as simple as providing some prototypes to get it to work again. That was how I fixed it before... Looking at the failure, I think it's just that (ie a lack of prototype causes gcc to assume an argument is int (which is 32-bits for us) and creates the call-site as such, but while compiling the function itself it creates a 64-bit integral for that argument)... HTH, -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 20 10:50:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id DB23A37B58D for ; Thu, 20 Jul 2000 10:50:21 -0700 (PDT) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id TAA78035; Thu, 20 Jul 2000 19:50:16 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id TAA55688; Thu, 20 Jul 2000 19:50:04 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Thu, 20 Jul 2000 19:50:03 +0200 (CEST) From: Leif Neland To: Doug White Cc: freebsd-current@FreeBSD.ORG Subject: Re: No /boot/loader In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 20 Jul 2000, Doug White wrote: > Your boot disk is now *required* (or will be very very soon) to have a > proper slice table in -CURRENT; dedicated disks are deprecated in order to > get a smarter boot0. > So dedicated disks are to be reformatted? Just to be on the safe side, is there a simple way to see if a disk is dedicated? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 20 11: 3:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from aesthetic.detachment.org (agcess.com [208.11.244.15]) by hub.freebsd.org (Postfix) with ESMTP id B0CE637B7A2; Thu, 20 Jul 2000 11:03:32 -0700 (PDT) (envelope-from tstromberg@rtci.com) Received: from rtci.com (helixblue@localhost [127.0.0.1]) by aesthetic.detachment.org (8.9.3/8.9.3) with ESMTP id OAA86498; Thu, 20 Jul 2000 14:03:07 -0400 (EDT) (envelope-from tstromberg@rtci.com) Message-ID: <39773ED9.B05E0EBE@rtci.com> Date: Thu, 20 Jul 2000 14:03:05 -0400 From: Thomas Stromberg X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Doug White Cc: Doug Barton , Mike Smith , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: No /boot/loader (dangerously dedicated) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White wrote: > > On Wed, 19 Jul 2000, Doug Barton wrote: > > As for geometry, I tried both with and without "dangerously > > dedicated." My understanding was that if I used the dos partition entry > > method that we should be able to pick up the geometry correctly, but > > should I try the old dos fdisk trick as well? Also, would the adaptec > > setting to translate >1G be affecting this? It's on currently, which it is > > on all my other motherboards of similar vintage. > > Your boot disk is now *required* (or will be very very soon) to have a > proper slice table in -CURRENT; dedicated disks are deprecated in order to > get a smarter boot0. > > Speaking of boot0 you might try using boot0cfg to force packet mode. Even though this does not directly affect -STABLE right now (I hope?), I think it'd probably be a good idea to maybe turn off the dangerously dedicated option in sysinstall (or at least turn the question off). At least in -CURRENT if nowhere else, so no one shoots themself in the foot. This would defititely help out at work, as I would no longer get the question from all of our users during the install "Should I be dedicated or not?" -- ------------------------------------------------------------------------ thomas r. stromberg tstromberg@rtci.com senior systems administrator http://www.afterthought.org/ research triangle commerce, inc. 1.919.657.1317 bless(\$Perl++); # the power to hack. http://www.perl.com/ #include /* the power to serve. http://www.freebsd.org/ */ ------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 20 11:58:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id C2FC237BB5E for ; Thu, 20 Jul 2000 11:58:50 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA99372; Thu, 20 Jul 2000 12:58:48 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA92648; Thu, 20 Jul 2000 12:58:43 -0600 (MDT) Message-Id: <200007201858.MAA92648@harmony.village.org> To: Leif Neland Subject: Re: No /boot/loader Cc: Doug White , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 20 Jul 2000 19:50:03 +0200." References: Date: Thu, 20 Jul 2000 12:58:43 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Leif Neland writes: : Just to be on the safe side, is there a simple way to see if a disk is : dedicated? fdisk -s ad0 If there's a slice table, then it will give you a summary report of the slices. If not it will report an error (and maybe give you a faked up listing). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 20 13:49:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 4B5A437B5B5; Thu, 20 Jul 2000 13:49:05 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.7/nospam) with UUCP id WAA10823; Thu, 20 Jul 2000 22:48:50 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id EE7C08865; Thu, 20 Jul 2000 22:45:05 +0200 (CEST) Date: Thu, 20 Jul 2000 22:45:05 +0200 From: Ollivier Robert To: freebsd-current@freebsd.org Cc: fenner@freebsd.org Subject: Re: trafshow doesn't work? Message-ID: <20000720224505.A87492@keltia.freenix.fr> Mail-Followup-To: freebsd-current@freebsd.org, fenner@freebsd.org References: <20000719165133.C511@samxie.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from kris@FreeBSD.org on Wed, Jul 19, 2000 at 02:06:48PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Bill Fenner added as "maintainer" of libpcap/tcpdump ] According to Kris Kennaway: > Fallout from the malloc.conf changes. tcpdump has the same bug. I think^W'm sure the bug is in libpcap though as several libpcap applications fail with the same error (tcpdump, ntop, trafshow). The problem is inside pcap_lookupdev(), "buf" is used to store interface data, then freed then the buffer is used again : -=-=- for (;;) { buf = malloc (buf_size); if (buf == NULL) { close (fd); (void)sprintf(errbuf, "out of memory"); return (NULL); } ifc.ifc_len = buf_size; ifc.ifc_buf = buf; memset (buf, 0, buf_size); ... for (cp = ifrp->ifr_name; !isdigit(*cp); ++cp) continue; n = atoi(cp); if (n < minunit) { minunit = n; mp = ifrp; } } free(buf); <<<<<<< (void)close(fd); if (mp == NULL) { (void)strcpy(errbuf, "no suitable device found"); return (NULL); } (void)strncpy(device, mp->ifr_name, sizeof(device) - 1); <<<<<<< device[sizeof(device) - 1] = '\0'; return (device); -=-=- The last free(buf) has filled "buf" with 0xd0 so "mp" points to the same area. If anyone has the address of the mailing list for libpcap, please send this patch. I won't commit it as it would get the file out of the vendor branch. Index: inet.c =================================================================== RCS file: /spare/FreeBSD-current/src/contrib/libpcap/inet.c,v retrieving revision 1.1.1.4 diff -u -2 -I.*$Id:.* -r1.1.1.4 inet.c --- inet.c 2000/01/30 00:32:41 1.1.1.4 +++ inet.c 2000/07/20 20:41:36 @@ -174,7 +174,7 @@ } } - free(buf); (void)close(fd); if (mp == NULL) { + free(buf); (void)strcpy(errbuf, "no suitable device found"); return (NULL); @@ -183,4 +183,5 @@ (void)strncpy(device, mp->ifr_name, sizeof(device) - 1); device[sizeof(device) - 1] = '\0'; + free(buf); return (device); } -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 20 13:58: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id 8A59237B82D; Thu, 20 Jul 2000 13:58:02 -0700 (PDT) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id 4B1664CE37; Thu, 20 Jul 2000 16:57:56 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id QAA20097; Thu, 20 Jul 2000 16:57:55 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id NAA03574; Thu, 20 Jul 2000 13:57:55 -0700 (PDT) Message-Id: <200007202057.NAA03574@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: roberto@keltia.freenix.fr Subject: Re: trafshow doesn't work? Cc: freebsd-current@freebsd.org, fenner@freebsd.org References: <20000719165133.C511@samxie.cl.msu.edu> <20000720224505.A87492@keltia.freenix.fr> Date: Thu, 20 Jul 2000 13:57:54 -0700 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I guess this is http://www.tcpdump.org/cgi-bin/cvsweb/libpcap/inet.c?r1=1.25&r2=1.26 The easiest thing to do is probably cvs import their rev 1.26 of inet.c . Shall I do this? Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 20 14:40:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id 63BE637B67E for ; Thu, 20 Jul 2000 14:40:14 -0700 (PDT) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id 8394D4CE0F; Thu, 20 Jul 2000 17:40:04 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id RAA22165; Thu, 20 Jul 2000 17:40:03 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id OAA04055; Thu, 20 Jul 2000 14:40:02 -0700 (PDT) Message-Id: <200007202140.OAA04055@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: sam@samxie.cl.msu.edu Subject: Re: trafshow doesn't work? Cc: freebsd-current@freebsd.org Date: Thu, 20 Jul 2000 14:40:02 -0700 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This should be fixed by rev 1.1.1.5 of src/contrib/libpcap/inet.c . Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 20 14:56:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 1953737C185 for ; Thu, 20 Jul 2000 14:56:22 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.7/nospam) with UUCP id XAA11882; Thu, 20 Jul 2000 23:04:40 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id D481A8865; Thu, 20 Jul 2000 23:03:35 +0200 (CEST) Date: Thu, 20 Jul 2000 23:03:35 +0200 From: Ollivier Robert To: Bill Fenner Cc: freebsd-current@freebsd.org Subject: Re: trafshow doesn't work? Message-ID: <20000720230335.A88500@keltia.freenix.fr> Mail-Followup-To: Bill Fenner , freebsd-current@freebsd.org References: <20000719165133.C511@samxie.cl.msu.edu> <20000720224505.A87492@keltia.freenix.fr> <200007202057.NAA03574@windsor.research.att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007202057.NAA03574@windsor.research.att.com>; from fenner@research.att.com on Thu, Jul 20, 2000 at 01:57:54PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Bill Fenner: > http://www.tcpdump.org/cgi-bin/cvsweb/libpcap/inet.c?r1=1.25&r2=1.26 Yes, that's almost my patch, I swear I didn't know :) > The easiest thing to do is probably cvs import their rev 1.26 of > inet.c . Shall I do this? That's probably the best, thanks! -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 20 15: 5:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id A2CC337B7F3 for ; Thu, 20 Jul 2000 15:05:27 -0700 (PDT) (envelope-from jhb@pike.osd.bsdi.com) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id PAA29795; Thu, 20 Jul 2000 15:05:08 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200007202205.PAA29795@pike.osd.bsdi.com> Subject: Re: No /boot/loader In-Reply-To: from Doug White at "Jul 20, 2000 08:46:36 am" To: Doug White Date: Thu, 20 Jul 2000 15:05:08 -0700 (PDT) Cc: freebsd-current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 19 Jul 2000, Doug Barton wrote: > > > > Disk geometry stuffup, or a 'real' disk error. > > > > Well, I put my money on real disk error, but only because it > > vindicates my position that we shouldn't have switched to this new kind of > > disk in the first place. > > > > As for geometry, I tried both with and without "dangerously > > dedicated." My understanding was that if I used the dos partition entry > > method that we should be able to pick up the geometry correctly, but > > should I try the old dos fdisk trick as well? Also, would the adaptec > > setting to translate >1G be affecting this? It's on currently, which it is > > on all my other motherboards of similar vintage. > > Your boot disk is now *required* (or will be very very soon) to have a > proper slice table in -CURRENT; dedicated disks are deprecated in order to > get a smarter boot0. > > Speaking of boot0 you might try using boot0cfg to force packet mode. > > Doug White | FreeBSD: The Power to Serve > dwhite@resnet.uoregon.edu | www.FreeBSD.org As the author of the new parts of boot0: "No". You are not required to have a proper slice table for -CURRENT. It is recommended, as you have to have it to use boot0, but you couldn't use the old boot0 with dedicated disks, either. Basically, only use dedicated modes _if_ the non-dedicated mode does not work. Also, if that happens, please let us know it is broke so we can fix it. Thanks. -- John Baldwin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 20 18:11:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 22DEC37B81E for ; Thu, 20 Jul 2000 18:11:32 -0700 (PDT) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id DAA25002; Fri, 21 Jul 2000 03:11:17 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id BAA45522; Fri, 21 Jul 2000 01:36:11 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Fri, 21 Jul 2000 01:36:11 +0200 (CEST) From: Leif Neland To: Warner Losh Cc: Doug White , freebsd-current@FreeBSD.ORG Subject: Re: No /boot/loader In-Reply-To: <200007201858.MAA92648@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 20 Jul 2000, Warner Losh wrote: > In message Leif Neland writes: > : Just to be on the safe side, is there a simple way to see if a disk is > : dedicated? > > fdisk -s ad0 > > If there's a slice table, then it will give you a summary report of > the slices. If not it will report an error (and maybe give you a > faked up listing). I have windows partitions on my disks here, so they can't be dedicated. fdisk -s ad[0,1,2] all reports invalid fdisk partition found. Does that mean that a dedicated disk has a slice table, a normal doesn't? Confused... Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 20 22:37: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 5CA3A37B5B4 for ; Thu, 20 Jul 2000 22:37:06 -0700 (PDT) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id HAA54789 for freebsd-current@freebsd.org; Fri, 21 Jul 2000 07:37:04 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id HAA15487 for ; Fri, 21 Jul 2000 07:36:46 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Fri, 21 Jul 2000 07:36:46 +0200 (CEST) From: Leif Neland To: freebsd-current@freebsd.org Subject: make kernel breakage: if_tap Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just cvsupped: Script started on Fri Jul 21 07:12:56 2000 CEST gina/usr/src/sys/compile/GINA # make clean ... ===> if_tap cd: can't cd to /usr/src/sys/modules/if_tap *** Error code 2 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/src/sys/compile/GINA. gina/usr/src/sys/compile/GINA # make depend ... ===> if_tap cd: can't cd to /usr/src/sys/modules/if_tap *** Error code 2 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/src/sys/compile/GINA. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 20 23: 4:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from evil.2y.net (ztown1-2-223.adsl.one.net [216.23.20.223]) by hub.freebsd.org (Postfix) with ESMTP id D20B337B658 for ; Thu, 20 Jul 2000 23:04:26 -0700 (PDT) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id CAA37303 for current@freebsd.org; Fri, 21 Jul 2000 02:12:28 -0400 (EDT) (envelope-from cokane) Date: Fri, 21 Jul 2000 02:12:28 -0400 From: Coleman Kane To: current@freebsd.org Subject: Voodoo cards Message-ID: <20000721021228.A37186@cokane.yi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently studied the tech docs for the Voodoo3 and Voodoo Banshee and committed a patch that might (hopefully) fix the trouble mixing the /dev/3dfx driver with XFree86 4.0. Could someone with a Voodoo3 or BAnshee try it out and give me dmesg and X output and an overall review of what occurred? I only have a voodoo2 and it works fine for me, though I'm not sharing the memory with X since it is a seperate card. -- Coleman Kane President, UC Free O.S. Users Group - http://pohl.ececs.uc.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 20 23:32:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 45AD837B60E for ; Thu, 20 Jul 2000 23:32:44 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA02161; Fri, 21 Jul 2000 00:32:40 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA97937; Fri, 21 Jul 2000 00:32:35 -0600 (MDT) Message-Id: <200007210632.AAA97937@harmony.village.org> To: Leif Neland Subject: Re: No /boot/loader Cc: Doug White , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 21 Jul 2000 01:36:11 +0200." References: Date: Fri, 21 Jul 2000 00:32:35 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Leif Neland writes: : : : On Thu, 20 Jul 2000, Warner Losh wrote: : : > In message Leif Neland writes: : > : Just to be on the safe side, is there a simple way to see if a disk is : > : dedicated? : > : > fdisk -s ad0 : > : > If there's a slice table, then it will give you a summary report of : > the slices. If not it will report an error (and maybe give you a : > faked up listing). : : I have windows partitions on my disks here, so they can't be dedicated. : fdisk -s ad[0,1,2] all reports : invalid fdisk partition found. Did you do that as root? All of my windows disks report valid partitions. From my sever: % fdisk -s da0 /dev/da0: 2231 cyl 255 hd 63 sec Part Start Size Type Flags 4: 1 35841014 0xa5 0x80 From my laptop: fdisk -s ad0 /dev/ad0: 559 cyl 240 hd 63 sec Part Start Size Type Flags 1: 63 2766897 0x0b 0x00 2: 2766960 5397840 0xa5 0x80 4: 8164800 272160 0xa0 0x00 I'm in group operator, so I can read the disks on my own. The part type 0xa0 is for the suspend to disk partition in my VAIO. : Does that mean that a dedicated disk has a slice table, a normal doesn't? No. That's backwards. A dedicated disk has no slice table (a dangerously dedicated disk, that is), and a "normal" one does have a slice table. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 20 23:53:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by hub.freebsd.org (Postfix) with ESMTP id E684D37B67C for ; Thu, 20 Jul 2000 23:53:21 -0700 (PDT) (envelope-from gdinolt@pacbell.net) Received: from pacbell.net ([63.199.31.55]) by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FY100JMTC8BMY@mta5.snfc21.pbi.net> for freebsd-current@freebsd.org; Thu, 20 Jul 2000 23:48:11 -0700 (PDT) Date: Thu, 20 Jul 2000 23:48:52 -0700 From: "George W. Dinolt" Subject: (noperiph:ahc0:0:-1:-1): ... error To: freebsd-current@freebsd.org Message-id: <3977F254.382B80D7@pacbell.net> MIME-version: 1.0 X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.0-20000214-CURRENT i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying to run a recent (as of today) and am seeing the following error when I try to boot:: (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. panic: Bogus resid sgptr value 0xbd68609 (I copied this from the console after the boot failure, there may be minor mistakes.) This started happening when I started compiling kernels built from sources cvsuped around Jul 18. I am not sure what is causing these messages. The "noperiph" message appears to come from xpt_print_path in /usr/src/sys/cam/cam_xpt.c while the panic seems to be written by ahc_calc_residual in /usr/src/sys/dev/aic7xxx/aic7xxx.c. From a quick look at the code, the problem is not directly in the code pointed to by the messages. I have an Adaptec 2940UW. A much older kernel reports it as with aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs. The Bios on the board is version 2.20.0 I have 4 drives and a UMAX scanner connected to the bus. More details available if needed. I am hopeful that someone will recognize the problem. Regards, George Dinolt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 20 23:53:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 1C49337B67C for ; Thu, 20 Jul 2000 23:53:36 -0700 (PDT) (envelope-from jhb@pike.osd.bsdi.com) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id XAA42478; Thu, 20 Jul 2000 23:53:08 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200007210653.XAA42478@pike.osd.bsdi.com> Subject: Re: No /boot/loader In-Reply-To: <200007210632.AAA97937@harmony.village.org> from Warner Losh at "Jul 21, 2000 00:32:35 am" To: Warner Losh Date: Thu, 20 Jul 2000 23:53:08 -0700 (PDT) Cc: dwhite@resnet.uoregon.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message Leif Neland writes: > : > : > : On Thu, 20 Jul 2000, Warner Losh wrote: > : > : > In message Leif Neland writes: > : > : Just to be on the safe side, is there a simple way to see if a disk is > : > : dedicated? > : > > : > fdisk -s ad0 > : > > : > If there's a slice table, then it will give you a summary report of > : > the slices. If not it will report an error (and maybe give you a > : > faked up listing). > : > : I have windows partitions on my disks here, so they can't be dedicated. > : fdisk -s ad[0,1,2] all reports > : invalid fdisk partition found. > > Did you do that as root? All of my windows disks report valid > partitions. > > >From my sever: > % fdisk -s da0 > /dev/da0: 2231 cyl 255 hd 63 sec > Part Start Size Type Flags > 4: 1 35841014 0xa5 0x80 > > >From my laptop: > fdisk -s ad0 > /dev/ad0: 559 cyl 240 hd 63 sec > Part Start Size Type Flags > 1: 63 2766897 0x0b 0x00 > 2: 2766960 5397840 0xa5 0x80 > 4: 8164800 272160 0xa0 0x00 > > I'm in group operator, so I can read the disks on my own. The part > type 0xa0 is for the suspend to disk partition in my VAIO. > > : Does that mean that a dedicated disk has a slice table, a normal doesn't? > > No. That's backwards. A dedicated disk has no slice table (a > dangerously dedicated disk, that is), and a "normal" one does have a > slice table. No, that's wrong, too. A normal disk has a proper slice table (slices start on cylinder boundaries and do not contain the MBR, thus leaving the first cylinder unused). A truly dedicated disk (disklabel auto ) uses a slightly improper slice table (slices still start and end on cylinder boundaries and even span the entire disk, however, the only slice contains the MBR, in fact, we end up writing boot1 into the MBR). A dangerously dedicated disk uses a fake, completely bogus slice table that has no relation at all to the drive's geometry. As with truly dedicated mode, the MBR is actually contained in boot1, but in dangerously dedicated mode we use the slice table hard-coded into the boot code. This slice table has 1 slice which is 50000 blocks long, or 25000k. The rest of the disk is marked as unused even though it is, in fact, used. The fact that it works at all is due to brokenness on our part (we don't check that partitions in a disklabel fit in the parent slice) and also results in several hacks in various portions of the code where we have to check for such bogusness and work around it. I'm not a very big fan of the dedicated modes if you couldn't tell. :) > Warner -- John Baldwin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 1:58:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 5887F37B79F for ; Fri, 21 Jul 2000 01:58:18 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (qmail 7565 invoked from network); 21 Jul 2000 08:58:03 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 21 Jul 2000 08:58:03 -0000 Date: Fri, 21 Jul 2000 18:58:05 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: John Baldwin Cc: Warner Losh , dwhite@resnet.uoregon.edu, freebsd-current@FreeBSD.ORG Subject: Re: No /boot/loader In-Reply-To: <200007210653.XAA42478@pike.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 20 Jul 2000, John Baldwin wrote: > No, that's wrong, too. A normal disk has a proper slice table (slices start > on cylinder boundaries and do not contain the MBR, thus leaving the first track > cylinder unused). A truly dedicated disk (disklabel auto ) uses a track > ... > at all to the drive's geometry. As with truly dedicated mode, the MBR is > actually contained in boot1, but in dangerously dedicated mode we use the > slice table hard-coded into the boot code. This slice table has 1 slice > which is 50000 blocks long, or 25000k. The rest of the disk is marked as > unused even though it is, in fact, used. The fact that it works at all is > due to brokenness on our part (we don't check that partitions in a disklabel > fit in the parent slice) and also results in several hacks in various portions > of the code where we have to check for such bogusness and work around it. No, that's wrong too :-) . We a lot of checking that partitions in a disklabel fit in the parent slice. We clip partitions that don't fit in various ways for backwards compatibility. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 3: 4:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 0722037B6BA for ; Fri, 21 Jul 2000 03:04:52 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id UAA07297; Fri, 21 Jul 2000 20:04:18 +1000 Date: Fri, 21 Jul 2000 20:04:20 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: John Polstra Cc: hm@hcs.de, current@FreeBSD.ORG Subject: Re: kernel compile failure without -O option In-Reply-To: <200007200231.TAA15177@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jul 2000, John Polstra wrote: > In article <20000719144614.7FE52483D@hcswork.hcs.de>, > Hellmuth Michaelis wrote: > > > > In the process of tracing down the problem of the kernel panic when booting > > a kernel with pcvt enabled, i tried to compile a kernel without the -O > > option to gcc and got this compile failure (sources from 18.7.2000 9:00 MET): > > > > cc -c -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > > -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include > > -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 > > -fomit-frame-pointer ../../i386/i386/atomic.c > > In file included from ../../i386/i386/atomic.c:47: > > machine/atomic.h: In function `atomic_set_char': > > machine/atomic.h:106: inconsistent operand constraints in an `asm' > > machine/atomic.h: In function `atomic_clear_char': > > machine/atomic.h:107: inconsistent operand constraints in an `asm' > [...] > > I have seen that same problem recently in a slightly different > context. After staring at the code for a very long time, I could > only conclude that the problem was a bug in gcc. Me too :-). I didn't reply to John's private mail about this (sorry), partly because the problem seemed to be an old one that I wasn't able to solve before. The "0" construct apparently doesn't work even with -O for gcc <= 2.8, so atomic.h is ifdefed to not use it for non-current gcc's, although it is strictly required for the input-output operands in atomic.h. There is also a problem with gcc's handling of volatile objects in atomic.h (it just pessimizes them). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 3:45:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id BC22037B859; Fri, 21 Jul 2000 03:45:08 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id DAA17660; Fri, 21 Jul 2000 03:45:08 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 21 Jul 2000 03:45:08 -0700 (PDT) From: Kris Kennaway To: Dan Moschuk Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <20000718104134.C1221@spirit.jaded.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jul 2000, Dan Moschuk wrote: > Well, how many other OSs out there allow /dev/random to be written to? FreeBSD, OpenBSD, NetBSD, Linux... Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 3:46:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id D43F837BAF4; Fri, 21 Jul 2000 03:46:31 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id DAA18360; Fri, 21 Jul 2000 03:46:31 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 21 Jul 2000 03:46:31 -0700 (PDT) From: Kris Kennaway To: Dan Moschuk Cc: Mark Murray , current@freebsd.org Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <20000718103729.A1221@spirit.jaded.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jul 2000, Dan Moschuk wrote: > | Gotcha - fix coming; I need to stash some randomness at shutdown time, and > | use that to reseed the RNG at reboot time. > > What about saving the state of the RNG and re-reading it on bootup? That > will allow Yarrow to continue right where it left off. :-) That's a bad thing. You don't want someone to be able to examine the exact PRNG state at next boot by looking at your hard disk after the machine has shut down. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 3:53:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id F119637B8E2; Fri, 21 Jul 2000 03:53:33 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id DAA27222; Fri, 21 Jul 2000 03:53:33 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 21 Jul 2000 03:53:31 -0700 (PDT) From: Kris Kennaway To: George Michaelson Cc: Paul Herman , Poul-Henning Kamp , Vadim Belman , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <16536.963966737@dstc.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jul 2000, George Michaelson wrote: > Where for instance do these ideas fit into the models proposed in > > draft-eastlake-randomness2-00.txt > > or the proceeding RFC? Well, Yarrow is an algorithm which is intended to provide a robust and secure source of cryptographic-strength random numbers (i.e. suitable for the purposes described in that draft). I dont think it's specifically mentioned there, but it's defined and described in a series of papers by Schneier et al. available on www.counterpane.com. As for the other parts of that document, it looks like there might be some useful discussion of entropy sources on commodity PC hardware and the issues with sampling such sources - I'll have to read it in more detail (and suggest other interested participants in this discussion also do so, along with the Yarrow papers). Thanks for pointing it out! Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 4:48:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat205.151.mpoweredpc.net [142.177.205.151]) by hub.freebsd.org (Postfix) with ESMTP id 46AC137B5F5 for ; Fri, 21 Jul 2000 04:48:13 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id IAA05099 for ; Fri, 21 Jul 2000 08:46:16 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 21 Jul 2000 08:46:16 -0300 (ADT) From: The Hermit Hacker To: freebsd-current@freebsd.org Subject: RSA problem with SSH ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just upgraded to the newest -current, and now can't use SSH: ssh: no RSA support in libssl and libcrypto. See ssl(8). Tried to read the 'ssl(8)' man page, but it comes back as: > man 8 ssl No entry for ssl in section 8 of the manual > man ssl No manual entry for ssl > Did mergemaster and saw the 'MAKE_RSAINTL' setting in /etc/defaults/make.conf, so did that and did a new 'make world' ... Even saw the note about /usr/ports/security/rsaref and installed that, no difference ... Read through /usr/src/UPDATING and can't seem to find anything that applies other then the mentioning of RANDOMDEV, which I have configured in ... So ... what am I missing that this missing man page seems to be indicated as the answer? :) Thanks ... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 4:55:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from jarrow.dev.nanoteq.co.za (jarrow.dev.nanoteq.co.za [196.7.114.30]) by hub.freebsd.org (Postfix) with ESMTP id A21C037B515 for ; Fri, 21 Jul 2000 04:55:21 -0700 (PDT) (envelope-from rbezuide@jarrow.dev.nanoteq.co.za) Received: (from rbezuide@localhost) by jarrow.dev.nanoteq.co.za (8.9.3/8.9.3) id NAA72184; Fri, 21 Jul 2000 13:53:13 +0200 (SAST) (envelope-from rbezuide) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 21 Jul 2000 13:53:12 +0200 (SAST) Reply-To: rbezuide@oskar.nanoteq.co.za From: Reinier Bezuidenhout To: The Hermit Hacker Subject: RE: RSA problem with SSH ... Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I had the same problem ... but in my case I did not have the RANDOMDEV compiled in ... so I loaded the kld and whala ... it worked ... Try loading the KLD .. also check that the lib's actually do include the RSA stuff (nm | grep RSA ) might help. Reinier On 21-Jul-00 The Hermit Hacker wrote: > > Just upgraded to the newest -current, and now can't use SSH: > > ssh: no RSA support in libssl and libcrypto. See ssl(8). > > Tried to read the 'ssl(8)' man page, but it comes back as: > >> man 8 ssl > No entry for ssl in section 8 of the manual >> man ssl > No manual entry for ssl >> > > Did mergemaster and saw the 'MAKE_RSAINTL' setting in > /etc/defaults/make.conf, so did that and did a new 'make world' ... > > Even saw the note about /usr/ports/security/rsaref and installed that, no > difference ... > > Read through /usr/src/UPDATING and can't seem to find anything that > applies other then the mentioning of RANDOMDEV, which I have configured in > ... > > So ... what am I missing that this missing man page seems to be indicated > as the answer? :) > > Thanks ... > > Marc G. Fournier ICQ#7615664 IRC Nick: > Scrappy > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: > scrappy@{freebsd|postgresql}.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ################################################################### # # # R.N. Bezuidenhout NetSeq Firewall # # rbezuide@oskar.nanoteq.co.za http://www.nanoteq.co.za # # # ################################################################### ---------------------------------- Date: 21-Jul-00 Time: 13:50:54 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 4:56:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout2.silyn-tek.de (mout2.silyn-tek.de [194.25.165.70]) by hub.freebsd.org (Postfix) with ESMTP id E304937B515 for ; Fri, 21 Jul 2000 04:56:36 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from [192.168.32.33] (helo=mx1.silyn-tek.de) by mout2.silyn-tek.de with esmtp (Exim 3.13 #1) id 13FbPs-00040c-00; Fri, 21 Jul 2000 13:56:32 +0200 Received: from p3e9d38e7.dip0.t-ipconnect.de ([62.157.56.231] helo=neutron.cichlids.com) by mx1.silyn-tek.de with esmtp (Exim 3.13 #1) id 13FbPq-0005FC-00; Fri, 21 Jul 2000 13:56:30 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id B3853AB91; Fri, 21 Jul 2000 13:58:15 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id CD67E14ABB; Fri, 21 Jul 2000 13:56:30 +0200 (CEST) Date: Fri, 21 Jul 2000 13:56:30 +0200 To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: RSA problem with SSH ... Message-ID: <20000721135630.A12383@cichlids.cichlids.com> Mail-Followup-To: The Hermit Hacker , freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from scrappy@hub.org on Fri, Jul 21, 2000 at 08:46:16AM -0300 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. From: alex@big.endian.de (Alexander Langer) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake The Hermit Hacker (scrappy@hub.org): > Just upgraded to the newest -current, and now can't use SSH: > ssh: no RSA support in libssl and libcrypto. See ssl(8). options RANDOMDEV into kernel, or load randomdev.ko That solved it for me (though you mentioned it). I'M USA_RESIDENT=NO, though. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 5: 9:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat193.142.mpoweredpc.net [142.177.193.142]) by hub.freebsd.org (Postfix) with ESMTP id F17A437B76D for ; Fri, 21 Jul 2000 05:09:02 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id JAA24765; Fri, 21 Jul 2000 09:06:54 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 21 Jul 2000 09:06:54 -0300 (ADT) From: The Hermit Hacker To: Alexander Langer Cc: freebsd-current@FreeBSD.ORG Subject: Re: RSA problem with SSH ... In-Reply-To: <20000721135630.A12383@cichlids.cichlids.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Great ... I added RANDOMDEV to the wrong kernel config file :( Thanks, fixed now ... On Fri, 21 Jul 2000, Alexander Langer wrote: > Thus spake The Hermit Hacker (scrappy@hub.org): > > > Just upgraded to the newest -current, and now can't use SSH: > > ssh: no RSA support in libssl and libcrypto. See ssl(8). > > options RANDOMDEV into kernel, or load randomdev.ko > > That solved it for me (though you mentioned it). > > I'M USA_RESIDENT=NO, though. > > Alex > -- > cat: /home/alex/.sig: No such file or directory > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 5:54: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (markm.ops.uunet.co.za [196.31.2.167]) by hub.freebsd.org (Postfix) with ESMTP id 7C7B537B97D; Fri, 21 Jul 2000 05:53:56 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id OAA00377; Fri, 21 Jul 2000 14:53:57 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007211253.OAA00377@grimreaper.grondar.za> To: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: In-Reply-To: ; from Kris Kennaway "Fri, 21 Jul 2000 03:46:31 MST." Date: Fri, 21 Jul 2000 14:53:57 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What about saving the state of the RNG and re-reading it on bootup? That > > will allow Yarrow to continue right where it left off. :-) > > That's a bad thing. You don't want someone to be able to examine the exact > PRNG state at next boot by looking at your hard disk after the machine has > shut down. It is a Yarrow-mandated procedure. Please read the Yarrow paper. If they can do that, they have either the console (==root) or they have root. Either way, who cares what they know about your machine, they have the whole darn thing :-O. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 7: 4:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id B8BC437B9F4 for ; Fri, 21 Jul 2000 07:04:12 -0700 (PDT) (envelope-from roberto@eurocontrol.fr) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.51.214]) by matrix.eurocontrol.fr (Postfix) with ESMTP id 9A07B5A9B for ; Fri, 21 Jul 2000 16:04:11 +0200 (CEST) Received: by caerdonn.eurocontrol.fr (Postfix, from userid 1193) id A845D4E5F; Fri, 21 Jul 2000 16:04:10 +0200 (CEST) Date: Fri, 21 Jul 2000 16:04:10 +0200 From: Ollivier Robert To: FreeBSD Current Users' list Subject: Current broken in ncurses ? Message-ID: <20000721160410.B44378@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Am I the only one with this ? cc -O -pipe -I. -I/src/src/lib/libncurses -I/src/src/lib/libncurses/../../contrib/ncurses/ncurses -I/src/src/lib/libncurses/../../contrib/ncurses/include -Wall -DFREEBSD_NATIVE -DNDEBUG -DHAVE_CONFIG_H -DTERMIOS -I/net/nas/roberto/sidhe/src/src/i386/usr/include -c /src/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/comp_scan.c -o comp_scan.o /src/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/comp_scan.c: In function `_nc_get_token': /src/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/comp_scan.c:184: `_nc_disable_period' undeclared (first use in this function) /src/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/comp_scan.c:184: (Each undeclared identifier is reported only once /src/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/comp_scan.c:184: for each function it appears in.) *** Error code 1 Stop in /src/src/lib/libncurses. -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- Ollivier.Robert@eurocontrol.fr The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 7:19: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id 7F57037BB34 for ; Fri, 21 Jul 2000 07:19:01 -0700 (PDT) (envelope-from roberto@eurocontrol.fr) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.51.214]) by matrix.eurocontrol.fr (Postfix) with ESMTP id 8D42A5A78 for ; Fri, 21 Jul 2000 16:19:00 +0200 (CEST) Received: by caerdonn.eurocontrol.fr (Postfix, from userid 1193) id 7C4D94E5F; Fri, 21 Jul 2000 16:19:00 +0200 (CEST) Date: Fri, 21 Jul 2000 16:19:00 +0200 From: Ollivier Robert To: FreeBSD Current Users' list Subject: ncurses breakage Message-ID: <20000721161900.C44378@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Never mind. cvs wasn't apparently able to "cvs update" correctly and I was using the old Makefile. Weird. -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- Ollivier.Robert@eurocontrol.fr The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 7:43:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by hub.freebsd.org (Postfix) with ESMTP id 0DED437BE1B for ; Fri, 21 Jul 2000 07:42:54 -0700 (PDT) (envelope-from ust@cert.siemens.de) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer goliath.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.10.1/8.10.1) with ESMTP id e6LEgpH21882; Fri, 21 Jul 2000 16:42:52 +0200 (MET DST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail1.siemens.de (8.10.1/8.10.1) with ESMTP id e6LEgp318797; Fri, 21 Jul 2000 16:42:51 +0200 (MET DST) Received: from alaska.cert.siemens.de (reims.mchp.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.10.2/8.10.2/Siemens CERT [ $Revision: 1.8 ]) with ESMTP id e6LEgoe07352; Fri, 21 Jul 2000 16:42:51 +0200 (CEST) Received: (from ust@localhost) by alaska.cert.siemens.de (8.10.2/8.10.2/alaska [ $Revision: 1.4 ]) id e6LEgo431934; Fri, 21 Jul 2000 14:42:50 GMT Date: Fri, 21 Jul 2000 16:42:50 +0200 From: Udo Schweigert To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: make kernel breakage: if_tap Message-ID: <20000721164250.A31883@alaska.cert.siemens.de> Mail-Followup-To: Leif Neland , freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from leifn@neland.dk on Fri, Jul 21, 2000 at 07:36:46AM +0200 X-Operating-System: FreeBSD 4.1-RC Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 21, 2000 at 07:36:46 +0200, Leif Neland wrote: > Just cvsupped: > > Script started on Fri Jul 21 07:12:56 2000 CEST > gina/usr/src/sys/compile/GINA # make clean > ... > ===> if_tap > cd: can't cd to /usr/src/sys/modules/if_tap Here too. src/sys/modules/if_tap is a completely empty dir (in the cvs tree). Seems a Makefile is missing here (or it should not be tried to build a module). Regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT | Fax : +49 89 636 41166 D-81730 Muenchen / Germany | email : ust@cert.siemens.de PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 8:58:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from spirit.jaded.net (shortbus.jaded.net [216.94.132.8]) by hub.freebsd.org (Postfix) with ESMTP id 8DC8B37BCAC; Fri, 21 Jul 2000 08:58:51 -0700 (PDT) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id LAA00864; Fri, 21 Jul 2000 11:58:46 -0400 (EDT) (envelope-from dan) Date: Fri, 21 Jul 2000 11:58:46 -0400 From: Dan Moschuk To: Kris Kennaway Cc: Mark Murray , current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak Message-ID: <20000721115846.C489@spirit.jaded.net> References: <20000718103729.A1221@spirit.jaded.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from kris@FreeBSD.org on Fri, Jul 21, 2000 at 03:46:31AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | > | Gotcha - fix coming; I need to stash some randomness at shutdown time, and | > | use that to reseed the RNG at reboot time. | > | > What about saving the state of the RNG and re-reading it on bootup? That | > will allow Yarrow to continue right where it left off. :-) | | That's a bad thing. You don't want someone to be able to examine the exact | PRNG state at next boot by looking at your hard disk after the machine has | shut down. I don't see how. If the attacker has physical access to the machine, there are plenty worse things to be done than just reading the state of a PRNG. If the random device is initialized in single user mode, and the file is then unlink()ed, I don't see any problems with that. -Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 9: 5:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.11.88.170]) by hub.freebsd.org (Postfix) with ESMTP id 472D437B7E1 for ; Fri, 21 Jul 2000 09:05:12 -0700 (PDT) (envelope-from jjreynold@home.com) Received: from whale.home-net (whale [192.168.1.2]) by cx587235-a.chnd1.az.home.com (8.9.3/8.9.3) with ESMTP id JAA80618 for ; Fri, 21 Jul 2000 09:05:10 -0700 (MST) (envelope-from jjreynold@home.com) Received: (from jjreynold@localhost) by whale.home-net (8.9.3/8.9.3) id JAA74296; Fri, 21 Jul 2000 09:05:10 -0700 (MST) (envelope-from jjreynold@home.com) From: John Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14712.29878.398344.577854@whale.home-net> Date: Fri, 21 Jul 2000 09:05:10 -0700 (MST) To: current@freebsd.org Subject: OT: Praise to all you guys! X-Mailer: VM 6.73 under Emacs 20.6.1 Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just wanted to send this message to -current since I know that you "-current" developers were the ones primarily responsible for 4-STABLE. I just recently upgraded my primary box here from 3.5-STABLE to 4.0-R -> 4.1-RC and notice tons and tons more "snappyness" with the box. It boots faster, I/O is faster, NFS is faster, the pcm driver is better, everything is faster and I haven't tripped over a single "show-stopper" yet! Bravo, congrats, and many thanks to all developers minor or major!!!! -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jjreynold@home.com FreeBSD 4.0-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 9:51:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 8371737BBBA; Fri, 21 Jul 2000 09:51:50 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id A158152; Fri, 21 Jul 2000 12:51:48 -0400 (AST) Message-ID: <39787FA4.A79BAE0B@vangelderen.org> Date: Fri, 21 Jul 2000 12:51:48 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Murray Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <200007211253.OAA00377@grimreaper.grondar.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > > > > What about saving the state of the RNG and re-reading it on bootup? That > > > will allow Yarrow to continue right where it left off. :-) > > > > That's a bad thing. You don't want someone to be able to examine the exact > > PRNG state at next boot by looking at your hard disk after the machine has > > shut down. > > It is a Yarrow-mandated procedure. Please read the Yarrow paper. Actually, it's not. You don not want to save the exact PRNG state to disk, ever. It's not Yarrow mandated procedure but a big security hole. That said, you do not write out the state of the PRNG, you write out a couple of blocks of output from which the state cannot be derived. That *is* okay and that's what you are doing. And just for completeness: it's not mandatory to do so. I don't know where you read that in the paper. > If they can do that, they have either the console (==root) or they have > root. Either way, who cares what they know about your machine, they have > the whole darn thing :-O. Someone may well compromise your randomness source without you noticing. And read your PGP mail for the coming couple of years because your PGP key was compromised without you noticing. Perfect Trojan horse to write for the FBI, IRS, anyone who doesn't like you. Oops. Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 9:55:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 0CA2C37BBBA; Fri, 21 Jul 2000 09:55:10 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 4B09F53; Fri, 21 Jul 2000 12:55:08 -0400 (AST) Message-ID: <3978806C.8BD1EDD6@vangelderen.org> Date: Fri, 21 Jul 2000 12:55:08 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Dan Moschuk Cc: Kris Kennaway , Mark Murray , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <20000718103729.A1221@spirit.jaded.net> <20000721115846.C489@spirit.jaded.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Moschuk wrote: > > | > | Gotcha - fix coming; I need to stash some randomness at shutdown time, and > | > | use that to reseed the RNG at reboot time. > | > > | > What about saving the state of the RNG and re-reading it on bootup? That > | > will allow Yarrow to continue right where it left off. :-) > | > | That's a bad thing. You don't want someone to be able to examine the exact > | PRNG state at next boot by looking at your hard disk after the machine has > | shut down. > > I don't see how. If the attacker has physical access to the machine, there > are plenty worse things to be done than just reading the state of a PRNG. > > If the random device is initialized in single user mode, and the file is > then unlink()ed, I don't see any problems with that. You generate a new PGP keypair and start using it. Your co-worker reboots your machine afterwards and recovers the PRNG state that happens to be stashed on disk. He can then backtrack and potentially recover the exact same random numbers that you used for your key. Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 10: 7:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 1147D37BDE3 for ; Fri, 21 Jul 2000 10:07:20 -0700 (PDT) (envelope-from jhb@pike.osd.bsdi.com) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id KAA67811; Fri, 21 Jul 2000 10:06:49 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200007211706.KAA67811@pike.osd.bsdi.com> Subject: Re: No /boot/loader In-Reply-To: from Bruce Evans at "Jul 21, 2000 06:58:05 pm" To: Bruce Evans Date: Fri, 21 Jul 2000 10:06:49 -0700 (PDT) Cc: Warner@pike.osd.bsdi.com, Losh , dwhite@resnet.uoregon.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > On Thu, 20 Jul 2000, John Baldwin wrote: > > > No, that's wrong, too. A normal disk has a proper slice table (slices start > > on cylinder boundaries and do not contain the MBR, thus leaving the first > track > > cylinder unused). A truly dedicated disk (disklabel auto ) uses a > track > > ... > > at all to the drive's geometry. As with truly dedicated mode, the MBR is > > actually contained in boot1, but in dangerously dedicated mode we use the > > slice table hard-coded into the boot code. This slice table has 1 slice > > which is 50000 blocks long, or 25000k. The rest of the disk is marked as > > unused even though it is, in fact, used. The fact that it works at all is > > due to brokenness on our part (we don't check that partitions in a disklabel > > fit in the parent slice) and also results in several hacks in various portions > > of the code where we have to check for such bogusness and work around it. > > No, that's wrong too :-) . We a lot of checking that partitions in a > disklabel fit in the parent slice. We clip partitions that don't fit in > various ways for backwards compatibility. > > Bruce Erm, maybe we clip partitions which aren't dangerously dedicated, but I've created test dangerously dedicated disks, and we certainly do not bother to actually change any of the slice information when we do so. disklabel(8) does for truly dedicated, but libdisk doesn't for dangerously dedicated. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 11: 3:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id A6D1537BDDF; Fri, 21 Jul 2000 11:03:43 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id LAA61495; Fri, 21 Jul 2000 11:06:41 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200007211806.LAA61495@troutmask.apl.washington.edu> Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <3978806C.8BD1EDD6@vangelderen.org> from "Jeroen C. van Gelderen" at "Jul 21, 2000 12:55:08 pm" To: "Jeroen C. van Gelderen" Date: Fri, 21 Jul 2000 11:06:41 -0700 (PDT) Cc: Dan Moschuk , Kris Kennaway , Mark Murray , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen C. van Gelderen wrote: > Dan Moschuk wrote: > > > > I don't see how. If the attacker has physical access to the machine, there > > are plenty worse things to be done than just reading the state of a PRNG. > > > > If the random device is initialized in single user mode, and the file is > > then unlink()ed, I don't see any problems with that. > > You generate a new PGP keypair and start using it. Your > co-worker reboots your machine afterwards and recovers > the PRNG state that happens to be stashed on disk. He > can then backtrack and potentially recover the exact same > random numbers that you used for your key. > I don't follow your logic. A normal boot/shutdown sequence would be: (1) power on (or shutdown -r) (2) in single-user mode (a) read /dev/saved_entropy into buffer (b) unlink /dev/saved_entropy (c) create /dev/saved_entropy with all zeros (d) test contents in buffer against all zeros (I) buffer contents is different from all zeros; initialize entropy pool (II) buffer contents matches all zeros; use a fall-back method. (3) go multi-user (4) normal shutdown (a) kick everybody off system (b) kill off daemons (c) umount all partitions except the partition with /dev (c) save entropy to /dev/saved_entropy (d) umount partition with /dev After a crash or panic, the system reboots. Step 2(c) has left a finger print to test for valid saved entropy. If all zeros are found use a suitable fallback method to stir the entropy. I don't see how co-worker can do what you suggest. And, if he can easily reboot your system, you have other problems to worry about. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 11:18: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from assurance.rstcorp.com (rstcorp2.daf.concentric.net [216.112.242.2]) by hub.freebsd.org (Postfix) with ESMTP id 855F837BDB2 for ; Fri, 21 Jul 2000 11:17:55 -0700 (PDT) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.10.1/8.10.1) id e6LIHsK09054 for ; Fri, 21 Jul 2000 14:17:54 -0400 Received: from sandbox.rstcorp.com(10.1.30.2) by assurance.rstcorp.com via smap (V2.1+anti-relay+anti-spam) id xma009048; Fri, 21 Jul 00 14:17:16 -0400 Received: from vorpal (vorpal.rstcorp.com [10.1.101.3]) by sandbox.rstcorp.com (8.9.3/8.9.3) with ESMTP id OAA08685 for ; Fri, 21 Jul 2000 14:17:16 -0400 (EDT) Received: by vorpal (Postfix, from userid 93) id B60E344; Fri, 21 Jul 2000 14:17:15 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14712.37803.399020.756017@vorpal.rstcorp.com> Date: Fri, 21 Jul 2000 14:17:15 -0400 (EDT) From: "Viren R.Shah" To: freebsd-current@freebsd.org Subject: Locale issues on -current X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid Reply-To: "Viren R.Shah" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I installed a recent snapshot of -current (a week ago) and I keep getting the following warnings: [vshah@vorpal] /etc> perl perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LC_ALL = (unset), LC_CTYPE = "en_US", LANG = (unset) are supported and installed on your system. If I set the appropriate env vars, I get: vorpal# perl -v perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LC_ALL = "C", LC_CTYPE = "en_US", LANG = "en_US.ISO_8859-1" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). This is perl, v5.6.0 built for i386-freebsd Copyright 1987-2000, Larry Wall Any ideas as to what I need to do? I tried searching the archives with no success [If this is more appropriate for -questions, let me know] Thanks Viren -- Viren R. Shah, viren@rstcorp.com, http://www.rstcorp.com/~vshah/ `Beware the Jabberwock, my son! The jaws that bite, the claws that catch! Beware the Jubjub bird, and shun the frumious Bandersnatch!' -- Lewis Carroll (Jabberwocky) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 12:24: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 6BBA137BE0A for ; Fri, 21 Jul 2000 12:24:01 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id VAA00707; Fri, 21 Jul 2000 21:23:53 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007211923.VAA00707@grimreaper.grondar.za> To: "Jeroen C. van Gelderen" Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <39787FA4.A79BAE0B@vangelderen.org> In-Reply-To: <39787FA4.A79BAE0B@vangelderen.org> ; from "Jeroen C. van Gelderen" "Fri, 21 Jul 2000 12:51:48 -0400." Date: Fri, 21 Jul 2000 21:23:53 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It is a Yarrow-mandated procedure. Please read the Yarrow paper. > > Actually, it's not. You don not want to save the exact > PRNG state to disk, ever. It's not Yarrow mandated > procedure but a big security hole. Section 2.1, last paragraph: "If a system is shut down, and restarted, it is desirable to store some high-entropy data (such as the key) in non-volatile memory. This allows the PRNG to be restarted in an unguessable state at the next restart. We call this data the reseed file." Perhaps "mandated" was a bit strong; "desired" might be better. > That said, you do not write out the state of the PRNG, > you write out a couple of blocks of output from which > the state cannot be derived. That *is* okay and that's > what you are doing. Writing the 256-bit key would have been OK according to the paper. > And just for completeness: it's not mandatory to do so. > I don't know where you read that in the paper. See above. > > If they can do that, they have either the console (==root) or they have > > root. Either way, who cares what they know about your machine, they have > > the whole darn thing :-O. > > Someone may well compromise your randomness source without > you noticing. And read your PGP mail for the coming couple > of years because your PGP key was compromised without you > noticing. Perfect Trojan horse to write for the FBI, IRS, > anyone who doesn't like you. Oops. Sure; we neet to be appropriately paranoid about that, but let's not get ridiculous. The seed file could certainly use some decent protection, but unfortunately, PC architectures don't come with SIMcards or the like. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 12:26:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 60F8D37BE0A for ; Fri, 21 Jul 2000 12:26:26 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id VAA00724; Fri, 21 Jul 2000 21:26:21 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007211926.VAA00724@grimreaper.grondar.za> To: "Jeroen C. van Gelderen" Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: <3978806C.8BD1EDD6@vangelderen.org> In-Reply-To: <3978806C.8BD1EDD6@vangelderen.org> ; from "Jeroen C. van Gelderen" "Fri, 21 Jul 2000 12:55:08 -0400." Date: Fri, 21 Jul 2000 21:26:21 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You generate a new PGP keypair and start using it. Your > co-worker reboots your machine afterwards and recovers > the PRNG state that happens to be stashed on disk. He > can then backtrack and potentially recover the exact same > random numbers that you used for your key. Said state is rm'med after use. If you didn't detect the breakin, your fault for poor intrusion detection. lets put the paranoia to practical use and detect the breakin, not nitpick the systems that are supposed to be protected. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 12:44:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62]) by hub.freebsd.org (Postfix) with ESMTP id C282E37C06F for ; Fri, 21 Jul 2000 12:44:27 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id MAA23203; Fri, 21 Jul 2000 12:42:50 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Fri, 21 Jul 2000 12:42:50 -0700 (PDT) From: Doug Barton X-Sender: doug@dt052n3e.san.rr.com To: Ollivier Robert Cc: "FreeBSD Current Users' list" Subject: Re: Current broken in ncurses ? In-Reply-To: <20000721160410.B44378@caerdonn.eurocontrol.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jul 2000, Ollivier Robert wrote: > Am I the only one with this ? > > cc -O -pipe -I. -I/src/src/lib/libncurses -I/src/src/lib/libncurses/../../contrib/ncurses/ncurses -I/src/src/lib/libncurses/../../contrib/ncurses/include -Wall -DFREEBSD_NATIVE -DNDEBUG -DHAVE_CONFIG_H -DTERMIOS -I/net/nas/roberto/sidhe/src/src/i386/usr/include -c /src/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/comp_scan.c -o comp_scan.o > /src/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/comp_scan.c: In function `_nc_get_token': > /src/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/comp_scan.c:184: `_nc_disable_period' undeclared (first use in this function) > /src/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/comp_scan.c:184: (Each undeclared identifier is reported only once > /src/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/comp_scan.c:184: for each function it appears in.) > *** Error code 1 > > Stop in /src/src/lib/libncurses. I just completed a make world here... try the usual cleaning /usr/obj and make cleandir in src and see if that helps. Good luck, Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 12:45: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62]) by hub.freebsd.org (Postfix) with ESMTP id 10AAF37C08F for ; Fri, 21 Jul 2000 12:45:01 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id MAA23236; Fri, 21 Jul 2000 12:44:51 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Fri, 21 Jul 2000 12:44:51 -0700 (PDT) From: Doug Barton X-Sender: doug@dt052n3e.san.rr.com To: John Reynolds Cc: current@freebsd.org Subject: Re: OT: Praise to all you guys! In-Reply-To: <14712.29878.398344.577854@whale.home-net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jul 2000, John Reynolds wrote: > Bravo, congrats, and many thanks to all developers minor or major!!!! You have no idea how nice it is to hear GOOD news for a change. Thank you for taking the time. Glad you're enjoying it, Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 12:48:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id D6D5E37BE93 for ; Fri, 21 Jul 2000 12:48:12 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id OAA10248; Fri, 21 Jul 2000 14:47:46 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Fri, 21 Jul 2000 14:47:46 -0500 (CDT) From: David Scheidt To: Mark Murray Cc: "Jeroen C. van Gelderen" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007211923.VAA00707@grimreaper.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jul 2000, Mark Murray wrote: : :Sure; we neet to be appropriately paranoid about that, but let's not :get ridiculous. The seed file could certainly use some decent protection, :but unfortunately, PC architectures don't come with SIMcards or the like. : Is it possible to combine the state of the disk based seed with some other source of real entropy? That would redudce the risk of having someone read your disks while the system is shutdown. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 13: 0:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from veldy.net (veldy-host201.dsl.visi.com [208.42.48.201]) by hub.freebsd.org (Postfix) with ESMTP id AB1BB37BE81 for ; Fri, 21 Jul 2000 13:00:29 -0700 (PDT) (envelope-from veldy@veldy.net) Received: from 95CTJ (fuggle.veldy.net [208.42.48.201]) by veldy.net (Postfix) with SMTP id F0DFC8C1B for ; Fri, 21 Jul 2000 15:01:49 -0500 (CDT) Message-ID: <017101bff34e$12ca9c10$dd29680a@tgt.com> From: "Thomas T. Veldhouse" To: Subject: Journaling Filesystem ? Date: Fri, 21 Jul 2000 14:58:43 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. I was wondering if there is any work on a Journaling filesystem to possible replace, or as an alternative to UFS. I have been following ReiserFS for Linux quite closely, and I have had the chance to experiment with it. It seems to be coming along nicely and the performance is great. Are there plans for something along this line for FreeBSD? Is there a project underway? This is not the sort of thing I am likely to be able to contribute much code too (although I would love to give it a shot), so I would volunteer to test it on my box :) Thanks, Tom Veldhouse veldy@veldy.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 13: 2:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id C96F637BE38 for ; Fri, 21 Jul 2000 13:02:20 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id WAA01222; Fri, 21 Jul 2000 22:02:10 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007212002.WAA01222@grimreaper.grondar.za> To: David Scheidt Cc: current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: In-Reply-To: ; from David Scheidt "Fri, 21 Jul 2000 14:47:46 EST." Date: Fri, 21 Jul 2000 22:02:10 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :Sure; we neet to be appropriately paranoid about that, but let's not > :get ridiculous. The seed file could certainly use some decent protection, > :but unfortunately, PC architectures don't come with SIMcards or the like. > : > > Is it possible to combine the state of the disk based seed with some other > source of real entropy? That would redudce the risk of having someone read > your disks while the system is shutdown. I'm working on haresting some more entropy; that should do what you want. (Things like disk activity, network stack, process tables and so on). If you are worried about someone reading the disk of a rebooting box, then you need to be worried about console access; if your attacker has console, you are screwed anyway. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 13: 4:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 7086C37BEA6 for ; Fri, 21 Jul 2000 13:04:32 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id QAA84436; Fri, 21 Jul 2000 16:04:29 -0400 (EDT) (envelope-from wollman) Date: Fri, 21 Jul 2000 16:04:29 -0400 (EDT) From: Garrett Wollman Message-Id: <200007212004.QAA84436@khavrinen.lcs.mit.edu> To: "Thomas T. Veldhouse" Cc: Subject: Journaling Filesystem ? In-Reply-To: <017101bff34e$12ca9c10$dd29680a@tgt.com> References: <017101bff34e$12ca9c10$dd29680a@tgt.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Are there plans for something along this line for FreeBSD? Is there a > project underway? No. Soft Updates provides most of the benefits without requiring changes to the on-disk layout. See . -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 13:13:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from veldy.net (veldy-host201.dsl.visi.com [208.42.48.201]) by hub.freebsd.org (Postfix) with ESMTP id B29E637B577 for ; Fri, 21 Jul 2000 13:13:46 -0700 (PDT) (envelope-from veldy@veldy.net) Received: from 95CTJ (fuggle.veldy.net [208.42.48.201]) by veldy.net (Postfix) with SMTP id 7AF748C37; Fri, 21 Jul 2000 15:15:23 -0500 (CDT) Message-ID: <019b01bff34f$f7bfeea0$dd29680a@tgt.com> From: "Thomas T. Veldhouse" To: "Garrett Wollman" Cc: References: <017101bff34e$12ca9c10$dd29680a@tgt.com> <200007212004.QAA84436@khavrinen.lcs.mit.edu> Subject: Re: Journaling Filesystem ? Date: Fri, 21 Jul 2000 15:12:16 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been using softupdates since 3.x. It works pretty well - but recovery was not as good as ReiserFS - so far. I didn't quite catch what the improvements that are underway for current. What is the difference between a journal and a snapshot? Tom Veldhouse veldy@veldy.net ----- Original Message ----- From: Garrett Wollman To: Thomas T. Veldhouse Cc: Sent: Friday, July 21, 2000 3:04 PM Subject: Journaling Filesystem ? > < said: > > > Are there plans for something along this line for FreeBSD? Is there a > > project underway? > > No. Soft Updates provides most of the benefits without requiring > changes to the on-disk layout. See > . > > -GAWollman > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 14:20:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (ftp.webmaster.com [209.10.218.74]) by hub.freebsd.org (Postfix) with ESMTP id 9F46737C0D5 for ; Fri, 21 Jul 2000 14:20:41 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([216.152.68.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Fri, 21 Jul 2000 14:20:06 -0700 From: "David Schwartz" To: "Jeroen C. van Gelderen" Cc: Subject: RE: randomdev entropy gathering is really weak Date: Fri, 21 Jul 2000 14:20:40 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <3978806C.8BD1EDD6@vangelderen.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You generate a new PGP keypair and start using it. Your > co-worker reboots your machine afterwards and recovers > the PRNG state that happens to be stashed on disk. He > can then backtrack and potentially recover the exact same > random numbers that you used for your key. If that is possible, then Yarrow's algorithm is badly broken. It should not be possible to run a PRNG backwards without knowing what it output. Once it outputs something, the state information neccessary to produce that output should be removed by the output process. Imagine if I have a PRNG in state 0 (which I'll call "S(0)"). It then outputs a particular 32-bit PRN, called 'A' and is now in a new state S(1). Now, if one tries to backtrack from S(1) to S(0), one needs to know A. For every possible 32-bit A that could have been output, there's a different corresponding S'(0) (state that might have been S(0)). Since the attacker does not know A, he does not know which S'(0) corresponds to S(0), and hence cannot backtrack. Since the people who developed this algorithm are pretty bright, I will conculde that this is not the case. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 17:57:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id 14E2437C1F2 for ; Fri, 21 Jul 2000 17:22:16 -0700 (PDT) (envelope-from nsayer@medusa.kfu.com) Received: from medusa.kfu.com (medusa.kfu.com [205.178.90.222]) by quack.kfu.com (8.9.3/8.9.3) with ESMTP id RAA20743 for ; Fri, 21 Jul 2000 17:22:15 -0700 (PDT) (envelope-from nsayer@medusa.kfu.com) Received: (from nsayer@localhost) by medusa.kfu.com (8.9.3/8.8.8) id RAA02194 for freebsd-current@freebsd.org; Fri, 21 Jul 2000 17:22:15 -0700 (PDT) (envelope-from nsayer) Date: Fri, 21 Jul 2000 17:22:15 -0700 (PDT) From: Nick Sayer Message-Id: <200007220022.RAA02194@medusa.kfu.com> To: freebsd-current@freebsd.org Subject: DHCP client problem? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Something changed very recently in the dhcp client stuff that seems to have broke my -current machine's ability to be a dhcp client. The symptom is that I see ifconfig: netmask 255.255.255.224: bad value come out of the script invocation, and the ip address does not get set. If I echo out the parameters and type in THE EXACT SAME command line myself, it works just fine. I suspect some sort of bizarre quoting conspiracy. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 18: 7:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat193.142.mpoweredpc.net [142.177.193.142]) by hub.freebsd.org (Postfix) with ESMTP id 29B1437C5C6 for ; Fri, 21 Jul 2000 18:07:23 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id VAA74010 for ; Fri, 21 Jul 2000 21:14:57 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 21 Jul 2000 21:14:57 -0300 (ADT) From: The Hermit Hacker To: freebsd-current@freebsd.org Subject: missing idea.h ... ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just tried to compile kde2 after upgrading to the latest 5.0-CURRENT and its reporting: In file included from /usr/include/openssl/pem.h:66, from /usr/include/openssl/ssl.h:147, from https.cc:42: /usr/include/openssl/evp.h:99: openssl/idea.h: No such file or directory its being included by a system file, so I can't blame the kde2 source for it ... I just set 'MAKE_IDEA' in my make.conf and am doing a new 'make world', but should not having that cause a problem? Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 18:55: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id D27E537B5F9; Fri, 21 Jul 2000 18:54:54 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id SAA78849; Fri, 21 Jul 2000 18:54:54 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 21 Jul 2000 18:54:54 -0700 (PDT) From: Kris Kennaway To: Mark Murray Cc: "Jeroen C. van Gelderen" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007211923.VAA00707@grimreaper.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jul 2000, Mark Murray wrote: > Section 2.1, last paragraph: > "If a system is shut down, and restarted, it is desirable to store some > high-entropy data (such as the key) in non-volatile memory. This allows > the PRNG to be restarted in an unguessable state at the next restart. We > call this data the reseed file." I'm all for storing a sample at shutdown and using it to help seed the PRNG at startup, but it shouldn't be the only seed used (for example, the case where the system has never been shut down (cleanly) before and so has no pre-existing seed file is a BIG corner case to consider since thats how the system is at the time it first generates SSH keys after a fresh install). It might be only an academic vulnerability, but if someone can read your HD during the time the system is shut down then I'd prefer them not to know the precise state when the system next starts up again. Yes, if they can read they can probably also write, but it seems like a mistake when there's nothing really gained by saving the complete state, as opposed to an extract. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 18:57:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 9F5F737B6CB; Fri, 21 Jul 2000 18:57:19 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id SAA78986; Fri, 21 Jul 2000 18:57:19 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 21 Jul 2000 18:57:19 -0700 (PDT) From: Kris Kennaway To: Mark Murray Cc: David Scheidt , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007212002.WAA01222@grimreaper.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jul 2000, Mark Murray wrote: > If you are worried about someone reading the disk of a rebooting box, > then you need to be worried about console access; if your attacker has > console, you are screwed anyway. For most people, yes. But it's like all of the buffer overflows in non-setuid utilities: they're not security risks for the vast majority of users, but who's to say there won't be a situation somewhere when it is one. Better not to take the risk, since it's not necessary here. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 19: 0:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from mercury.mich.com (mercury.mich.com [64.79.64.32]) by hub.freebsd.org (Postfix) with ESMTP id 9494C37B5F9 for ; Fri, 21 Jul 2000 19:00:56 -0700 (PDT) (envelope-from will@almanac.yi.org) Received: from argon.gryphonsoft.com (pm002-033.dialup.bignet.net [64.79.80.81]) by mercury.mich.com (8.9.3/8.9.3) with ESMTP id VAA07443; Fri, 21 Jul 2000 21:59:41 -0400 Received: by argon.gryphonsoft.com (Postfix, from userid 1000) id C3286197E; Fri, 21 Jul 2000 21:57:59 -0400 (EDT) Date: Fri, 21 Jul 2000 21:57:59 -0400 From: Will Andrews To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: missing idea.h ... ? Message-ID: <20000721215759.B36849@argon.gryphonsoft.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from scrappy@hub.org on Fri, Jul 21, 2000 at 09:14:57PM -0300 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 21, 2000 at 09:14:57PM -0300, The Hermit Hacker wrote: > Just tried to compile kde2 after upgrading to the latest 5.0-CURRENT and > its reporting: > > In file included from /usr/include/openssl/pem.h:66, > from /usr/include/openssl/ssl.h:147, > from https.cc:42: > /usr/include/openssl/evp.h:99: openssl/idea.h: No such file or directory > > its being included by a system file, so I can't blame the kde2 source for > it ... I just set 'MAKE_IDEA' in my make.conf and am doing a new 'make > world', but should not having that cause a problem? I don't encounter such problems in my KDE 20000721 builds. I build on 4.1-RC with full OpenSSL sources. BTW: I should have a webpage/ftpsite etc. ready for port test builds tomorrow.. bug me if it's not announced soon. 8) -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 19: 6:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat193.142.mpoweredpc.net [142.177.193.142]) by hub.freebsd.org (Postfix) with ESMTP id 2517D37C1C6 for ; Fri, 21 Jul 2000 19:06:42 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id XAA88771; Fri, 21 Jul 2000 23:04:43 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 21 Jul 2000 23:04:43 -0300 (ADT) From: The Hermit Hacker To: Will Andrews Cc: freebsd-current@FreeBSD.ORG Subject: Re: missing idea.h ... ? In-Reply-To: <20000721215759.B36849@argon.gryphonsoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jul 2000, Will Andrews wrote: > On Fri, Jul 21, 2000 at 09:14:57PM -0300, The Hermit Hacker wrote: > > Just tried to compile kde2 after upgrading to the latest 5.0-CURRENT and > > its reporting: > > > > In file included from /usr/include/openssl/pem.h:66, > > from /usr/include/openssl/ssl.h:147, > > from https.cc:42: > > /usr/include/openssl/evp.h:99: openssl/idea.h: No such file or directory > > > > its being included by a system file, so I can't blame the kde2 source for > > it ... I just set 'MAKE_IDEA' in my make.conf and am doing a new 'make > > world', but should not having that cause a problem? > > I don't encounter such problems in my KDE 20000721 builds. I build on > 4.1-RC with full OpenSSL sources. I just finished a "make world" with MAKE_IDEA enabled in make.conf, and the idea.h file is now in /usr/include/openssl *shrug* > BTW: I should have a webpage/ftpsite etc. ready for port test builds > tomorrow.. bug me if it's not announced soon. 8) If it helps any, I setup an anoncvs mirror for most of the stuff ... not sure if it helps any, since you are working off of snapshots, but its updated every 4hrs from the central repository, and the CVSROOT for it was announced on kde-devel ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 19:51:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from amonduul.ecn.ou.edu (amonduul.ecn.ou.edu [129.15.119.201]) by hub.freebsd.org (Postfix) with ESMTP id E8CA237B5CF for ; Fri, 21 Jul 2000 19:51:30 -0700 (PDT) (envelope-from servalan!rmtodd@amonduul.ecn.ou.edu) Received: from servalan (3293 bytes) by amonduul.ecn.ou.edu via rmail with P:uucp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for freebsd.org!freebsd-current; Fri, 21 Jul 2000 21:47:18 -0500 (CDT) (Smail-3.2.0.111 2000-Feb-17 #1 built 2000-Apr-4) Received: from localhost (2729 bytes) by servalan.servalan.com via sendmail with P:stdio/R:smart_host/T:uux (sender: ) (ident using unix) id for ; Fri, 21 Jul 2000 20:29:30 -0500 (CDT) (Smail-3.2.0.106 1999-Mar-31 #1 built 1999-Aug-10) Message-Id: Date: Fri, 21 Jul 2000 20:29:30 -0500 (CDT) From: rmtodd@servalan.servalan.com (Richard Todd) To: freebsd-current@freebsd.org, "George W. Dinolt" Subject: Re: (noperiph:ahc0:0:-1:-1): ... error Newsgroups: servalan.mailinglist.fbsd-current References: X-Newsreader: NN version 6.5.3 (NOV) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In servalan.mailinglist.fbsd-current you write: >I am trying to run a recent (as of today) and am seeing the following >error when I try to boot:: >(noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. >panic: Bogus resid sgptr value 0xbd68609 >(I copied this from the console after the boot failure, there may be >minor mistakes.) >This started happening when I started compiling kernels built from >sources cvsuped around Jul 18. >I am not sure what is causing these messages. The "noperiph" message >appears to come from xpt_print_path in /usr/src/sys/cam/cam_xpt.c while >the panic seems to be written by ahc_calc_residual in >/usr/src/sys/dev/aic7xxx/aic7xxx.c. From a quick look at the code, the >problem is not directly in the code pointed to by the messages. >I have an Adaptec 2940UW. A much older kernel reports it as 2940 Ultra SCSI adapter> with aic7880 Wide Channel A, SCSI Id=7, >16/255 SCBs. The Bios on the board is version 2.20.0 >I have 4 drives and a UMAX scanner connected to the bus. More details >available if needed. I saw something similar, but not identical, when trying to boot a -current kernel made last night. I saw the (noperiph...) message you saw. After that, the machine didn't panic, but it didn't work very well, either. It did, after a few seconds, detect the SCSI tape drive I had (sa0), but failed on detecting the SCSI disk and CDROM, repeatedly timing out and resetting the bus. Alas, I didn't have the presence of mind to write down the exact messages; I'll try to do that tonight, assuming the bug is still present in the src I'm cvsupping now. This was on an SMP box (Tyan Thunder 100GX), with an aic7895 SCSI controller, and the following three SCSI devices: sa0 at ahc0 bus 0 target 0 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) Mounting root from ufs:/dev/da0s2a da0 at ahc0 bus 0 target 6 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) cd0 at ahc0 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 20:21:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 81A6F37C240 for ; Fri, 21 Jul 2000 20:21:48 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id UAA15862; Fri, 21 Jul 2000 20:21:23 -0700 Date: Fri, 21 Jul 2000 20:21:25 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Richard Todd , "George W. Dinolt" Cc: freebsd-current@FreeBSD.ORG Subject: Re: (noperiph:ahc0:0:-1:-1): ... error In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You'll have to raise issue on freebsd-scsi. I sent the likely owner of the issue mail, but they don't monitor -current. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 20:36:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 42C8237B7FF; Fri, 21 Jul 2000 20:36:33 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id UAA86483; Fri, 21 Jul 2000 20:36:33 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 21 Jul 2000 20:36:33 -0700 (PDT) From: Kris Kennaway To: David Schwartz Cc: "Jeroen C. van Gelderen" , current@freebsd.org Subject: RE: randomdev entropy gathering is really weak In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jul 2000, David Schwartz wrote: > > You generate a new PGP keypair and start using it. Your > > co-worker reboots your machine afterwards and recovers > > the PRNG state that happens to be stashed on disk. He > > can then backtrack and potentially recover the exact same > > random numbers that you used for your key. > > If that is possible, then Yarrow's algorithm is badly broken. It > should not be possible to run a PRNG backwards without knowing what it > output. Once it outputs something, the state information neccessary to > produce that output should be removed by the output process. Yarrow only reseeds every so often when it has enough entropy accumulated, and changes its internal key using a "generator gate" every few inputs (the paper suggests 10). So if you break the state of the algorithm (e.g. if it were stored on disk after a reboot) you can learn up to 10 previous PRNG outputs with that key, back to the previous generator gate or reseed. This issue is common to all PRNGs that don't reseed with every output value - it's discussed in the Yarrow paper, which you should read :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 20:40:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.11.88.170]) by hub.freebsd.org (Postfix) with ESMTP id E7DCA37B7FF for ; Fri, 21 Jul 2000 20:40:02 -0700 (PDT) (envelope-from jjreynold@home.com) Received: from whale.home-net (whale [192.168.1.2]) by cx587235-a.chnd1.az.home.com (8.9.3/8.9.3) with ESMTP id UAA23762; Fri, 21 Jul 2000 20:40:02 -0700 (MST) (envelope-from jjreynold@home.com) Received: (from jjreynold@localhost) by whale.home-net (8.9.3/8.9.3) id UAA21104; Fri, 21 Jul 2000 20:40:02 -0700 (MST) (envelope-from jjreynold@home.com) From: John Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14713.6034.340826.387300@whale.home-net> Date: Fri, 21 Jul 2000 20:40:02 -0700 (MST) To: Doug Barton Cc: current@freebsd.org Subject: Re: OT: Praise to all you guys! In-Reply-To: References: <14712.29878.398344.577854@whale.home-net> X-Mailer: VM 6.73 under Emacs 20.6.1 Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Friday, July 21, Doug Barton wrote: ] > > You have no idea how nice it is to hear GOOD news for a > change. yes I do ... :) ... I work in a semi-support role at work where I hear lots of "it's broken" complaints. I know how frustrating it gets sometimes. > Thank you for taking the time. No problem. I figured since everything did go so darned smoothly and the system is SO much speedier, I just had to tip the hat via e-mail. Of course, it did help to RTFM /usr/src/UPDATING and -stable well in advance of my 3->4 transition though :) > Glad you're enjoying it, :) -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jjreynold@home.com FreeBSD 4.0-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 21 21:26: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 1B6A137B72F; Fri, 21 Jul 2000 21:26:07 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id VAA91491; Fri, 21 Jul 2000 21:26:06 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 21 Jul 2000 21:26:06 -0700 (PDT) From: Kris Kennaway To: Mark Murray Cc: "Jeroen C. van Gelderen" , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jul 2000, Kris Kennaway wrote: > > Section 2.1, last paragraph: > > "If a system is shut down, and restarted, it is desirable to store some > > high-entropy data (such as the key) in non-volatile memory. This allows > > the PRNG to be restarted in an unguessable state at the next restart. We > > call this data the reseed file." After rereading the paper in more detail, Step 7 of the reseed algorithm seems not entirely consistent with this: they explicitly refer to writing out "the next 2k bits of output from the generator to the seed file" (slightly different terminology, but I couldn't find any other references to the "seed file") Another important point is that Yarrow-160 is not useful for generating keys >160 bits, because of Shannon's theorem and the fact that it uses SHA-1. You seem to be using a blowfish-based hash function with 256-bit keysize (do you have a reference for using blowfish in that fashion?), but the point stands. It seems we would need to use an alternative interface which either synchronously reseeds with every output to generate stronger random data, or just taps into the (hashed) entropy pools directly. This was also a problem with our /dev/urandom (by design), but not with /dev/random since that tapped the entropy pool directly. Incidentally, it also looks like a problem with OpenBSD's /dev/arandom which is a stream cipher (arc4 with 256-bit key) periodically reseeded. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 0:10:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62]) by hub.freebsd.org (Postfix) with ESMTP id 3F5ED37BB9A for ; Sat, 22 Jul 2000 00:10:43 -0700 (PDT) (envelope-from DougB@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id AAA25201; Sat, 22 Jul 2000 00:10:39 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <397948EF.C1C7C396@gorean.org> Date: Sat, 22 Jul 2000 00:10:39 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Viren R.Shah" Cc: freebsd-current@freebsd.org Subject: Re: Locale issues on -current References: <14712.37803.399020.756017@vorpal.rstcorp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Viren R.Shah" wrote: > > I installed a recent snapshot of -current (a week ago) and I keep > getting the following warnings: > > [vshah@vorpal] /etc> perl > perl: warning: Setting locale failed. > perl: warning: Please check that your locale settings: > LC_ALL = (unset), > LC_CTYPE = "en_US", > LANG = (unset) > are supported and installed on your system. I get the same thing. It's LC_CTYPE that's causing the problem. I was half thinking that it was something related to gnome, but I haven't worked very hard to fix it. Unsetting that variable makes the warning go away, whether that fixes the problem or not. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 0:43:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 8138337C250; Sat, 22 Jul 2000 00:42:27 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id JAA05424; Sat, 22 Jul 2000 09:42:24 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007220742.JAA05424@grimreaper.grondar.za> To: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: In-Reply-To: ; from Kris Kennaway "Fri, 21 Jul 2000 18:54:54 MST." Date: Sat, 22 Jul 2000 09:42:24 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm all for storing a sample at shutdown and using it to help seed the > PRNG at startup, but it shouldn't be the only seed used (for example, the > case where the system has never been shut down (cleanly) before and so has > no pre-existing seed file is a BIG corner case to consider since thats how > the system is at the time it first generates SSH keys after a fresh > install). Agreed; we need more entropy sources that are available early enough to be useful. > It might be only an academic vulnerability, but if someone can read your > HD during the time the system is shut down then I'd prefer them not to > know the precise state when the system next starts up again. Yes, if they > can read they can probably also write, but it seems like a mistake when > there's nothing really gained by saving the complete state, as opposed to > an extract. Academic argument noted; with more entropy sources, this situation will improve. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 1: 4:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 811B237B69C; Sat, 22 Jul 2000 01:04:10 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id KAA05467; Sat, 22 Jul 2000 10:04:08 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007220804.KAA05467@grimreaper.grondar.za> To: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: In-Reply-To: ; from Kris Kennaway "Fri, 21 Jul 2000 21:26:06 MST." Date: Sat, 22 Jul 2000 10:04:08 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > After rereading the paper in more detail, Step 7 of the reseed algorithm > seems not entirely consistent with this: they explicitly refer to writing > out "the next 2k bits of output from the generator to the seed file" > (slightly different terminology, but I couldn't find any other references > to the "seed file") He doesn't talk about it too much :-(. > Another important point is that Yarrow-160 is not useful for generating > keys >160 bits, because of Shannon's theorem and the fact that it uses > SHA-1. You seem to be using a blowfish-based hash function with 256-bit > keysize (do you have a reference for using blowfish in that fashion?), but > the point stands. It seems we would need to use an alternative interface > which either synchronously reseeds with every output to generate stronger > random data, or just taps into the (hashed) entropy pools directly. Lots of references: Schneier's "Applied Cryptography" talks about using Good Hashes for crypto and Good Crypto for hashes. Schneier's site at www.counterpane.com will give you plenty. It is also an extension and improvement on the way OpenBSD do their bcrypt (passwd) hash. > This was also a problem with our /dev/urandom (by design), but not with > /dev/random since that tapped the entropy pool directly. Incidentally, it > also looks like a problem with OpenBSD's /dev/arandom which is a stream > cipher (arc4 with 256-bit key) periodically reseeded. The differnce with the old system and Yarrow is yarrow's self-recovery property; Yarrow screens its internal state from the ouside world very heavily, and provides enough perturbation of it from its copious :-) entropy harvesting to keep the state safe from compromise. Yarrow also keeps multiple (fast/slow pools + key) states, and the long, slow interactions between those give much better protection that the old system which was pretty much a simple PRNG+simple random perturbations. (I know MD5 is not "simple", but it is deterministic, and was only used once). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 1:14:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 42BCB37B69C; Sat, 22 Jul 2000 01:14:32 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id BAA13384; Sat, 22 Jul 2000 01:14:31 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 22 Jul 2000 01:14:30 -0700 (PDT) From: Kris Kennaway To: Mark Murray Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007220804.KAA05467@grimreaper.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Jul 2000, Mark Murray wrote: > Lots of references: Schneier's "Applied Cryptography" talks about > using Good Hashes for crypto and Good Crypto for hashes. Schneier's > site at www.counterpane.com will give you plenty. I havent been able to get my hands on Applied Cryptography, but I don't recall seeing anything like this on the website. I'll check again. > The differnce with the old system and Yarrow is yarrow's self-recovery > property; Yarrow screens its internal state from the ouside world > very heavily, and provides enough perturbation of it from its > copious :-) entropy harvesting to keep the state safe from compromise. Yeah, I know all this and agree that Yarrow makes a better /dev/urandom, but it doesn't change the fact that Yarrow-256 is only good for 256 bits of entropy between reseeding operations. You can pull all you want out of it but will never get more than 256 bits until it reseeds. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 1:51: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from dfw-smtpout4.email.verio.net (dfw-smtpout4.email.verio.net [129.250.36.44]) by hub.freebsd.org (Postfix) with ESMTP id E369037B96D for ; Sat, 22 Jul 2000 01:51:00 -0700 (PDT) (envelope-from gjohnson@gs.verio.net) Received: from [129.250.38.64] (helo=dfw-mmp4.email.verio.net) by dfw-smtpout4.email.verio.net with esmtp (Exim 3.12 #7) id 13Fuzr-0000Yd-00 for freebsd-current@freebsd.org; Sat, 22 Jul 2000 08:50:59 +0000 Received: from [204.1.124.74] (helo=power) by dfw-mmp4.email.verio.net with smtp (Exim 3.15 #4) id 13Fuzr-0007iL-00 for freebsd-current@FreeBSD.ORG; Sat, 22 Jul 2000 08:50:59 +0000 Message-ID: <00bd01bff3b9$f519eec0$4a7c01cc@gs.verio.net> From: "Tony Johnson" To: Subject: buildworld error Date: Sat, 22 Jul 2000 03:50:59 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00BA_01BFF390.0C18DF20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_00BA_01BFF390.0C18DF20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable When I was doing a make world on my system for 5.0-current, I was = getting this error: =3D=3D=3D> sys/boot/i386/boot2 as --defsym FLAGS=3D0x80 /usr/src/sys/boot/i386/boot2/boot1.s -o = boot1.o ld -nostdlib -static -N -e start -Ttext 0x7c00 -o boot1.out boot1.o objcopy -S -O binary boot1.out boot1 dd if=3D/dev/zero of=3Dboot2.ldr bs=3D512 count=3D1 2>/dev/null *** Error code 1 =20 Stop in /usr/src/sys/boot/i386/boot2. *** Error code 1 =20 Stop in /usr/src/sys/boot/i386. *** Error code 1 =20 Stop in /usr/src/sys/boot. *** Error code 1 =20 Stop in /usr/src/sys. *** Error code 1 =20 Stop in /usr/src. *** Error code 1 =20 Stop in /usr/src. *** Error code 1 =20 Stop in /usr/src. su-2.04# =20 ------=_NextPart_000_00BA_01BFF390.0C18DF20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
When I was doing a make world on my = system for=20 5.0-current, I was getting this error:
 
=3D=3D=3D> = sys/boot/i386/boot2
as  --defsym=20 FLAGS=3D0x80 /usr/src/sys/boot/i386/boot2/boot1.s -o boot1.o
ld = -nostdlib=20 -static -N -e start -Ttext 0x7c00 -o boot1.out boot1.o
objcopy -S -O = binary=20 boot1.out boot1
dd if=3D/dev/zero of=3Dboot2.ldr bs=3D512 count=3D1=20 2>/dev/null
*** Error code 1
 
Stop in=20 /usr/src/sys/boot/i386/boot2.
*** Error code 1
 
Stop in=20 /usr/src/sys/boot/i386.
*** Error code 1
 
Stop in=20 /usr/src/sys/boot.
*** Error code 1
 
Stop in = /usr/src/sys.
***=20 Error code 1
 
Stop in /usr/src.
*** Error code=20 1
 
Stop in /usr/src.
*** Error code 1
 
Stop = in=20 /usr/src.
su-2.04#        &nbs= p;            = ;   =20
------=_NextPart_000_00BA_01BFF390.0C18DF20-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 2: 2:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 47FE437BB9A; Sat, 22 Jul 2000 02:02:31 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id LAA05901; Sat, 22 Jul 2000 11:02:26 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007220902.LAA05901@grimreaper.grondar.za> To: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: In-Reply-To: ; from Kris Kennaway "Sat, 22 Jul 2000 01:14:30 MST." Date: Sat, 22 Jul 2000 11:02:26 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The differnce with the old system and Yarrow is yarrow's self-recovery > > property; Yarrow screens its internal state from the ouside world > > very heavily, and provides enough perturbation of it from its > > copious :-) entropy harvesting to keep the state safe from compromise. > > Yeah, I know all this and agree that Yarrow makes a better /dev/urandom, > but it doesn't change the fact that Yarrow-256 is only good for 256 bits > of entropy between reseeding operations. You can pull all you want out of > it but will never get more than 256 bits until it reseeds. Aaah! I understand your question better; this is the "conservation of entropy" argument which Yarrow "breaks". Because of Yarrow's cryptographic protection of its internal state, its frequent reseeds and its clever geneation mechanism, this paradigm is less important - the output is 256-bit safe (Blowfish safe) for any size of output[*]. When you read 1000 bits, I am not selling you 1000 bits each guaranteed random, I am selling you 1000 bits that are predictable within the constraints of needing to crack 256-bit Blowfish. [*] Assuming no errors on the part of the implementor (me). :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 2:21:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id E423837B71B; Sat, 22 Jul 2000 02:21:15 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id CAA21274; Sat, 22 Jul 2000 02:21:15 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 22 Jul 2000 02:21:15 -0700 (PDT) From: Kris Kennaway To: Mark Murray Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007220902.LAA05901@grimreaper.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Jul 2000, Mark Murray wrote: > Because of Yarrow's cryptographic protection of its internal state, its > frequent reseeds and its clever geneation mechanism, this paradigm is > less important - the output is 256-bit safe (Blowfish safe) for any size > of output[*]. When you read 1000 bits, I am not selling you 1000 bits > each guaranteed random, I am selling you 1000 bits that are predictable > within the constraints of needing to crack 256-bit Blowfish. So what it if I want/need 257 bits? :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 3: 7: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 97A5B37B6FC for ; Sat, 22 Jul 2000 03:07:01 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.9.3/8.9.3) with ESMTP id LAA04590; Sat, 22 Jul 2000 11:01:05 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id LAA84762; Sat, 22 Jul 2000 11:01:24 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200007221001.LAA84762@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Michael Lucas Cc: current@FreeBSD.org, brian@Awfulhak.org Subject: Re: MS CHAP v2 in -current? In-Reply-To: Message from Michael Lucas of "Mon, 17 Jul 2000 15:50:52 EDT." <200007171950.PAA05990@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 22 Jul 2000 11:01:22 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ping... > > Does anyone know if ms chap v2 will be integrated into -current any > time soon? I need it for pptpclient. > > If anyone has any patches they'd like public testing on, I'll volunteer. :) I have some code submitted by Nathan Blinkert - I'll apply them later today. > ==ml -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 4:18:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from afs.itc.keio.ac.jp (afs.itc.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with SMTP id 2FE6E37B648 for ; Sat, 22 Jul 2000 04:18:32 -0700 (PDT) (envelope-from hosokawa@itc.keio.ac.jp) Received: (qmail 20510 invoked from network); 22 Jul 2000 11:18:30 -0000 Received: from pppb30.yk.rim.or.jp (HELO localhost.FromTo.Cc) (202.247.186.130) by afs.itc.keio.ac.jp with SMTP; 22 Jul 2000 11:18:30 -0000 Date: Sat, 22 Jul 2000 20:18:30 +0900 Message-ID: <86ittyjtvd.wl@ringo.FromTo.Cc> From: Tatsumi Hosokawa To: nsayer@quack.kfu.com Cc: freebsd-current@freebsd.org Subject: Re: DHCP client problem? In-Reply-To: In your message of "Fri, 21 Jul 2000 17:22:15 -0700 (PDT)" <200007220022.RAA02194@medusa.kfu.com> References: <200007220022.RAA02194@medusa.kfu.com> User-Agent: Wanderlust/1.1.0 (Overjoyed) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 9) (Canyonlands) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Fri, 21 Jul 2000 17:22:15 -0700 (PDT), Nick Sayer wrote: > > Something changed very recently in the dhcp client stuff that seems > to have broke my -current machine's ability to be a dhcp client. > > The symptom is that I see > > ifconfig: netmask 255.255.255.224: bad value > > come out of the script invocation, and the ip address does not get > set. My -current machine (cvsupped only a few hours ago) has the same problem. > If I echo out the parameters and type in THE EXACT SAME command line > myself, it works just fine. I suspect some sort of bizarre > quoting conspiracy. :-) Maybe here? (in http://www.freebsd.org/cgi/cvsweb.cgi/src/contrib/isc-dhcp/client/scripts/freebsd.diff?r1=1.11&r2=1.12) - if [ x$old_ip_address = x ] || [ x$old_ip_address != x$new_ip_address ] || \ - [ x$reason = xBOUND ] || [ x$reason = xREBOOT ]; then - ifconfig $interface inet $new_ip_address $new_netmask_arg \ - $new_broadcast_arg $medium + if [ "x$old_ip_address" = "x" ] || [ "x$old_ip_address" != "x$new_ip_address" ] || \ + [ "x$reason" = "xBOUND" ] || [ "x$reason" = "xREBOOT" ]; then + ifconfig "$interface" inet "$new_ip_address" "$new_netmask_arg" \ + "$new_broadcast_arg" "$medium" --------------------------- Tatsumi Hosokawa hosokawa@itc.keio.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 4:38:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id D991B37BE2A for ; Sat, 22 Jul 2000 04:38:18 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (qmail 5616 invoked from network); 22 Jul 2000 11:38:10 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 22 Jul 2000 11:38:10 -0000 Date: Sat, 22 Jul 2000 21:38:21 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: John Baldwin Cc: Warner@pike.osd.bsdi.com, Losh , dwhite@resnet.uoregon.edu, freebsd-current@FreeBSD.ORG Subject: Re: No /boot/loader In-Reply-To: <200007211706.KAA67811@pike.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jul 2000, John Baldwin wrote: > Bruce Evans wrote: > > On Thu, 20 Jul 2000, John Baldwin wrote: > > > ... > > > unused even though it is, in fact, used. The fact that it works at all is > > > due to brokenness on our part (we don't check that partitions in a disklabel > > > fit in the parent slice) and also results in several hacks in various portions > > > of the code where we have to check for such bogusness and work around it. > > > > No, that's wrong too :-) . We a lot of checking that partitions in a > > disklabel fit in the parent slice. We clip partitions that don't fit in > > various ways for backwards compatibility. > Erm, maybe we clip partitions which aren't dangerously dedicated, but > I've created test dangerously dedicated disks, and we certainly do not > bother to actually change any of the slice information when we do so. > disklabel(8) does for truly dedicated, but libdisk doesn't for dangerously > dedicated. The dangerously dedicated case has one slice covering the whole disk. We unclip the slice info from the magic 50000 sectors to the size of the whole disk (as reported by the driver) to handle this. Reading the slice info using DIOCGSLICEINFO shows the full size, but no changes are made to the mbr. This is in the kernel. I'm not sure exactly what libdisk does, but it is constrained by what the kernel will accept. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 4:42: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 7D2A637BE2A for ; Sat, 22 Jul 2000 04:41:57 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.9.3/8.9.3) with ESMTP id MAA05006; Sat, 22 Jul 2000 12:36:31 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id MAA12122; Sat, 22 Jul 2000 12:36:50 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200007221136.MAA12122@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Brian Somers Cc: Michael Lucas , current@FreeBSD.org, brian@Awfulhak.org Subject: Re: MS CHAP v2 in -current? In-Reply-To: Message from Brian Somers of "Sat, 22 Jul 2000 11:01:22 BST." <200007221001.LAA84762@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 22 Jul 2000 12:36:50 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Ping... > > > > Does anyone know if ms chap v2 will be integrated into -current any > > time soon? I need it for pptpclient. > > > > If anyone has any patches they'd like public testing on, I'll volunteer. :) > > I have some code submitted by Nathan Blinkert - I'll apply them later > today. Oops, it doesn't work yet, and I'm off on holidays tomorrow, so it's not a good idea for me to commit I'm afraid. I've put the patch at http://www.Awfulhak.org/mschap2.patch for those interested.... > > ==ml -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 5: 0:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id C694737B5C9; Sat, 22 Jul 2000 05:00:29 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id OAA06345; Sat, 22 Jul 2000 14:00:26 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007221200.OAA06345@grimreaper.grondar.za> To: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: In-Reply-To: ; from Kris Kennaway "Sat, 22 Jul 2000 02:21:15 MST." Date: Sat, 22 Jul 2000 14:00:26 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 22 Jul 2000, Mark Murray wrote: > > > Because of Yarrow's cryptographic protection of its internal state, its > > frequent reseeds and its clever geneation mechanism, this paradigm is > > less important - the output is 256-bit safe (Blowfish safe) for any size > > of output[*]. When you read 1000 bits, I am not selling you 1000 bits > > each guaranteed random, I am selling you 1000 bits that are predictable > > within the constraints of needing to crack 256-bit Blowfish. > > So what it if I want/need 257 bits? :-) Read them. You'll get them. If you want higher quality randomness than Yarrow gives, read more than once. Do other stuff; play. Don't get stuck in the "I have exhausted the randomness pool" loop; Yarrow does not play that game. From the Yarrow paper: ``Yarrow's outputs are cryptographically derived. Systems that use Yarrow's outputs are no more secure than the generation mechanism used.'' We currently have Yarrow-256(Blowfish); wanna make it Yarrow-1024? I could make it so. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 5:29:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from soso.eecs.umich.edu (soso.eecs.umich.edu [141.213.4.24]) by hub.freebsd.org (Postfix) with ESMTP id 35A2C37B8B9 for ; Sat, 22 Jul 2000 05:29:47 -0700 (PDT) (envelope-from binkertn@umich.edu) Received: from localhost (binkertn@localhost) by soso.eecs.umich.edu (8.10.0.Beta10/8.10.0.Beta6) with ESMTP id e6MCTNH29877; Sat, 22 Jul 2000 08:29:27 -0400 (EDT) X-Authentication-Warning: soso.eecs.umich.edu: binkertn owned process doing -bs Date: Sat, 22 Jul 2000 08:29:23 -0400 (EDT) From: Nathan Binkert X-Sender: binkertn@soso.eecs.umich.edu To: Brian Somers Cc: Michael Lucas , current@FreeBSD.ORG Subject: Re: MS CHAP v2 in -current? In-Reply-To: <200007221136.MAA12122@hak.lan.Awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The patch does work for client side. I have verified that I can connect to a windows server using chap v2, but I forgot to do something for server. Shouldn't take me long. If you need the server part before Brian gets back, let me know. Nathan > Oops, it doesn't work yet, and I'm off on holidays tomorrow, so it's > not a good idea for me to commit I'm afraid. > > I've put the patch at http://www.Awfulhak.org/mschap2.patch for those > interested.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 8: 4:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 6E47B37B5C5 for ; Sat, 22 Jul 2000 08:04:14 -0700 (PDT) (envelope-from jhb@pike.osd.bsdi.com) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id IAA98549; Sat, 22 Jul 2000 08:03:44 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200007221503.IAA98549@pike.osd.bsdi.com> Subject: Re: No /boot/loader In-Reply-To: from Bruce Evans at "Jul 22, 2000 09:38:21 pm" To: Bruce Evans Date: Sat, 22 Jul 2000 08:03:44 -0700 (PDT) Cc: imp@village.org, dwhite@resnet.uoregon.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > On Fri, 21 Jul 2000, John Baldwin wrote: > > > Bruce Evans wrote: > > > On Thu, 20 Jul 2000, John Baldwin wrote: > > > > ... > > > > unused even though it is, in fact, used. The fact that it works at all is > > > > due to brokenness on our part (we don't check that partitions in a disklabel > > > > fit in the parent slice) and also results in several hacks in various portions > > > > of the code where we have to check for such bogusness and work around it. > > > > > > No, that's wrong too :-) . We a lot of checking that partitions in a > > > disklabel fit in the parent slice. We clip partitions that don't fit in > > > various ways for backwards compatibility. > > > Erm, maybe we clip partitions which aren't dangerously dedicated, but > > I've created test dangerously dedicated disks, and we certainly do not > > bother to actually change any of the slice information when we do so. > > disklabel(8) does for truly dedicated, but libdisk doesn't for dangerously > > dedicated. > > The dangerously dedicated case has one slice covering the whole disk. We > unclip the slice info from the magic 50000 sectors to the size of the whole > disk (as reported by the driver) to handle this. Reading the slice info > using DIOCGSLICEINFO shows the full size, but no changes are made to the > mbr. This is in the kernel. I'm not sure exactly what libdisk does, but > it is constrained by what the kernel will accept. > > Bruce Ok, so we normally do clip slice information, except in the case of a dangerously dedicated slice. Which works fine so long as no one ever creates a 50000 block slice in the 4th entry, as we will expand that slice to cover all of the disk. It also means that kernel, like the loader, has to special case when it sees a dangeriously dedicated slice, which is rather evil, IMO. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 8:31:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 770EB37B66C; Sat, 22 Jul 2000 08:31:45 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 38DFD52; Sat, 22 Jul 2000 11:31:43 -0400 (AST) Message-ID: <3979BE5F.9FADF58A@vangelderen.org> Date: Sat, 22 Jul 2000 11:31:43 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Sat, 22 Jul 2000, Mark Murray wrote: > > > Lots of references: Schneier's "Applied Cryptography" talks about > > using Good Hashes for crypto and Good Crypto for hashes. Schneier's > > site at www.counterpane.com will give you plenty. > > I havent been able to get my hands on Applied Cryptography, but I don't > recall seeing anything like this on the website. I'll check again. > > > The differnce with the old system and Yarrow is yarrow's self-recovery > > property; Yarrow screens its internal state from the ouside world > > very heavily, and provides enough perturbation of it from its > > copious :-) entropy harvesting to keep the state safe from compromise. > > Yeah, I know all this and agree that Yarrow makes a better /dev/urandom, > but it doesn't change the fact that Yarrow-256 is only good for 256 bits > of entropy between reseeding operations. You can pull all you want out of > it but will never get more than 256 bits until it reseeds. You don't care in practice, 256 bits are unguessable. If you do care, you load a different random module :-) Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 8:38: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 5930037B9A1; Sat, 22 Jul 2000 08:38:00 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 29E6852; Sat, 22 Jul 2000 11:37:58 -0400 (AST) Message-ID: <3979BFD6.9DFEE454@vangelderen.org> Date: Sat, 22 Jul 2000 11:37:58 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Fri, 21 Jul 2000, Mark Murray wrote: > > > Section 2.1, last paragraph: > > "If a system is shut down, and restarted, it is desirable to store some > > high-entropy data (such as the key) in non-volatile memory. This allows > > the PRNG to be restarted in an unguessable state at the next restart. We > > call this data the reseed file." > > I'm all for storing a sample at shutdown and using it to help seed the > PRNG at startup, but it shouldn't be the only seed used (for example, the > case where the system has never been shut down (cleanly) before and so has > no pre-existing seed file is a BIG corner case to consider since thats how > the system is at the time it first generates SSH keys after a fresh > install). > > It might be only an academic vulnerability, but if someone can read your > HD during the time the system is shut down then I'd prefer them not to > know the precise state when the system next starts up again. Yes, if they > can read they can probably also write, but it seems like a mistake when > there's nothing really gained by saving the complete state, as opposed to > an extract. Well, academic or not (not when you run financial transactioning systems on FreeBSD) you can edit rc.shutdown to not write out a seed file. You don't have to use it but it's good that it's there. Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 9:38: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 579BD37C320 for ; Sat, 22 Jul 2000 09:37:54 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id CAA17771; Sun, 23 Jul 2000 02:37:30 +1000 Date: Sun, 23 Jul 2000 02:37:43 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: John Baldwin Cc: imp@village.org, dwhite@resnet.uoregon.edu, freebsd-current@FreeBSD.ORG Subject: Re: No /boot/loader In-Reply-To: <200007221503.IAA98549@pike.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Jul 2000, John Baldwin wrote: > Bruce Evans wrote: > > The dangerously dedicated case has one slice covering the whole disk. We > > unclip the slice info from the magic 50000 sectors to the size of the whole > > disk (as reported by the driver) to handle this. Reading the slice info > > using DIOCGSLICEINFO shows the full size, but no changes are made to the > > mbr. This is in the kernel. I'm not sure exactly what libdisk does, but > > it is constrained by what the kernel will accept. > > > > Bruce Please don't quote signatures or other irrelevant points. > Ok, so we normally do clip slice information, except in the case of a > dangerously dedicated slice. Which works fine so long as no one ever There is nothing to clip, since the dangerously dedicated slice is the whole disk. > creates a 50000 block slice in the 4th entry, as we will expand that sector > slice to cover all of the disk. It also means that kernel, like the loader, Normal 50000-sector slices are very unlikely to be misinterpreted as dangerously dedicated ones. A 5000-sector slice is (or should be) only interpreted as dangerously dedicated if: 1. all bytes in the partition table have certain values, in particular: 2. the slice type is 0xA5 ("FreeBSD"). 3. the starting sector is 0 absolute. This is is strictly invalid for normal slices. 4. the ending C/H/S is 255/255/255. 50000-sector slices starting at absolute 0 can't reach that far. > has to special case when it sees a dangeriously dedicated slice, which is > rather evil, IMO. It's no more evil than the boot signature. The garbage in the partition table is treated as a signature. It is more authoritative because it is larger and more magic. The loader really shouldn't know about the dangerously dedicated case. Its detection of the dangerously dedicated case is buggy. It only checks the conditions (2) and (3) above (and that the slice size is 50000). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 10:41:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from lola.heim10.tu-clausthal.de (lola.heim10.tu-clausthal.de [139.174.241.25]) by hub.freebsd.org (Postfix) with ESMTP id E11FA37B90F for ; Sat, 22 Jul 2000 10:41:51 -0700 (PDT) (envelope-from norbert.irmer@heim9.tu-clausthal.de) Received: from heim9.tu-clausthal.de (localhost.heim10.tu-clausthal.de [127.0.0.1]) by lola.heim10.tu-clausthal.de (8.9.3/8.9.3) with ESMTP id TAA72682 for ; Sat, 22 Jul 2000 19:41:48 +0200 (CEST) (envelope-from norbert.irmer@heim9.tu-clausthal.de) Message-ID: <3979DCDC.CFFFD61A@heim9.tu-clausthal.de> Date: Sat, 22 Jul 2000 19:41:48 +0200 From: Norbert Irmer X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: buildworld failure Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsup'ed the lastest sources of ~current, but got the following after only a few seconds cd /usr/src/usr.sbin/mtree; make _EXTRADEPEND echo mtree: /usr/obj/usr/src/i386/usr/lib/libc.a /usr/obj/usr/src/i386/usr/lib/libmd.a >> .depend cc -O -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/mtree/compare.c cc -O -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/mtree/../../usr.bin/cksum/crc.c cc -O -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/mtree/create.c cc -O -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/mtree/excludes.c cc -O -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/mtree/misc.c /usr/src/usr.sbin/mtree/misc.c: In function `flags_to_string': /usr/src/usr.sbin/mtree/misc.c:120: warning: assignment makes pointer from integer without a cast cc -O -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/mtree/mtree.c cc -O -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/mtree/spec.c cc -O -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/mtree/verify.c cc -O -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/usr/src/i386/usr/include -o mtree compare.o crc.o create.o excludes.o misc.o mtree.o spec.o verify.o -lmd misc.o: In function `flags_to_string': misc.o(.text+0x89): undefined reference to `fflagstostr' spec.o: In function `set': spec.o(.text+0x5f5): undefined reference to `strtofflags' *** Error code 1 Do I have to do something special before I can do a 'make buildworld', or is ~current currently broken ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 10:49:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 67AEC37B90F; Sat, 22 Jul 2000 10:49:34 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id KAA43756; Sat, 22 Jul 2000 10:49:31 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200007221749.KAA43756@gndrsh.dnsmgr.net> Subject: Re: randomdev entropy gathering is really weak In-Reply-To: from Kris Kennaway at "Jul 21, 2000 06:54:54 pm" To: kris@FreeBSD.ORG (Kris Kennaway) Date: Sat, 22 Jul 2000 10:49:30 -0700 (PDT) Cc: mark@grondar.za (Mark Murray), jeroen@vangelderen.org (Jeroen C. van Gelderen), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 21 Jul 2000, Mark Murray wrote: > > > Section 2.1, last paragraph: > > "If a system is shut down, and restarted, it is desirable to store some > > high-entropy data (such as the key) in non-volatile memory. This allows > > the PRNG to be restarted in an unguessable state at the next restart. We > > call this data the reseed file." > > I'm all for storing a sample at shutdown and using it to help seed the > PRNG at startup, but it shouldn't be the only seed used (for example, the > case where the system has never been shut down (cleanly) before and so has > no pre-existing seed file is a BIG corner case to consider since thats how > the system is at the time it first generates SSH keys after a fresh > install). > > It might be only an academic vulnerability, but if someone can read your > HD during the time the system is shut down then I'd prefer them not to > know the precise state when the system next starts up again. Yes, if they > can read they can probably also write, but it seems like a mistake when > there's nothing really gained by saving the complete state, as opposed to > an extract. And for folks like us who do mass installs via dd if=/dev/da1 of=/dev/da2, where da1 is a mastered image created via ``make installworld DESTDIR=/mnt'', the corner case is very large. I have been bitten by an event where the master disk was booted once before replication, and thus all systems had _IDENTICAL_ /etc/ssh contents. Not a very good idea !! We have amended the manufacturing process now, so that part of the disk replication is the nuking and regeneration of /etc/ssh. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 11:17:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id A308637BBC4 for ; Sat, 22 Jul 2000 11:17:05 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (qmail 1233 invoked from network); 22 Jul 2000 18:17:01 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 22 Jul 2000 18:17:01 -0000 Date: Sun, 23 Jul 2000 04:17:13 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Norbert Irmer Cc: freebsd-current@FreeBSD.ORG Subject: Re: buildworld failure In-Reply-To: <3979DCDC.CFFFD61A@heim9.tu-clausthal.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Jul 2000, Norbert Irmer wrote: > I cvsup'ed the lastest sources of ~current, but got the > following after only a few seconds > > cd /usr/src/usr.sbin/mtree; make _EXTRADEPEND > ... > cc -O -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/usr/src/i386/usr/include -o mtree compare.o crc.o > create.o excludes.o misc.o mtree.o spec.o verify.o -lmd > misc.o: In function `flags_to_string': > misc.o(.text+0x89): undefined reference to `fflagstostr' > spec.o: In function `set': > spec.o(.text+0x5f5): undefined reference to `strtofflags' > *** Error code 1 > > Do I have to do something special before I can do a 'make buildworld', or > is ~current currently broken ? Bootstrapping from 4.0 and previous versions to 4.1 and -current is broken, because mtree depends on new library features but must be built before the new libraries. You have to somehow bootstrap the new libraries. Maybe copy them from a current snapshot. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 12: 1:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (ftp.webmaster.com [209.10.218.74]) by hub.freebsd.org (Postfix) with ESMTP id 181FA37B5A7; Sat, 22 Jul 2000 12:01:47 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([216.152.68.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Sat, 22 Jul 2000 12:01:11 -0700 From: "David Schwartz" To: "Mark Murray" , "Kris Kennaway" Cc: Subject: RE: randomdev entropy gathering is really weak Date: Sat, 22 Jul 2000 12:01:44 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <200007221200.OAA06345@grimreaper.grondar.za> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From the Yarrow paper: > ``Yarrow's outputs are cryptographically derived. Systems that > use Yarrow's > outputs are no more secure than the generation mechanism used.'' > > We currently have Yarrow-256(Blowfish); wanna make it Yarrow-1024? I could > make it so. > > M > -- > Mark Murray It doesn't matter if it's Yarrow-256, Yarrow-1024, or Yarrow-1000000000. /dev/random should block if the system does not contain as much real entropy as the reader desires. Otherwise, the PRNG implementation will be the weakest link for people who have deliberately selected higher levels of protection from cryptographic attack. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 12:17:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.targetnet.com (mail.targetnet.com [207.245.246.3]) by hub.freebsd.org (Postfix) with ESMTP id 5389837B69C for ; Sat, 22 Jul 2000 12:17:25 -0700 (PDT) (envelope-from james@targetnet.com) Received: from james by mail.targetnet.com with local (Exim 3.02 #1) id 13G4lz-0000ES-00; Sat, 22 Jul 2000 15:17:19 -0400 Date: Sat, 22 Jul 2000 15:17:19 -0400 From: James FitzGibbon To: "Thomas T. Veldhouse" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Journaling Filesystem ? Message-ID: <20000722151719.B99818@targetnet.com> References: <017101bff34e$12ca9c10$dd29680a@tgt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <017101bff34e$12ca9c10$dd29680a@tgt.com> Organization: Targetnet.com Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Thomas T. Veldhouse (veldy@veldy.net) [000721 16:01]: > Hello. I was wondering if there is any work on a Journaling filesystem to > possible replace, or as an alternative to UFS. I have been following > ReiserFS for Linux quite closely, and I have had the chance to experiment > with it. It seems to be coming along nicely and the performance is great. > Are there plans for something along this line for FreeBSD? Is there a > project underway? At the Usenix 2000 Conference, a paper comparing Softupdates to a Journalling Filesystem was presented. The author said that the tests were performed on a FreeBSD box. AFAIK, the code is not yet available, but one of the other attendees mentioned that it would be 'some time in the near future'. The journally system allowed for the journal to exist as a file on the filesystem in question, or on a separate partition (which would be mounted synchronously to provide a level of protection from crashes). That having been said, the performance of the filesystem was not significantly different from softupdates. You can get at the paper if you're a Usenix member. The authors included Margo Selzer and Kirk McKusick, but the talk was given by another of the authors whose name I can't recall at the moment. -- j. James FitzGibbon james@targetnet.com Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 12:40:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id C8AE537B8BF for ; Sat, 22 Jul 2000 12:40:16 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id VAA37028; Sat, 22 Jul 2000 21:39:57 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007221939.VAA37028@grimreaper.grondar.za> To: "David Schwartz" Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak References: In-Reply-To: ; from "David Schwartz" "Sat, 22 Jul 2000 12:01:44 MST." Date: Sat, 22 Jul 2000 21:39:56 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > /dev/random should block if the system does not contain as much real entropy > as the reader desires. Otherwise, the PRNG implementation will be the > weakest link for people who have deliberately selected higher levels of > protection from cryptographic attack. I don't want to rehash this thread from the beginning. Please go back, read the Yarrow paper, and recognise that Yarrow is not an entropy-counter, it is a cryptographically secure PRNG. The "count random bits and block" model does not apply. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 14:33:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom0-159.telepath.com [216.14.0.159]) by hub.freebsd.org (Postfix) with SMTP id 21A2C37B8BF for ; Sat, 22 Jul 2000 14:33:42 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 17542 invoked by uid 100); 22 Jul 2000 20:38:15 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14714.1591.596666.737427@guru.mired.org> Date: Sat, 22 Jul 2000 15:38:15 -0500 (CDT) To: current@freebsd.org Subject: Perl libraries install in wrong place... X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe this belongs in ports, but it looks like the problem is actually somewhere inside the Perl build, which I think means it belongs here. Basically, some (all?) ports that install perl libraries want to install them in /usr/local, without paying proper heed to PREFIX. Things wind up in /usr/local, and I then get complaints about missing files for them when I deinstall the port. Further, ${LOCALBASE}/lib/perl5 has no actual files in it - just directories. ImageMagick is one such port. A make install generates the following output fragment: Manifying blib/man3/Image::Magick.3 Installing /usr/local/lib/perl5/site_perl/5.6.0/mach/auto/Image/Magick/Magick.so Installing /usr/local/lib/perl5/site_perl/5.6.0/mach/auto/Image/Magick/Magick.bs Files found in blib/arch: installing files in blib/lib into architecture dependent library tree Installing /usr/local/lib/perl5/site_perl/5.6.0/mach/auto/Image/Magick/autosplit.ix Installing /usr/local/lib/perl5/site_perl/5.6.0/mach/Image/Magick.pm Installing /usr/local/lib/perl5/5.6.0/man/man3/Image::Magick.3 Writing /usr/local/lib/perl5/site_perl/5.6.0/mach/auto/Image/Magick/.packlist Even though LOCALBASE is set to /usr/opt in /etc/make.conf. Only the Perl portion of the port does this, and Perl has magic that I don't understand for doing such libraries. Since I don't find the string /local/ in the Perl stuff, this makes me think it may be in the Perl configuration, not the port. Any help from someone who understands the perl package system would be greatly appreciated. Thanx, ; Sat, 22 Jul 2000 14:49:04 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 09BBFF3; Sat, 22 Jul 2000 14:49:04 -0700 (PDT) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) with ESMTP id OAA09053; Sat, 22 Jul 2000 14:49:03 -0700 (PDT) Message-ID: <397A16CE.E49EB0D@cup.hp.com> Date: Sat, 22 Jul 2000 14:49:02 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Evans Cc: freebsd-current@FreeBSD.ORG Subject: Re: buildworld failure References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > > Bootstrapping from 4.0 and previous versions to 4.1 and -current is broken, > because mtree depends on new library features but must be built before the > new libraries. You have to somehow bootstrap the new libraries. Maybe > copy them from a current snapshot. Grrr... Is there a clean way to fix this, other than reverting the -L incompatibility? Did we bump the libc version number when the strtofflags/fflagstostr functions went in? -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 15:11:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 3D4BA37B582; Sat, 22 Jul 2000 15:11:40 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA28590; Sat, 22 Jul 2000 15:11:40 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 22 Jul 2000 15:11:39 -0700 (PDT) From: Kris Kennaway To: Mark Murray Cc: current@FreeBSD.org Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <200007221200.OAA06345@grimreaper.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Jul 2000, Mark Murray wrote: > > So what it if I want/need 257 bits? :-) > > Read them. You'll get them. If you want higher quality randomness than > Yarrow gives, read more than once. Do other stuff; play. Don't get stuck > in the "I have exhausted the randomness pool" loop; Yarrow does not play > that game. I think you're missing the point. The only way I can get a random number with more than n bits of entropy out of Yarrow-n is if I sample either side of a reseed operation, which in general comes down to timing guesswork and having to make assumptions about the PRNG implementation. If you want to generate a cryptographic key of length n bits then you really want >n bits of entropy in the random source you're deriving it from, otherwise your key is actually much weaker than advertised because it's easier for the attacker to attack the state of the PRNG that derived it than to attack the key itself. > >From the Yarrow paper: > ``Yarrow's outputs are cryptographically derived. Systems that use Yarrow's > outputs are no more secure than the generation mechanism used.'' > > We currently have Yarrow-256(Blowfish); wanna make it Yarrow-1024? I could > make it so. Well, if we did that then how about generating 2048-bit keys? :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 15:11:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix1.free.fr (postfix1.free.fr [212.27.32.21]) by hub.freebsd.org (Postfix) with ESMTP id 77A5937BA2F for ; Sat, 22 Jul 2000 15:11:38 -0700 (PDT) (envelope-from jaco@titine.fr.eu.org) Received: from titine.fr.eu.org (toulouse-1-4-154.dial.proxad.net [213.228.4.154]) by postfix1.free.fr (Postfix) with ESMTP id 2B21028188 for ; Sun, 23 Jul 2000 00:11:31 +0200 (MEST) Received: by titine.fr.eu.org (Postfix, from userid 1000) id 9ADCE14827; Sat, 22 Jul 2000 23:55:51 +0200 (CEST) X-Attribution: Jaco To: current@FreeBSD.ORG Subject: Re: Perl libraries install in wrong place... References: <14714.1591.596666.737427@guru.mired.org> From: Eric Jacoboni Date: 22 Jul 2000 23:55:50 +0200 In-Reply-To: Mike Meyer's message of "Sat, 22 Jul 2000 15:38:15 -0500 (CDT)" Message-ID: <87k8edu8wp.fsf@titine.fr.eu.org> Lines: 17 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Mike" =3D=3D Mike Meyer writes: Mike> Basically, some (all?) ports that install perl libraries want to Mike> install them in /usr/local, without paying proper heed to Mike> PREFIX. Things wind up in /usr/local, and I then get complaints about Mike> missing files for them when I deinstall the port. Further, Mike> ${LOCALBASE}/lib/perl5 has no actual files in it - just Mike> directories. Yes, same for me... It seems there is a mess with Perl ports since the 5.6.0 upgrade. For my own, i've decided to make all modules by hand, waiting for the fix. --=20 --------------------------------------------------------- =C9ric Jacoboni =AB No sport, cigars! =BB (W. Churchill) --------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 15:19:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 8EA7637BAEE; Sat, 22 Jul 2000 15:19:29 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA29493; Sat, 22 Jul 2000 15:19:29 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 22 Jul 2000 15:19:29 -0700 (PDT) From: Kris Kennaway To: "Jeroen C. van Gelderen" Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <3979BE5F.9FADF58A@vangelderen.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Jul 2000, Jeroen C. van Gelderen wrote: > You don't care in practice, 256 bits are unguessable. Actually, I do..that's the entire point of using long keys. > If you do care, you load a different random module :-) The core of my complaint is that even though our old PRNG did crappy entropy handling, we used to have such a method, which is now gone. I'd like to see yarrow hang off /dev/urandom and have /dev/random tap directly into the entropy pool (perhaps a third pool separate from Yarrow's fast/slow) so I can generate my large keys safely. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 15:35:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from lola.heim10.tu-clausthal.de (lola.heim10.tu-clausthal.de [139.174.241.25]) by hub.freebsd.org (Postfix) with ESMTP id 3564337B506 for ; Sat, 22 Jul 2000 15:35:18 -0700 (PDT) (envelope-from norbert.irmer@heim9.tu-clausthal.de) Received: from heim9.tu-clausthal.de (localhost.heim10.tu-clausthal.de [127.0.0.1]) by lola.heim10.tu-clausthal.de (8.9.3/8.9.3) with ESMTP id AAA97539 for ; Sun, 23 Jul 2000 00:35:12 +0200 (CEST) (envelope-from norbert.irmer@heim9.tu-clausthal.de) Message-ID: <397A219C.6BE5B7@heim9.tu-clausthal.de> Date: Sun, 23 Jul 2000 00:35:08 +0200 From: Norbert Irmer X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: buildworld failure References: <397A16CE.E49EB0D@cup.hp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marcel Moolenaar wrote: > > Bruce Evans wrote: > > > > Bootstrapping from 4.0 and previous versions to 4.1 and -current is broken, > > because mtree depends on new library features but must be built before the > > new libraries. You have to somehow bootstrap the new libraries. Maybe > > copy them from a current snapshot. > > Grrr... > > Is there a clean way to fix this, other than reverting the -L > incompatibility? > Did we bump the libc version number when the strtofflags/fflagstostr > functions went in? > Thanks for the information. I could solve this dilemma by adding the source file 'strtofflags.c' from the new 'libc' sources temporarily to the sources of 'mtree'. Then I could do a 'buildworld'. Afterwards I replaced the old libc with the new libc, removed 'strtofflags.c' from the sources of 'mtree' again, and rebuild it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 16: 0:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id 7A4ED37B5D6 for ; Sat, 22 Jul 2000 16:00:18 -0700 (PDT) (envelope-from jazepeda@pacbell.net) Received: from ppp-207-214-149-176.snrf01.pacbell.net ([207.214.149.176]) by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FY400GXUFV33K@mta6.snfc21.pbi.net> for freebsd-current@FreeBSD.ORG; Sat, 22 Jul 2000 15:59:33 -0700 (PDT) Date: Sat, 22 Jul 2000 16:00:29 -0700 (PDT) From: Alex Zepeda Subject: Re: missing idea.h ... ? In-reply-to: X-Sender: alex@zippy.pacbell.net To: The Hermit Hacker Cc: Will Andrews , freebsd-current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jul 2000, The Hermit Hacker wrote: > If it helps any, I setup an anoncvs mirror for most of the stuff ... not > sure if it helps any, since you are working off of snapshots, but its > updated every 4hrs from the central repository, and the CVSROOT for it was > announced on kde-devel ... What really needs to be done is fixing up of the kconsole grantpty code, the socket credentials code in kdesu(d) as well as some of the system info gathering for kcontrol as well as ksysguard. But that's just if you're looking for some code to hack on :) - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 17: 7: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 8F67937C36E; Sat, 22 Jul 2000 17:06:53 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 411404F; Sat, 22 Jul 2000 20:06:46 -0400 (AST) Message-ID: <397A3716.A14DBF38@vangelderen.org> Date: Sat, 22 Jul 2000 20:06:46 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Sat, 22 Jul 2000, Jeroen C. van Gelderen wrote: > > > You don't care in practice, 256 bits are unguessable. > > Actually, I do..that's the entire point of using long keys. I agree that you need long RSA keys ... but the real discussion isn't really about key length but rather about the overall complexity of attacking the key: The complexity of factoring a 1024-bit RSA keys is on the order of 2^71 operations. For a 3214-bit key it is roughly equivalent to 2^101 complexity. (See [1][2] for gloriously arcane details.) Now, assuming that you generate a 3214-bit RSA key from a 256-bit entropy pool, the complexity of factoring it (2^101) is much lower than the complexity of guessing the entropy pool from which it was generated (2^256); Actually, factoring is the most efficient attack up to the point where you are using something like a 13841-bit RSA key[3]. So, for practical key purposes Yarrow-256 is in excess of complexity requirements. (I can't say anything about other uses than crypto but seeing as the promise of /dev/random is cryptographically secure random numbers this should not pose a problem.) That said, there is nothing to prevent the system admin from tweaking the Yarrow security parameters so that Yarrow will only spit out as many bits or pseudo-randomness as it gathers bits of entropy.[4] Check out http://www.cryptosavvy.com/table.htm and preferrably the full paper at http://www.cryptosavvy.com/cryptosizes.pdf if you remain unconvinced :-) Cheers, Jeroen [1] Numbers from http://www.cryptosavvy.com/table.htm . [2] Yes, this sortof means that using >= 128-bit keys is overkill for most applications that use assymmetric algorithms for key-negotiation :-) [3] http://www.cryptosavvy.com/suggestions.htm [4] And if you really would like to restore the old semantics of /dev/[u]random, you could code it into Yarrow. Just make /dev/random block based on the entropy estimation that Yarrow keeps anyway. -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 17:41:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 57D6C37B5BD; Sat, 22 Jul 2000 17:41:15 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id RAA41916; Sat, 22 Jul 2000 17:41:15 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 22 Jul 2000 17:41:15 -0700 (PDT) From: Kris Kennaway To: "Jeroen C. van Gelderen" Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: randomdev entropy gathering is really weak In-Reply-To: <397A3716.A14DBF38@vangelderen.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Jul 2000, Jeroen C. van Gelderen wrote: > I agree that you need long RSA keys ... but the real > discussion isn't really about key length but rather about > the overall complexity of attacking the key: Okay, using RSA keys wasn't the best example to pick, but Yarrow also seems easy to misuse in other cases: for example if you want to generate multiple 256-bit symmetric keys (or other random data) at the same time, each additional key after the first won't contain any additional entropy, so if you break the state of the PRNG at the time the first one was generated you get the others for free (until the thing reseeds). This design tradeoff is discussed in section 4.1 of the paper. > That said, there is nothing to prevent the system admin > from tweaking the Yarrow security parameters so that > Yarrow will only spit out as many bits or pseudo-randomness > as it gathers bits of entropy.[4] Well, I don't see a way to tune this without modifying the Yarrow design, since the entropy pool is intentionally decoupled from the output mechanism, and it seems like it would add additional (unnecessary) overhead anyway to use it in that fashion. Indications are we can probably get quite a lot of usable entropy from a standard system (on the order of many kilobytes per second - but I need to read more of the literature about processing of entropy samples) - in this case I think maintaining a third pool which is directly tapped by /dev/random, and leaving Yarrow sitting behind /dev/urandom is the way to go. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 18:43:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail1.nc.rr.com (fe1.southeast.rr.com [24.93.67.48]) by hub.freebsd.org (Postfix) with ESMTP id 336B137B709 for ; Sat, 22 Jul 2000 18:43:31 -0700 (PDT) (envelope-from tstromberg@rtci.com) Received: from sudden.detachment.org ([24.25.3.165]) by mail1.nc.rr.com with Microsoft SMTPSVC(5.5.1877.357.35); Sat, 22 Jul 2000 21:43:25 -0400 Received: from rtci.com (localhost [127.0.0.1]) by sudden.detachment.org (8.9.3/8.9.3) with ESMTP id JAA01089 for ; Wed, 19 Jul 2000 09:23:25 -0400 (EDT) (envelope-from tstromberg@rtci.com) Message-ID: <3975ABCC.2855103F@rtci.com> Date: Wed, 19 Jul 2000 09:23:24 -0400 From: "Thomas R. Stromberg" Organization: Research Triangle Commerce, Inc. X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: SBLive (value) References: <200007190443.VAA72036@realtime.exit.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Frank Mayhar wrote: > > Kent Hauser wrote: > > I've again been trying to get my sound support working. > > The problem I have is the machine panic's (RAM parity error) > > whenever I (for instance) play an mp3. > > This is a known problem with the SBLive and machines with ECC memory. So > far no sign of a fix for it. > > Jordan, if you read this, please email me the address to send the memory > stick. I'll contribute it to the cause. (I'll need a receipt, though. ;-) > -- > Frank Mayhar frank@exit.com http://www.exit.com/ > Exit Consulting http://store.exit.com/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message I get the panic myself without ECC memory. I posted a crash dump myself a few weeks ago. This also affects -STABLE I believe. Would be neat to fix for 4.1, but probably a little late. The GNATS entry is at: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=19022 / Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 21:38:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id CEC2937B803 for ; Sat, 22 Jul 2000 21:38:47 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e6N4ccD93571; Sat, 22 Jul 2000 21:38:39 -0700 (PDT) Date: Sat, 22 Jul 2000 21:38:38 -0700 (PDT) From: Doug White To: Bruce Evans Cc: Norbert Irmer , freebsd-current@FreeBSD.ORG Subject: Re: buildworld failure In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Jul 2000, Bruce Evans wrote: > > Do I have to do something special before I can do a 'make buildworld', or > > is ~current currently broken ? > > Bootstrapping from 4.0 and previous versions to 4.1 and -current is broken, > because mtree depends on new library features but must be built before the > new libraries. You have to somehow bootstrap the new libraries. Maybe > copy them from a current snapshot. Incidentally, whoever broke this should be shot and strung -- I thought that upgrading from the latest -STABLE to -CURRENT was a supported operation? Copying files from snapshots to bootstrap yourself is just plain unacceptable. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 21:43:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat193.142.mpoweredpc.net [142.177.193.142]) by hub.freebsd.org (Postfix) with ESMTP id 7A05037B565 for ; Sat, 22 Jul 2000 21:43:43 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id BAA82473 for ; Sun, 23 Jul 2000 01:41:45 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 23 Jul 2000 01:41:45 -0300 (ADT) From: The Hermit Hacker To: freebsd-current@freebsd.org Subject: KDE2 hangs in 5.0-CURRENT but not in 4.1RC ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been spending the past few days trying to get KDE2 from anoncvs to work on my 5.0-CURRENT machine, totally unsuccessfully. I can get it to compile and then run 'startx', but it appears to hang on the ksmserver process ... Will Andrews, who is working on the KDE2 ports, has the same thing running on his 4.1RC system, so I'm starting to wonder if the "bug" is in FreeBSD vs KDE2 ... From what I've been able to determine, the 'hang' is in ksmserver, which is the last thing that 'startkde' runs. After it hangs, I've done a 'gcore' of the process, with the results showing the following: Script started on Sun Jul 23 01:19:11 2000 > gdb `which ksmserver` core.12615 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... warning: exec file is newer than core file. Core was generated by `ksmserver'. Reading symbols from /usr/local/lib/libkdecore.so.3...done. Reading symbols from /usr/local/lib/libkde-qt-addon.so.3...done. Reading symbols from /usr/X11R6/lib/libSM.so.6...done. Reading symbols from /usr/X11R6/lib/libICE.so.6...done. Reading symbols from /usr/local/lib/libDCOP.so.1...done. Reading symbols from /usr/local/lib/libqt.so...done. Reading symbols from /usr/local/lib/libpng.so.4...done. Reading symbols from /usr/lib/libz.so.2...done. Reading symbols from /usr/local/lib/libjpeg.so.9...done. Reading symbols from /usr/X11R6/lib/libXext.so.6...done. Reading symbols from /usr/X11R6/lib/libX11.so.6...done. Reading symbols from /usr/lib/libstdc++.so.3...done. Reading symbols from /usr/lib/libm.so.2...done. Reading symbols from /usr/lib/libc.so.4...done. Reading symbols from /usr/libexec/ld-elf.so.1...done. #0 0x289659c4 in select () from /usr/lib/libc.so.4 (gdb) bt #0 0x289659c4 in select () from /usr/lib/libc.so.4 #1 0x2881a1b5 in _XWaitForReadable () from /usr/X11R6/lib/libX11.so.6 #2 0x2881ab59 in _XRead () from /usr/X11R6/lib/libX11.so.6 #3 0x2881b69c in _XReply () from /usr/X11R6/lib/libX11.so.6 #4 0x28807520 in XInternAtom () from /usr/X11R6/lib/libX11.so.6 #5 0x28872b62 in _XimFilterPropertyNotify () from /usr/X11R6/lib/libX11.so.6 #6 0x288391f5 in XFilterEvent () from /usr/X11R6/lib/libX11.so.6 #7 0x282e1c28 in QApplication::x11ProcessEvent () from /usr/local/lib/libqt.so #8 0x282e16cf in QApplication::processNextEvent () from /usr/local/lib/libqt.so #9 0x2837fa0b in QApplication::enter_loop () from /usr/local/lib/libqt.so #10 0x282e165b in QApplication::exec () from /usr/local/lib/libqt.so #11 0x80546f1 in main (argc=2, argv=0xbfbffa90) at main.cpp:80 (gdb) quit > exit exit Script done on Sun Jul 23 01:19:30 2000 I'm at a loss as to where to look from here ... but if the same code appears to be working fine under 4.1RC and not 5.0-CURRENT, suspecting a bug in KDE2 appears to be the wrong path to be searching ... Thoughts? Comments? Suggestions on where further to look? Thanks ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 22:10:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id A432F37B864 for ; Sat, 22 Jul 2000 22:10:50 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id WAA00602 for ; Sat, 22 Jul 2000 22:10:43 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id WAA99344; Sat, 22 Jul 2000 22:10:43 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sat, 22 Jul 2000 22:10:43 -0700 (PDT) Message-Id: <200007230510.WAA99344@vashon.polstra.com> To: current@freebsd.org Reply-To: current@freebsd.org Subject: Re: buildworld failure In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Doug White wrote: > > Incidentally, whoever broke this should be shot and strung -- I thought > that upgrading from the latest -STABLE to -CURRENT was a supported > operation? > > Copying files from snapshots to bootstrap yourself is just plain > unacceptable. In general -current has been a cesspool for the past year, and things haven't been so great in -stable either. We shouldn't even _need_ an UPDATING file because there shouldn't have to be any special updating procedures. We got by without them just fine the first few years I was involved with the project. An upgrade was make world and build a kernel -- nothing more. Breaking make world used to be considered a major embarrassment. Now it's practically a daily occurrance. Some developers just aren't being careful enough. The biggest problem is they don't restore their systems to a 100% pristine state before they test. Their own make world runs falsely succeed, because they already had the key header file, library, or utility installed from earlier testing and they didn't take care to revert it before trying a make world. Doing it right takes some thought and some care. I would like to see more of that and less impatience around here. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 23:19:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 54BB137B8C0 for ; Sat, 22 Jul 2000 23:19:17 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA13979 for ; Sun, 23 Jul 2000 00:19:15 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA18613 for ; Sun, 23 Jul 2000 00:19:03 -0600 (MDT) Message-Id: <200007230619.AAA18613@harmony.village.org> To: current@freebsd.org Subject: World broken Date: Sun, 23 Jul 2000 00:19:03 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG makeworld from -stable is broken. Needless to say this is completely and totally unacceptible. Would the people involved with the mtree and settofflags changes please get together and fix this right. cc -O -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/home/imp/FreeBSD/src/i386/usr/include -o mtree compare.o crc.o create.o excludes.o misc.o mtree.o spec.o verify.o -lmd misc.o: In function `flags_to_string': misc.o(.text+0x89): undefined reference to `fflagstostr' spec.o: In function `set': spec.o(.text+0x5f5): undefined reference to `strtofflags' *** Error code 1 I'm kludging mtree so that make buildworld isn't broken. Don't remove the kludge until such time as the underlying problems have been corrected. FLAME ON Can't people test the changes they make? I mean this one bit me in less than a minute for a buildworld. Less than a minute. GRUMP. I'm not amused. FLAME OFF I got here checking an UPDATING entry someone sent me saying that one needed to do a makeinstall in libc before this would succeed.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 22 23:54:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (ftp.webmaster.com [209.10.218.74]) by hub.freebsd.org (Postfix) with ESMTP id 62DD137B5BD for ; Sat, 22 Jul 2000 23:54:14 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([216.152.68.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Sat, 22 Jul 2000 23:53:15 -0700 From: "David Schwartz" To: "Mark Murray" Cc: Subject: RE: randomdev entropy gathering is really weak Date: Sat, 22 Jul 2000 23:53:48 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <200007221939.VAA37028@grimreaper.grondar.za> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > /dev/random should block if the system does not contain as much > real entropy > > as the reader desires. Otherwise, the PRNG implementation will be the > > weakest link for people who have deliberately selected higher levels of > > protection from cryptographic attack. > I don't want to rehash this thread from the beginning. Please go > back, read the Yarrow paper, and recognise that Yarrow is not an > entropy-counter, it is a cryptographically secure PRNG. The "count > random bits and block" model does not apply. Then the current implementation cannot provide the usual semantics for /dev/random, while it can provide the semantics for /dev/urandom. As I understand it, /dev/random is supposed to provide true randomness suitable for generating keys of unlimited length, whereas /dev/urandom is supposed to provide cryptographically-strong randomness for general applications. If people want /dev/random to seed 1024-bit keys, /dev/random must be stronger than a 1024-bit key. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message