[knetattach] [Bug 327133] New: knetattach becomes unresponsive when examining a cert

Per (phobie) kdebugs.phobie at safersignup.com
Mon Nov 4 15:13:37 GMT 2013


https://bugs.kde.org/show_bug.cgi?id=327133

            Bug ID: 327133
           Summary: knetattach becomes unresponsive when examining a cert
    Classification: Unclassified
           Product: knetattach
           Version: unspecified
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: kdebugs.phobie at safersignup.com

Webdav connections fails/freezes if a user examines a self-signed certificate.
A workaround is to open the notification,
stop the "Examining"-"Transfers"-action,
close knetattach and
start over.

Reproducible: Always

Steps to Reproduce:
1. Open knetattach
2. Select "Webfolder (webdav)"
3. Enter any values for "Name", "User" and "Folder"
4. Enter any webserver with a self-signed-certificate under "Server" i.e.
"www.us.army.mil"
5. Check "Use encryption"
6. Click "Save & Connect"
7. Click "Details" on "Server Authentication - KDE Network Wizard"-window
8. Click "Close" on "KDE SSL Information - KDE Network Wizard"-window
Actual Results:  
Clicking on "Details"
opens the "KDE SSL Information - KDE Network Wizard"-window and
closes the "Server Authentication - KDE Network Wizard" window.
After closing the certificate-information, we are left with a blocked
main-window and a running "Examining"-"Transfers"-action.

Expected Results:  
Do not close the "Server Authentication"-window when clicking on "Details" to
let the user accept or reject the certificate after examining it.
Stop the "Examining"-"Transfers"-action when closing the
certificate-information-window.

Btw. if you chose to not save your password, it should be cached until the
session is closed. I need to type it three times from creation to using the
folder in dolphin.

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list