| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
- QL1S/QL1C
- single-char QString efficiency
- explicit ctors
- normalized signals & slots
|
|
|
|
|
|
| |
- QL1S
- one stupid kDebug less
- codingstyle
|
|
|
|
|
|
|
|
|
|
| |
I hope I addressed here a number of fixes in my first implementation:
- working hasSSLValid() function (checking cert validity and chain errors)
- escaping certificate strings
- typos (Sha256/Md5, supportedCipherBits/usedCipherBits)
- encryption check (at least I hope so)
CCMAIL: rich@kde.org
|
|
|
|
|
|
| |
Hopefully addressed the problems against our (new) SSL code.
CCMAIL:timb@nth-dimension.org.uk
|
| |
|
| |
|
| |
|
|
|
|
| |
Now we are ready for the fight...
|
|
|
|
|
|
|
| |
These are last changes to clean up and improve SSL rekonq
communications.
It is yet missing a proper SSL errors API integration. You just need
to wait for the next commit...
|
|
|
|
|
|
| |
Now they really seem "similar" to the ones provided by Google Chrome
and Firefox.
They all need further improvements, anyway...
|
|
While the widget "copies" and "rethink" Google Chrome actual one,
the dialog has been implemented starting from the comparison
between the ones we have in KDE, Google Chrome's and Firefox's.
I have to start from somewhere...
|