Closed #2515 as completed via 01fb42d42ca710bf24e3af841d43b4e3d60b3aef.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2515#event-10967022569
You are receiving this because you are subscribed to this thread.
Message ID:
__
I guess the remaining thing here is to explicitly document the rpm API behavior
wrt this.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2515#issuecomment-1810020028
You are receiving this because you are subscribed to this thread.
Me
>so you if you restrict version to rpm 4.18 and newer, you can just do
>"can_sign = TRUE".
That's exactly what I'm doing. I was just afraid of returning a false positive.
But if since rpm >= 4.18 rpm only returns signing capable subkeys it's fine.
I should just change my comment in the librepo c
I'm afraid none of that info is exposed as such in the rpm API.
That said, since rpm >= 4.18 rpm only returns signing capable subkeys and in
the first place, so you if you restrict version to rpm 4.18 and newer, you can
just do "can_sign = TRUE".
--
Reply to this email directly or view it on Gi
GpgMe provides a lot of information (attributes) about keys/subkeys -
`revoked`, `expired`, `can_sign`,
So far we have used `can_sign` in the librepo library. How to get this
information via librpm API?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-m
