Re: requesting help working around boot failures with supermicro atom board

On Mon, Oct 05, 2015 at 01:18:53PM -0400, dewey.hyl...@gmail.com wrote: > unfortunately, not on my end. i have hopes that mike larkin may find something > when he gets a chance to look, but i am past the limit of my capabilities and > supermicro support has discontinued responding to me. their

Re: requesting help working around boot failures with supermicro atom board

On Tue, Sep 15, 2015 at 02:45:02AM +, Dewey Hylton wrote: > Mark Kettenis xs4all.nl> writes: > > > > > > # sysctl -a|grep 'sensors.*temp' > > > hw.sensors.cpu0.temp0=30.00 degC > > > hw.sensors.lm1.temp0=0.00 degC > > > hw.sensors.lm1.temp1=14.00 degC > > > hw.sensors.lm1.temp2=14.00 degC >

Re: IKED and encapsulated peers

On Mon, Oct 05, 2015 at 07:52:28PM BST, Jason Tubnor wrote: > On 5 October 2015 at 22:00, Jason Tubnor wrote: > > > > > Solved! > > > > > > I have attached a man 5 iked.conf patch that clears up an example used in > > the man page. > > > > The gz diff was stripped by demime,

Re: Is OpenSMTPD worthy of OpenBSD inclusion?

By now the thread starter should already be well aware that the correct thing would have been to ask for some comforting words the report from the third party code audit was and is going to result in further improvements. And then thank the developers for sharing the audit details, the work done

Re: Strange network issue during startup

On Tue, Oct 06, 2015 at 08:01 +0200, Alessandro DE LAURENZIS wrote: > Hello Mike, > > Thanks for your feedback, > > On Mon 05/10/2015 16:43, Mike Belopuhov wrote: > > > > Can you please add an "ifconfig -A" invocation to your hostname.trunk0: > > > > trunkproto failover > > trunkport em0 > >

Re: Is OpenSMTPD worthy of OpenBSD inclusion?

On Tue, Oct 06, 2015 at 02:20:31AM +0300, Kimmo Paasiala wrote: > On Mon, Oct 5, 2015 at 10:52 PM, Артур Истомин wrote: > > On Mon, Oct 05, 2015 at 01:07:24PM -0400, STeve Andre' wrote: > >> The smtpd code is very good. > > > > static void > > filter_tx_io(struct io *io, int

Support for ActivCard, CRYPTOCard and SNK-004 authentication tokens

Hello, We're currently evaluating if we should keep providing support for ActivCard, CRYPTOCard and SNK-004 authentication tokens via login_token(8). If you're a user of "activ", "crypto", "snk" or "token" authentication methods (check your /etc/login.conf), please speak up so that we could

Re: "dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

