hazaar/hazaar-dbi
1
0
Fork 0
Code Issues Pull requests Projects Releases 8 Packages Wiki Activity Actions

Query on encrypted fields #70

New issue
Closed
opened 2021-03-31 01:10:13 +00:00 by jamie · 3 comments
jamie commented 2021-03-31 01:10:13 +00:00 (Migrated from git.hazaar.io)
Copy link

I need to be able to query on an encrypted field. I am encrypting an API key in the database and need to take the key given when a client host requests API access and lookup that key in the database. Currently I would have to do this manually but I can make this nicer by doing it transparently during the query.

I need to be able to query on an encrypted field. I am encrypting an API key in the database and need to take the key given when a client host requests API access and lookup that key in the database. Currently I would have to do this manually but I can make this nicer by doing it transparently during the query.
jamie commented 2021-03-31 22:35:31 +00:00 (Migrated from git.hazaar.io)
Copy link

created merge request !42 to address this issue

created merge request !42 to address this issue
jamie commented 2021-03-31 22:35:31 +00:00 (Migrated from git.hazaar.io)
Copy link

mentioned in merge request !42

mentioned in merge request !42
jamie commented 2021-04-01 03:37:41 +00:00 (Migrated from git.hazaar.io)
Copy link

Yeah, I'ma dumbass. This isn't going to be possible. Using algorithms like AES and such means that the IV is stored in the encrypted value so we can't get encrypt the search criteria and generate the exact same result. So without significant changes that would probably result is massive performance impacts, this is going to be a futile effort.

Yeah, I'ma dumbass. This isn't going to be possible. Using algorithms like AES and such means that the IV is stored in the encrypted value so we can't get encrypt the search criteria and generate the exact same result. So without significant changes that would probably result is massive performance impacts, this is going to be a futile effort.
jamie (Migrated from git.hazaar.io) closed this issue 2021-04-01 03:37:46 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
1.4-develop
1.3-develop
release-2.3.1
release-2.3.0
release-2.2.5
release-2.2.4
release-2.2.3
release-2.2.2
release-2.2.1
release-2.2.0
release-2.1.0
release-2.0.3
release-2.0.2
release-2.0.1
release-1.4.1
release-1.3.2
release-2.0.0
release-1.4.0
release-1.3.1
release-1.3.0
release-1.2.11
release-1.2.10
release-1.2.9
release-1.2.8
release-1.2.7
release-1.2.6
release-1.2.5
release-1.2.4
release-1.2.3
release-1.2.2
release-1.2.1
release-1.2.0
release-1.1.9
release-1.1.8
release-1.1.7
release-1.1.6
release-1.1.5
release-1.1.4
release-1.1.3
release-1.1.2
release-1.1.1
release-1.1.0
release-1.0.8
release-1.0.7
release-1.0.6
release-1.0.5
release-1.0.4
release-1.0.3
release-1.0.2
release-1.0.1
release-1.0.0
Labels
Clear labels   
bug

   
confirmed

   
critical

   
discussion

   
documentation

   
Doing

   
enhancement

   
suggestion

   
support

   
To Do
No labels
bug
confirmed
critical
discussion
documentation
Doing
enhancement
suggestion
support
To Do
Milestone
Clear milestone
No items
No milestone
Release 2.4.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: hazaar/hazaar-dbi#70
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?