Not

Hacker

News!

Not

Hacker

News!

AI-observed conversations & context

Daily AI-observed summaries, trends, and audience signals pulled from Hacker News so you can see the conversation before it hits your feed.

LiveBeta

Explore

Home
Hiring
Products
Companies
Discussion
Q&A
Privacy Policy

Resources

Visit Hacker News
HN API
Modal cronjobs
Meta Llama

Briefings

Inbox recaps on the loudest debates & under-the-radar launches.

Connect

Not affiliated with Hacker News or Y Combinator. We simply enrich the public API with analytics.

Git Repo Mount | Not Hacker News!

Not

Hacker

News!

Home
Products
Git Repo Mount

Product Launch

anonymous

1 points

1 comments

Posted21 days agoActive21 days ago

Git Repo Mount

github.com

launchedlibrarydevelopers

Key Features

mounts git repository as a file systemviews commits and branches as files

Tech Stack

gitfuse

Not

Hacker

News!

AI-observed conversations & context

Daily AI-observed summaries, trends, and audience signals pulled from Hacker News so you can see the conversation before it hits your feed.

LiveBeta

Explore

Home
Hiring
Products
Companies
Discussion
Q&A

gitfile systemconventional_commits

Discussion (1 comments)

Showing 1 comments

lhmiles

21 days ago

The author asked me to mention that it's possible to maliciously cause a (64-bit) hash collision. In other words, you can make changes to safe file.py and evil file.py until they have the same hash. Then if you read file.py on cmt abc123 in normal git land, then run python /commits/abc123/file.py, it is possible to read the safe one and run the evil one. I think this is only a risk if you are reading from an external source but executing inside the mount, which is a weird thing to do.

View on Hacker NewsHN ID: 46250928Mood: informative

Resources

Visit Hacker News
HN API
Modal cronjobs
Meta Llama

Briefings

Inbox recaps on the loudest debates & under-the-radar launches.

Connect

Not affiliated with Hacker News or Y Combinator. We simply enrich the public API with analytics.