From george at ceetonetechnology.com Tue Dec 1 19:13:16 2015 From: george at ceetonetechnology.com (George Rosamond) Date: Tue, 1 Dec 2015 19:13:16 -0500 Subject: [talk] 2015 NYC Tech Meta-Party Message-ID: <565E379C.6000205@ceetonetechnology.com> Details are set for the 2015 NYC Tech Meta-Party, with dozens of user groups and sponsors, including NYC*BUG. The party is Monday, December 14th starting at 7 PM at Clyde Frazier's at 485 10th Avenue between 37th and 38th Streets. The open bar and hors d'oeuvres last until the sponsor money runs out. As usual, RSVPs are required, and NYC*BUG, also as usual, avoids using any third-party services. To RSVP send an email to RSVP at lists.nycbug.org, and an auto-reply will confirm your reservation. Each attendee should RSVP, as the email address used is your entry 'key'. The RSVP list closes at 6 PM on Sunday, December 13th, but maybe earlier. There is no December meeting, but we'll return to our monthly meetings January 6th. BSDTV/Patrick posted the Stephen R Bourne meeting at: https://youtube.com/user/BSDTVvideos *** BSDCan 2016 will be held 10-11 (Fri-Sat) June, 2015 in Ottawa, at the University of Ottawa. It will be preceded by two days of tutorials on 8-9 June (Wed-Thu). The call for presentations is now open: http://www.bsdcan.org/2016/papers.php From george at ceetonetechnology.com Sun Dec 6 20:59:15 2015 From: george at ceetonetechnology.com (George Rosamond) Date: Sun, 6 Dec 2015 20:59:15 -0500 Subject: [talk] Dec 14th NYC Tech Meta-Party Message-ID: <5664E7F3.3080502@ceetonetechnology.com> RSVPs should be done ASAP by emailing to RSVP at lists.nycbug.org. The party begins at 7 PM and is being held at Clyde Frazier's at 485 10th Avenue between 37th and 38th streets. The open bar and free hors d'oeuvres last until the funds run out. Note that the BSDCan call for papers is now open. The details on the January 6th meeting are forthcoming. From george at ceetonetechnology.com Fri Dec 11 18:10:52 2015 From: george at ceetonetechnology.com (George Rosamond) Date: Fri, 11 Dec 2015 18:10:52 -0500 Subject: [talk] FreeBSD 10.2-stable "random device not loaded" Message-ID: <566B57FC.2070708@ceetonetechnology.com> Just updated a box to #r292122 with GENERIC, found this wildly confidence-building note in the dmesg: random device not loaded; using insecure entropy Two lines later in the dmesg it does say: random: initialized I don't see anything online recently about this... except for one unanswered post on freebsd-questions@ in late October. Thought I'd post here before I dug further... g From jpb at jimby.name Fri Dec 11 21:58:22 2015 From: jpb at jimby.name (Jim B.) Date: Fri, 11 Dec 2015 21:58:22 -0500 Subject: [talk] FreeBSD 10.2-stable "random device not loaded" In-Reply-To: <566B57FC.2070708@ceetonetechnology.com> References: <566B57FC.2070708@ceetonetechnology.com> Message-ID: <20151212025822.GA62089@jimby.name> * George Rosamond [2015-12-11 18:11]: > Just updated a box to #r292122 with GENERIC, found this wildly > confidence-building note in the dmesg: > > random device not loaded; using insecure entropy > > Two lines later in the dmesg it does say: > > random: initialized > > I don't see anything online recently about this... except for one > unanswered post on freebsd-questions@ in late October. > > Thought I'd post here before I dug further... > > g > John Mark-Gurney may known a something about it. He's pretty up to date on the crypto stuff. My 0.02, Jim B., From george at ceetonetechnology.com Sat Dec 12 21:24:56 2015 From: george at ceetonetechnology.com (George Rosamond) Date: Sat, 12 Dec 2015 21:24:56 -0500 Subject: [talk] Monday Holiday Party Message-ID: <566CD6F8.8020203@ceetonetechnology.com> The organizers need some volunteers to do a shift at the doors. If interested, please ping me directly offlist. Again, remember to RSVP ASAP as per www.nycbug.org. g From george at ceetonetechnology.com Sun Dec 13 16:59:28 2015 From: george at ceetonetechnology.com (George Rosamond) Date: Sun, 13 Dec 2015 16:59:28 -0500 Subject: [talk] Monday, Dec 14 NYC Tech Meta-Party Message-ID: <566DEA40.7060806@ceetonetechnology.com> 19:00, Clyde Frazier's: 485 10th Ave btwn 37th and 38th St Notice: ASAP send RSVP mail to rsvp at lists dot nycbug dot org Abstract The party is Monday, December 14th starting at 7 PM at Clyde Frazier's at 485 10th Avenue between 37th and 38th Streets. The open bar and hors d'oeuvres last until the sponsor money runs out. As usual, RSVP's are required, and NYC*BUG, also as usual, avoids using any third-party services. To RSVP send an email to rsvp at lists dot nycbug dot org, and an auto-reply will confirm your reservation. Each attendee should RSVP, as the email address used is your entry 'key'. The RSVP list closes at 6 PM on Sunday, December 13th. NYC*BUG volunteers are needed to assist at the door! Also, we are going to have a small presence to collect donations for the FreeBSD Foundation, so more volunteers necessary. From george at ceetonetechnology.com Tue Dec 15 23:19:27 2015 From: george at ceetonetechnology.com (George Rosamond) Date: Tue, 15 Dec 2015 23:19:27 -0500 Subject: [talk] NYC Tech MetaParty Message-ID: <5670E64F.7050200@ceetonetechnology.com> We solicited people for donations to the FreeBSD Foundation at the party last night, in an effort to increase the number of donors. Ike, Thomas and myself walked around with a sign and a receipt book, and managed to collect $165 from 21 people. Particularly considering we didn't have anything to give away like stickers, and there was nothing to *really* prove we were collecting for the foundation, it was definitely a success. As it's year-end, we definitely encourage everyone to give generously to the BSD project of their choice. g From jhb at freebsd.org Wed Dec 16 18:42:21 2015 From: jhb at freebsd.org (John Baldwin) Date: Wed, 16 Dec 2015 15:42:21 -0800 Subject: [talk] FreeBSD 10.2-stable "random device not loaded" In-Reply-To: <566B57FC.2070708@ceetonetechnology.com> References: <566B57FC.2070708@ceetonetechnology.com> Message-ID: <1762889.3DA0Qbz2qd@ralph.baldwin.cx> On Friday, December 11, 2015 06:10:52 PM George Rosamond wrote: > Just updated a box to #r292122 with GENERIC, found this wildly > confidence-building note in the dmesg: > > random device not loaded; using insecure entropy > > Two lines later in the dmesg it does say: > > random: initialized > > I don't see anything online recently about this... except for one > unanswered post on freebsd-questions@ in late October. > > Thought I'd post here before I dug further... Humm, any luck on more info? I haven't seen that on HEAD, and GENERIC on stable/10 includes device random so that seems odd. -- John Baldwin From pete at nomadlogic.org Wed Dec 16 19:10:12 2015 From: pete at nomadlogic.org (Pete Wright) Date: Wed, 16 Dec 2015 16:10:12 -0800 Subject: [talk] FreeBSD 10.2-stable "random device not loaded" In-Reply-To: <1762889.3DA0Qbz2qd@ralph.baldwin.cx> References: <566B57FC.2070708@ceetonetechnology.com> <1762889.3DA0Qbz2qd@ralph.baldwin.cx> Message-ID: <5671FD64.7000305@nomadlogic.org> On 12/16/15 15:42, John Baldwin wrote: > On Friday, December 11, 2015 06:10:52 PM George Rosamond wrote: >> Just updated a box to #r292122 with GENERIC, found this wildly >> confidence-building note in the dmesg: >> >> random device not loaded; using insecure entropy >> >> Two lines later in the dmesg it does say: >> >> random: initialized >> >> I don't see anything online recently about this... except for one >> unanswered post on freebsd-questions@ in late October. >> >> Thought I'd post here before I dug further... > > Humm, any luck on more info? I haven't seen that on HEAD, and GENERIC > on stable/10 includes device random so that seems odd. > i am *not* seeing this on one of my KVM instances here running HEAD r292065: pwright at bsd-current:/usr/src % dmesg|grep -i random random: unblocking device. random: entropy device external interface random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" this is a sandy bridge (E3xxx) Intel CPU on the hypervisor fwiw. cheers, -pete -- Pete Wright pete at nomadlogic.org twitter => @nomadlogicLA From pete at nomadlogic.org Wed Dec 16 19:12:37 2015 From: pete at nomadlogic.org (Pete Wright) Date: Wed, 16 Dec 2015 16:12:37 -0800 Subject: [talk] FreeBSD 10.2-stable "random device not loaded" In-Reply-To: <5671FD64.7000305@nomadlogic.org> References: <566B57FC.2070708@ceetonetechnology.com> <1762889.3DA0Qbz2qd@ralph.baldwin.cx> <5671FD64.7000305@nomadlogic.org> Message-ID: <5671FDF5.2070500@nomadlogic.org> On 12/16/15 16:10, Pete Wright wrote: > > > On 12/16/15 15:42, John Baldwin wrote: >> On Friday, December 11, 2015 06:10:52 PM George Rosamond wrote: >>> Just updated a box to #r292122 with GENERIC, found this wildly >>> confidence-building note in the dmesg: >>> >>> random device not loaded; using insecure entropy >>> >>> Two lines later in the dmesg it does say: >>> >>> random: initialized >>> >>> I don't see anything online recently about this... except for one >>> unanswered post on freebsd-questions@ in late October. >>> >>> Thought I'd post here before I dug further... >> >> Humm, any luck on more info? I haven't seen that on HEAD, and GENERIC >> on stable/10 includes device random so that seems odd. >> > > > i am *not* seeing this on one of my KVM instances here running HEAD r292065: > > pwright at bsd-current:/usr/src % dmesg|grep -i random > random: unblocking device. > random: entropy device external interface > random: registering fast source Intel Secure Key RNG > random: fast provider: "Intel Secure Key RNG" > > > this is a sandy bridge (E3xxx) Intel CPU on the hypervisor fwiw. strike that - freebsd detects this as a E312xx but the hypervisor is a E5-2697 v2 which is also a sandy bridge, but a different rev than the E3xxxx -pete -- Pete Wright pete at nomadlogic.org twitter => @nomadlogicLA From george at ceetonetechnology.com Wed Dec 16 23:41:52 2015 From: george at ceetonetechnology.com (George Rosamond) Date: Wed, 16 Dec 2015 23:41:52 -0500 Subject: [talk] FreeBSD 10.2-stable "random device not loaded" In-Reply-To: <5671FDF5.2070500@nomadlogic.org> References: <566B57FC.2070708@ceetonetechnology.com> <1762889.3DA0Qbz2qd@ralph.baldwin.cx> <5671FD64.7000305@nomadlogic.org> <5671FDF5.2070500@nomadlogic.org> Message-ID: <56723D10.7060801@ceetonetechnology.com> Pete Wright: > > > On 12/16/15 16:10, Pete Wright wrote: >> >> >> On 12/16/15 15:42, John Baldwin wrote: >>> On Friday, December 11, 2015 06:10:52 PM George Rosamond wrote: >>>> Just updated a box to #r292122 with GENERIC, found this wildly >>>> confidence-building note in the dmesg: >>>> >>>> random device not loaded; using insecure entropy >>>> >>>> Two lines later in the dmesg it does say: >>>> >>>> random: initialized >>>> >>>> I don't see anything online recently about this... except for one >>>> unanswered post on freebsd-questions@ in late October. >>>> >>>> Thought I'd post here before I dug further... >>> >>> Humm, any luck on more info? I haven't seen that on HEAD, and GENERIC >>> on stable/10 includes device random so that seems odd. >>> >> >> >> i am *not* seeing this on one of my KVM instances here running HEAD r292065: >> >> pwright at bsd-current:/usr/src % dmesg|grep -i random >> random: unblocking device. >> random: entropy device external interface >> random: registering fast source Intel Secure Key RNG >> random: fast provider: "Intel Secure Key RNG" >> >> >> this is a sandy bridge (E3xxx) Intel CPU on the hypervisor fwiw. > > strike that - freebsd detects this as a E312xx but the hypervisor is a > E5-2697 v2 which is also a sandy bridge, but a different rev than the E3xxxx Thanks Pete and John. Again, here's the relevant part of the dmesg: random device not loaded; using insecure entropy ioapic0 irqs 0-23 on motherboard random: initialized Someone hit me offlist on this, and apparently it's Supermicro motherboard-related. Yes, vague, but I need to do more searching after that. g From pete at nomadlogic.org Thu Dec 17 01:09:39 2015 From: pete at nomadlogic.org (Pete Wright) Date: Wed, 16 Dec 2015 22:09:39 -0800 Subject: [talk] FreeBSD 10.2-stable "random device not loaded" In-Reply-To: <56723D10.7060801@ceetonetechnology.com> References: <566B57FC.2070708@ceetonetechnology.com> <1762889.3DA0Qbz2qd@ralph.baldwin.cx> <5671FD64.7000305@nomadlogic.org> <5671FDF5.2070500@nomadlogic.org> <56723D10.7060801@ceetonetechnology.com> Message-ID: <567251A3.1030904@nomadlogic.org> On 12/16/2015 08:41 PM, George Rosamond wrote: > Pete Wright: >> >> >> On 12/16/15 16:10, Pete Wright wrote: >>> >>> >>> On 12/16/15 15:42, John Baldwin wrote: >>>> On Friday, December 11, 2015 06:10:52 PM George Rosamond wrote: >>>>> Just updated a box to #r292122 with GENERIC, found this wildly >>>>> confidence-building note in the dmesg: >>>>> >>>>> random device not loaded; using insecure entropy >>>>> >>>>> Two lines later in the dmesg it does say: >>>>> >>>>> random: initialized >>>>> >>>>> I don't see anything online recently about this... except for one >>>>> unanswered post on freebsd-questions@ in late October. >>>>> >>>>> Thought I'd post here before I dug further... >>>> >>>> Humm, any luck on more info? I haven't seen that on HEAD, and GENERIC >>>> on stable/10 includes device random so that seems odd. >>>> >>> >>> >>> i am *not* seeing this on one of my KVM instances here running HEAD r292065: >>> >>> pwright at bsd-current:/usr/src % dmesg|grep -i random >>> random: unblocking device. >>> random: entropy device external interface >>> random: registering fast source Intel Secure Key RNG >>> random: fast provider: "Intel Secure Key RNG" >>> >>> >>> this is a sandy bridge (E3xxx) Intel CPU on the hypervisor fwiw. >> >> strike that - freebsd detects this as a E312xx but the hypervisor is a >> E5-2697 v2 which is also a sandy bridge, but a different rev than the E3xxxx > > Thanks Pete and John. > > Again, here's the relevant part of the dmesg: > > random device not loaded; using insecure entropy > ioapic0 irqs 0-23 on motherboard > random: initialized > > Someone hit me offlist on this, and apparently it's Supermicro > motherboard-related. Yes, vague, but I need to do more searching after > that. > what's the full dmesg look like? if for nothing else just curiosity :) -p -- Pete Wright pete at nomadlogic.org From jhb at freebsd.org Fri Dec 18 12:44:50 2015 From: jhb at freebsd.org (John Baldwin) Date: Fri, 18 Dec 2015 09:44:50 -0800 Subject: [talk] FreeBSD 10.2-stable "random device not loaded" In-Reply-To: <56723D10.7060801@ceetonetechnology.com> References: <566B57FC.2070708@ceetonetechnology.com> <5671FDF5.2070500@nomadlogic.org> <56723D10.7060801@ceetonetechnology.com> Message-ID: <13449486.Urfn4Fs5RV@ralph.baldwin.cx> On Wednesday, December 16, 2015 11:41:52 PM George Rosamond wrote: > Pete Wright: > > > > > > On 12/16/15 16:10, Pete Wright wrote: > >> > >> > >> On 12/16/15 15:42, John Baldwin wrote: > >>> On Friday, December 11, 2015 06:10:52 PM George Rosamond wrote: > >>>> Just updated a box to #r292122 with GENERIC, found this wildly > >>>> confidence-building note in the dmesg: > >>>> > >>>> random device not loaded; using insecure entropy > >>>> > >>>> Two lines later in the dmesg it does say: > >>>> > >>>> random: initialized > >>>> > >>>> I don't see anything online recently about this... except for one > >>>> unanswered post on freebsd-questions@ in late October. > >>>> > >>>> Thought I'd post here before I dug further... > >>> > >>> Humm, any luck on more info? I haven't seen that on HEAD, and GENERIC > >>> on stable/10 includes device random so that seems odd. > >>> > >> > >> > >> i am *not* seeing this on one of my KVM instances here running HEAD r292065: > >> > >> pwright at bsd-current:/usr/src % dmesg|grep -i random > >> random: unblocking device. > >> random: entropy device external interface > >> random: registering fast source Intel Secure Key RNG > >> random: fast provider: "Intel Secure Key RNG" > >> > >> > >> this is a sandy bridge (E3xxx) Intel CPU on the hypervisor fwiw. > > > > strike that - freebsd detects this as a E312xx but the hypervisor is a > > E5-2697 v2 which is also a sandy bridge, but a different rev than the E3xxxx > > Thanks Pete and John. > > Again, here's the relevant part of the dmesg: > > random device not loaded; using insecure entropy > ioapic0 irqs 0-23 on motherboard > random: initialized > > Someone hit me offlist on this, and apparently it's Supermicro > motherboard-related. Yes, vague, but I need to do more searching after > that. Hmm, that seems like a bit of an order of operations thing where something is asking for random bits before device random is initialized. I'm not sure what would be asking for it that early though. -- John Baldwin From george at ceetonetechnology.com Fri Dec 18 23:16:02 2015 From: george at ceetonetechnology.com (George Rosamond) Date: Fri, 18 Dec 2015 23:16:02 -0500 Subject: [talk] FreeBSD 10.2-stable "random device not loaded" In-Reply-To: <13449486.Urfn4Fs5RV@ralph.baldwin.cx> References: <566B57FC.2070708@ceetonetechnology.com> <5671FDF5.2070500@nomadlogic.org> <56723D10.7060801@ceetonetechnology.com> <13449486.Urfn4Fs5RV@ralph.baldwin.cx> Message-ID: <5674DA02.4030605@ceetonetechnology.com> John Baldwin: > On Wednesday, December 16, 2015 11:41:52 PM George Rosamond wrote: >> Pete Wright: >>> >>> >>> On 12/16/15 16:10, Pete Wright wrote: >>>> >>>> >>>> On 12/16/15 15:42, John Baldwin wrote: >>>>> On Friday, December 11, 2015 06:10:52 PM George Rosamond wrote: >>>>>> Just updated a box to #r292122 with GENERIC, found this wildly >>>>>> confidence-building note in the dmesg: >>>>>> >>>>>> random device not loaded; using insecure entropy >>>>>> >>>>>> Two lines later in the dmesg it does say: >>>>>> >>>>>> random: initialized >>>>>> >>>>>> I don't see anything online recently about this... except for one >>>>>> unanswered post on freebsd-questions@ in late October. >>>>>> >>>>>> Thought I'd post here before I dug further... >>>>> >>>>> Humm, any luck on more info? I haven't seen that on HEAD, and GENERIC >>>>> on stable/10 includes device random so that seems odd. >>>>> >>>> >>>> >>>> i am *not* seeing this on one of my KVM instances here running HEAD r292065: >>>> >>>> pwright at bsd-current:/usr/src % dmesg|grep -i random >>>> random: unblocking device. >>>> random: entropy device external interface >>>> random: registering fast source Intel Secure Key RNG >>>> random: fast provider: "Intel Secure Key RNG" >>>> >>>> >>>> this is a sandy bridge (E3xxx) Intel CPU on the hypervisor fwiw. >>> >>> strike that - freebsd detects this as a E312xx but the hypervisor is a >>> E5-2697 v2 which is also a sandy bridge, but a different rev than the E3xxxx >> >> Thanks Pete and John. >> >> Again, here's the relevant part of the dmesg: >> >> random device not loaded; using insecure entropy >> ioapic0 irqs 0-23 on motherboard >> random: initialized >> >> Someone hit me offlist on this, and apparently it's Supermicro >> motherboard-related. Yes, vague, but I need to do more searching after >> that. > > Hmm, that seems like a bit of an order of operations thing where something is > asking for random bits before device random is initialized. I'm not sure what > would be asking for it that early though. > Yes, definitely. What could be requesting entropy before Yarrow initializes? I have to look a bit more into it when I get a chance. g From george at ceetonetechnology.com Sat Dec 19 10:06:07 2015 From: george at ceetonetechnology.com (George Rosamond) Date: Sat, 19 Dec 2015 10:06:07 -0500 Subject: [talk] Announce: AsiaBSDCon 2016 CFP Message-ID: <5675725F.4090603@ceetonetechnology.com> GNN tells us: I would like to announce AsiaBSDCon in the next year, 10-13 March 2016 in Tokyo, Japan. You might see BSDCan 2016 call for papers, but please do not forget this will be held before it ;) You can find the details at: http://2016.asiabsdcon.org and the CFP can be found at: http://2016.asiabsdcon.org/cfp.html Papers, videos, and photos of the past AsiaBSDCon can also be found there (last year's ones are not ready yet but will be added soon). The venue of AsiaBSDCon 2016 will be the same as before. The paper submission deadline is *January 8, 2016*. Tutorial proposals are also being accepted but note that the deadline is December 31, 2015 (1 week before). Please spread this to your friends in BSD communities and your GSoC students, and encourage them to attend (and write a paper). If you are planning to submit a paper but you need some more time, financial support, and/or visa application support to visit Japan, please contact secretary at asiabsdcon.org. Thank you! From jpb at jimby.name Sat Dec 19 16:12:22 2015 From: jpb at jimby.name (Jim B.) Date: Sat, 19 Dec 2015 16:12:22 -0500 Subject: [talk] FreeBSD 10.2-stable "random device not loaded" In-Reply-To: <5674DA02.4030605@ceetonetechnology.com> References: <566B57FC.2070708@ceetonetechnology.com> <5671FDF5.2070500@nomadlogic.org> <56723D10.7060801@ceetonetechnology.com> <13449486.Urfn4Fs5RV@ralph.baldwin.cx> <5674DA02.4030605@ceetonetechnology.com> Message-ID: <20151219211222.GA84778@jimby.name> * George Rosamond [2015-12-18 23:16]: > John Baldwin: > > On Wednesday, December 16, 2015 11:41:52 PM George Rosamond wrote: > >> Pete Wright: > >>> > >>> > >>> On 12/16/15 16:10, Pete Wright wrote: > >>>> > >>>> > >>>> On 12/16/15 15:42, John Baldwin wrote: > >>>>> On Friday, December 11, 2015 06:10:52 PM George Rosamond wrote: > >>>>>> Just updated a box to #r292122 with GENERIC, found this wildly > >>>>>> confidence-building note in the dmesg: > >>>>>> > >>>>>> random device not loaded; using insecure entropy > >>>>>> > >>>>>> Two lines later in the dmesg it does say: > >>>>>> > >>>>>> random: initialized > >>>>>> > >>>>>> I don't see anything online recently about this... except for one > >>>>>> unanswered post on freebsd-questions@ in late October. > >>>>>> > >>>>>> Thought I'd post here before I dug further... > >>>>> > >>>>> Humm, any luck on more info? I haven't seen that on HEAD, and GENERIC > >>>>> on stable/10 includes device random so that seems odd. > >>>>> > >>>> > >>>> > >>>> i am *not* seeing this on one of my KVM instances here running HEAD r292065: > >>>> > >>>> pwright at bsd-current:/usr/src % dmesg|grep -i random > >>>> random: unblocking device. > >>>> random: entropy device external interface > >>>> random: registering fast source Intel Secure Key RNG > >>>> random: fast provider: "Intel Secure Key RNG" > >>>> > >>>> > >>>> this is a sandy bridge (E3xxx) Intel CPU on the hypervisor fwiw. > >>> > >>> strike that - freebsd detects this as a E312xx but the hypervisor is a > >>> E5-2697 v2 which is also a sandy bridge, but a different rev than the E3xxxx > >> > >> Thanks Pete and John. > >> > >> Again, here's the relevant part of the dmesg: > >> > >> random device not loaded; using insecure entropy > >> ioapic0 irqs 0-23 on motherboard > >> random: initialized > >> > >> Someone hit me offlist on this, and apparently it's Supermicro > >> motherboard-related. Yes, vague, but I need to do more searching after > >> that. > > > > Hmm, that seems like a bit of an order of operations thing where something is > > asking for random bits before device random is initialized. I'm not sure what > > would be asking for it that early though. > > > > Yes, definitely. What could be requesting entropy before Yarrow > initializes? > > I have to look a bit more into it when I get a chance. > Try booting verbose. The demsg will have all the verbose info. My 2 (Arkansas hick version) Jim B. From george at ceetonetechnology.com Sun Dec 20 11:26:00 2015 From: george at ceetonetechnology.com (George Rosamond) Date: Sun, 20 Dec 2015 11:26:00 -0500 Subject: [talk] FreeBSD 10.2-stable "random device not loaded" In-Reply-To: <20151219211222.GA84778@jimby.name> References: <566B57FC.2070708@ceetonetechnology.com> <5671FDF5.2070500@nomadlogic.org> <56723D10.7060801@ceetonetechnology.com> <13449486.Urfn4Fs5RV@ralph.baldwin.cx> <5674DA02.4030605@ceetonetechnology.com> <20151219211222.GA84778@jimby.name> Message-ID: <5676D698.9000800@ceetonetechnology.com> Jim B.: > * George Rosamond [2015-12-18 23:16]: >> John Baldwin: >>> On Wednesday, December 16, 2015 11:41:52 PM George Rosamond wrote: >>>> Pete Wright: >>>>> >>>>> >>>>> On 12/16/15 16:10, Pete Wright wrote: >>>>>> >>>>>> >>>>>> On 12/16/15 15:42, John Baldwin wrote: >>>>>>> On Friday, December 11, 2015 06:10:52 PM George Rosamond wrote: >>>>>>>> Just updated a box to #r292122 with GENERIC, found this wildly >>>>>>>> confidence-building note in the dmesg: >>>>>>>> >>>>>>>> random device not loaded; using insecure entropy >>>>>>>> >>>>>>>> Two lines later in the dmesg it does say: >>>>>>>> >>>>>>>> random: initialized >>>>>>>> >>>>>>>> I don't see anything online recently about this... except for one >>>>>>>> unanswered post on freebsd-questions@ in late October. >>>>>>>> >>>>>>>> Thought I'd post here before I dug further... >>>>>>> >>>>>>> Humm, any luck on more info? I haven't seen that on HEAD, and GENERIC >>>>>>> on stable/10 includes device random so that seems odd. >>>>>>> >>>>>> >>>>>> >>>>>> i am *not* seeing this on one of my KVM instances here running HEAD r292065: >>>>>> >>>>>> pwright at bsd-current:/usr/src % dmesg|grep -i random >>>>>> random: unblocking device. >>>>>> random: entropy device external interface >>>>>> random: registering fast source Intel Secure Key RNG >>>>>> random: fast provider: "Intel Secure Key RNG" >>>>>> >>>>>> >>>>>> this is a sandy bridge (E3xxx) Intel CPU on the hypervisor fwiw. >>>>> >>>>> strike that - freebsd detects this as a E312xx but the hypervisor is a >>>>> E5-2697 v2 which is also a sandy bridge, but a different rev than the E3xxxx >>>> >>>> Thanks Pete and John. >>>> >>>> Again, here's the relevant part of the dmesg: >>>> >>>> random device not loaded; using insecure entropy >>>> ioapic0 irqs 0-23 on motherboard >>>> random: initialized >>>> >>>> Someone hit me offlist on this, and apparently it's Supermicro >>>> motherboard-related. Yes, vague, but I need to do more searching after >>>> that. >>> >>> Hmm, that seems like a bit of an order of operations thing where something is >>> asking for random bits before device random is initialized. I'm not sure what >>> would be asking for it that early though. >>> >> >> Yes, definitely. What could be requesting entropy before Yarrow >> initializes? >> >> I have to look a bit more into it when I get a chance. >> > > Try booting verbose. The demsg will have all the verbose info. > > My 2 (Arkansas hick version) I do that by default on all FreeBSD boxes, but good advice. :) rc_debug="YES" rc_info="YES" I'll be on the box this week and give an update. g From george at ceetonetechnology.com Wed Dec 23 08:49:16 2015 From: george at ceetonetechnology.com (George Rosamond) Date: Wed, 23 Dec 2015 08:49:16 -0500 Subject: [talk] ISC shifting license to MPL 2.0 Message-ID: <567AA65C.9070600@ceetonetechnology.com> ISC is moving Kea (the replacement for ISC DHCP) to the MPL 2.0 from the ISC license. "There is no longer a good reason for ISC to have its own license, separate from everything else, even though we had and were using our license years before most of these other licenses existed." https://www.isc.org/blogs/kea-license-2-0/ g From george at ceetonetechnology.com Wed Dec 30 11:10:28 2015 From: george at ceetonetechnology.com (George Rosamond) Date: Wed, 30 Dec 2015 11:10:28 -0500 Subject: [talk] January 6 meeting Message-ID: <568401F4.2070102@ceetonetechnology.com> For January, we're going to do an installfest-type event. Nothing fancy, but it's a good opportunity to bring in a laptop (maybe with a spare disk) or other hardware to hack on. Web site and announce will be updated shortly. Meeting is at 645 PM at Stone Creek as usual. In the background, we'll be playing a Kirk McKusick video on "Introduction to the FreeBSD Open Source Operating System LiveLessons" complements of Heather at Pearson. It's a full ten hours long, but everyone will at least get a flavor of the video. We should be using this meeting to ping those interested in testing out one BSD or another.. .they are out there, so connect with them for the meeting. g From jpb at jimby.name Thu Dec 31 12:20:47 2015 From: jpb at jimby.name (Jim B.) Date: Thu, 31 Dec 2015 12:20:47 -0500 Subject: [talk] January 6 meeting In-Reply-To: <568401F4.2070102@ceetonetechnology.com> References: <568401F4.2070102@ceetonetechnology.com> Message-ID: <20151231172047.GA18430@jimby.name> * George Rosamond [2015-12-30 11:10]: > For January, we're going to do an installfest-type event. > > Nothing fancy, but it's a good opportunity to bring in a laptop (maybe > with a spare disk) or other hardware to hack on. > > Web site and announce will be updated shortly. Meeting is at 645 PM at > Stone Creek as usual. > > In the background, we'll be playing a Kirk McKusick video on > "Introduction to the FreeBSD Open Source Operating System LiveLessons" > complements of Heather at Pearson. > > It's a full ten hours long, but everyone will at least get a flavor of > the video. > > We should be using this meeting to ping those interested in testing out > one BSD or another.. .they are out there, so connect with them for the > meeting. > > g > Hi Gman, Great idea on the install fest. To help out I'll send you a link to the BSDA study DVD to burn 5 or so copies to give away. It has the latest version of DFly, FBSD, NBSD, and OBSD. You can install from the DVD or run each as a "live DVD". However, the DVD only supports 64bit Intel/AMD Architectures, so it wont work for folks bringing 32bit hardware, or Old Sparc 5s :-) Sending in next email... Jim B. From george at ceetonetechnology.com Thu Dec 31 12:21:46 2015 From: george at ceetonetechnology.com (George Rosamond) Date: Thu, 31 Dec 2015 12:21:46 -0500 Subject: [talk] January 6 meeting In-Reply-To: <20151231172047.GA18430@jimby.name> References: <568401F4.2070102@ceetonetechnology.com> <20151231172047.GA18430@jimby.name> Message-ID: <5685642A.9070606@ceetonetechnology.com> Jim B.: > * George Rosamond [2015-12-30 11:10]: >> For January, we're going to do an installfest-type event. >> >> Nothing fancy, but it's a good opportunity to bring in a laptop (maybe >> with a spare disk) or other hardware to hack on. >> >> Web site and announce will be updated shortly. Meeting is at 645 PM at >> Stone Creek as usual. >> >> In the background, we'll be playing a Kirk McKusick video on >> "Introduction to the FreeBSD Open Source Operating System LiveLessons" >> complements of Heather at Pearson. >> >> It's a full ten hours long, but everyone will at least get a flavor of >> the video. >> >> We should be using this meeting to ping those interested in testing out >> one BSD or another.. .they are out there, so connect with them for the >> meeting. >> >> g >> > > Hi Gman, > > Great idea on the install fest. To help out I'll send you a link > to the BSDA study DVD to burn 5 or so copies to give away. It has > the latest version of DFly, FBSD, NBSD, and OBSD. You can install > from the DVD or run each as a "live DVD". However, the DVD only > supports 64bit Intel/AMD Architectures, so it wont work for folks > bringing 32bit hardware, or Old Sparc 5s :-) > > Sending in next email... Awesome. Appreciated JB. I assume you are sending offlist... g