Page 4 of 5 FirstFirst ... 2345 LastLast
Results 31 to 40 of 43

Thread: Login screen certificate not authentic

  1. #31
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    17,048

    Default Re: Login screen certificate not authentic

    On Mon, 23 Nov 2009 07:36:01 +0000, john hudson wrote:

    > But checked the source code this morning when there was no message and
    > it appears identical; so that doesn't help.


    Yeah, it's a cluster of servers as I understand it, so the code should
    all be the same on all of them.

    An IP address *might* help, but you'd have to catch it probably with lsof
    -i - I don't think a DNS name will help (and it might be that it's all
    behind a L4 switch, in which case even an IP address won't help much).

    I'll update the bug and note that you've seen it again.

    Jim
    --
    Jim Henderson
    openSUSE Forums Moderator

  2. #32
    Join Date
    Jun 2008
    Location
    West Yorkshire, UK
    Posts
    3,448

    Default Re: Login screen certificate not authentic

    Tried that today when there were no problems and it does indeed yield IP numbers; so I have made a note of those and will try again when I next encounter the message to see if there are any differences.

  3. #33
    Join Date
    Jun 2008
    Location
    West Yorkshire, UK
    Posts
    3,448

    Default Re: Login screen certificate not authentic

    Ok This is what lsof -i displays when there are no problems:
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    kio_http 3837 john 39u IPv4 18522 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:56131->ew-in-f102.1e100.net:http (ESTABLISHED)
    kio_http 3918 john 27u IPv4 18442 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:58036->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3960 john 8u IPv4 18615 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45647->secure-www.novell.com:https (ESTABLISHED)
    kio_http 3961 john 9u IPv4 18184 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:33857->81.22.39.115:http (CLOSE_WAIT)
    kio_http 3966 john 9u IPv4 17840 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:35890->wy-in-f149.1e100.net:http (ESTABLISHED)
    kio_http 3967 john 12u IPv4 18208 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:33862->81.22.39.115:http (CLOSE_WAIT)
    kio_http 4000 john 8u IPv4 18611 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45643->secure-www.novell.com:https (ESTABLISHED)
    kio_http 4001 john 8u IPv4 18692 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:47674->66.235.133.1:https (ESTABLISHED)

    This is what lsof -i displays when the certificate is inauthentic: the repetitions appear to relate to the error messages.

    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    kio_http 3973 john 33u IPv4 23502 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:33722->cds29.lon9.msecn.net:http (CLOSE_WAIT)
    kio_http 3994 john 20u IPv4 23602 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:59367->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 4007 john 17u IPv4 23664 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:59372->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 4014 john 14u IPv4 23670 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:59373->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 4040 john 14u IPv4 23496 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:54225->ww-in-f149.1e100.net:http (ESTABLISHED)
    kio_http 4044 john 12u IPv4 23655 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:59371->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 4049 john 9u IPv4 23598 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:59366->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 4055 john 10u IPv4 23671 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:59374->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 4133 john 9u IPv4 23902 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:55840->narwal.opensuse.org:https (ESTABLISHED)
    kio_http 4134 john 10u IPv4 23892 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:55838->narwal.opensuse.org:https (ESTABLISHED)
    kio_http 4135 john 8u IPv4 23901 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:55839->narwal.opensuse.org:https (ESTABLISHED)

    I didn't think to run lsof -i after clearing the error messages and before logging in. So this is what lsof -i displays after the error messages have been dismissed and the login completed.

    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    kio_http 3968 john 33u IPv4 26376 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45123->cot.novell.com:http (ESTABLISHED)
    kio_http 3977 john 19u IPv4 26280 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45116->cot.novell.com:http (ESTABLISHED)
    kio_http 3983 john 36u IPv4 26261 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45115->cot.novell.com:http (ESTABLISHED)
    kio_http 3994 john 20u IPv4 26158 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45109->cot.novell.com:http (ESTABLISHED)
    kio_http 4007 john 17u IPv4 26247 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45113->cot.novell.com:http (ESTABLISHED)
    kio_http 4014 john 14u IPv4 26505 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:43528->ez-in-f138.1e100.net:http (ESTABLISHED)
    kio_http 4042 john 14u IPv4 26163 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45110->cot.novell.com:http (ESTABLISHED)
    kio_http 4044 john 12u IPv4 26372 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45122->cot.novell.com:http (ESTABLISHED)
    kio_http 4049 john 12u IPv4 26311 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45119->cot.novell.com:http (ESTABLISHED)
    kio_http 4055 john 10u IPv4 26385 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45124->cot.novell.com:http (ESTABLISHED)
    kio_http 4140 john 8u IPv4 26423 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:43526->ez-in-f138.1e100.net:http (ESTABLISHED)

  4. #34
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    17,048

    Default Re: Login screen certificate not authentic

    On Tue, 24 Nov 2009 09:36:01 +0000, john hudson wrote:

    > Tried that today when there were no problems and it does indeed yield IP
    > numbers; so I have made a note of those and will try again when I next
    > encounter the message to see if there are any differences.


    Sounds good.

    Jim



    --
    Jim Henderson
    openSUSE Forums Moderator

  5. #35
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    17,048

    Default Re: Login screen certificate not authentic

    Will pass this information along as well - thanks!

    Jim



    --
    Jim Henderson
    openSUSE Forums Moderator

  6. #36
    Join Date
    Jun 2008
    Location
    West Yorkshire, UK
    Posts
    3,448

    Default Re: Login screen certificate not authentic

    I got the following when I logged out this morning:

    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    kio_http 4225 john 16u IPv4 30615 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:58637->66.235.132.152:http (ESTABLISHED)
    kio_http 4266 john 10u IPv4 30640 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:50340->narwal.opensuse.org:https (CLOSE_WAIT)
    kio_http 4267 john 8u IPv4 30639 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:50339->narwal.opensuse.org:https (CLOSE_WAIT)

    and this when I got to the login screen this evening before signing on:

    kio_http 3845 john 11u IPv4 14250 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:44738->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3849 john 9u IPv4 14159 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:44733->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3851 john 10u IPv4 14172 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:44736->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3854 john 11u IPv4 14170 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:44735->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3862 john 9u IPv4 14056 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:44758->ww-in-f148.1e100.net:http (ESTABLISHED)
    kio_http 3868 john 9u IPv4 13201 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:55619->ww-in-f148.1e100.net:http (ESTABLISHED)
    kio_http 3887 john 9u IPv4 14158 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:44732->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3901 john 9u IPv4 14420 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:42027->narwal.opensuse.org:https (CLOSE_WAIT)
    kio_http 3902 john 10u IPv4 14435 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:42029->narwal.opensuse.org:https (CLOSE_WAIT)
    kio_http 3903 john 8u IPv4 14432 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:42028->narwal.opensuse.org:https (CLOSE_WAIT)

    As before, the repeats appear to relate to the error messages.

    It's a while since it happened more than once in several days.

  7. #37
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    17,048

    Default Re: Login screen certificate not authentic

    On Wed, 25 Nov 2009 22:16:01 +0000, john hudson wrote:

    > I got the following when I logged out this morning:


    Just got a note from the developer looking into it, and the lsof outputs
    have been very helpful - he's going to do some digging tomorrow morning,
    but it seems that there's a request somewhere that's asking for http
    rather than https and he believes that's the underlying cause.

    Thanks for your patience and assistance in tracking this down - I'm
    probably away for the rest of the week for the US Thanksgiving holiday,
    but I'll check on Monday and see how the bug is progressing.

    Jim

    --
    Jim Henderson
    openSUSE Forums Moderator

  8. #38
    Join Date
    Jun 2008
    Location
    West Yorkshire, UK
    Posts
    3,448

    Default Re: Login screen certificate not authentic

    Don't know how helpful this will be but the output is varying a bit; on a couple of occasions I only got one error message whereas on others it has been three or more.

    Login evening 26/11/2009
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    kio_http 3908 john 31u IPv4 16483 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:54950->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3909 john 41u IPv4 16451 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:57259->cot.novell.com:http (ESTABLISHED)
    kio_http 3910 john 52u IPv4 16482 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:54949->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3911 john 30u IPv4 16484 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:54951->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3980 john 12u IPv4 16032 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:54595->vrp2.fra.xpc-mii.net:http (CLOSE_WAIT)
    kio_http 4011 john 9u IPv4 16709 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:35460->narwal.opensuse.org:https (ESTABLISHED)
    kio_http 4012 john 10u IPv4 16737 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:35462->narwal.opensuse.org:https (ESTABLISHED)
    kio_http 4013 john 8u IPv4 16740 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:35463->narwal.opensuse.org:https (ESTABLISHED)

    Login morning 27/11/2009
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    kio_http 3967 john 22u IPv4 22945 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45784->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3968 john 10u IPv4 22983 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45793->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3969 john 15u IPv4 22966 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45786->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3971 john 11u IPv4 22968 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45788->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3972 john 11u IPv4 22975 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45791->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3974 john 11u IPv4 22940 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45779->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3975 john 9u IPv4 22778 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:47441->ww-in-f149.1e100.net:http (ESTABLISHED)
    kio_http 3977 john 10u IPv4 22969 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45789->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3979 john 11u IPv4 22943 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45782->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3982 john 10u IPv4 22939 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45778->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3983 john 13u IPv4 22970 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45790->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 4018 john 10u IPv4 21855 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:57461->ww-in-f149.1e100.net:http (ESTABLISHED)
    kio_http 4020 john 9u IPv4 22942 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45781->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 4021 john 9u IPv4 22944 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45783->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 4024 john 9u IPv4 22998 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45794->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 4025 john 8u IPv4 22938 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45777->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 4026 john 9u IPv4 22941 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45780->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 4097 john 8u IPv4 22982 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45792->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 4098 john 9u IPv4 23163 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:51909->narwal.opensuse.org:https (CLOSE_WAIT)
    kio_http 4099 john 9u IPv4 23220 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:51914->narwal.opensuse.org:https (ESTABLISHED)
    kio_http 4100 john 9u IPv4 23229 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:51915->narwal.opensuse.org:https (ESTABLISHED)

    Login evening 27/11/2009
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    kio_http 8802 john 18u IPv4 55088 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:47573->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 8804 john 16u IPv4 54520 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:53905->ww-in-f149.1e100.net:http (ESTABLISHED)
    kio_http 8806 john 18u IPv4 55161 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:49519->ey-in-f102.1e100.net:http (ESTABLISHED)
    kio_http 8988 john 9u IPv4 54983 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:53986->ww-in-f149.1e100.net:http (ESTABLISHED)
    kio_http 9005 john 9u IPv4 55386 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:53901->secure-www.novell.com:https (ESTABLISHED)
    kio_http 9006 john 8u IPv4 55387 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:36846->narwal.opensuse.org:https (ESTABLISHED)
    kio_http 9007 john 8u IPv4 55484 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:54937->66.235.133.11:https (SYN_SENT)

    Login evening 28/11/2009
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    kio_http 3906 john 12u IPv4 15711 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:50747->82.109.196.45:http (CLOSE_WAIT)
    kio_http 3911 john 12u IPv4 16035 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45577->ww-in-f138.1e100.net:http (ESTABLISHED)
    kio_http 3968 john 9u IPv4 15747 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:34192->77.67.20.162:http (ESTABLISHED)
    kio_http 3969 john 9u IPv4 15958 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:33660->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3978 john 9u IPv4 16261 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:39374->66.235.133.11:https (ESTABLISHED)
    kio_http 3979 john 8u IPv4 16172 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:60198->secure-www.novell.com:https (ESTABLISHED)
    kio_http 3980 john 8u IPv4 16175 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:45076->narwal.opensuse.org:https (CLOSE_WAIT)

    Login evening 29/11/2009
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    kio_http 4400 john 9u IPv4 22919 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:57135->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 4402 john 8u IPv4 22823 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:54456->cot.novell.com:http (ESTABLISHED)
    kio_http 4404 john 9u IPv4 22946 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:57139->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 4405 john 9u IPv4 22945 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:57138->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 4407 john 8u IPv4 22911 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:57132->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 4420 john 9u IPv4 23183 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:60189->narwal.opensuse.org:https (ESTABLISHED)
    kio_http 4421 john 9u IPv4 23225 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:60195->narwal.opensuse.org:https (ESTABLISHED)
    kio_http 4422 john 9u IPv4 23224 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:60194->narwal.opensuse.org:https (ESTABLISHED)

    Login morning 30/11/2009
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    kio_http 3856 john 12u IPv4 17096 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:35717->wy-in-f100.1e100.net:http (ESTABLISHED)
    kio_http 3872 john 15u IPv4 17221 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:57917->84.53.132.35:http (ESTABLISHED)
    kio_http 3873 john 19u IPv4 17490 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:47562->narwal.opensuse.org:http (CLOSE_WAIT)
    kio_http 3987 john 9u IPv4 17087 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:34736->ww-in-f148.1e100.net:http (ESTABLISHED)
    kio_http 3990 john 9u IPv4 17668 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:40802->narwal.opensuse.org:https (CLOSE_WAIT)
    kio_http 3991 john 8u IPv4 17582 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:35741->wy-in-f100.1e100.net:http (ESTABLISHED)
    kio_http 3997 john 9u IPv4 17181 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:34751->ww-in-f148.1e100.net:http (ESTABLISHED)
    kio_http 4025 john 8u IPv4 17777 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:38109->scm-api2.oak1.omniture.com:https (ESTABLISHED)
    kio_http 4026 john 8u IPv4 17697 0t0 TCP 82-47-182-199.cable.ubr01.hali.blueyonder.co.uk:40807->narwal.opensuse.org:https (ESTABLISHED)

  9. #39
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    17,048

    Default Re: Login screen certificate not authentic

    On Mon, 30 Nov 2009 08:46:01 +0000, john hudson wrote:


    > Don't know how helpful this will be but the output is varying a bit; on
    > a couple of occasions I only got one error message whereas on others it
    > has been three or more.


    One question that has come up in diagnosing this is which browser you're
    using, and if you can duplicate with more than one?

    Jim



    --
    Jim Henderson
    openSUSE Forums Moderator

  10. #40
    Join Date
    Jun 2008
    Location
    West Yorkshire, UK
    Posts
    3,448

    Default Re: Login screen certificate not authentic

    I'm now on Firefox but didn't get any error messages. I use Konqueror routinely, since before I joined the forum, and I started this thread when the messages first appeared on this forum.

    It has occurred before on the Build Service, but not on the main site or Bugzilla or any other openSUSE or Novell related sites, and recently on a website in the city of London but I use Konqueror intensively because of the research I do and must have been on hundreds of sites all over the world over the past few years. Yet the error messages have only ever appeared on three sites, this being the third.

    Over the past weekend, I have had error messages nearly every time I logged on - which is probably the most intense period since I first reported the issue but I have had none on logging off for several days.

Page 4 of 5 FirstFirst ... 2345 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •