GIT Vulnerability
-
For those of you who haven't heard, there's a newly discovered vulnerability in GIT that could be an issue if a repository is compromised. You probably should update your version of it if you haven't yet.
EDIT: If you only connect to GitHub, the comments on the article indicate that they have patched the server to prevent the exploit.
-
Linux clients are not affected if they run in a case-sensitive filesystem
This is interesting. 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.
-
TIL there are case insensitive filesystems in Linux. TIL there are case insensitive filesystems.
-
-
Windows sees no difference between c:\USERS and C:\Users. Makes sense to me, I'd hate to have to remember if a file was saved in documents or Documents
-
Is there any good reason for case sensitive filenames? I've only ever seen it cause problems.
-
TIL there are case insensitive filesystems in Linux. TIL there are case insensitive filesystems.
most modern file systems are better described as Case-sensitive or case-folding.
NTFS is an example of the latter while EXT3 is an example of the former.
NTFS is case sensitive in that it keeps the original casing of your file, but case insensitive in that it allows you to refer to the file using any casing. that would be case folding. compares as case insensitive but preserves original casing.
-
When I smell a WTF it has to come from MS. /root is not the same than /Root and if you have trouble with that it's something in your brain.
-
TIL there are case insensitive filesystems in Linux.
FAT.
[root@dellxps-pjh tmp]# dd if=/dev/zero of=floppy.img bs=512 count=2880 2880+0 records in 2880+0 records out 1474560 bytes (1.5 MB) copied, 0.00760588 s, 194 MB/s [root@dellxps-pjh tmp]# losetup /dev/loop0 floppy.img [root@dellxps-pjh tmp]# mkdosfs /dev/loop0 mkfs.fat 3.0.24 (2013-11-23) [root@dellxps-pjh tmp]# mkdir /mnt/myfloppy [root@dellxps-pjh tmp]# mount -t msdos /dev/loop0 /mnt/myfloppy [root@dellxps-pjh tmp]# ls /mnt/myfloppy/ [root@dellxps-pjh tmp]# echo "Hello world" >/mnt/myfloppy/QWERTY [root@dellxps-pjh tmp]# cat /mnt/myfloppy/QWERTY Hello world [root@dellxps-pjh tmp]# cat /mnt/myfloppy/qwerty Hello world [root@dellxps-pjh tmp]#
-
/root is not the same than /Root and if you have trouble with that it's something in your brain.
well. yes, but i'd appreciate it if i cannot create both /root and /Root because that way confusion lies. particularly if you are going to expose the file as a CIFS mountpoint to windows.
\windows will happily see both folders, btu can only enter whichever one happens to be first in the directory listing
-
IMHO filesystems should be case sensitive (= you can only access a file by using its correct name), but should disallow creating two files with the same name but different case in a directory.
It would at least prevent those kind of problems.
-
-
-
It doesn't solve any problems, but only causes (mostly minor) ones.
-
c:\USERS and C:\Users
That's actually a problem on my work computer.
Apparently some software totally bombed the "My Documents" symlink in my%userprofile%
directory, so now I haveDocuments
(the actual documents folder),My Documents
(the symlink that redirects old programs to use the Documents folder) andMy Documents
(a mostly empty folder that I can't delete, because reasons).
Fortunately it's not really disrupting anything, but I haven't gotten around to editing the structure to get rid of that folder, so it's always a nice reminder whenever I need to drill down to my Documents folder by hand.
-
imPORtaNt business model data.jpg
-
TIL there are case insensitive filesystems.
Have you been living under a rock for the past 30 years?
-
Nope, but FS stuff is out of my scope of stuff I care enough to read more than two paragraphs and if it's FAT or NTFS I stop in the title.
-
Because if I wanted that I would write it like that, I don't want a FS to tell me how am I supposed to name my stuff. The same goes for programming languages.
-
You still can. As someone mentioned above, NTFS does it right: It preserves case and uses it for display, but doesn't allow you to do braindead-stupid things like having multiple files named the same except for case.
-
Apparently, from what I was reading on Hacker News, NTFS is case sensitive (Windows Services for UNIX presents itself as such) but the Windows environment presents it as case preserving
-
doesn't allow you to do braindead-stupid things
And so a filesystem has to come and rescue me from my own stupidity? Thank you but no. Remember Clippy?
Anyway, I won't continue with this stupid discussion.
-
As someone mentioned above, NTFS does it right: It preserves case and uses it for display, but doesn't allow you to do braindead-stupid things like having multiple files named the same except for case.
NTFS does no such thing. It's Windows that doesn't let you actually use the case sensitivity of the file system.
-
Why can't I include / or \x00 in my filenames? COME ON LINUX FILESYSTEM PEOPLE GET IT TOGETHER
-
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?
APPARENTLY SOMETHING THAT YOU TRY TO POST WITH ALL CAPS ISN'T DESCRIPTIVE ENOUGH SO NOW I'LL PUT IN A FAKE CHARACTER. THANKS @DISCOURSEBOT @CODINGHORRORBOT
-
@JazzyJosh - Days Since Last Discourse Bug: 0
-
@JazzyJosh Is Doing It Wrong™
-
\x00
that one you can*.... it's just a really stupid idea because just about every utility and program ever will go kerblammo on you if you try to do anything with a file(folder) so named
*: in some file systems anyway. it's technically legal on the EXT family of file systems IIRC but none of the drivers currently in use support it (because of how badly it makes things misbehave i think)
-
APPARENTLY SOMETHING THAT YOU TRY TO POST WITH ALL CAPS ISN'T DESCRIPTIVE ENOUGH SO NOW I'LL PUT IN A FAKE CHARACTER
alsi you can't have a topic title in all caps...
but fortunately for the likes thread a lowercase l looks prettymuch the same as a capital I in sans-serif font.
-
Apparently, from what I was reading on Hacker News, NTFS is case sensitive (Windows Services for UNIX presents itself as such) but the Windows environment presents it as case preserving
Makes sense. I've seen digital cameras with NTFS formatting that had both "/dcim" and "/DCIM" folders but only one of them worked.
-
-
-
Your attitude smells more of the usual Microsoft hating bullshit than anything rational.
@op thanks for the heads up, be upgrading my git tonight
-
When you update Atlassian SourceTree to fix this, it'll break the pinned icon on the taskbar.
-
When you update
Atlassian SourceTreealmost any windows program, it'll break the pinned icon on the taskbar.FTFY.
Having worked on MSI modules, I know that's not an easy thing to deal with. I have found if you run the uninstall after the install (RemoveExistingProducts scheduled after InstallFinalize), the shortcut will survive. Usually. (if you change the install location during an upgrade, the shortcut will break)
-
I've got an Xbox, so I'm not a MS hater, I just know what works and what's crap. NTFS is to filesystems what the Zune was for MP3 players.
-
NTFS has Works fine for me mate, for about since I been using Win 2000.
You are complaining about unrealistic scenario on what seems like some ideological stance that just doesn't make any sense in the real work. Even this is a bit of a WTF:
Because if I wanted that I would write it like that, I don't want a FS to tell me how am I supposed to name my stuff. The same goes for programming languages.
I can't think of a language that does have reserved words.
Every platform has it quirks that are mostly by supporting legacy and I don't see any WTF in not supporting files that only differ by case in the same directory. It isn't such a big deal and the only reason you are fussing about it seems to me because the first comment you made was "I expect this shit from Microsoft"
I hear the same complaints about IE even when IE is doing something to spec. So I heard all this shit before.
-
NTFS is to filesystems what the Zune was for MP3 players.
Have you ever used one? The Zune HD is great (don't know about the other models).
-
NTFS is to filesystems what the Zune was for MP3 players.
I loved my 80 GB Zune. I used it to watch movies on my way to work for like 2 years until its screen broke. At the time, you could not buy a better device for watching video on the go. Apple had a model that could do it, but its battery lasted like 2/3rds of one movie.
-
How did they store videos in MP3 files?
-
\windows will happily see both folders, btu can only enter whichever one happens to be first in the directory listing
I wonder if the \?\ "trick" works.
-
Anyway, I won't continue with this stupid discussion.
Wow, someone got his jimmies rustled.
-
>mott555:
digital cameras with NTFS formattingTRWTF
No, you are TRWTF for not seeing how important 4GB+ files are.
-
-
I hear the same complaints about IE even when IE is doing something to spec.
Remember Windows Mojave?
-
Zunes were just that good.
-
It's (the beginning of the path of) an alternate way to represent a file. IIRC it allows you to do things you normally can't do. You might be able to disambiguate the two files in your example.
I'm not sure how it actually works, I have just read about it in passing.
-
Because there are literally zero filesystems other than FAT and NTFS.
-
I'm not sure how it actually works, I have just read about it in passing.
neither do i. google gave me 0 results.
also probably if i knew the alternate name to the file... and i could probably find it programatically.
-
Because there are literally zero filesystems other than FAT and NTFS.
You got an ext3 or reiserfs driver for Windows?
If so, I don't want to know about it. Your pendantry, which wasn't dickweedy enough for a flag, is getting in the way of my joke.