| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| | |
Conflicts:
NEWS
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Otherwise, if a caller kept a ref to the GAsyncResult after control had
returned to the channel, the channel could have freed the GString
already.
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=45554
Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
Reviewed-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
|
| | |
|
|/ |
|
|
|
|
|
| |
The pointer goes stale when the result is consumed,
and it trips an assertion if the manager gets a new challenge.
|
| |
|
|
|
|
|
| |
Server-side base classes tend to be named TpBase*, so rename this class to
make it more consistent with other base classes to be used by CMs.
|
| |
|
|
|
|
|
|
|
|
|
| |
Instead of having both prompt_async() and prompt_for_channel_async() call the
same _finish() function, provide a separate function for the custom channel
case. This function will also return the custom channel that was originally
passed to prompt_for_channel_async(). This way, the API user doesn't need to
carry around the channel in user_data in the case that they need to query the
channel for information after the prompt has completed.
|
|
|
|
|
|
|
| |
This API allows applications to supply their own channel object to be used in
the password manager. The use case for this is when an authentication channel
needs to implement additional interfaces. In this case, they can inherit from
TpSimplePasswordChannel and implement these custom interfaces in the subclass.
|
| |
|
|
|
|
| |
Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
|
|
|
|
| |
Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
|
| |
|
|
|
|
| |
Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
|
|
|
|
|
|
| |
GError*
Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
|
|
|
|
| |
Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
|
|
Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
|