| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
This line should have a single sentence.
|
| |
|
| |
|
|
|
|
|
| |
The `(allow-none)` annotation was deprecated for `(nullable)` and
`(optional)` to solve some ambiguous uses of the tag.
|
|
|
|
|
|
|
| |
This adds the secret_value_unref_to_password function that
unreferences and returns the stored secret in non-pageable memory.
This is supposed to be used with secret_password_lookup_binary*
functions.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=785034
|
|
|
|
| |
This is with the exception of the 'path' functions.
|
| |
|
|
|
|
|
|
|
|
|
| |
Passwords and other secrets are allowed to be empty strings, therefore
the check for length != 0 is wrong.
Add tests for empty SecretValue contents.
https://bugzilla.gnome.org/show_bug.cgi?id=694787
|
|
|
|
|
|
| |
This works around a crash in pygobject.
https://bugzilla.gnome.org/show_bug.cgi?id=694448
|
|
|
|
| |
* Add add more warnings to unstable API documentation
|
|
|
|
|
|
|
| |
* C callers need to use libsecret-0 pkg-config file for stable and
libsecret-unstable for unstable stuff.
* Vala callers need to '--pkg libsecret-unstable' for unstable
* GObject Introspection callers need to use the SecretUnstable package
|
|
* Death by a thousand paper cuts from gir and vapi not liking
the fact that the secret.h file was not usable uninstalled
and installed in the same way.
|