| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
In 0e205fce5fbfa8f2c6f6ac0acc890311ff333d04 I improperly assumed that
the cancellable would always be valid. Avoid criticals when it is NULL.
|
|
|
|
|
|
|
|
|
| |
Calling g_cancellable_disconnect() inside a cancelled handler is a
guaranteed deadlock. Cancellables should only be canceled once, so we
don't need to worry about a second cancellation occurring. I think it's
sufficent to disconnect when the InitClosure is freed.
Fixes #86
|
|
|
|
|
|
|
|
|
|
|
|
| |
GLib is discussing deprecating/removing it upstream [1] since it has
only limited uses. Next to that, it seems to bork stack traces here when
using ASAN (for which you also have to specify `G_SLICE=always-malloc`
and some other envvars too).
In other words, let's just get rid of using `GSlice` and call the
allocation APIs directly.
[1]: https://gitlab.gnome.org/GNOME/glib/-/issues/1079
|
|
|
|
|
|
|
|
| |
That way, we have a function we can also call in case we want to provide
a synchronous constructor.
This also fixes some cases where the `EggTpm2Context` was not properly
cleaned up in case of some error paths.
|
|
|
|
| |
A small cleanup
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Our GAsyncInitable implementations in SecretService, SecretCollection,
and SecretItem internally wrap GDBusProxy::init_async and perform
additional error processing. To chain up we used to pass around a
single GTask, which caused an issue in the (additional) error path:
GDBusProxy::init_async may have already called
g_task_return_boolean(task, TRUE) and in that case GLib produces the
following warning:
g_task_return_error: assertion '!task->ever_returned' failed
This fixes the issue by creating a temporary GTask around
GDBusProxy::init_async call.
Signed-off-by: Daiki Ueno <dueno@src.gnome.org>
|
| |
|
| |
|
|
|
|
| |
Only one doc will appear in gir and gi-docgen docs.
|
|
|
|
|
| |
Indentations by more than four spaces make gi-docgen read them as a
quote block.
|
| |
|
|
|
|
| |
Macros do not use Returns annotation.
|
|
|
|
| |
This line should have a single sentence.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
These changes fix the existing deprecated-declarations
warnings found during the build process.
Related to: https://gitlab.gnome.org/GNOME/libsecret/-/merge_requests/43
|
|
|
|
|
|
|
| |
Some Secret Service API backend implementations (like keepassxc)
throws UnknownObject (instead of UnknownMethod as gnome-keyring do)
after creating an item in the non-existent
/org/freedesktop/secrets/aliases/default.
|
|
|
|
|
| |
These changes add TPM2 derived encryption key to secret
file backend.
|
| |
|
|
|
|
| |
It is already closed a few lines above
|
|
|
|
|
|
|
| |
The documentation of g_dbus_error_register_error_domain suggests that
the argument passed to it should not be volatile.
Signed-off-by: Daiki Ueno <dueno@src.gnome.org>
|
|
|
|
|
| |
These changes specifically fix the issues flagged by clang-analyzer.
Fixes: #59
|
|
|
|
|
|
|
| |
When full filenames are used in generated sources it makes the resulting
debug packages non-reproducible. Best practise is to use basename instead.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
| |
`GSimpleAsyncResult` is deprecated in favor of `GTask`.
|
|
|
|
| |
`GSimpleAsyncResult` is deprecated in favor of `GTask`.
|
| |
|
|
|
|
| |
This looks cleaner for the docs generated by the several bindings.
|
| |
|
|
|
|
|
| |
The `(allow-none)` annotation was deprecated for `(nullable)` and
`(optional)` to solve some ambiguous uses of the tag.
|
|
|
|
|
| |
Give our API consumers an extra hint if they're using varargs without an
appropriate `NULL`-sentinel.
|
|
|
|
| |
Fixes: https://gitlab.gnome.org/GNOME/libsecret/-/issues/54
|
|
|
|
|
| |
Fixes an issue with annotations that would cause
Rust bindings to generate incorrectly.
|
| |
|
|
|
|
|
|
|
|
|
| |
Our official instructions only tell how to build with Meson, our CI is
only done with Meson and I wouldn't be surprised if most developers only
used Meson as well.
In other words, the autotools build is outdated. Let's say our goodbye
and drop it in the next stable release.
|
| |
|
|
|
|
|
| |
Make sure libgcrypt is initialized before any SecretFileCollection
instance uses it.
|
|
|
|
| |
Also add a test suite argument to more easily distinguish them.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Add an option 'introspection' for meson which could control whether
build GIR files or not.
Signed-off-by: Kai Kang <kai.kang@windriver.com>
|
|
|
|
|
|
|
| |
The on_portal_retrieve_secret() can connect a GCancellable, but it
doesn't disconnect from it (only when the cancellable is cancelled),
which means when the cancellable is cancelled later, when the GTask
is gone, the callback is called with already freed data.
|
|
|
|
|
|
|
| |
Libraries shouldn't really use `g_message()` as it will show up in
consumer application outputs. Let's use `g_info()` instead.
Fixes https://gitlab.gnome.org/GNOME/libsecret/issues/40
|
|
|
|
|
| |
Some people might want to statically link to libsecret, so use the more
general `library()` target to build libsecret.
|
|
|
|
|
|
| |
As the GVariant serialization format does not record the original
endianness of integer values, we need to ensure that it doesn't change
between write and load.
|
|
|
|
|
|
|
| |
This is similar to 0be63575ff47f19cff3688985c7f00e92bc25541 but for
test-file-collection.c.
Fixes #36.
|