| 00:17.40 | *** join/#maemo sunshavi (~user@190.234.106.90) |
| 00:29.19 | *** join/#maemo realitygaps (~realityga@2a01:4a0:3::5096:aeb) |
| 00:29.19 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 00:44.16 | DocScrutinizer05 | ~flashing |
| 00:44.16 | infobot | somebody said maemo-flashing was http://wiki.maemo.org/Updating_the_tablet_firmware, or - on linux PC - download&extract http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir.tgz, cd into it, do sudo ./flash-it-all.sh |
| 00:44.49 | DocScrutinizer05 | particularly http://wiki.maemo.org/Updating_the_tablet_firmware#N900 |
| 00:45.58 | DocScrutinizer05 | >>(flashing the) eMMC aka *VANILLA*, which will replace the complete content of N900's internal 32 GB eMMC storage (embedded MMC), which is: the /home partition which has your stored browser passwords and game highscores and calendar and contacts etc.<< |
| 00:46.44 | DocScrutinizer05 | vs >>(flashing the) FIASCO aka *COMBINED*, also referred to as "rootfs"<< which obviously does not touch those items in /home |
| 00:47.12 | DocScrutinizer05 | then also >>It is strongly advised you regularly use the Backup application to create backups of your settings and data to a safe storage.<< |
| 00:48.20 | DocScrutinizer05 | >>The Backup application will save: [...]<< |
| 00:48.48 | *** join/#maemo pigeon (~pigeon@eth5284.nsw.adsl.internode.on.net) |
| 00:50.11 | DocScrutinizer05 | also see: |
| 00:50.14 | DocScrutinizer05 | ~bm |
| 00:50.14 | infobot | it has been said that backupmenu is http://talk.maemo.org/showthread.php?t=63975 |
| 00:50.36 | DocScrutinizer05 | which is yet another backup method than the above referenced Backup App |
| 00:51.49 | DocScrutinizer05 | I think I accomplished my daily duty of avoiding "RTFM" replies |
| 00:56.25 | *** join/#maemo sunshavi (~user@190.234.106.90) |
| 01:06.43 | *** join/#maemo fishbulb (cbd6808f@gateway/web/freenode/ip.203.214.128.143) |
| 01:07.00 | fishbulb | hey, every time this freenode webchat times out the text disappears |
| 01:07.23 | fishbulb | someone said something about a flasher and backup app? |
| 01:07.34 | fishbulb | is there a working whatsapp? |
| 01:08.15 | fishbulb | or any other way to either send pictures or chat on the n900 |
| 01:08.21 | fishbulb | with people who have normal phones |
| 01:14.36 | DocScrutinizer05 | http://mg.pov.lt/maemo-irclog |
| 01:15.19 | DocScrutinizer05 | yappari they said |
| 01:16.40 | *** join/#maemo FlameReaper-PC (~FR@175.139.21.117) |
| 01:23.59 | fishbulb | it's not in the repos |
| 01:27.30 | fishbulb | um, the backupmenu restores the exact settings |
| 01:28.02 | fishbulb | I don't know how but clicking on the repo install thing changed something that broke the phone |
| 01:28.23 | fishbulb | fMMS won't send or open pictures properly anymore |
| 01:28.43 | fishbulb | this is pretty crucial, I use it all the time |
| 01:29.10 | fishbulb | I get the mms, it comes through from a number, and fmms can't open it |
| 01:31.38 | fishbulb | it says the picture is sent, then the other person doesn't get it |
| 01:37.07 | DocScrutinizer05 | fishbulb: please, if you repeat this "clicking on the repo install thing broke the phone" an N+1th time, I have to add you to my ignore list, to protect my sanity |
| 01:37.37 | DocScrutinizer05 | no matter if true or (most likely) incorrect, we *all* have heard it now |
| 01:38.57 | *** join/#maemo at1as (~at1as@kurios.r4780y.com) |
| 01:40.21 | fishbulb | ok I'm not sure how to diagnose how exactly fMMS stopped working |
| 01:40.36 | fishbulb | 100% stopped working when it was working perfectly before |
| 01:45.09 | *** join/#maemo dimw1t (~at1as@kurios.r4780y.com) |
| 01:46.58 | *** join/#maemo krnlyng (~liar@178.112.150.212.wireless.dyn.drei.com) |
| 01:49.51 | DocScrutinizer05 | when you didn't change anything, then probably something in the provider's infra/config changed. Nothing unheard of, actually. Providers do it all the time |
| 01:50.50 | DocScrutinizer05 | did you make sure your account is actually working, I.E. you have a psitive balance and sending SMS and data connection are all fine? |
| 01:53.04 | DocScrutinizer05 | [2016-01-10 Sun 14:10:47] <freemangordon> fishbulb: double check http://support.vodafone.com.au/articles/FAQ/PXT-MMS-settings against your fmms settings [2016-01-10 Sun 17:06:41] <fishbulb> I've double checked all of that :/ |
| 01:53.26 | fishbulb | yeah just ignore that last part |
| 01:53.52 | DocScrutinizer05 | I suspect it needs a triple check then, involving googling for additional info about recent changes or problems on provider side |
| 01:54.06 | fishbulb | that's only the 10th + |
| 01:54.12 | fishbulb | time where I say all the settings are correct |
| 01:57.32 | *** join/#maemo Kabouik (~quassel@65.76.93.92.rev.sfr.net) |
| 02:00.00 | fishbulb | all the settings are exactly right |
| 02:06.41 | *** join/#maemo eMHa__ (~mh@p579DB8C7.dip0.t-ipconnect.de) |
| 02:19.13 | DocScrutinizer05 | and it's the at least 2nd time I try to tell you that "correct" is a literally relative term, since it needs a reference to which it compares for correctness. When you say your settings are correct in relation to http://support.vodafone.com.au/articles/FAQ/PXT-MMS-settings then maybe that site is _not_ correct. That's why I said "...involving googling for additional info about recent changes or problems on provider side" |
| 02:22.11 | DocScrutinizer05 | from discontinuing an obsolete service on a particular deprecated APN to introducing a new version of the protocol used, there's a virtually endless number of possible changes on provider side |
| 02:22.56 | DocScrutinizer05 | frals: ^^^ any comments? |
| 02:24.42 | *** join/#maemo pozitrono (~nu@109.201.143.40) |
| 02:30.25 | DocScrutinizer05 | [2016-01-10 Sun 14:26:59] <freemangordon> what log says it that their DNS has no clue about pxt.vodafone.net.au [2016-01-10 Sun 14:27:09] <fishbulb> their dns? [2016-01-10 Sun 14:27:13] <freemangordon> yes [2016-01-10 Sun 14:27:16] <fishbulb> so it's their fault probably |
| 02:32.03 | DocScrutinizer05 | (([2016-01-10 Sun 14:27:32] <fishbulb> I recieved an mms <fishbulb> it came to the phone, but I can't download the picture )) that's exactly a symptom of SMS with 'URL' to download the multimedia content arrived, but the URL doesn't resolve due to ^^^ |
| 02:33.14 | DocScrutinizer05 | I heard providers now and then have malfunctions. Sometimes for days or even weeks |
| 02:33.33 | *** join/#maemo esaym153 (~esaym153@75-1-182-8.lightspeed.snantx.sbcglobal.net) |
| 02:36.01 | *** join/#maemo Humpelstilzchen (erik@x55b02dc9.dyn.telefonica.de) |
| 02:38.37 | fishbulb | vodafone says there's no problem |
| 02:38.52 | fishbulb | this phone hasnt' been flashed in years |
| 02:47.29 | *** join/#maemo heroux (sandroco@gateway/shell/insomnia247/x-gwyygcgmzcsdzcyv) |
| 02:57.27 | DocScrutinizer05 | there are two options: 1) wait for frals suggesting how to do in-depth analysis and debugging of this. I doubt it will get any better than what freemangordon already told you, without frals who's the author of fMMS. 2) completely delete and reinstall fMMS, redo all config and test again. |
| 03:19.24 | DocScrutinizer05 | ((vodafone says...)) I witnessed a 1 week complete breakdown of the 2G functionality of the cell servicing the area where I live. O2 never admitted any problems |
| 03:23.30 | DocScrutinizer05 | anyway a complete flashing can't hurt, particularly after using fapman and doing so since years without flashing. |
| 03:29.40 | *** join/#maemo heroux (sandroco@gateway/shell/insomnia247/x-nmodombdvamzgllu) |
| 03:33.25 | *** join/#maemo at1as (~at1as@kurios.r4780y.com) |
| 03:42.42 | *** join/#maemo Kilroo (~Kilroo@98.27.26.236) |
| 03:47.34 | *** join/#maemo krnlyng (~liar@178.112.150.212.wireless.dyn.drei.com) |
| 03:59.05 | *** join/#maemo heroux (sandroco@gateway/shell/insomnia247/x-gzxsoriravueuwfe) |
| 04:03.22 | *** join/#maemo Vajb (~Vajb@85-76-146-255-nat.elisa-mobile.fi) |
| 04:19.35 | *** join/#maemo Kilroo (~Kilroo@98.27.26.236) |
| 04:47.10 | *** join/#maemo shamus (~shmaus@ip-206-192-194-12.marylandheights.ip.cablemo.net) |
| 04:52.37 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 04:55.06 | KotCzarny | <fishbulb> I'm pretty sure I did apt-get upgrade with the testing repo in there |
| 04:55.08 | KotCzarny | lol |
| 05:01.33 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 05:19.42 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 05:23.41 | *** join/#maemo esaym153 (~esaym153@75-1-182-8.lightspeed.snantx.sbcglobal.net) |
| 05:34.47 | *** join/#maemo auenf (David@120.155.97.223) |
| 05:45.30 | *** join/#maemo Venusaur (~wdwrwf@wikipedia/Antonio-Lopez) |
| 05:46.08 | *** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 05:46.59 | *** join/#maemo rosseaux (~BeRo@2a00:1828:2000:859::2) |
| 05:49.30 | *** join/#maemo till (~till@vispillo.org) |
| 05:50.24 | *** join/#maemo krnlyng (~liar@178.112.150.212.wireless.dyn.drei.com) |
| 05:56.10 | *** join/#maemo rosseaux (~BeRo@228.66.238.89.in-addr.arpa.manitu.net) |
| 06:07.19 | *** join/#maemo Vajb (~Vajb@85-76-17-41-nat.elisa-mobile.fi) |
| 06:13.00 | *** join/#maemo till (~till@vispillo.org) |
| 06:15.05 | *** join/#maemo stryngs (~stryngs@unaffiliated/stryngs) |
| 06:59.35 | frals | fishbulb: check fmms.log and see what error is reported when its trying to fetch the mms |
| 07:02.42 | frals | and as DocScrutinizer05 said, theres about a million different reasons it can randomly fail, most of them on the provider side |
| 07:03.04 | freemangordon | frals: nslookup cannot resolve the host needed to fetch the content |
| 07:03.30 | frals | ah, right |
| 07:04.10 | frals | try manually connecting to their MMS apn and resolve the host, otherwise the operator is most likely having issues with their service |
| 07:04.38 | freemangordon | frals: "manually connecting" - how? |
| 07:05.14 | frals | easiest is probably modifying the "internet apn" through internet conenction settings to use the same settings as the MMS APN and just connect thru the normal ui |
| 07:05.26 | frals | but its been a couple of years since i last used a n900 :) |
| 07:06.03 | freemangordon | hmm, yeah |
| 07:06.17 | freemangordon | fishbulb: ^^^ |
| 07:13.22 | frals | just scrolled waaaay back, make sure the proxy is set as well |
| 07:13.49 | freemangordon | he said the proxy is set-up |
| 07:14.05 | freemangordon | been asked several times |
| 07:14.09 | frals | aight |
| 07:14.48 | DocScrutinizer05 | hi frals :-) |
| 07:15.00 | DocScrutinizer05 | thanks for helping out |
| 07:15.07 | frals | shame the log pastebin expired, but easiest way to see if its fMMS or operator is by connecting through the standard interface and see if it works there |
| 07:15.40 | frals | the magic scripts i hacked together to bring up 2 connections at the same time arent as good as they should be.. but they mostly work ;) |
| 07:15.44 | frals | no worries :) |
| 07:15.51 | DocScrutinizer05 | frals: is sending MMS also involving sending of a SMS, or is that SMS only on receiver side? |
| 07:16.19 | frals | sms only on receiver, http on sender |
| 07:16.25 | DocScrutinizer05 | ack, ta |
| 07:17.13 | frals | the "problem" is that sending is usually just posting to the mmsc, which some oeprators have accessible through all their APNs, while getting the mms *might* be on a different host thats only accessible through their mms apn |
| 07:17.25 | DocScrutinizer05 | so when fMMS says "MMS sent", this means it actually could upload the content via HTTP |
| 07:17.31 | frals | yeah |
| 07:18.05 | frals | and that the server on the other side didnt say http 4xx as reply iirc |
| 07:18.06 | freemangordon | then it seems the APN is correct |
| 07:18.19 | DocScrutinizer05 | the TX APN yes |
| 07:18.21 | freemangordon | if he is able to send |
| 07:18.28 | freemangordon | it is only one APN |
| 07:19.01 | *** join/#maemo lobito (~lobito@190.177.201.22) |
| 07:19.02 | frals | mmsc might not be accessible if hes not connected to the "right" APN, which is used for retrieving |
| 07:19.27 | DocScrutinizer05 | I suspected wrong APN all the time actually |
| 07:19.33 | freemangordon | frals: could we have different APNs for sending and receiving? |
| 07:19.48 | DocScrutinizer05 | freemangordon: see frals' post 3 up |
| 07:20.22 | freemangordon | ah, you mean he is connected to the "internet" APN and is able to send, but not receive? that makes sense |
| 07:20.28 | DocScrutinizer05 | or are you asling if fMMS supports this per default |
| 07:20.50 | freemangordon | yes, if this is supported |
| 07:21.03 | frals | not supported in fmms |
| 07:21.09 | DocScrutinizer05 | frals: is there a way to ask modem which is the APN currently used? |
| 07:21.24 | frals | uh icd had some stuff for that iirc |
| 07:21.34 | DocScrutinizer05 | AT cmd? |
| 07:21.44 | frals | gets bit tricky since fmms connects to 2 APNs in most cases... ) |
| 07:21.51 | DocScrutinizer05 | sorry, shouldn't pester you when google would do |
| 07:22.27 | frals | basically fmms has a setting to automatically connect you to the mms apn in the background without disrupting the internet connection.. might be that vodafone stopped supporting multiple contexts at the same time |
| 07:22.27 | DocScrutinizer05 | so the BB5 actually supports 2 concurrent APN? |
| 07:22.40 | frals | yeah, not sure what the upper limit was but 2 was fine |
| 07:22.48 | DocScrutinizer05 | 4 iirc |
| 07:22.53 | freemangordon | frals: he said he uses "havoc" mode |
| 07:22.54 | DocScrutinizer05 | upper limit |
| 07:23.06 | frals | ok, havoc tries to connect automagically in the background |
| 07:23.19 | frals | i hope i logged something if it failed to do that... |
| 07:23.25 | DocScrutinizer05 | hehehe |
| 07:23.42 | frals | but could be that he was connected to internet apn, and then the mms apn connect failed, and then that could explain what he was seeing |
| 07:23.55 | frals | changing connection mode to the safe one could be worth trying |
| 07:24.15 | DocScrutinizer05 | I suggest using pnatd to ask modem which contexts/APN (there was even another better name, no?) are active |
| 07:24.27 | frals | anyway have to run to work, please ping me when he shows up / if i can help with anything else :) |
| 07:24.50 | freemangordon | has to run too |
| 07:25.08 | DocScrutinizer05 | another idea: aiui fMMS creates a second network device for the second context/APN. So we could use wireshark to see what's going on there |
| 07:25.33 | DocScrutinizer05 | frals: freemangordon: have a nice day both of you guys! |
| 07:27.08 | DocScrutinizer05 | (wireshark) actually a simple ifconfig before and after sending or trying to receive a MMS should already do, to see if any and how much traffic wnet via each of the two APN |
| 07:28.17 | *** join/#maemo LauRoman (~LauRoman@5-14-183-115.residential.rdsnet.ro) |
| 07:28.54 | DocScrutinizer05 | iirc (long ago that I last looked at MMS from some distance) you even need to tell provider that your device can handle and wants to use MMS, so the provider enables some services (possibly the special APN) for you |
| 07:30.56 | DocScrutinizer05 | unless fishbulb gets rootsh and network tools (dig/host, ifconfig, etc pp) installed, and learns how to connect to phone via ssh session from PC, we won't get anywhere debugging this |
| 07:32.27 | DocScrutinizer05 | first pretty simple test: spoil the standard APN for data connectivity, so we can be sure fMMS doesn't use "the internet" to send MMS |
| 07:33.39 | DocScrutinizer05 | anyway I have to run as well. Need to sort my 2015 taxes |
| 07:33.48 | DocScrutinizer05 | bbl |
| 07:35.31 | DocScrutinizer05 | heck! when you google for 3GPP AT commands, 2nd hit is "radekp" :-) |
| 07:35.56 | DocScrutinizer05 | http://radekp.github.io/qtmoko/api/atcommands.html |
| 07:36.48 | DocScrutinizer05 | HAH! "PDP context" was the name |
| 07:41.09 | DocScrutinizer05 | ok, BB5 (aka N900) supports THREE PDP contexts: http://paste.opensuse.org/30269195 |
| 07:41.38 | KotCzarny | frals: does fmms come with apn db or it fetches it from somewhere? |
| 07:42.18 | DocScrutinizer05 | http://ukblog.im-mobility.com/public/support/Nokia/Nokia_CS-10_AT_Command_Set.pdf search: "AT+CGDCONT" |
| 07:42.39 | DocScrutinizer05 | or jump to page 180 |
| 07:42.45 | DocScrutinizer05 | o/ l8rs |
| 07:45.47 | DocScrutinizer05 | MEH!!! |
| 07:45.49 | DocScrutinizer05 | AT+CGPADDR=1 |
| 07:45.51 | DocScrutinizer05 | ERROR |
| 07:48.12 | frals | KotCzarny: the device ships with mms apn db (since pr1.1 or 1.2) :) |
| 07:49.13 | DocScrutinizer05 | duh, what? |
| 07:49.31 | DocScrutinizer05 | sorry i'm missing context |
| 07:49.42 | DocScrutinizer05 | opens chanlog |
| 07:54.06 | *** join/#maemo raandoom (~raandoom@195.16.110.223) |
| 07:54.21 | KotCzarny | frals, that's what i thought, because n900 didnt support mms, and settings were magically filled :) |
| 07:57.52 | *** join/#maemo vakkov (~vakkov@94.190.228.159) |
| 08:02.47 | DocScrutinizer05 | mms apn db? really now? |
| 08:03.07 | DocScrutinizer05 | heck that thing must be out of date now |
| 08:24.58 | frals | DocScrutinizer05: yeah, if fishbulb is comfy in the terminal it should be pretty easy to figure out where things go wrong |
| 08:25.02 | *** join/#maemo florian_kc (~fuchs@Maemo/community/contributor/florian) |
| 08:25.22 | frals | yeah, probably a tad out of date by now.. :) |
| 08:26.00 | frals | otoh from what i heard back while working on fmms operators rarely changed those settings |
| 08:26.38 | frals | someone could always write a small script to parse the OTA provisioning messages the operator sends out, but i didnt want to even look at that after reading the mms "standard" :D |
| 08:26.44 | KotCzarny | but it can happen |
| 08:28.52 | frals | yeah |
| 08:29.19 | frals | biggest issue is usually new mvnos |
| 08:37.43 | *** join/#maemo freemangordon_ (~ivo@92.247.16.100) |
| 08:39.52 | *** join/#maemo geaaru (~geaaru@host170-152-static.43-88-b.business.telecomitalia.it) |
| 08:42.10 | fishbulb | hey did I mention I can send MMS to myself |
| 08:44.28 | bencoh | I think you did |
| 08:45.24 | fishbulb | yappari seems to work |
| 08:45.30 | fishbulb | and be available on most phones |
| 08:45.52 | *** join/#maemo robink (quasselcor@unaffilated/robink) |
| 09:01.11 | frals | fishbulb: can you post the logfile to pastebin so i can have a look? |
| 09:01.21 | frals | include sending to yourself + failing to retrieve one if possible |
| 09:02.42 | fishbulb | hi I'm here for a few minutes |
| 09:03.14 | fishbulb | I'll post the one log file I have and make another one too |
| 09:06.10 | ceene | fishbulb: yappari works indeed, but do not create any group or whatsapp will ban you |
| 09:06.17 | ceene | that's something i'd really like to fix, but i don't know how |
| 09:06.57 | bencoh | ceene: did you try dumping traffic and compare it to what does an android phone to create groups? |
| 09:07.01 | fishbulb | ok. I just need one way of sending pictures to normal people's phones |
| 09:07.35 | ceene | bencoh: it's easier than that, we have decompiled code of official whatsapp |
| 09:07.45 | ceene | and i can't for the life of me get which is the difference between theirs and mine |
| 09:07.54 | bencoh | ceene: oh and, maybe you should disable the "create group" function meanwhile |
| 09:08.04 | ceene | that's true |
| 09:08.13 | ceene | i placed a big red warning explaining that |
| 09:08.20 | ceene | but still a couple people got banned |
| 09:08.21 | KotCzarny | ceene, then packet dump |
| 09:08.25 | KotCzarny | could be easier |
| 09:08.25 | bencoh | ceene: this is why dumping traffic might be a good idea :) |
| 09:08.34 | ceene | traffic is encrypted |
| 09:08.35 | bencoh | if you cant work it out from the decompiled source |
| 09:08.37 | ceene | and all that |
| 09:08.53 | ceene | xmpp protocol is first binary encoded |
| 09:08.57 | ceene | and then it goes through ssl |
| 09:09.03 | ceene | so it's quite a headache |
| 09:09.10 | bencoh | TPROXY + ssltunnel (for instance) |
| 09:09.38 | bencoh | but yeah, it's a pain |
| 09:09.59 | fishbulb | http://pastebin.com/KVTqCMFV |
| 09:10.36 | fishbulb | this is me trying to send one and trying to open one |
| 09:10.46 | fishbulb | I think I try to open one first |
| 09:10.53 | fishbulb | and then I send one maybe? |
| 09:13.45 | frals | hmm |
| 09:17.00 | frals | im thinking it doesnt work because of the failure to resolve the mmsc host to ip |
| 09:17.15 | frals | and the fmms_magic script doesnt early out there, it pretends everything is fine even though it goes bonkers |
| 09:17.43 | frals | can you try changing connection mode to the safe one |
| 09:18.29 | frals | "polite" or "rude" |
| 09:18.52 | frals | try "rude" first, it'll bring down the current connection though |
| 09:19.30 | *** join/#maemo xorly (~xorly@ip-86-49-15-121.net.upcbroadband.cz) |
| 09:20.33 | frals | or edit your normal 3G internet connection to use the MMS settings and see if you can receive mms while using that |
| 09:27.34 | KotCzarny | frals: what those rude/polite modes are for? |
| 09:32.32 | frals | * Polite (Default behavior <0.6): Only switch to MMS connection if no connection is active, otherwise do nothing (pretty much) |
| 09:32.35 | frals | * Rude: Force a disconnect of the active connection regardless of what it is, connect to MMS APN and then reconnect to the old one. |
| 09:32.38 | frals | * Havoc: Try to bring up a connection to the MMS APN in parallell with whatever is active, this is what most other phones do. Note that to get this functionality on the N900 there are a few ugly hacks active which might break stuff, but it *should* work |
| 09:32.42 | frals | http://talk.maemo.org/showthread.php?t=39737 ;) |
| 09:33.34 | frals | fishbulb: so, change 3g internet connection settings to look like the mms one, set connection mode in fmms to polite, manually ocnnect to your 3g connection and then try to fetch the mms |
| 09:34.19 | KotCzarny | frals: thx |
| 09:34.19 | fishbulb | oh some info |
| 09:34.29 | fishbulb | I don't really have the internet going all the time |
| 09:35.59 | KotCzarny | frals: may i propose names: 'lazy connect', 'force mms apn' and 'parallel' ? |
| 09:36.23 | fishbulb | it's never going actually. |
| 09:36.35 | fishbulb | there's no autodisconnect stuff |
| 09:36.39 | fishbulb | whoa, bowie is dead? |
| 09:36.43 | frals | KotCzarny: needed one word to fit in the UI ;) |
| 09:37.34 | KotCzarny | :) |
| 09:55.40 | fishbulb | hey |
| 09:55.49 | fishbulb | sorry I'm not gonna be much use right now |
| 09:57.49 | fishbulb | it's like 9pm and there's stuff happening |
| 10:01.06 | *** join/#maemo wnd (~wnd@katei.fi) |
| 10:01.18 | *** join/#maemo ecloud (quassel@nat/digia/x-wywybrbvokldffhv) |
| 10:02.34 | *** join/#maemo ssvb (~ssvb@dsl-espbrasgw1-54fa71-124.dhcp.inet.fi) |
| 10:04.48 | *** join/#maemo aloril (~aloril@dsl-tkubrasgw1-54fa3f-129.dhcp.inet.fi) |
| 10:07.45 | *** join/#maemo `0660 (olli@37.16.104.148) |
| 10:09.37 | *** join/#maemo Tenhi_ (~tenhi@static-ip-69-64-50-196.inaddr.ip-pool.com) |
| 10:30.19 | *** join/#maemo raandoom (~raandoom@195.16.110.223) |
| 10:32.27 | *** join/#maemo Kabouik_ (~quassel@65.76.93.92.rev.sfr.net) |
| 10:34.29 | *** join/#maemo Kabouik__ (~quassel@65.76.93.92.rev.sfr.net) |
| 10:37.07 | *** join/#maemo Kabouik (~quassel@65.76.93.92.rev.sfr.net) |
| 10:39.32 | *** join/#maemo Kabouik_ (~quassel@65.76.93.92.rev.sfr.net) |
| 10:42.40 | *** join/#maemo xes_ (~xes@unaffiliated/xes) |
| 10:51.54 | *** join/#maemo eMHa__ (~mh@185.36.21.1) |
| 11:06.07 | *** join/#maemo realitygaps (~realityga@2a01:4a0:3::5096:aeb) |
| 11:06.07 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 11:32.39 | *** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 11:36.19 | jonwil | hi |
| 11:41.58 | ceene | hi |
| 11:42.04 | ceene | jonwil: i don't know if you read me last night |
| 11:42.09 | ceene | but i've hacked something onto qt4 |
| 11:42.18 | ceene | and i've got it to connect to tlsv1.2 servers :) |
| 11:42.20 | jonwil | yeah I saw you did something with QT4 and newer openssl |
| 11:42.23 | jonwil | thats a good start |
| 11:42.24 | ceene | yeah! :) |
| 11:42.47 | ceene | something nice about qt |
| 11:43.01 | ceene | is that it doesn't link against openssl, but uses dlopen |
| 11:43.11 | ceene | and searches for the most up to date version |
| 11:43.18 | jonwil | nice one |
| 11:43.33 | ceene | so the patch i made last night is only needed to support new protocols |
| 11:43.42 | ceene | but at least, simply installing openssl1 will make qt use it |
| 11:47.32 | *** join/#maemo dreamer (~henk@unaffiliated/dreamer) |
| 11:58.12 | *** join/#maemo Vajb (~Vajb@85-76-15-196-nat.elisa-mobile.fi) |
| 12:00.50 | *** join/#maemo geaaru (~geaaru@host170-152-static.43-88-b.business.telecomitalia.it) |
| 12:05.12 | ceene | there are quite a few changes on qt's network/ssl module between 4.7 and 5 |
| 12:05.24 | ceene | so i din't know how feasible it is to backport all of that |
| 12:14.45 | bencoh | we probably dont need everything just to use the right TLSv*_method (or whatever the enum/functions is) anyway |
| 12:15.07 | ceene | if that's the case, probably something very similar to what i've already done is enough |
| 12:15.18 | bencoh | I'd just patch 4.7 with the few lines need to enable tlsv>1.0 |
| 12:15.56 | ceene | which should be the default protocol, if any? |
| 12:17.16 | bencoh | most probably yeah |
| 12:17.17 | bencoh | \/43 |
| 12:17.19 | bencoh | woops |
| 12:18.16 | *** join/#maemo Arch-TK (Arch-TK@fsf/member/Arch-TK) |
| 12:18.37 | ceene | i can see you're pretty excited about this :P |
| 12:19.29 | ceene | i'm thinking |
| 12:19.40 | ceene | that a priority based system could work |
| 12:19.56 | ceene | try first tlsv1_2, if can't connect, try again tlsv1_1 |
| 12:19.57 | ceene | etc |
| 12:20.08 | bencoh | KISS, we're talking about ssl/tls ;p |
| 12:20.15 | ceene | yeah, but |
| 12:20.18 | ceene | if i change the enums |
| 12:20.25 | ceene | we'd need to recompile every qt app out there |
| 12:20.30 | ceene | and i don't want that |
| 12:20.38 | ceene | i want all qt applications to use the most secure protocol by default |
| 12:21.01 | ceene | even if they don't know nothing about tlsv1.2, which they don't because qt4.7 didn't support it |
| 12:21.02 | bencoh | current code goes through the protocols list in enum order? |
| 12:21.11 | ceene | nope |
| 12:21.13 | ceene | current one |
| 12:21.20 | ceene | uses either user chosen protocol |
| 12:21.32 | ceene | or a default one, which is case QSsl::AnyProtocol: |
| 12:21.32 | ceene | <PROTECTED> |
| 12:21.32 | ceene | <PROTECTED> |
| 12:21.35 | ceene | <PROTECTED> |
| 12:21.45 | bencoh | then you dont need to insert values in-between two enums, just add it at the end (?) |
| 12:22.10 | ceene | but in that case i'll need to change the default to one of the new protocols |
| 12:22.17 | ceene | otherwise, they wouldn't be usuable by anyone |
| 12:22.27 | ceene | i can add the tlsv1.2 code, but no application will know to chose it |
| 12:22.42 | ceene | and sslv3 is completely deprecated, so I guess we shouldn't even allow it |
| 12:22.49 | bencoh | just change the default: line |
| 12:22.58 | ceene | and set what? |
| 12:23.00 | ceene | tlsv1.2? |
| 12:23.01 | bencoh | sslv2 is deprecated as well |
| 12:23.06 | ceene | lol |
| 12:23.08 | ceene | ok |
| 12:23.16 | ceene | so should i just set tlsv1.2 as the default |
| 12:23.23 | ceene | and let applications choose something older if they want |
| 12:23.30 | bencoh | I think there is a generic tlsv1 call in openssl1.x |
| 12:23.42 | ceene | there may be, let me grep for it |
| 12:24.45 | ceene | TLS_method(), TLS_server_method(), TLS_client_method() |
| 12:24.46 | ceene | A TLS/SSL connection established with these methods may understand the SSLv3, TLSv1, TLSv1.1 and TLSv1.2 protocols. |
| 12:25.03 | ceene | but it alows sslv3 |
| 12:25.19 | bencoh | I think you can also pass it some flags to disable any protocol |
| 12:25.30 | bencoh | (same goes for ciphers) |
| 12:25.48 | bencoh | I dunno if we want to completely drop sslv3 from default |
| 12:26.03 | ceene | maybe not |
| 12:26.08 | bencoh | what does qt5 do for default? |
| 12:26.40 | ceene | i think... |
| 12:27.07 | ceene | <PROTECTED> |
| 12:27.13 | ceene | i don't know where it does that |
| 12:27.21 | ceene | but that comment is under SecureProtocols |
| 12:27.33 | ceene | so i think it accepts everything and then disables those |
| 12:28.11 | jonwil | In regards to what we enable/disable by default we should follow the practice of whatever others are doing (i.e. what QT5 does or what Firefox does or what Chrome does) |
| 12:28.27 | ceene | qt5 doesn't disable it completely |
| 12:28.33 | ceene | but seems to exclude it from the list of secure protocols |
| 12:28.33 | jonwil | Any site out there that actually needs SSLv3 and will fail with TLS is probably not a site worth caring about |
| 12:29.07 | ceene | <PROTECTED> |
| 12:29.07 | ceene | <PROTECTED> |
| 12:29.14 | ceene | but you are free to choose sslv3 if you want |
| 12:29.46 | ceene | if i can invoke tls_method() and then disable sslv3, the i could set that as the default |
| 12:30.01 | ceene | but let people choose sslv3 if they explicitely want to |
| 12:30.57 | jonwil | Both browsers here on my system disable SSLv3 completly and only enable TLS (1.0, 1.1 and 1.2) |
| 12:31.53 | ceene | uhm |
| 12:32.03 | ceene | that documentation i pasted before about TLS_method() seems to be wrong |
| 12:32.10 | ceene | or non matching my openssl-1 version |
| 12:32.21 | bencoh | ceene: be careful, I'm sure TLS_client_method() is in openssl-0.9.x |
| 12:32.28 | ceene | as there's no match for TLS_client_method |
| 12:32.32 | ceene | yep, it's not there on 1 |
| 12:32.33 | bencoh | right ;) |
| 12:32.46 | ceene | so... what's the alternative on openssl-1? |
| 12:32.51 | jonwil | internet explorer lets you enable SSLv2 and SSLv3 if you need to but they are off on my system |
| 12:33.05 | jonwil | and my other browser doesn't even have options for SSL |
| 12:33.06 | bencoh | ceene: I dont remember :) |
| 12:33.16 | ceene | ok, don't worry |
| 12:33.47 | jonwil | Its great that we are updating OpenSSL and QT and stuff but we still need to figure out how to update nss in microb |
| 12:33.57 | jonwil | and I am still getting nowhere with updating the root CA store |
| 12:36.19 | ceene | it seems tls_method will be back on openssl-1.1 |
| 12:36.55 | ceene | or maybe not |
| 12:37.00 | ceene | i don't understand openssl changelogs |
| 12:37.13 | bencoh | I think nobody understands openssl as a whole |
| 12:37.39 | ceene | lol |
| 12:37.43 | ceene | yeah, i think that's it |
| 12:37.46 | ceene | it'll be on openssl-1.1 |
| 12:37.50 | ceene | which is yet to be released |
| 12:39.09 | bencoh | ceene: SSLv23_client_method in openssl-1.0.x allows tlsv1 |
| 12:39.26 | bencoh | and you can later restrict to disable sslv2 (or v3 for that matters) using SSL_set_options |
| 12:39.40 | ceene | but only v1.0 |
| 12:39.50 | bencoh | and in case you're wondering, yes, this API is plain shit. |
| 12:40.04 | ceene | yep |
| 12:40.09 | ceene | the names don't make any sense |
| 12:40.17 | ceene | nothing makes any sense in fact |
| 12:40.31 | ceene | i just want a secure_client() and a secure_server() |
| 12:40.34 | bencoh | :)) |
| 12:41.10 | ceene | that's why it's called open-ssl instead of o-secure-sl |
| 12:41.18 | ceene | because it's open, but being secure is something yet to proof |
| 12:42.01 | bencoh | anyway, unless you want to rewrite the qt/ssl glue to use libressl, we'll have to deal with it |
| 12:42.21 | ceene | i don't think so |
| 12:42.41 | bencoh | ? |
| 12:43.23 | ceene | that i'll rewrite that |
| 12:43.27 | ceene | i'll just deal with it :P |
| 12:46.15 | bencoh | :) |
| 12:52.02 | *** join/#maemo Vajb (~Vajb@85-76-14-255-nat.elisa-mobile.fi) |
| 12:53.43 | *** join/#maemo ced117 (~ced117@opensuse/member/ced117) |
| 13:00.01 | ceene | i gotta go now |
| 13:00.08 | ceene | but i'm doing that we've talked about |
| 13:00.20 | ceene | i hope this week i can post somewhere a couple of .deb so they can be tested |
| 13:00.29 | ceene | cya! |
| 13:00.35 | bencoh | please rather send a couple of git links :) |
| 13:00.39 | bencoh | but thx :) |
| 13:04.47 | *** join/#maemo troulouliou_div2 (~troulouli@unaffiliated/troulouliou-div2/x-0271439) |
| 13:26.57 | *** join/#maemo at1as (~at1as@kurios.r4780y.com) |
| 13:29.48 | *** join/#maemo realitygaps (~realityga@2a01:4a0:3::5096:aeb) |
| 13:29.48 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 13:29.53 | *** join/#maemo darkschneider (~gab@93-32-51-166.ip32.fastwebnet.it) |
| 14:23.07 | *** join/#maemo troulouliou_div2 (~troulouli@unaffiliated/troulouliou-div2/x-0271439) |
| 14:32.12 | *** join/#maemo vakkov (~vakkov@94.190.229.99) |
| 14:42.33 | DocScrutinizer05 | hmm, something for Pali, a pity he's not around: |
| 14:42.53 | DocScrutinizer05 | >>Device units do exist on the file system, solely for ordering purposes. They are generated only for devices tagged âsystemdâ for udev to interpret in its rulesets. They have no options, and have their primary use to implement a so-called âdevice-based executionâ, which is a conditional execution of units based on udev device availability â this is, in fact, done with the cooperation of udev itself which understands rules like |
| 14:42.55 | DocScrutinizer05 | SYSTEMD_WANTS=. << http://blog.darknedgy.net/technology/2015/10/11/0/ |
| 14:50.56 | DocScrutinizer05 | OOOUUUUUUUUuuuuuUUUU! >>Automount units then are a further variation, as they drive autofs, though do explicitly queue jobs. In practice, theyâre used to extend regular mount units by having mount points be attached lazily, i.e. deferring only until they are accessed.<< |
| 14:56.15 | *** join/#maemo Vajb (~Vajb@85-76-101-21-nat.elisa-mobile.fi) |
| 14:57.21 | *** join/#maemo BCMM (~BCMM@unaffiliated/bcmm) |
| 15:00.33 | DocScrutinizer05 | I've read ~40% now (up to >>The transaction manager<<) and I feel a strong nausea |
| 15:01.14 | DocScrutinizer05 | not because of the article but because of what it describes |
| 15:04.46 | *** join/#maemo krnlyng (~liar@178.112.150.212.wireless.dyn.drei.com) |
| 15:05.37 | *** join/#maemo realitygaps (~realityga@2a01:4a0:3::5096:aeb) |
| 15:05.37 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 15:38.24 | *** join/#maemo Kabouik (~quassel@147.99.219.229) |
| 15:59.56 | *** join/#maemo pozitron (nu@gateway/vpn/mullvad/x-xbvawvcdwlqkrimd) |
| 16:07.27 | *** join/#maemo xorly (~xorly@ip-86-49-15-121.net.upcbroadband.cz) |
| 16:20.47 | *** join/#maemo xorly (~xorly@ip-86-49-15-121.net.upcbroadband.cz) |
| 16:21.06 | *** join/#maemo ccnnjj (~matt@cl-598.bos-01.us.sixxs.net) |
| 16:40.41 | *** join/#maemo krnlyng (~liar@77.117.24.252.wireless.dyn.drei.com) |
| 16:47.34 | *** join/#maemo realitygaps (~realityga@2a01:4a0:3::5096:aeb) |
| 16:47.34 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 16:59.00 | *** join/#maemo lobito1 (~lobito@190.177.201.172) |
| 16:59.20 | *** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 17:13.31 | *** join/#maemo Vajb (~Vajb@85-76-140-161-nat.elisa-mobile.fi) |
| 17:23.39 | *** join/#maemo sparetire_ (~sparetire@unaffiliated/sparetire) |
| 17:37.29 | *** join/#maemo ashneo76 (~ashneo76@switch2.403main.web-pass.com) |
| 18:23.46 | *** join/#maemo FlameReaper (~assassin@115.132.156.186) |
| 18:26.16 | *** join/#maemo krnlyng (~liar@178.112.129.129.wireless.dyn.drei.com) |
| 18:34.55 | *** join/#maemo eMHa__ (~mh@p579DB8C7.dip0.t-ipconnect.de) |
| 18:42.10 | *** join/#maemo disco_stu (~wrt54gl@190.211.82.70) |
| 18:53.33 | *** join/#maemo lufik (~luf@ip-89-103-184-51.net.upcbroadband.cz) |
| 18:58.11 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 19:17.43 | *** join/#maemo M4rtinK (~M4rtinK@ip-37-188-138-209.eurotel.cz) |
| 19:18.34 | *** join/#maemo futpib (~futpib@176.214.26.7) |
| 19:20.27 | *** join/#maemo vectis3 (~user@79-64-237-162.host.pobb.as13285.net) |
| 19:36.25 | *** join/#maemo krnlyng (~liar@77.116.96.41.wireless.dyn.drei.com) |
| 19:44.23 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 20:10.43 | *** join/#maemo vakkov_ (~vakkov@79.132.29.22) |
| 20:29.37 | *** join/#maemo ccnnjj (~matt@cl-598.bos-01.us.sixxs.net) |
| 20:34.49 | freemangordon | Wizzup_: you have gentoo booting on n900 with mainline kernel, ain't? |
| 20:55.38 | *** join/#maemo ult (~root@95.32.206.69) |
| 21:02.06 | *** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 21:06.29 | *** join/#maemo krnlyng (~liar@178.112.135.245.wireless.dyn.drei.com) |
| 21:17.18 | *** join/#maemo vectis3 (~user@79-64-237-162.host.pobb.as13285.net) |
| 21:34.52 | freemangordon | Pali: poweroff -f on device does nothing, is that expected? |
| 21:36.18 | Pali | freemangordon: no idea... look into /etc/init.d/mini* scripts |
| 21:36.35 | Pali | there are scripts which do shutdown/reboot |
| 21:44.16 | *** part/#maemo ult (~root@95.32.206.69) |
| 21:45.21 | *** join/#maemo xray256 (~xray256@176.249.31.157) |
| 21:53.06 | *** join/#maemo Arch-KT (Arch-TK@fsf/member/Arch-TK) |
| 21:54.26 | *** join/#maemo LjL (~ljl@unaffiliated/ljl) |
| 21:58.29 | *** join/#maemo Venusaur (~wdwrwf@wikipedia/Antonio-Lopez) |
| 22:08.43 | *** join/#maemo krnlyng_ (~liar@83.175.90.24) |
| 22:13.01 | *** join/#maemo ebzzry (~user@112.203.142.120) |
| 23:19.48 | *** join/#maemo pigeon (~pigeon@eth5284.nsw.adsl.internode.on.net) |
| 23:53.47 | *** join/#maemo pozitrono (~nu@108.61.123.75) |