2015-10-07 1:38 GMT+08:00 Ted Unangst : > Mikael wrote: > > 2015-10-07 0:58 GMT+08:00 Ted Unangst : > > > > > > the disklabel is the second sector of the openbsd part of the disk. > > > > > > *3: A6 0 1 2 - 243200 254 63 [ 64:

Re: "dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

Aha got it. So then I'll just learn that sector 80 and up are "safe" for "user data", and it's up to all users to take care that any non-UFS/swap/RAID partitions never go below 80. But how does the behavior of the first added partition by default overlapping the disklabel "save butts" - Does

Re: "dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

On 2015-10-06 19:25, Mikael wrote: > So then I'll just learn that sector 80 and up are "safe" for "user data", > and it's up to all users to take care that any non-UFS/swap/RAID partitions > never go below 80. I don't think you can expect swap partitions to honour those first sectors...

Re: Strange network issue during startup

Hello Mike, Thanks for your feedback, On Mon 05/10/2015 16:43, Mike Belopuhov wrote: > > Can you please add an "ifconfig -A" invocation to your hostname.trunk0: > > trunkproto failover > trunkport em0 > trunkport iwn0 > !/sbin/ifconfig -A >/root/ifconfig.out 2>&1 > dhcp > > And send me the

Re: rdomain 0 and dafault route

hi > On Tue, Oct 06, 2015 at 06:49:29AM +0200, Holger Glaess wrote: >> hi >> >> just a simple question >> >> how can i setup an kind of "default route" in rdomain 0 >> to , for example , rdomain 2. >> >> i have 3 rdomain >> >> the default one >> one with the internet connection ( rdomain 1 ) >>

Re: "dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

There were also some excellent diagrams generated the last time this came up for discussion: https://marc.info/?l=openbsd-misc=141520160709490=2 FWIW. Brian

Re: Captive portal with OpenBSD as a hostap

On Mon, Oct 5, 2015 at 1:26 PM, laudarch wrote: > I made a custom implementation and a diff to authpf, will share that > later just in case anyone wants it. > > I hope this helps you, it pretty simple > http://bastienceriani.fr/?p=70 > Thanks laudarch ... Very close to what I

Re: rdomain 0 and dafault route

On Tue, Oct 06, 2015 at 08:58:24AM +0200, Holger Glaess wrote: > hi > > > On Tue, Oct 06, 2015 at 06:49:29AM +0200, Holger Glaess wrote: > >> hi > >> > >> just a simple question > >> > >> how can i setup an kind of "default route" in rdomain 0 > >> to , for example , rdomain 2. > >> > >> i have 3

Re: OpenBGPd error /bsd: bgpd(): syscall 105

On 02.10.2015 10:40, Atanas Vladimirov wrote: On 01.10.2015 20:00, Sebastien Marie wrote: On Thu, Oct 01, 2015 at 12:21:33PM -0400, Michael McConville wrote: Atanas Vladimirov wrote: > Snapshot from sep 30 bgpd didn't startup: > Oct 1 08:32:28 ns /bsd: bgpd(28055): syscall 105 > Oct 1

Re: Is OpenSMTPD worthy of OpenBSD inclusion?

On 18:47 Mon 05 Oct , Jason A. Donenfeld wrote: > I maintain both distribution packages for it (Gentoo), as well as my > entire infrastructure, which is based on OpenSMTPD. I've "bet the > farm" on the project, so to speak. Oh, so you were that guy who released "stable" ebuild without Berkeley DB

Fwd: [EdLUG] 5th International LDAP Conference 11-13/11/2015

FYI: 22 peer-reviewed paper programme includes: 3 different async talks Yubikey, OATH-HOTP & OpenID auth talks Samba4 + twin tracked significant practical tutorial day - laptop required (Advanced track with a strong focus on security) - Forwarded message from Edinburgh Linux Users Group

Re: "dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

2015-10-07 1:44 GMT+08:00 Mikael : > > Ah sure. > > Perhaps I misunderstood the level of "foolproofness" that the disklabel > tool's autogenerated default value was intended to give - > > Just curious, now that structural things like this are at stake (i.e. some > user

Re: OpenBGPd SNMP

On Mon, Oct 05, 2015 at 10:34:01AM +, Stuart Henderson wrote: > On 2015-10-04, Mike Hammett wrote: > > Are there any packages out there that expose OpenBGPd or other OpenBSD > > parameters via SNMP? Would like to check generic health of the system, > > number of

Re: "dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

On 2015-10-06, Theo de Raadt wrote: >> Wait, sorry - so the disklabel tool says that the c partition starts at >> offset 0 , that's logical indeed as data always starts at offset 0. >> >> By some reason, the disklabel tool however doesn't want partitions on the >> first

Re: "dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

On Tue, Oct 6, 2015 at 2:48 PM, Benny Lofgren wrote: > It is well known and understood since decades what's on these first > sectors of a) a disk, b) of the BSD usable area and c) of each partition > (type). Why are you having trouble accepting that things are the way > they

Re: "dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

>On Tue, Oct 6, 2015 at 2:48 PM, Benny Lofgren wrote: >> It is well known and understood since decades what's on these first >> sectors of a) a disk, b) of the BSD usable area and c) of each partition >> (type). I don't think (c) is something commonly known.

pkg question: dnsmasq alternatives?

We have various OpenBSD machines acting as gateways for NAT LANs. We need a handful of services for these, mainly a dhcp server that can do mac-based fixed addressing, dns server that can attach and reverse names associated with these fixed addresses, dns black-holeing, the ability to

Re: dd if=/dev/zero of=/dev/mykeydisk; bioctl -k /dev/mykeydisk ... = will use 0x00 as key, or will generate a secure key?

2015-10-06 19:25 GMT+08:00 Jiri B : > On Tue, Oct 06, 2015 at 07:17:19PM +0800, Mikael wrote: > > You > > > > 1) Fill your keydisk with zeroes and > > > > 2) Apply "bioctl -k" on it. > > ^^^ this is not exact cmd arg, is it? > > j. > No, exact key argument is bioctl -C force -c C

