| 00:21.04 | *** join/#openmoko-cdevel radish (~radish@unaffiliated/stryx/x-3871776) |
| 02:15.25 | pabs3 | I don't think I've ever been on #openmoko |
| 02:16.32 | pabs3 | I would say openmoko is dead and this channel and #openmoko should be closed and we should create something like #openmobile |
| 02:30.07 | *** join/#openmoko-cdevel NormanD_ (~NormanQ@218.30.116.186) |
| 02:51.10 | *** join/#openmoko-cdevel morphis_ (~morphis@pD9ED6304.dip0.t-ipconnect.de) |
| 03:22.05 | pabs3 | http://venturebeat.com/2017/01/10/inside-project-ara-googles-revolutionary-modular-phone/ |
| 05:10.56 | *** join/#openmoko-cdevel DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 06:16.35 | *** join/#openmoko-cdevel Q-Master^Work (~q-master@217.175.38.170) |
| 06:56.43 | PaulFertser | pabs3: people still occassionally come here; I'd prefer #openmoko to be redirected to #openmoko-cdevel. |
| 06:59.08 | pabs3 | I'd redirect both to something else |
| 07:02.12 | PaulFertser | btw, totally offtopic but I can't just figure it out, the Debian wiki recommends to use subkeys and to store the primary signing key somewhere offline in a secure place. But should it be protected by a passphrase? And if yes, how to remember it if it's used so rarely? |
| 07:03.57 | pabs3 | one option would be diceware and or storing the passphrase on paper with copies in a few secure places |
| 07:05.41 | PaulFertser | I also do not understand if it makes sense to store it on external stm32 device with gnuk (and flash reading protected) or if I'll just have more problems than it's worth. |
| 07:08.43 | PaulFertser | And I should have at least two devices like that to have a backup? |
| 07:09.01 | PaulFertser | I'm clearly missing some "best practices" document. |
| 07:09.45 | pabs3 | there is this, but it doesn't cover anything like what you are asking about: https://help.riseup.net/en/security/message-security/openpgp/best-practices |
| 07:09.55 | PaulFertser | Yes, seen that. |
| 07:10.07 | PaulFertser | But I'm struggling with practical implementation :) |
| 07:10.36 | *** join/#openmoko-cdevel morphis (~morphis@pD9ED6304.dip0.t-ipconnect.de) |
| 07:10.58 | pabs3 | paperkey is another example of a backup solution |
| 07:11.15 | PaulFertser | I'm considering using http://wiki.stm32duino.com/index.php?title=Blue_Pill as I do not see how e.g. FST-01 is any better. But I can't understand if it's worth it at all. |
| 07:11.27 | pabs3 | also https://joeyh.name/code/keysafe/ |
| 07:16.38 | PaulFertser | Even if I did have a safe at home, then I guess I'd keep the key at home as well, so it'd not be really secure either. |
| 07:25.53 | PaulFertser | Another related question: http://pgp.mit.edu/pks/lookup?search=fercerpav%40gmail.com&op=index&fingerprint=on how it might have happened that the 8-bit key id is the same? I do not remember doing anything special. |
| 07:28.11 | pabs3 | IIRC someone uploaded the evil32 dataset to the keyservers: https://evil32.com/ |
| 07:28.25 | pabs3 | so you may have got caught up in that |
| 07:31.06 | PaulFertser | pabs3: aha, thank you, that explains it. |
| 07:34.06 | *** join/#openmoko-cdevel jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 08:01.03 | *** join/#openmoko-cdevel daniele_athome (~daniele_a@net-47-53-132-231.cust.vodafonedsl.it) |
| 08:19.28 | *** join/#openmoko-cdevel ao2 (~ao2@cl-35.trn-01.it.sixxs.net) |
| 09:21.13 | *** join/#openmoko-cdevel NormanD (~NormanQ@218.30.116.183) |
| 09:38.21 | *** join/#openmoko-cdevel ThibG (~ThibG@maths.r-prg.net.univ-paris7.fr) |
| 09:51.26 | *** join/#openmoko-cdevel dhiru_ (~xchat@117.96.254.143) |
| 09:54.50 | *** join/#openmoko-cdevel patinux (~patinux@unaffiliated/patinux) |
| 11:37.35 | *** join/#openmoko-cdevel JaMa (~martin@217.30.68.212) |
| 12:04.26 | *** join/#openmoko-cdevel NormanD (~NormanQ@218.30.116.4) |
| 12:27.40 | *** join/#openmoko-cdevel Q-Master^Work (~q-master@217.175.38.170) |
| 12:49.32 | *** join/#openmoko-cdevel NormanD (~NormanQ@218.30.116.186) |
| 13:44.53 | *** join/#openmoko-cdevel paulk-blaze (~paulk@no3.u-bordeaux.fr) |
| 14:49.40 | *** join/#openmoko-cdevel morphis (~morphis@pD9ED6304.dip0.t-ipconnect.de) |
| 15:00.53 | DocScrutinizer05 | pabs3: how does it make sense to "close" a channel and redirect users to a new non-existing one? Just because of channel name?? :-o |
| 15:01.11 | DocScrutinizer05 | that's plain silly |
| 15:02.05 | DocScrutinizer05 | channel "renaming" is one of the most complicated and futile actions on IRC |
| 15:03.24 | DocScrutinizer05 | even more fultile and complicated than domain name change for a well established URL/site |
| 15:04.15 | DocScrutinizer05 | for the latter you at very least have CNAME. which you can sustain forever. No similar thing on IRC |
| 15:05.55 | DocScrutinizer05 | doing what you suggest would result in 2 channels becoming 3 (2 old ones plus the new one) |
| 15:07.27 | DocScrutinizer05 | PaulFertser: redirects are always only temporarily |
| 15:35.53 | *** join/#openmoko-cdevel morphis (~morphis@pD9ED6304.dip0.t-ipconnect.de) |
| 15:39.31 | *** mode/#openmoko-cdevel [+o DocScrutinizer05] by ChanServ |
| 15:42.22 | *** topic/#openmoko-cdevel by DocScrutinizer05 -> Please /join #Openmoko | Openmoko Community Developers Channel - discussion on all firmware images, packages and software | SHR: http://shr-project.org | #hackable1 | #openmoko-debian | #qtmoko | #android-on-freerunner | CIA notifications in #freesmartphone.org | Logs: ~logs & http://logs.nslu2-linux.org/livelogs/openmoko-cdevel.txt |
| 15:42.49 | *** mode/#openmoko-cdevel [-o DocScrutinizer05] by ChanServ |
| 15:58.35 | DocScrutinizer05 | I'll eventually set up a forward from this channel to #openmoko. This may (and will) fail for some users under certain circumstances - e.g. they might have blocked forwards |
| 16:00.13 | DocScrutinizer05 | please consider reconfiguring your autojoins accordingly. Keeping both channels on autojoin doesn't usually hurt - can get cleaned out after a few months when this channel moved over to #openmoko completely |
| 16:00.42 | *** join/#openmoko-cdevel patinux (~patinux@unaffiliated/patinux) |
| 16:02.27 | DocScrutinizer05 | please contribute to merging both chan /topic into one, not losing relevant info. Simply post suggestions to #openmoko |
| 16:03.29 | DocScrutinizer05 | thanks! |
| 16:59.22 | antrik | DocScrutinizer05: uh... did you capitalise #Openmoko in the topic on purpose?... |
| 16:59.53 | DocScrutinizer05 | no, except for nicer looks. It doesn't make a difference |
| 17:00.34 | antrik | meh, I think it's more confusing than anything :-) |
| 17:00.40 | *** mode/#openmoko-cdevel [+o DocScrutinizer05] by ChanServ |
| 17:00.48 | *** topic/#openmoko-cdevel by DocScrutinizer05 -> Please /join #openmoko | Openmoko Community Developers Channel - discussion on all firmware images, packages and software | SHR: http://shr-project.org | #hackable1 | #openmoko-debian | #qtmoko | #android-on-freerunner | CIA notifications in #freesmartphone.org | Logs: ~logs & http://logs.nslu2-linux.org/livelogs/openmoko-cdevel.txt |
| 17:00.51 | *** mode/#openmoko-cdevel [-o DocScrutinizer05] by ChanServ |
| 22:51.13 | *** join/#openmoko-cdevel daniele_athome (~daniele_a@net-47-53-132-231.cust.vodafonedsl.it) |