Compatibility with data from deprecated bjornvoesten/laravel-ciphersweet

[sebastiansson]

Is the indexes and encrypted data generated by bjornvoesten/laravel-ciphersweet compatible with this package? After installing this package, I get no results when searching with this package:

User::query() ->whereEncrypted('social_security_number', '=', '123-456-789') ->orWhereEncrypted('social_security_number', '=', '123-456-789') ->get();

I have the same CIPHERSWEET_KEY and ENCRYPTION_CRYPTO in my .env as I had when using the old package (bjornvoesten/laravel-ciphersweet).

I tried generating a new model instance with this package and the index row seems much shorter than the old package. So the data generated seem to differ?

[bjornvoesten]

I'm really sorry about the very late response, I have been very busy lately.
If i'm being hones, I haven't tested this scenario and don't have the time to do so right now.
Did you find the answer yourselves already?

[sebastiansson]

No worries, thanks for the response anyway!

No, we're investegating on migrating to this from bjornvoesten/laravel-ciphersweet. So I was thinking of a way to migrate without having to re-encrypt all the data in our db. So my hope was that I could swap the repo and use the data we already had.

Would you be open to explain why you abandoned the bjornvoesten/laravel-ciphersweet repo and what's the difference between the repos? So we can decide if we need to swap repos or can continue using bjornvoesten/laravel-ciphersweet.

[sebastiansson]

Had anytime looking into this @bjornvoesten?

[bjornvoesten]

Has been a long ago and to be honest I am not working on projects anymore which uses this, and also can't find the time / motivation to dive into it again. As far as I can remember I wanted to do a rewrite, and in hindsight I could've probably done this in a major release.