| lkcl | haha you got it. took me a while to work out, too :) | 00:18 |
|---|---|---|
| lkcl | night | 00:18 |
| mePy2[m] | Hello @lk | 09:38 |
| mePy2[m] | * Hello lkcl I completed the image. What should I do now? | 09:39 |
| lkcl | cool! ahh probably just email it to me. normally - you know those step-by-step procedures you didn't want to wait for? they include sending me an ssh key... :) | 11:32 |
| lkcl | so just email it to me for now, and i'll commit it to the libre-soc repo | 11:32 |
| mePy2[m] | where I could read those procedures? | 11:33 |
| mePy2[m] | * where can I read those procedures? | 11:34 |
| mePy2[m] | <lkcl "so just email it to me for now, "> ok | 11:34 |
| mePy2[m] | <lkcl "so just email it to me for now, "> It’s fine | 11:34 |
| lkcl | mePy2[m]: main thing "say hello on mailing list, let people know you exist and what you want to do, help with, y'know just general introduction | 12:59 |
| lkcl | as part of that, review the charter and ask questions if you have any, and let people know you're happy to abide by it | 12:59 |
| lkcl | it summarises "always do good, never do harm" which is about as simple as a Charter can possibly get. | 13:00 |
| lkcl | then i'm happy to add your ssh key to repos. | 13:01 |
| lkcl | you're familiar with git? | 13:01 |
| lkcl | if not, then skip that and just email me (direct) the file, and i'll upload it to the wiki for you | 13:02 |
| lkcl | i haven't enabled attachment / file-upload because people could abuse it to do things like "upload 1 Gbyte file" (wark-wark) | 13:04 |
| * mePy2[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/zahhUoBEglngaxpxBdpMROES/message.txt > | 13:12 | |
| mePy2[m] | lkcl: thanks | 13:12 |
| lkcl | use "ssh-keygen -t rsa" and this creates an id_rsa (private key) and id_rsa.pub (public key) | 13:14 |
| lkcl | NEVER send anyone the private key - ever | 13:15 |
| mePy2[m] | I should already have one. How can I see it? | 13:15 |
| lkcl | the public key you can share with anyone, even put it on your website like a GPG public key. | 13:15 |
| lkcl | if you're using linux: | 13:15 |
| lkcl | ls -altr ~/.ssh | 13:15 |
| mePy2[m] | Ok | 13:15 |
| mePy2[m] | I’m writing the mail to the list | 13:16 |
| lkcl | try not to lose your ssh keys (some people "reinstall" their OS and forget to take backups) | 13:16 |
| lkcl | "oh i've got a problem i'll solve it by reinstalling just like this is windows or sumfink" :) | 13:16 |
| lkcl | and of course: no ssh priv-pubkey pair, no access to repos (doh). | 13:17 |
| lkcl | what i'm saying is: they're unique, and if you lose either of them you can't recover them / recreate them. | 13:17 |
| lkcl | ok | 13:18 |
| mePy2[m] | Yeah... that’s why I asked mhm | 13:26 |
| mePy2[m] | Thank you | 13:26 |
| mePy2[m] | Did it (mail to ml). It took some time! Finally I have done it! | 13:38 |
| mePy2[m] | `id_rsa.pub` ? | 13:48 |
| lkcl | yay! | 13:51 |
| mePy2[m] | Mhm, is there a way to see when and where I used the key in the past? | 13:51 |
| mePy2[m] | Anyway, the private key is much longer, is it normal? | 13:51 |
| mePy2[m] | (Anyway, I will send you the `id_rsa.pub` file by email) | 13:57 |
| mePy2[m] | * I am going to send you the `id_rsa.pub` file by email | 13:57 |
| lkcl | mePy2[m]: only by having access to the server(s) that you logged in to and viewing /var/log/auth.log | 14:02 |
| lkcl | that's if the sysadmin has kept the logs | 14:02 |
| lkcl | yes normal | 14:02 |
| lkcl | star | 14:02 |
| sorear | ssh-keygen -t ed25519, much shorter :) | 14:06 |
| lkcl | sorear: :) | 14:09 |
| lkcl | doh. for another time/project, that one. he's sent me the id_rsa.pub already | 14:10 |
| mePy2[m] | sorear: that one creates another key though, right? I’ll make a little search. Thank you anyway | 14:12 |
| sorear | you can make any number of ssh keys using the -i option to set the filename | 14:13 |
| mePy2[m] | I still do not know very well what is the purpose of a ssh key. Does having more than one make sense? Maybe to use them for different scopes, works? | 16:08 |
| * dcz has different keys for different identities, different forge accounts | 16:42 | |
| dcz | the purpose is to gain access to remote systems usually | 16:43 |
| dcz | in a way that the other party can verify that whoever uses the key is actually you and not some impostor | 16:44 |
| mePy2[m] | lkcl: and others too. What is the scope of the images? | 17:57 |
| mePy2[m] | I am thinking, is SVG really what we want?... There should be 2CAD programs that can help you actually make the circuit and animate it. | 18:00 |
| mePy2[m] | * I am thinking, is SVG really what we want?... There should be 2D CAD programs that can help you actually make the circuit and animate it. | 18:06 |
| sorear | mePy2[m]: a ssh key is harder to leak (since the other side only has the .pub file) but otherwise similar to a password | 18:12 |
| sorear | if you want to have different devices with different levels of access, they need different keys | 18:13 |
| sorear | having a separate key for everything is less critical than it is for passwords but it makes it easier to control what gets access to what | 18:13 |
| mePy2[m] | sorear: thanks | 18:33 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!