sha1collisiondetection
Cesium
sha1collisiondetection | Cesium | |
---|---|---|
7 | 3 | |
1,291 | 325 | |
- | - | |
0.0 | 9.7 | |
17 days ago | 11 days ago | |
C | C# | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sha1collisiondetection
- ScrapScript: In-Development Language with Some Cool Features (Not Mine)
-
Is it ever possible for 2 commits to have the same hash?
It's far more likely that somebody would try to artificially create a collision. There is code in git to try to detect this https://github.com/cr-marcstevens/sha1collisiondetection
-
C compiler in .NET
First milestone is to be able to compile this code https://github.com/cr-marcstevens/sha1collisiondetection/ using Cesium.
-
Hash collisions and exploitations – Instant MD5 collision
For sha1, people made a system where you can detect the patterns that lead to a collision, and (for example) replace it with a different hash only for inputs that would be a problem. https://github.com/cr-marcstevens/sha1collisiondetection i think git does this to eek more life out of sha1.
I imagine you could take a similar counter-cryptnalysis approach to md5. (I am out of my depth here, so there could be reasons this doesnt work for md5 im unaware of)
- Library and command line tool to detect SHA-1 collisions (2017)
-
Apart from using exec.Command, is there a better way to check version of any external system app in /usr/local/bin like fzf or nodejs using go?
I'm saying that Git is on my side of opinion, that's why Git added collision detection (hardened SHA1) and added support for more stronger hashes and Git's goal is transition out of SHA1. The same is with fossil, that added hardened SHA1 since 2017 and by default uses SHA3 for new repositories.
- SHA-1 'Fully and Practically Broken' by New Collision
Cesium
-
C compiler in .NET
Because Hacktoberfest is runing, I would like to share small project in which I'm participating. ForNeVeR/Cesium: C compiler for the CLI platform (github.com)
-
Isolates, MicroVMs, and WebAssembly (In 2022)
Technically you can always write you own C compiler like this project https://github.com/ForNeVeR/Cesium. Obviosuly C++ is much more complicated journey and require real investment. But at this point this is not CoreCLR limitations mostly.
- C Compiler for the CLI Platform
What are some alternatives?
pocorgtfo - a "Proof of Concept or GTFO" mirror with an extensive index with also whole issues or individual articles as clean PDFs.
krustlet - Kubernetes Rust Kubelet [Moved to: https://github.com/krustlet/krustlet]
smhasher - Hash function quality and speed tests
wabt - The WebAssembly Binary Toolkit
collisions - Hash collisions and exploitations
dwarf-2-sourcemap - A DWARF to SourceMaps converter for WASM
OrangeC - OrangeC Compiler And Tool Chain
wyrcan
runwasi - Facilitates running Wasm / WASI workloads managed by containerd
hippo - The WebAssembly Platform
wagi - Write HTTP handlers in WebAssembly with a minimal amount of work