Menu

#41 Stealth mode desactivate himself when waste is restarted

open
md5chap
None
2
2004-09-29
2004-06-22
Anonymous
No

I found this bug after a reboot, it couldnt connect
automatically to other node of my network. The
"Activate stealth mode" tickbox doesnt seems to save
its states when waste closes. (sorry for aproximative
english)

Discussion

  • PacketCollision

    PacketCollision - 2004-06-22

    Logged In: YES
    user_id=1051319

    I can confirm this with waste 1.5beta2.

    STEPS TO REPRODUCE BUG:
    1)Open WASTE
    2)check "activate stealth mode" in Preferences->Password
    3)close preferences
    4)close WASTE
    5)reopen WASTE

    Checkbox will not be checked.

     
  • Eric

    Eric - 2004-06-22

    Logged In: YES
    user_id=945916

    Looking into it.

     
  • Eric

    Eric - 2004-06-22
    • assigned_to: nobody --> md5chap
     
  • md5chap

    md5chap - 2004-06-23

    Logged In: YES
    user_id=1059934

    This is a gui-problem only....
    The stealth mode does ONLY work if you have a password
    supplied.
    The stealth mode hides the handshake between clients by
    using a password.
    I will mention that on the password tab in the next version....

     
  • Gonzo Granzeau

    Gonzo Granzeau - 2004-06-28

    Logged In: YES
    user_id=328

    I cannot duplicate this problem, but I suspect it's because
    the other end he's connecting to gets demoted to 0 rank when
    it's not able to eventually connect to it. So it might be
    related to this bug:

    http://sourceforge.net/tracker/index.php?func=detail&aid=976399&group_id=82356&atid=565809

    I would recommend the person save a copy of the directory,
    reinstall fresh, and the import the keys again and see if
    that fixes the issue.

     
  • Chris

    Chris - 2004-09-29
    • priority: 5 --> 2
     
  • Chris

    Chris - 2004-09-29

    Logged In: YES
    user_id=573676

    The window itself should disallow the checkbox if there is
    not a network name > 15chars. The [?] button explains this,
    but apparently the checkbox behaviour is causing some
    confusion.

    I'm lowering the priority of this bug since its cosmetic only

     

Log in to post a comment.

MongoDB Logo MongoDB