stf on Nostr: in liboprf we have an updatable OPRF without using a pairing, and with klutschnik we ...
in liboprf we have an updatable OPRF without using a pairing, and with klutschnik we have a project that does updatable public key encryption, for data at rest. why is their upstream academic research not even mentioned in this paper:
https://eprint.iacr.org/2025/175Hugo Krawczyk is even a colleague of some of these authors.
#upke #crypto #oprf
Published at
2025-02-07 15:31:00Event JSON
{
"id": "8c1587ef12411ce0f4979e338809e1a62940542ea678b7d214cb564a7ac65002",
"pubkey": "b887bffcf63863763c712604944ba34cf6b4674aba9d9ad586fda383be9f07c8",
"created_at": 1738942260,
"kind": 1,
"tags": [
[
"t",
"upke"
],
[
"t",
"crypto"
],
[
"t",
"oprf"
],
[
"proxy",
"https://chaos.social/users/stf/statuses/113963319981156002",
"activitypub"
]
],
"content": "in liboprf we have an updatable OPRF without using a pairing, and with klutschnik we have a project that does updatable public key encryption, for data at rest. why is their upstream academic research not even mentioned in this paper: https://eprint.iacr.org/2025/175\n\nHugo Krawczyk is even a colleague of some of these authors.\n\n#upke #crypto #oprf",
"sig": "5883a3bd9da18f83bd7f71a07b2368da59111f5ddfbe6f9029c528434a8af5170e3e1d5db662886651c86a840e308d963440cc328cdc838089cdebf4e992189d"
}
