Cybersecurity

5726 readers

106 users here now

c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.

THE RULES

Instance Rules

Be respectful. Everyone should feel welcome here.
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
No Ads / Spamming.
No pornography.

Community Rules

Idk, keep it semi-professional?
Nothing illegal. We're all ethical here.
Rules will be added/redefined as necessary.

If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.

Learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]

Notable mention to [email protected]

founded 1 year ago

MODERATORS

kid

[email protected]

Critical Git vulnerability allows RCE when cloning repositories with submodules (CVE-2024-32002) (www.helpnetsecurity.com)

submitted 6 months ago by kid to c/cybersecurity

4 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 6 months ago* (last edited 6 months ago) (1 children)

Yeah. I wanted to like submodules, but submodules, to me, ended up feeling like one feature too many in git.

I mainly run into submodules that have been setup accidentally by cloning inside an existing clone. That situation is, of course, not great.

Even for the many reasonable use cases for submodules, I generally end up letting my actual package manager do the work, instead. I'm generally happier for it, since life tends to be simpler when my package manager of choice knows about any required libraries.

[–] Altreus 3 points 6 months ago

Agreed. Haven't yet found a use case that isn't better handled by either build tools or "don't do that"