Viewing profile — hn_p4ttern
hn_p4ttern
HN member- Joined
- Wed, Mar 27, 2024, 9:56 AM UTC
- HN karma
- -1
- Public activity
- 7 items
- HN profile
- View on Hacker News ↗
About hn_p4ttern
No profile information was provided.
Recent public activity
-
comment
Comment #39841710
> "I believe there is one more step. You have to somehow get the collision into the repository." Yes, Exactly. So, is it necessary to change SHA-1 having in git ? At the moment, I …
-
comment
Comment #39841683
> "For now the SHA-1 collisions are easily detectable, but it could get worse." Your opinion: prove it! And Again, if you instead of trolling actually read the post in THIS BRANCH …
-
comment
Comment #39840461
My point is: why you should change hashing algorithm in GIT ??? Let's elaborate: 1. Do SHA-1 put a security risk in GIT ? 2. Is that practically exploitable in any way? In some app…
-
comment
Comment #39839664
[flagged]
-
comment
Comment #39839528
1) We are talking about sha1, md5 is out of topic 2) This is the main topic ! Being able to generate >>valid code >specific purpose 3) A.K.A your answer is total nonsense. Everyone…
-
comment
Comment #39837363
IMHO "be padded into a comment" is included in "is valid code", still 1 in is a good approximation of that probability. Please, correct me if I'm wrong.
-
comment
Comment #39837232
Is it used to sign a commit, right ? Which are the probabilities to have a collision that: a) is still code b) is still code AND is code similar to a previous commit c) is still co…