aboutsummaryrefslogtreecommitdiffstats
path: root/common/rfb/CSecurityRSAAES.cxx
Commit message (Collapse)AuthorAgeFilesLines
* Always flush sockets on shutdown()Pierre Ossman5 days1-0/+15
| | | | | | | | The system shutdown() function doesn't drop buffered data, so neither should we. We had one fix in place, but that didn't cover all cases. Move this handling to all socket like classes we have.
* Change some assertions to exceptionsPierre Ossman2024-11-221-1/+3
|
* Capitalize some more logging and exceptionsPierre Ossman2024-11-221-13/+13
|
* Use standard library naming for exceptionsPierre Ossman2024-11-061-8/+8
| | | | | This makes things more consistent since we mix with the standard library exceptions so often.
* Use specific class for protocol problemsPierre Ossman2024-11-061-7/+7
| | | | Make it easier to identify communication issues.
* Use standard exception classesPierre Ossman2024-11-061-6/+6
| | | | | Use the more specific already included exception classes for common errors to keep things more understandable.
* Correctly handling rejecting server keyPierre Ossman2024-09-041-1/+1
| | | | | This is the user actively rejecting the connection, and should be signalled as such for correct behaviour.
* Move getUserPasswd()/showMsgBox() to CConnectionKang Lin2024-08-301-4/+3
| | | | | 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-12/+12
| | | | | | | | 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.
* Use nullptr in all C++ codePierre Ossman2024-06-241-9/+10
| | | | | It's more readable than 0, and a bit safer than NULL, so let's try to follow modern norms.
* 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.
* Remove unused rfb/util.h includesPierre Ossman2023-02-041-0/+1
| | | | | | | | These files don't use anything from this header, so remove the include. This exposes some missing includes in other places, though. So add an explicit include in the files that were relying on an indirect inclusion.
* Remove "str" prefix from string helpersPierre Ossman2023-02-041-1/+1
| | | | | This matches the naming in STL, which is what we are mostly mimicing now that we are using std::string for these functions.
* Use std::string instead of CharArrayPierre Ossman2023-02-041-3/+2
| | | | | Let's use a more common type instead of something homegrown. Should be more familiar to new developers.
* Return std::string instead of dynamic allocationsPierre Ossman2023-02-041-18/+15
| | | | | | 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 stdint typesPierre Ossman2023-02-011-38/+38
| | | | | Avoid having our own custom stuff and instead use the modern, standard types, for familiarity.
* Explicitly mark switch case fall throughPierre Ossman2023-01-051-0/+3
| | | | | This allows us to separate accidental fall through from explicit ones, which allows us to turn on such checks in the compiler.
* Fix RSA-AES state machinesPierre Ossman2023-01-051-22/+19
| | | | | | | | | | If there isn't enough data, then the client reading the hash will fall down and try to read the subtype instead, which isn't correct. Invert the logic so we get a more consistent way through where we only break out when there is insufficient data. Do the same for the server code, for consistency.
* Add support for RSA-AES security typespdlan2022-09-011-0/+461