Blakey don't ssh
-
First thing that comes to mind is you can obviously see what was happening just by using the scrollbar,
That's not necessarily true. The script'll output what it outputs. And there's no guarantee even if the script is puking out all the text that the person reading knows what it means or can interpret it in a reasonable fashion.
By contrast, at a minimum a GUI has to put in a text box or something and then write code to spew output to it (and remember, hopefully, not to forget to send any output there.)
Who's talking about a GUI?
We're talking about WSH, or a C# console application, or PowerShell. Nobody mentioned a GUI until you just now.
Where the fuck did I say it was? Oh that's right, I didn't. +1 for blakey's shoulder aliens.
So why are you asking for it? You said that was one of the criteria you were looking for.
-
-
Show me where I asked for it. Oh that's right, you can't. Dumbshit.
-
That's not necessarily true. The script'll output what it outputs.
But that is what I meant, so it's tautologically true.
I didn't say it was a huge advantage. It's mainly just something for the "a bit easier" column.
Who's talking about a GUI?
Sorry, I forgot you can't handle change or topic drift.
-
Are you logging in over http/https or ssh?
Goddamned, Ben, you know the answer to that. SSH. Stop being fucking stupid.
I'd love to be able to log in via HTTPS, then I can trash all this SSH shit and GitHub for Windows and SourceTree and just use Visual Studio. But the server doesn't support HTTPS.
Dumbshit.
Well double dumbass on you!
-
I didn't say it was a huge advantage. It's mainly just something for the "a bit easier" column.
Doesn't matter. It's not in his expectation of How Things Should Be so no one else should care about it either or they're weird or wrong.
-
Sorry, I forgot you can't handle change or topic drift.
Use the clutch if you're gonna switch gears.
-
Does your company have a separate account on the server hosting the git repository for each person? I doubt it. More likely, there's just the
git
account and it knows who you are based on public key.
-
Does your company have a separate account on the server hosting the git repository for each person?
How the fuck would I know?
I doubt it. More likely, there's just the git account and it knows who you are based on public key.
Why the fuck do I care?
Look, the situation is shitty. I don't know or care why it's shitty. I'm not interested in implementation details, as you well-know but are pretending you don't.
-
-
also this thread is getting repetitive as shit.
Export an SSH-2 key in OpenSSH format
Export an SSH-2 key in OpenSSH format
Export an SSH-2 key in OpenSSH format
Export an SSH-2 key in OpenSSH format
Export an SSH-2 key in OpenSSH format
Export an SSH-2 key in OpenSSH format
Export an SSH-2 key in OpenSSH format
Export an SSH-2 key in OpenSSH format
Export an SSH-2 key in OpenSSH format
Export an SSH-2 key in OpenSSH format
Export an SSH-2 key in OpenSSH format
Export an SSH-2 key in OpenSSH format
Export an SSH-2 key in OpenSSH format
Export an SSH-2 key in OpenSSH format
Export an SSH-2 key in OpenSSH format
Export an SSH-2 key in OpenSSH format
-
Use the clutch if you're gonna switch gears.
I'm not interested in implementation details.
-
-
Well like I said I dropped Github for Windows a long time ago.. But even then it was kinda possible. UI wise I agree but then Again I find the best UI often a simple matlab or python script.
-
Right; but SourceTree can't use that key because it's not in "PuTTY" format.
Dude, FUCKING TRY IT. I FUCKING DARE YOU. THAT KEY WILL NOT WORK IN SOURCETREE.
TRWTF is the PuTTY ssh key format
-
The entire argument for it seems to be "we don't encrypt the public key", which is already what every other SSH implementation does. And then they have some gibberish about how they have some kind of hash of the key inside the key. Because apparently we live in a world where private keys are editable by random third parties and having multiple files is an impossibility.
-
It has been a while since I've had to dive into the depths of PKI implimentation but...
The whole point of a public key is to give it away. Like a stranger in a window-less van with "Free Candi" spary-painted on the side.
If you want to verify someone has the corresponding private key you make them digitally sign a message.
:WTF: would someone do with an encrypted public key?
-
The public key is part of the private key so you can recover it if you lose the public half but still have the private half. Normally, an unencrypted copy of the public key is stored in a file ending in
.pub
in the format expected byauthorized_keys
, but PuTTY decided it would be better to invalidate the entire key if the public part was corrupted, use a proprietary binary format for something that already has a standard textual format, and make the default export format for the public half use PEM format, which is what the private key uses in OpenSSH and no SSH server that I know of will accept in itsauthorized_keys
file or equivalent. And make it so users who don't understand public key cryptography give away their private key without knowing what they're doing.
-
@delfinom said:
TortoiseGit works fine too as long as you install it and Git for Windows with the OpenSSH option.
Tortoise Git is the only client that has ever corrupted a Git database on me. I don't trust TortoiseShellCache or WETF it is not to improperly lock the database.TortoiseGit is simply a wrapper around libgit2 which is basically used by everyone elses clients.
-
Back when I used TortoiseGIT, libgit2 didn't even exist yet.
-
Back when I used TortoiseGIT, libgit2 didn't even exist yet.
Good time to try it again then huh?
-
No, because I know how to use the CLI and it's more powerful and less likely to corrupt my installation of Windows.
-
No, because I know how to use the CLI and it's more powerful and less likely to corrupt my installation of Windows.
How did it go from corrupting a git repo to corrupting to your OS???
-
Badly programmed shell extensions do bad things.
-
I have to use 3 different Git clients, because all Git clients are half-baked.
I have to use 1 different Git clients, because all my Git clients are not half-baked...
-
I use 2 different Git clients, because Windows does not have a simple equivalent to
sudo apt-get install git
.
-
Eh true, I do as well. But they're both built from basically the same source so... meh. Pendantry and such.
-
Badly programmed shell extensions do bad things.
While an undoubtedly true statement, does that apply in this case? If not, why introduce it to this argument?
-
@ben_lubar said:
Badly programmed shell extensions do bad things.
While an undoubtedly true statement, does that apply in this case? If not, why introduce it to this argument?
I'm confused how a bunch of registry entries to display some shortcuts in the right click menu can do bad things.
-
It's one registry entry that makes explorer call into a DLL saying "here's the context menu, do your thang!" And the DLL can do whatever it wants, including format your hard drive. Normally, TortoiseGit determines what actions are appropriate (is this file in a repo? what's its status?) and adds them to the menu, complete with icons, but with that software formatting your hard drive isn't entirely unexpected either, since they're more focused on Aero Glassing the entire thing than coding it correctly.
-
It's one registry entry that makes explorer call into a DLL saying "here's the context menu, do your thang!" And the DLL can do whatever it wants, including format your hard drive. Normally, TortoiseGit determines what actions are appropriate (is this file in a repo? what's its status?) and adds them to the menu, complete with icons, but with that software formatting your hard drive isn't entirely unexpected either, since they're more focused on Aero Glassing the entire thing than coding it correctly.
Errr, Windows will actively refuse to format the drive if it has the system partition.
-
I meant "undefined and undesirable behavior can/will occur." Other commenters here have reported repository metadata corruption, file corruption in files unrelated to any Git repository, and Explorer hanging (due to dangling IPC) and crashing (due to memory corruption). And you should know by know that "format your hard drive" is a dysphemism for that sort of behavior, similar to the C standard's "nasal daemons".