[OmniOS-discuss] Ang: Re: Wiki is slightly broken

Hi! -"OmniOS-discuss" skrev: - Till: Jacob Vosmaer Från: Eric Sproul Sänt av: "OmniOS-discuss" Datum: 2016-04-25 22:01 Kopia: omnios-discuss Ärende: Re: [OmniOS-discuss] Wiki is

Re: [OmniOS-discuss] Wiki is slightly broken

On Mon, 25 Apr 2016 22:06:05 +0200 Jacob Vosmaer wrote: > > Chrome 50.0.2661.86 (64-bit), OS X 10.11.4. > > If omniti.com was added to the HSTS preload list very recently it may not > be hard-coded in Chrome 49 yet? > Same here: Chrome Version 50.0.2661.86 (64-bit),

Re: [OmniOS-discuss] Wiki is slightly broken

On Mon, Apr 25, 2016 at 4:06 PM, Jacob Vosmaer wrote: > Chrome 50.0.2661.86 (64-bit), OS X 10.11.4. > > If omniti.com was added to the HSTS preload list very recently it may not be > hard-coded in Chrome 49 yet? That could well be. Lucky me, I guess.

Re: [OmniOS-discuss] Wiki is slightly broken

On Mon, Apr 25, 2016 at 3:50 PM, Jacob Vosmaer wrote: > https://chromium.googlesource.com/chromium/src/+/41f8478faaf6c41b2b484e167b3dbb6a95674839/net/http/transport_security_state_static.json#5796 > > I suspect somebody submitted omniti.com via

Re: [OmniOS-discuss] Wiki is slightly broken

When I load that HTTP link with the 'Network' tab of the Chrome dev tools open I first see a '307 internal redirect response' which takes me to https://omnios.omniti.com/wiki.php/WikiStart , which then loads without CSS (i.e. the 'broken' state). If I click where the Green Lock of Trust should be

Re: [OmniOS-discuss] Wiki is slightly broken

Hi Eric, All may not be well after all: I was having a hard time clearing omniti.com from my Chrome's local HSTS list... turns out omniti.com is hard-coded in Chromium(!).

Re: [OmniOS-discuss] Wiki is slightly broken

On Mon, Apr 25, 2016 at 2:55 PM, Jacob Vosmaer wrote: > Thanks Eric! > > It seems like I accidentally took this thread off-list. I think the summary > for everyone else is: HSTS on omniti.com accidentally trickled down to > omnios.omniti.com, affecting visitors who loaded

Re: [OmniOS-discuss] Wiki is slightly broken

Thanks Eric! It seems like I accidentally took this thread off-list. I think the summary for everyone else is: HSTS on omniti.com accidentally trickled down to omnios.omniti.com, affecting visitors who loaded up omnios.omniti.com at just the right (wrong) time. HSTS headers should have been fixed

Re: [OmniOS-discuss] R151018: kernel panic when iSCSI target goes south

Hi Dan, Am 25.04.16 um 16:23 schrieb Dan McDonald: This one is a NULL pointer dereference. If you're still running with kmem_flags = 0xf, the dump will be especially useful. Dan Sent from my iPhone (typos, autocorrect, and all) On Apr 25, 2016, at 3:27 AM, Stephan Budach

Re: [OmniOS-discuss] R151018: kernel panic when iSCSI target goes south

This one is a NULL pointer dereference. If you're still running with kmem_flags = 0xf, the dump will be especially useful. Dan Sent from my iPhone (typos, autocorrect, and all) > On Apr 25, 2016, at 3:27 AM, Stephan Budach wrote: > > Hi, > > I have been struck by

[OmniOS-discuss] R151018: kernel panic when iSCSI target goes south

Hi, I have been struck by kernel panics on my OmniOS boxes lateley, when any one of the target hosts, where the system get it's LUNs from, experiences a kernel panic itself. When this happens, my RSF-1 node immediately panics as well. Looking at the vmdump, it shows this: