Why is git/ssh/gpg so hard? They could've made it so much

>>58704296
Because cryptologists = math people, kernel programmers and UNIX(TM) programmers are sperglords, not actual people.

>git is hard
Wow memorising git commit -m is so difficult
>ssh is hard
Wow connecting to a server the same way you connect and log in to a website is so hard
>gpg is hard
Wow pasting your ssh key is so hard

Fucking kys newfriend, if you want to at least seem passable buy a Nokia N9

>>58704429
>memorising
>s
stopped reading there, if you can't even spell memorizing then why should I care what you think

>>58704296
RTFM you noob

>>58704438
He writes English not American.

>>58704429
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The RSA host key for 1.2.3.4 has changed,
and the key for the according IP address 1.2.3.4
is unchanged. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
Offending key for IP in /home/cyka/.ssh/known_hosts:10
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
12:23:34:56:21:g3:g9:93:86:af:4r:bb:11:5d:f8:h9.
Please contact your system administrator.
Add correct host key in /home/blyad/.ssh/known_hosts to get rid of this message.
Host key verification failed.

File: 1485528544715.jpg (42KB, 473x355px) Image search: [Google]

42KB, 473x355px

>>58704623
how about fucking delete that file and try reconnecting again how does that sound

File: op.jpg (24KB, 433x173px) Image search: [Google]

24KB, 433x173px

Is that you, OP?

File: 1482593617147.jpg (47KB, 564x400px) Image search: [Google]

47KB, 564x400px

>>58704429
>git commit -m
>Not taking your time to type out a proper multiline commit message in a text editor so that your comrades actually get a thorough understanding of what you did

This time with image

>>58704682
my code is self-documenting :o)

>>58704648
>dude generate an ssh key locally
>then connect to the server
>ahahah dude generate a key again, this time on the server
>add both to gitlab
>just repeat if something went wrong lmao

>>58704701
Ah yes, because commit messages like "fixed bug" or "refactored x" are incredibly clear. Not to mention that some changes don't make sense without knowing the intention of it, which you usually can't fit in 80 characters.

>Using Windows 10 as anything other than an OS for your gaming machine

Congratulations, you played yourselves.

I use Linux and Mac OS X as my main operating systems. My win10 machine is a glorified gaming console with a functional internet browser.

>>58704727
Which is why, on any reasonably sized project, you make several commits for separate changes, instead of one large commit for everything.

Additionally, comment your fucking code, that'll help make it clear.

Op I use these tools at work all day every day. If all the things I use, these are something I don't have to think about, like the easiest shit.