| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Those will be moved to a different branch for the time being since other stuff needs to be changed first
|
|
|
|
| |
keychain and with a warning to the user
|
|
|
|
|
|
| |
* Remove forward SDK declaration for 10.8 and below (since that is the minimum required development SDK)
* Fix one case where a method unconditionally required a 10.9+ runtime
* Move all of the forward/backward hacks into their own file
|
| |
|
|
|
|
| |
This should also eliminate a few use-after-free crashes
|
|
|
|
| |
(From the department of commits to be rolled back soon)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
- Fix long-standing intermittent crashes caused by connection errors after SSH tunnels were established
- Fix edits causing keychain -25299 errors (Issue #1340)
- Allow changes of favourite type to be saved rather than disassociating the edit from the selection
- Fix the favourites view scrolling to the top when there's no selection and connection details are being edited
- Fix some issues with automatic naming of connections on connection type change
|
|
|
|
| |
than deleting and recreating them. This has two advantages: firstly, it matches the Apple recommendation, as it preserves keychain item access lists and comments for keychain items when they are edited; secondly, it works around a bug in 10.7 which appears to be a Keychain cacheing issue, causing password retrievals to return the original keychain item on launch - which is no longer valid after deletion/recreation. This addresses Issue #1197.
|
|
|
|
| |
instead of an empty string; the MySQL manual suggests that maybe we should be doing this, and it may address Issue #1065.
|
|
|
|
|
|
|
|
|
| |
- Fix further compiler warnings, including a couple of bugs
- Disable the -wselector warnings (Multiple definition types for selector) as they're currently unsupported in LLVM
- Disable the -wconversion warnings (Prototype conversion) warnings as we usually can't affect protocol declaration
- Disable the -wstrict-selector-match (Strict selector matching) due to too many false positives
|
|
|
|
|
|
|
| |
- Change MCPConnection.m to no longer use a reference to tableWindow to attach sheets - instead use a delate error display method if available
- Rework TableSource and TableContent sheetDidEnd methods into per-task methods rather than overloading contextInfo
- Rework SPAlertSheets to perform actions on the main thread, with the loss of (unused) support for a didDismissSelector. This addresses a number of crashes logged by the crash reporter
|
|
|
|
| |
favorites (Thanks Hans).
|
|
|
|
| |
inspection of leaks and Clang static analysis.
|
|
|
|
|
|
| |
- Fix incorrect uses of [NSString stringWithFormat:] with preconstructed strings and no arguments in SPUserManager
- To fix display issues, replace NSBeginAlertSheet (which includes automatic sprintf expansion of the message) with a safely-escaped SPBeginAlertSheet in many files
|
|
|
|
|
|
|
| |
release builds, including a large number of 64bit compatibility upgrades and tweaks
- Upgrade RegexKitLite to 3.3
|
|
|
|
|
|
| |
must be a \0 terminated cString
- fixed that and replaced the deprecated method [NSString stringWithCString:length] again
|
|
|
|
| |
r1313 leads to the issue that no password can be read from the keychain; reverted to r1212 in order to keep SP workable until a fix is found
|
|
|
|
| |
SPQueryConsole rename.
|
|
|
|
| |
a dialog to user, suggesting the repair their Keychain or contact us if the problem persists.
|
|
|
|
|
|
|
| |
by checking a keychain item is present before trying to load it
- Also make keychain checks more robust when supplying nil values as some of the parameters
|
|
|