Re: dd if=/dev/zero of=/dev/mykeydisk; bioctl -k /dev/mykeydisk ... = will use 0x00 as key, or will generate a secure key?

On Tue, Oct 06, 2015 at 07:17:19PM +0800, Mikael wrote: > You > > 1) Fill your keydisk with zeroes and > > 2) Apply "bioctl -k" on it. > > Does this mean your key is now zeroes, meaning completely unsafe, or did > bioctl make a key for you? > > > The keydisk gets some "OPENBSDSR KEYDISK005"

dd if=/dev/zero of=/dev/mykeydisk; bioctl -k /dev/mykeydisk ... = will use 0x00 as key, or will generate a secure key?

You 1) Fill your keydisk with zeroes and 2) Apply "bioctl -k" on it. Does this mean your key is now zeroes, meaning completely unsafe, or did bioctl make a key for you? The keydisk gets some "OPENBSDSR KEYDISK005" header but it says nowhere if it actually made a key for you. If it generates

Re: dd if=/dev/zero of=/dev/mykeydisk; bioctl -k /dev/mykeydisk ... = will use 0x00 as key, or will generate a secure key?

On Tue, Oct 06, 2015 at 07:17:19PM +0800, Mikael wrote: > You > > 1) Fill your keydisk with zeroes and > > 2) Apply "bioctl -k" on it. ^^^ this is not exact cmd arg, is it? j.

Re: dd if=/dev/zero of=/dev/mykeydisk; bioctl -k /dev/mykeydisk ... = will use 0x00 as key, or will generate a secure key?

2015-10-06 19:54 GMT+08:00 Stefan Sperling : > On Tue, Oct 06, 2015 at 07:32:45PM +0800, Mikael wrote: > > 2015-10-06 19:27 GMT+08:00 Stefan Sperling : > > > Perhaps this will answer your questions: > > >

Re: dd if=/dev/zero of=/dev/mykeydisk; bioctl -k /dev/mykeydisk ... = will use 0x00 as key, or will generate a secure key?

On Tue, Oct 06, 2015 at 07:32:45PM +0800, Mikael wrote: > 2015-10-06 19:27 GMT+08:00 Stefan Sperling : > > Perhaps this will answer your questions: > > http://www.openbsd.org/papers/eurobsdcon2015-softraid-boot.pdf > > > > That one mentions nothing of what the keydisk is supposed

Re: dd if=/dev/zero of=/dev/mykeydisk; bioctl -k /dev/mykeydisk ... = will use 0x00 as key, or will generate a secure key?

On Tue, Oct 06, 2015 at 08:04:01PM +0800, Mikael wrote: > Aha. So at "-k" time, if there's no key on the keydisk structure already, > it'll make one. So this is how you can use one and the same keydisk for > multiple volumes. Yes. Per volume you need one disklabel partition of type RAID which you

Re: vpn from subnet to subnet through a 3rd enpoint?

Em 06-10-2015 10:35, Markus Rosjat escreveu: > as the subject states is it possible to do that ? Yes, it is. > My tunnels working from the 3rd subnet in each of the other 2 subnets > and back from then. I really want to connect from subnet 1 to subnet 2 > over the enpoint in the 3rd subnet. Are

Re: cu with XMODEM won't transfer file

Hello On 10/05/15 19:59, Nicholas Marriott wrote: On Mon, Oct 05, 2015 at 10:07:21AM -0700, Philip Guenther wrote: On Mon, Oct 5, 2015 at 6:54 AM, Kim Zeitler wrote: I am trying to transfer a new firmware to a switch using cu(1) with XMODEM using a USB-to-RS232

