Do you guys usually exposes the dependencies as in...

# random

[Ianmedeiros]

Do you guys usually exposes the dependencies as interfaces and inject a different implementation on tests, or do you make them open?

The downside of exposing interfaces just to make it testable is that you need to @Bind the implementation with dagger instead of just annotating the class constructor with @Inject.

Any considerations about that?

[jlleitschuh]

MD5: 344aab9758bb0d018b93739e7893fb3a

[Kristoffer Andersen]

You got me.

[Matteo Mirk]

could someone explain the joke to me? 😅

[LeoColman]

If you reverse that MD5, it stands for never gonna give you up

[LeoColman]

So anybody that searched it got rick rolled.

[itnoles]

https://www.youtube.com/watch?v=VIYs1ZXrYwg▾

😛

[Matteo Mirk]

I didn’t know hashes could be reversed… I thought md*, sha* and the like were one-way encodings! 🤔

[Kristoffer Andersen]

They are! The "reversal" is looking up the hash in a database of known hashes.

[LeoColman]

And IIRC, MD5 is somewhat easy to reverse nowadays, isn't it?

[jlleitschuh]

MD5 is considered cryptographicly broken. As is SHA1

SHA1 has been cryptographicly broken for years, but here's the most recent nail in the coffin
https://sha-mbles.github.io/

[Matteo Mirk]

Thanks for the insights, people! Yeah silly me… of course I knew about dictionary and collision attacks on hashes but for some reason I didn’t remeber at the moment