GIT Vulnerability
-
You got an ext3 or reiserfs driver for Windows?
No, but these people do.
<I ignored the rest of your post because it wasn't important.>
-
You got an ext3 or reiserfs driver for Windows
yews, i do. the reiserfs one is buggy as Lucifer's jockstrap, but the EXT3 one is pretty solid.
-
Plus, reiserfs was written by a murderer, let's not forget that!
-
Plus, reiserfs was written by a murderer, let's not forget that!
was he ever actually tried for that? Last i checked he was trying to avoid extradition on that one.
-
He, uh, was found guilty more than 6 1/2 years ago... http://en.wikipedia.org/wiki/Hans_Reiser#Trial_and_verdict
-
huh...TIL it's been more than 7 years since i paid any attention to the guy...
-
I WANT TO MAKE A FILE OUT OF BREAD AND WHEN I PRINT IT GET A PIECE OF BREAD AT MY DESK. COME ON SCIENCE WHEN WILL I HAVE THIS?
I don't understand this at all, but its presentation has convinced me that it is indubitably correct.
-
You got an ext3 or reiserfs driver for Windows?
Not to mention this was in like 2008 or 2009 and I don't believe exFAT was a thing yet (or not common).
-
HFS+ has a pretty big install base.
-
HFS+ has a pretty big install base.
Does that have a Windows driver?
This sentence is your preemptive don't bother ranting about how the fuck would you know warning because I'm joking and your persona doesn't understand metaphor, which you may feel free to ignore or not.
-
I'm eating pho.
-
It suggests that there's a security check somewhere that compares paths as strings in a case-sensitive manner, so on case insensitive filesystems an attacker can bypass the check.
[quote=Ars]"An attacker can craft a malicious Git tree that will cause Git to overwrite its own .git/config file when cloning or checking out a repository, leading to arbitrary command execution in the client machine," Thursday's advisory warned.[/quote]
Quite probably not even a security check - the "crafting" required might even be as simple as adding .Git/config to the tree.
-
Good on ya. I had an estimated $100 meal at a steakhouse Wednesday courtesy of my company's Christmas lunch.
Honestly, we had 10 people show up and the place had a minimum price of like $1000 for private lunches, and nobody said "hey, let's go somewhere a little bit cheaper."
-
-
-
TDEMSYR.
-
-
I actually have a few nice things to say about NTFS. I am a pretty big fan of extended-attribute-type things at least in theory, so I am a fan of NTFS's alternate data streams. (I'm a bit... less enamored with its division between ADSs and xattrs, but nothing's perfect.) I keep holding out hope that one day it will be possible to actually take full advantage of xattrs and that they won't disappear if you blink at them funny... Combine that with things like ACLs and quotas and such, and I think you get a pretty capable file system.
None of those things are unique, and NTFS wasn't the first at any of them, but they had them well before a lot of the FSs that Linux folks hold up as better, like the extn series. Even now NTFS trumps the ext series in xattr support by a wide margin.
And then you see things like Transactional NTFS; that's an example of something that I think you'd be unlikely to see coming out of most of the *nix camp because it's too big of a departure from the traditional Unix/POSIX interface. And I think it was a great idea, and it's a shame that MS deprecated it.
-
It doesn't solve any problems, but only causes (mostly minor) ones.
Actually, case-insensitivity causes more problems thanks to Unicode. With ASCII it's simple, but Unicode can and does introduce new characters that may only differ in case. NTFS solves this by writing a case-folding map on the volume when it's formatted, and this means that disks formatted in different Windows versions can have different ideas about which filenames are to be treated as equal.
@FrostCat said:You got an ext3 or reiserfs driver for Windows?
No, but it natively supports UDF, which works just fine on disks.
@FrostCat said:Does that have a Windows driver?
IIRC, there's a read-only one in Boot Camp, but it's buggy like all Apple-provided Windows software.
-
With ASCII it's simple, but Unicode can and does introduce new characters that may only differ in case.
There's also normalization state to worry about in Unicode. It's very much TRWTF…
-
Mildly amusing:
ALERT! Two "git" related security vunerabilities
Warning! Upgrade now! There is a security hole in the git client.
UNTIL YOU UPGRADE: Do not "git clone" or "git pull" from untrusted sources.
AFTER YOU UPGRADE: Do not "git clone" or "git pull" from untrusted sources. THE CODE YOU JUST DOWNLOADED IS UNTRUSTED AND SHOULD NOT BE RUN, YOU FOOL!
-
It's OK, I have a regex that describes all the safe upgrade sources
-
/^$/g
that sounds about right. ;-)
-
WTF? Have you hacked my machine?
-
nah. i just read it straight from your mind through your keyboard.
-
/me snugs tinfoil hat down a little tighter
-
/me snugs tinfoil hat down a little tighter
oh, you're wearing an amplifier!
i thought it was a little easier than normal to read your mind. ;-)