vpn from subnet to subnet through a 3rd enpoint?

Hi there, as the subject states is it possible to do that ? My tunnels working from the 3rd subnet in each of the other 2 subnets and back from then. I really want to connect from subnet 1 to subnet 2 over the enpoint in the 3rd subnet. so subnet 1 <---> subnet 3 ; works fine subnet 2

Re: "dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

Mikael wrote: > The script below includes extra considerations to see through any kernel > caching of the disklabel, by rebooting between every relevant step. > > "dd if=/dev/srandom of=/dev/rwd0e bs=1024 count=1" does also wipe the > disklabel. > > "dd if=/dev/srandom of=/dev/wd0a bs=1024

Re: "dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

> > Have I (and some others) misunderstood anything about how BSD disklabelling > > works? > > the disklabel is the second sector of the openbsd part of the disk. > > *3: A6 0 1 2 - 243200 254 63 [ 64: 3907024001 ] OpenBSD > > so, if you overwrite sector 65, you will

"dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

The script below includes extra considerations to see through any kernel caching of the disklabel, by rebooting between every relevant step. "dd if=/dev/srandom of=/dev/rwd0e bs=1024 count=1" does also wipe the disklabel. "dd if=/dev/srandom of=/dev/wd0a bs=1024 count=1" does not wipe the

Re: "dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

2015-10-07 0:58 GMT+08:00 Ted Unangst : > > the disklabel is the second sector of the openbsd part of the disk. > > *3: A6 0 1 2 - 243200 254 63 [ 64: 3907024001 ] OpenBSD > > so, if you overwrite sector 65, you will overwrite disklabel. normally the > 'a'

Re: "dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

2015-10-07 1:07 GMT+08:00 Theo de Raadt : > > > Have I (and some others) misunderstood anything about how BSD > disklabelling > > > works? > > > > the disklabel is the second sector of the openbsd part of the disk. > > > > *3: A6 0 1 2 - 243200 254 63 [

Re: "dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

Mikael wrote: > 2015-10-07 0:58 GMT+08:00 Ted Unangst : > > > > the disklabel is the second sector of the openbsd part of the disk. > > > > *3: A6 0 1 2 - 243200 254 63 [ 64: 3907024001 ] OpenBSD > > > > so, if you overwrite sector 65, you will overwrite

Re: "dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

Mikael wrote: > 2015-10-07 0:45 GMT+08:00 Ted Unangst : > > > Mikael wrote: > > > The script below includes extra considerations to see through any kernel > > > caching of the disklabel, by rebooting between every relevant step. > > > > > > "dd if=/dev/srandom of=/dev/rwd0e

Re: "dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

> > But your fingers don't know it. > > > > > Right, time for fingers to learn. > > Will look forward to learn how it "saved many a butt" and what's the lowest > "safe" offset (..64 + 8*2 = 81+?..) (if that will actually make sense when > understanding the whole thing) through the Q:s in my last

Re: "dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

> Wait, sorry - so the disklabel tool says that the c partition starts at > offset 0 , that's logical indeed as data always starts at offset 0. > > By some reason, the disklabel tool however doesn't want partitions on the > first 64 sectors (console dump below), i.e. on the first 32KB (why?).

Re: "dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

2015-10-07 0:45 GMT+08:00 Ted Unangst : > Mikael wrote: > > The script below includes extra considerations to see through any kernel > > caching of the disklabel, by rebooting between every relevant step. > > > > "dd if=/dev/srandom of=/dev/rwd0e bs=1024 count=1" does also

Re: "dd if=/dev/srandom of=/dev/wd0e bs=1024 count=1" WIPES my wd0 disklabel. Is this intended, bug, how come, how workaround ??? Incl reproduction script+console output+dmesg

2015-10-07 1:14 GMT+08:00 Theo de Raadt : > > > But your fingers don't know it. > > > > > > > > Right, time for fingers to learn. > > > > Will look forward to learn how it "saved many a butt" and what's the > lowest > > "safe" offset (..64 + 8*2 = 81+?..) (if that will