**** BEGIN LOGGING AT Sun Apr 16 03:00:03 2017 Apr 16 06:45:03 http://www.techamok.com/?pid=18516 Apr 16 06:45:06 funsies Apr 16 06:52:49 and 'leaked' means even mor funsies Apr 16 07:18:24 pagurus' connection must be worse than mine. Apr 16 08:02:48 maxd: apparently, or just shitty irc client Apr 16 09:00:43 how do i VPN Apr 16 09:02:15 * freemangordon wonders who hacked kerio's account Apr 16 09:02:30 :< Apr 16 09:02:35 no like Apr 16 09:02:40 in maemo Apr 16 09:02:45 possibly something with a GUI Apr 16 09:03:00 i wonder if i can just proxy the SIP stuff actually Apr 16 09:03:23 kerio: there are a couple of choices in HAM Apr 16 09:03:23 but SIP uses udp, and my usual solution of shoving everything into ssh won't work Apr 16 09:30:45 fmg: can you ban pagurus temporarily? Apr 16 10:53:33 whoa Apr 16 10:54:06 that dude has a pattern Apr 16 10:54:09 not shitty client Apr 16 10:54:22 seem intentional Apr 16 10:54:26 or maybe not Apr 16 12:34:17 kerio: openvpn all the things Apr 16 14:29:02 report this guy to staff Apr 16 14:36:18 is there some sort of log for the builtin SIP client? Apr 16 14:58:22 kerio, try /var/logs? (not sure if that is valid) Apr 16 14:58:28 and/or syslog Apr 16 14:58:30 hmm Apr 16 15:00:36 kerio: apart from the eventdb you mean? Apr 16 15:00:38 debug logs? Apr 16 15:21:33 kerio: what are you doing? are you hitting the bug about the wrong source ip into sip packets? Apr 16 15:21:41 xes: no clue Apr 16 15:21:51 i don't really know how SIP works Apr 16 15:22:25 however, zoiper on my computer through the n900 connection works Apr 16 15:22:40 which was pretty amazing, since the n900 was using a vpn to my home machine, but Apr 16 15:23:34 kerio: if you are using sip inside a vpn you need to correct sip source ip into maemo Apr 16 15:23:42 how do i do that :< Apr 16 15:27:08 mc-tool update $acct string:local-ip-address="$OPENVPN_IP" Apr 16 15:27:23 the local ip? Apr 16 15:27:29 because i have at least two NATs from this Apr 16 15:27:56 there should also a wiki somewhere about this issue... Apr 16 15:28:11 what's mc-tool Apr 16 15:28:37 oh, libmissioncontrol-utils Apr 16 15:29:09 D: Apr 16 15:29:44 then maybe you have to fix some wrong packet with an iptables snat Apr 16 15:30:05 nouuu Apr 16 15:35:44 DocScrutinizer05: why not a forward-ban to ##fix_your_connection Apr 16 15:49:21 kerio: tell me how to do that Apr 16 15:50:30 * DocScrutinizer05 doesn't know about forward-bans in freenode Apr 16 16:08:54 1 Apr 16 16:09:02 oops sorry Apr 16 16:09:14 DocScrutinizer05: append `$##fix_your_connection` to the ban mask Apr 16 16:11:10 I don't see a difference, I think this works only with chanserv akick Apr 16 16:11:40 DocScrutinizer05 sets mode +b pagurus!*@* Apr 16 16:11:53 so? Apr 16 16:11:53 are you doing /mode +b pagurus!*@*$##fix_your_connection Apr 16 16:11:58 yes Apr 16 16:12:03 meh no Apr 16 16:12:39 yay Apr 16 16:12:56 let's see if pagurus ends up there Apr 16 16:13:27 wait, pagurus is here Apr 16 16:13:28 :o Apr 16 16:13:35 I don't see much anyway, since usually I have ignore join/nick/part Apr 16 16:14:04 pagurus: please fix your connection Apr 16 16:16:21 hey guys, sorry for the join spam Apr 16 16:16:51 its my reconnect script for rcirc in emacs, I tried to fix it... Apr 16 16:17:03 damn daily disconnect Apr 16 16:20:37 np. just maybe consider to test with a list of dummy channels to autojoin, until you're happy with how the script works Apr 16 16:27:17 ah ok Apr 16 16:27:29 gg Apr 16 16:29:44 kerio: I start to forget skills since I never use then :-S https://freenode.net/kb/answer/channelmodes Apr 16 16:43:14 zoiper on ios connects just fine to SIP :< Apr 16 16:52:17 * DocScrutinizer05 gets headache trying to grok https://en.wikipedia.org/wiki/IPv4_subnetting_reference#Classful_networks Apr 16 16:56:07 DocScrutinizer05 i can cheat my home ISP ;o Apr 16 16:56:30 hm? Apr 16 16:56:44 i have a VDSL at home Apr 16 16:56:49 so my landline goes through voip Apr 16 16:57:03 however, it's all managed Apr 16 16:57:12 eew Apr 16 16:57:19 they don't just give you the SIP parameters Apr 16 16:57:21 BUT Apr 16 16:57:38 they give you an app to do phone calls from a smartphone if you're connected to the wifi Apr 16 16:57:54 MITM the app, get the credentials, VPN Apr 16 16:58:02 i can use my landline anywhere in the world now ;o Apr 16 16:58:21 hmm, weird intricate approach but nifty Apr 16 16:58:48 and i have free national calls from my landline ;o Apr 16 16:58:58 :-) Apr 16 16:59:10 now if only i could do that from the n900... >:( Apr 16 16:59:24 oh ugh Apr 16 16:59:55 tbh i only managed to take and receive calls with zoiper (desktop and ios) Apr 16 17:00:01 how about installing asterisk 'at home'? Apr 16 17:00:13 DocScrutinizer05: that could be an option Apr 16 17:00:28 can it work as a "SIP bouncer" of sorts? Apr 16 17:00:35 sure Apr 16 17:00:41 ༼ つ ◕_◕ ༽つ gibe config Apr 16 17:00:44 asterisk is a B2B-UA Apr 16 17:01:21 i will only install asterisk if it's available in the freebsd ports Apr 16 17:01:27 it is ;o Apr 16 17:01:27 aka back to back user agent Apr 16 17:02:12 DocScrutinizer05: that sounds like a pretty amazing idea actually Apr 16 17:02:19 where the fuck were you like 6 hours ago Apr 16 17:02:25 you should be able to make asterisk log in to your managed VoIP as if tiwere a client, and connect to asterisk via SIP from N900 Apr 16 17:02:51 i can even run it in a jail ;o Apr 16 17:02:52 i like jails Apr 16 17:02:55 s/tiwere/it were/ Apr 16 17:02:55 DocScrutinizer05 meant: you should be able to make asterisk log in to your managed VoIP as if it were a client, and connect to asterisk via SIP from N900 Apr 16 17:05:13 DocScrutinizer05: what are the cpu requirements for asterisk? Apr 16 17:05:25 will i ever run into CPU bottlenecks, for instance Apr 16 17:05:46 added benefit: you can use asterisk to call any extension from any extension, and you can even have multiple 'public lines' in same PBX Apr 16 17:06:13 no, asterisk doesn't do any heavy lifting with CPU Apr 16 17:06:22 doesn't it do audio transcoding tho Apr 16 17:06:37 basically works like a packet forwarder Apr 16 17:06:56 it *might* do transcoding, yes Apr 16 17:07:11 but on a ridiculous rate, for modern PCs Apr 16 17:07:17 oh right, phones Apr 16 17:08:32 DocScrutinizer05 theres ONE HUNDRED AND ELEVEN CONFIG FILES Apr 16 17:09:00 yes, it's a PITA to cinfig Apr 16 17:09:15 https://en.wikipedia.org/wiki/Back-to-back_user_agent Apr 16 17:09:44 why can't i just use sippy_b2bua Apr 16 17:11:50 https://en.wikipedia.org/wiki/Asterisk_(PBX) Apr 16 17:12:05 I don't know sippy_b2bua Apr 16 17:12:16 you prolly can use it as well Apr 16 17:12:42 any B"BUA should do Apr 16 17:12:46 B2BUA Apr 16 17:16:45 kerio: yop dawg, heard you like jails. So how about running https://en.wikipedia.org/wiki/FreePBX_Distro in a VM jail to have jails in your jails Apr 16 17:16:59 Operating system GNU/Linux Apr 16 17:17:07 DISGUSTING Apr 16 17:25:53 * DocScrutinizer05 feels like "Huh? WTF?!" each time wikipedia starts babbling about their "primary source" policies. Like >>This article relies too much on references to primary sources. Please improve this by adding secondary or tertiary sources.<< Apr 16 17:27:12 seems you can't write your own stuff in wikipedia, and you can't quote original sources. You need to quote others quoting original sources or writing their original stuff, which is weird and I feel like I got this comletely wrong Apr 16 17:29:48 DocScrutinizer05: socat UDP4-RECVFROM:5060,fork UDP4-SENDTO:5.97.53.8:5060 Apr 16 17:29:51 https://en.wikipedia.org/wiki/Wikipedia:Verifiability >>Wikipedia does not publish original research. Its content is determined by published information rather than the beliefs or experiences of its editors.<< Apr 16 17:29:54 this is so fucking dumb lmao Apr 16 17:30:32 kerio: this is SIP only, what about RTP? Apr 16 17:30:38 what is RTP Apr 16 17:30:51 the 'payload channel' for VoIP Apr 16 17:31:33 SIP= Session INITIATION Protocol, RTP = Realtime TRANSFER Protocol Apr 16 17:32:46 SIP negotiates RTP...- between both clients Apr 16 17:32:49 well i was able to PLACE a call at least Apr 16 17:32:52 :^) Apr 16 17:33:18 DocScrutinizer05: this doesn't make a lot of sense tho Apr 16 17:33:37 why was i able to make it work by routing just that one address in openvpn then Apr 16 17:33:46 oh i guess that the address is the same Apr 16 17:33:49 NFC Apr 16 17:34:43 while SIP is usually via a registrar server, the real payload aka call is client<->client usually Apr 16 17:36:33 https://en.wikipedia.org/wiki/File:SIP_call_flow_between_UA,_Redirect_Server,_Proxy_and_UA.png --> "Media (RTP)" in red Apr 16 17:37:52 yeah but the other "client" is always some fake thing Apr 16 17:38:12 because this is strictly landline-landline Apr 16 17:38:35 i guess that the SIP registrar also acts as the other client Apr 16 17:38:36 https://en.wikipedia.org/wiki/File:SIP-B2BUA-call-flow.png Apr 16 17:39:01 yes, registrars often act as B2VUA too Apr 16 17:39:06 B2BUA Apr 16 17:40:03 particularly registrars resp VoIP providers have gateways VoIP<->POTS Apr 16 17:40:52 so more often than not you have a call setup like VoIP<->POTS- - - POTS<->VoIP Apr 16 17:42:50 if you call a phone number (not a SIP address), you regularly end on your provider's gateway to POTS Apr 16 17:47:06 SIP is a tad more compley than most people tend to think. See https://en.wikipedia.org/wiki/Session_Initiation_Protocol Apr 16 17:47:16 complex Apr 16 17:48:34 if you want to learn about it, I strongly recommend using twinklephone, written by one of the authors of the IETF SIP RFCs Apr 16 17:50:56 twinkle has great logging that helps understand what's really going on Apr 16 17:51:54 (NEVER EVER use the "show log" menu item, it is braindead Qt shit that needs ~100byte of RAM for each byte of text in log) Apr 16 17:52:12 but Twinkle is available for Linux only Apr 16 17:52:19 no Apr 16 17:52:26 that's what the page says :< Apr 16 17:52:53 twinkle been developed and tested at least on BSD, linux, Solaris, and a number of other platforms Apr 16 17:55:22 the GUI should run on all platforms that have Qt3, the CLI client on all POSIX platforms Apr 16 17:56:47 DocScrutinizer05: does it support OSS Apr 16 17:56:55 OSS? Apr 16 17:57:16 /dev/dsp Apr 16 17:57:22 this is a waaay too ambiguous acronym Apr 16 17:57:29 aah yes, it does Apr 16 17:57:57 DocScrutinizer05: how do i diagnose the maemo sip cleint Apr 16 17:57:58 client Apr 16 17:58:00 it even started with that only Apr 16 17:58:42 kerio: (maemo client) sorry NFC, it's telepathy-sofiasip Apr 16 17:59:00 maybe you find details googling for that term Apr 16 18:00:14 https://en.wikipedia.org/wiki/Telepathy_(software) >>Rakia: for the Session Initiation Protocol (SIP), using Nokia's open source Sofia-SIP library<< Apr 16 18:02:13 i mean it should work Apr 16 18:02:15 but it doesn't D: Apr 16 18:02:33 wireshark to the rescue :-) Apr 16 18:02:52 it has grat dissectors for SIP/RTP Apr 16 18:02:57 great* Apr 16 18:03:13 can i just tcpdump Apr 16 18:03:16 or do i have to use tshark Apr 16 18:03:31 see wirehsarl manual Apr 16 18:03:53 I think wireshark also can read in zxpdump logs Apr 16 18:04:02 tcpdump Apr 16 18:04:12 but tshark is prolly simpler to use Apr 16 18:04:36 and there's tshark for maemo Apr 16 18:04:59 you can connect to it via your desktop PC wireshark GUI frontend remotely Apr 16 18:05:26 nah i'm using tshark on the other end of the vpn Apr 16 18:05:31 should work regardless Apr 16 18:05:42 make sure tshark filters out and thus doesn't report own traffic Apr 16 18:07:23 the funny old "forkbomb" effect when running tcpdump via ssh remote login X-P Apr 16 18:07:50 tcpdump logging own logging (*5) Apr 16 18:08:16 is this thing even working Apr 16 18:08:22 this thing = vpn Apr 16 18:10:31 DocScrutinizer05: btw the SIP thing worked immediately on iOS Apr 16 18:10:33 just sayin Apr 16 18:10:34 WTF?! my ssh login to N900 had a 15s freeze lag Apr 16 18:11:01 usedns no Apr 16 18:12:24 IroN900:~# ps -l 7192 Apr 16 18:12:25 F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD Apr 16 18:12:27 0 S 29999 7192 1 0 80 0 - 1884 sys_po ? 0:06 /usr/lib/telepathy/telepathy-sofiasip Apr 16 18:12:51 honestly i just gave up Apr 16 18:14:27 connecting N900 to arbitrary standard SIP registrars is "just do it" Apr 16 18:15:47 plus you even could run asterisk on N900 locally and connect to that :-P Apr 16 18:16:23 which makes for a nice and simple migration path to Neo900's modem Apr 16 18:26:09 DocScrutinizer05: except that it doesnt fucking work Apr 16 18:26:16 because of some weird incompatibility with VPNs Apr 16 18:27:37 builtin android client Apr 16 18:27:39 works Apr 16 18:27:41 10/10 Apr 16 18:34:00 DocScrutinizer05: are you saying that running asterisk locally is going to be the simplest way to do phone calls on the neo900 Apr 16 18:37:07 anyway this SIP thing is nitfy Apr 16 18:37:09 nifty Apr 16 18:37:19 i'll investigate running a local asterisk Apr 16 18:37:39 to not require the whole openvpn shebang Apr 16 18:44:50 kerio: I say that running asterisk locally is the simplest way to *implement* phonecalls in *maemo* Neo900 Apr 16 18:46:37 as long as you want to do them calls via the maemo dialler-ui Apr 16 18:47:09 otherwise use an arbitrary dialer, there's a shitload of them Apr 16 18:47:11 https://github.com/systemd/systemd/issues/5644 Apr 16 18:50:37 those generic dialers however won't integrate with contacts, call-log, notifications, vibra, audio management, 911-features, holdbutton functionality on headsets, younameit Apr 16 18:51:59 recaller, mediaplayer pause on call, screenblanker and proximity sensor, ... Apr 16 19:00:21 Wizzup: ROTFL Apr 16 19:00:52 >>maybe handover dev of this toy to someone with unix experience<< FULL ACK Apr 16 19:01:04 or just nuke the whole pile of shit Apr 16 19:10:47 Oh, cool, systemd is on github apparently. Now, I don't have to go to twitter to troll you guys Apr 16 19:10:49 ;) Apr 16 19:11:41 https://github.com/systemd/systemd/issues/5740 Apr 16 19:11:46 this one is nice too Apr 16 19:12:04 to the reddit Apr 16 19:29:14 >>It certainly doesn't help it isn't defined anywhere what path_is_safe means and for what it is "safe". << https://github.com/systemd/systemd/pull/5655 -- pathetic and embarrassing Apr 16 19:32:26 ~nosystemd Apr 16 19:32:27 i heard nosystemd is https://devuan.org http://without-systemd.org/wiki/index.php/Arguments_against_systemd http://blog.darknedgy.net/technology/2015/10/11/0/ Apr 16 19:39:23 wtf https://github.com/vshatskyi/black-screen Apr 16 19:40:54 well, if you have space cpu power, why not, otherwise: meh Apr 16 19:41:44 that's what my desktop was lacking Apr 16 19:41:49 more javascript in my terminal emulator Apr 16 19:42:15 mmm, sploits that sploit you while you are sploiting? Apr 16 21:48:45 apropos twinkle: funny what stuff I wrote a nearly 10 years ago http://paste.ubuntu.com/24396559 Apr 16 21:49:43 prolly even older since that file is already migrated from a yet older box/system Apr 16 21:50:45 meanwhile both bash and I learned how to do such multithreaded stuff a tad smarter Apr 16 21:52:39 and SIP registrars learned to not listen to the IP announced in SIP messages and rather use STUN/ICE and server assisted SIP to establish a call even to clients behind NAT Apr 16 21:54:21 and nobody really does direct IP2IP VoIP (without registrar) anymore Apr 16 21:55:45 if anybody except me ever did Apr 16 21:56:50 DocScrutinizer05: yeah because SIP is a shit protocol Apr 16 21:57:19 not really. Just complex Apr 16 21:57:56 and not made from beginning with stuff like roaming and all sorts of nasty NATs in mind Apr 16 22:00:26 SMTP is a real shit protocol ;-D Apr 16 22:03:04 at least SMTP uses one connection :< Apr 16 22:11:19 ftp doesn't Apr 16 22:11:56 but yeah, multiple ports are actually a nightmare. at least in SIP you can fix the ports to use Apr 16 22:12:31 for ftp you have *lots* of fun with NATs Apr 16 22:13:15 also for IRC DCC btw Apr 16 22:13:34 which is in many aspects similar to SIP VoIP Apr 16 22:17:53 A initiating a ftp file transfer from B to C is very similar to SIP A connecting B and C in a call, by A either forwarding a inbound call or steeping out of a 3way-conference Apr 16 22:21:38 the problem always is NATs don't open receive ports, that's why they are considered a good safeguard against active attacks from 'outside' but that implies they also are a problem for stuff like ftp or SIP Apr 16 22:22:31 VPN is just a glorified distributed NAT Apr 16 22:23:24 so you have exactly same issues like with any other (local) NAT Apr 16 22:38:34 Hello guys, hope you had a nice Easter day. Apr 16 22:38:58 I'm trying to learn the last couple of things from Debian before switching to Devuan. Apr 16 22:40:06 Now I have a strange issue about key mapping. I have been able to map some symbols to the fourth level. But with my surprise, the fourth level is not working for the keys a, z and x. And just for them - the rest is working. Apr 16 22:40:12 Anybody know about a similar issue? Apr 16 22:40:54 no Apr 16 22:42:25 http://wiki.maemo.org/N900_Hardware_Subsystems#Keyboard Apr 16 22:49:09 I read it (without thinking too much about the details...). If I got it, Sh-Fn-x and Sh-Fn-z produce the same hardware event. So it is not possible to map them to different symbols. Is this right? Apr 16 22:56:02 sorry, I just closed it so can't tell if z/x is right. The rest is correct Apr 16 22:58:09 note that this stuff is merely deduced from schematics, I didn't verify against device behavior when I wrote it Apr 16 22:59:19 anyway this is generally one of the reasons to use "sticky qualifier keys", like shift-down shift up a-down a-up -> uppercase-A Apr 16 23:01:39 this works in maemo for shift and blue, not though for ctrl. And I think it doesn't work in the generic debian kbd driver either Apr 16 23:07:00 the canonical pattern is (not found in maemo): press qualifier once: sticky for next keypress (like explained above). Press qualifier twice: lock (like capslock for pressing shift twice). With lock engaged any further press of the qualifier key will unlock and not create sticky state Apr 16 23:08:40 so for repeated pressing a qualifier, the sequence is sticky -> locked -> off -> sticky -> locked -> off ->... Apr 16 23:09:52 ooh sorry, maemo DOES that too Apr 16 23:11:03 it kist lacks to show recent state, though that had been very very easy via indicator LED Apr 16 23:11:09 just* Apr 16 23:16:46 Ok, thank you, got it. Would be interesting to enable these sticky qualifier keys in Debian as well. But it's not necessary, so I won't investigate further. Apr 16 23:17:50 I *think* maemo does it on X11 level Apr 16 23:18:06 not sure though Apr 16 23:18:25 could as well be kernel level Apr 16 23:19:36 pr anything intermediate. keybpard service layering is a mystery to me. I have studied it from bottom to top a dozen times already and each single time I forgot about bottom details when I reached top Apr 16 23:19:45 or* Apr 16 23:21:17 :) Apr 16 23:25:06 hmm, maybe useful (for me and my problem): https://unix.stackexchange.com/questions/116629/how-do-keyboard-input-and-text-output-work Apr 16 23:28:39 >>The device file transmits key up/down events with a scan code, which may or may not be identical to the value transmitted by the hardware (the kernel may translate the scan code from a keyboard-dependent value to a common value, and Linux doesn't retransmit the scan codes that it doesn't know).<< Apr 16 23:31:05 now it gets funny only with >>There are two mechanisms to configure the mapping from keycodes to keysyms:<< Apr 16 23:39:20 there's also http://homepages.cwi.nl/~aeb/linux/kbd/scancodes-8.html#kccb2 and http://compsoc.man.ac.uk/~shep/pedals.html which I bookmarked for a particular reason. The latter might be interesting for you too Apr 16 23:53:01 evtest is rather great Apr 17 00:39:55 Maemo does it at the HIM level. Apr 17 00:40:11 (the sticky keys mechanism) Apr 17 00:40:26 HIM = hildon-input-method **** ENDING LOGGING AT Mon Apr 17 03:00:01 2017