aboutsummaryrefslogtreecommitdiffstats
path: root/common/rfb/CSecurityDH.cxx
Commit message (Collapse)AuthorAgeFilesLines
* Capitalize some more logging and exceptionsPierre Ossman2024-11-221-4/+4
|
* Use standard library naming for exceptionsPierre Ossman2024-11-061-2/+2
| | | | | This makes things more consistent since we mix with the standard library exceptions so often.
* Use specific class for protocol problemsPierre Ossman2024-11-061-2/+2
| | | | Make it easier to identify communication issues.
* Use standard exception classesPierre Ossman2024-11-061-4/+4
| | | | | Use the more specific already included exception classes for common errors to keep things more understandable.
* Move getUserPasswd()/showMsgBox() to CConnectionKang Lin2024-08-301-1/+1
| | | | | Problems with the original code: A process can only establish one connection. After modification, multiple connections can be supported.
* Avoid connection failed exceptionPierre Ossman2024-08-131-2/+2
| | | | | The usage of this is unclear as it is never caught. Use the general exception class, to stay consistent with all other protocol handling.
* Don't abuse auth failure exceptionPierre Ossman2024-08-071-4/+4
| | | | | | | | This exception is for when the user fails to authenticate, not all possible errors that might occur during the authentication phase. Use more appropriate exception types for the various other problems that might occur, so that we can present things more accurately to the user.
* Avoid shadowing variablesPierre Ossman2024-06-241-2/+2
| | | | | It's a source of confusion and possibly bugs to reuse the same variable name for multiple things.
* Consistently use uint8_t for data buffersPierre Ossman2023-03-181-2/+2
| | | | | These will always be byte streams at heart, so let's try to keep them with a proper type. Should make it clearer how they will be used.
* Return std::string instead of dynamic allocationsPierre Ossman2023-02-041-9/+8
| | | | | | We mostly use classical C strings, but the memory management around them can get confusing and error prone. Let's use std::string for the cases where we need to return a newly allocated string.
* Use std::vector for basic data arraysPierre Ossman2023-02-011-16/+15
| | | | | Avoid our own custom types in favour of what's already included with C++.
* Use stdint typesPierre Ossman2023-02-011-3/+4
| | | | | Avoid having our own custom stuff and instead use the modern, standard types, for familiarity.
* Fix CRLF line endingsPierre Ossman2023-01-171-150/+150
| | | | Everything else uses LF line endings, so fix up the few stray ones.
* Add client-side support for the DH security type.Dinglan Peng2022-12-271-0/+150