Skip to main content

Home/ Diigo Community/ autologin no longer working
Jim McClintock

autologin no longer working - 116 views

Firefox 3.5 beta bug resolved

started by Jim McClintock on 01 May 09
  • Graham Perrin
    #2 Graham Perrin on 01 May 09
     
    Please let us know versions of your:

    * operating system
    * browser
    * toolbar.

    Thanks.
  • Jim McClintock
    #3 Jim McClintock on 03 May 09
     
    WindowsServer 2003 SP2
    Firefox 3.5 beta 4
    Diigo version 3.1.6.13
  • Jim McClintock
    #4 Jim McClintock on 06 May 09
     
    Haven't heard from anyone, so I'm reposting this info. If anyone can help, please let me know.

    WindowsServer 2003 SP2
    Firefox 3.5 beta 4
    Diigo version 3.1.6.13

    Thanks in advance for any guidance anyone can provide.
  • Graham Perrin
    #5 Graham Perrin on 06 May 09
     
    > Firefox 3.5 beta 4

    That version of Firefox is not supported.
  • Graham Perrin
    #7 Graham Perrin on 07 May 09
     
    Elsewhere in this forum, there's a topic explaining how to force an unsupported workaround.
  • Jim McClintock
    #8 Jim McClintock on 07 May 09
     
    Does the workaround make autologin work? I already changed the rdf file from FF3.1 to FF 3.5 b4, but that didn't make the auto login work.

    If there's something more to the workaround, could you please provide me a link to it. Thanks!
  • Jim McClintock
    #10 Jim McClintock on 14 May 09
     
    I have had Nightly Tester Tools installed since the first betas for Firefox 3.0. It doesn't fix whatever problem arises from Diigo's interaction withe Firefox 3.5 Beta 4.

    What I don't understand is why login credentials are not included in Diigo's options/preference settings, thereby providing for permanent inclusion of user login info in the Diigo settings file instead of (apparently) relying upon stored cookies as the vehicle for storing user login info. Cookies are a much less reliable storage medium.
  • Graham Perrin
    #11 Graham Perrin on 21 May 09
     
    > (apparently) relying upon stored cookies as the vehicle for
    > storing user login info.

    AFAIK:

    * the cookie contains no credentials, no login info

    * the cookie is granted after secure communication of credentials.

    > permanent inclusion of user login info in the Diigo settings file

    From a security perspective, passwords should never be stored in preference/settings files.
  • Jim McClintock
    #12 Jim McClintock on 21 May 09
     
    Graham,

    Thanks for your responses. How do I get someone from diigo to address this issue. Autologin worked. For firefo rmd thru beta 3.3
    Final release for 3.5 will be sometime this summer, so diigo will have to address it soon anyway, I would think. I don't really care how diigo does it, but Mozilla itelf uses a stored login/ password for its Weave extension, Google does same for Google toolbarn StumbleUpon does same for its toolbar, AccuWeather does same for its extension, etc.
    Apparently all these vendors find it acceptable from a security perspective to store passwords locally.

    Anyway, thanks for your help,
  • Graham Perrin
    #13 Graham Perrin on 21 May 09
     
    Hi Jim

    Diigo people periodically remind us (the group) that all messages are read by them but that (for example) they

    > may not be able to answer every single email / post personally :-)

    I guess that attention will not shift to beta versions of browsers until after priority issues have been addressed.

    Kind regards
    Graham
  • Graham Perrin
    #14 Graham Perrin on 05 Aug 09
  • Graham Perrin
    #20 Graham Perrin on 06 Aug 09
  • Graham Perrin
    #22 Graham Perrin on 07 Aug 09
     
    Jim McClintock wrote:

    > The problem I experienced related to a beta version of Firefox. I
    > eventually realized it wasn't Diigo specific in any way

    Thanks to Jim for the positive feedback. It's good to know that the problem was not related to Diigo. With that in mind I have removed the Diigo-related tags from this topic.

    This topic (originated by Jim) remains resolved.

To Top

Start a New Topic » « Back to the Diigo Community group