| 00:00.58 | *** join/#maemo atlas27 (~atlas@120.89.112.162) |
| 00:21.56 | *** join/#maemo infobot (ibot@208.53.50.136) |
| 00:21.57 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf (or ~tabletsdev ~combined ~emmc ~flasher) sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 00:21.58 | *** mode/#maemo [+v infobot] by ChanServ |
| 00:25.45 | *** join/#maemo gurmble (~grumble@freenode/staff/grumble) |
| 00:37.05 | *** join/#maemo grumble (~grumble@freenode/staff/grumble) |
| 01:04.08 | *** join/#maemo Hijinks20 (~Hijinks@2001:1284:f015:d7df:ca8d:83ff:fe4d:5707) |
| 01:17.14 | *** join/#maemo chainsawbike (~chainsawb@unaffiliated/chainsawbike) |
| 01:42.00 | *** join/#maemo Anaphylaxis3 (~Anaphylax@x4d0c6440.dyn.telefonica.de) |
| 01:42.49 | *** join/#maemo paraxial23 (~paraxial@190-37-139-130.dyn.dsl.cantv.net) |
| 01:44.24 | *** join/#maemo FalconSpy (falconspy@unaffiliated/falconspy) |
| 01:50.21 | *** join/#maemo sarka6 (~sarka@1.215.58.243) |
| 01:56.50 | *** join/#maemo Orez27 (~Orez@218.151.20.212) |
| 02:04.41 | *** join/#maemo lucyoa (~lucyoa@2a01cb00867252002d4f54f9049c9762.ipv6.abo.wanadoo.fr) |
| 02:28.20 | *** join/#maemo newuser__ (drrty@gateway/vpn/privateinternetaccess/drrty) |
| 03:15.10 | *** join/#maemo tm (~sinnlos@unaffiliated/tm) |
| 03:32.00 | *** join/#maemo phlixi (~phlixi@ppp-62-216-213-94.dynamic.mnet-online.de) |
| 03:46.56 | *** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 04:02.03 | *** join/#maemo Kilroo (~Kilroo@98.27.17.253) |
| 04:15.56 | *** join/#maemo spiiroin (~spiiroin@82-203-175-168.bb.dnainternet.fi) |
| 04:16.00 | *** join/#maemo Quick_Wango9 (~Quick_Wan@KD111087214050.ppp.dion.ne.jp) |
| 04:31.33 | *** join/#maemo Juesto (~AndC@186.143.135.242) |
| 04:31.33 | *** join/#maemo Juesto (~AndC@unaffiliated/juest) |
| 04:38.20 | *** join/#maemo ravelo (uid244116@neo900/community/supporter/ravelo) |
| 05:11.40 | *** join/#maemo spiiroin (~spiiroin@2001:998:2a:deaf:28d4:ae52:2777:a997) |
| 05:40.19 | *** join/#maemo Fairy17 (~Fairy@178.253.58.5) |
| 05:58.51 | *** join/#maemo shentey (~shentey@x55b458c4.dyn.telefonica.de) |
| 06:00.30 | *** join/#maemo QueenElsa (~QueenElsa@FL1-133-202-206-244.ngn.mesh.ad.jp) |
| 06:03.37 | *** join/#maemo movsb (~movsb@i60-36-226-37.s42.a034.ap.plala.or.jp) |
| 06:06.13 | *** join/#maemo frankie22 (~frankie@cpc99310-croy26-2-0-cust4.19-2.cable.virginm.net) |
| 06:06.52 | *** join/#maemo dafox (~dafox@188.206.98.192) |
| 06:13.51 | *** join/#maemo heroux_ (sandroco@gateway/shell/insomnia247/x-dmehemwfbdgjilar) |
| 07:02.00 | *** join/#maemo skaji28 (~skaji@c-71-227-135-234.hsd1.wa.comcast.net) |
| 07:14.44 | *** join/#maemo brolin_empey (~brolin@brolin.be) |
| 07:20.23 | *** join/#maemo Kabouik_ (~kabouik@158.38.1.70) |
| 07:27.10 | *** join/#maemo jurop (~Jurop@151.62.243.185) |
| 07:28.07 | *** join/#maemo jupart11 (~jupart@211.214.73.52) |
| 07:35.01 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 07:39.10 | *** join/#maemo geaaru (~geaaru@host170-152-static.43-88-b.business.telecomitalia.it) |
| 07:41.07 | *** join/#maemo Kabouik_ (~kabouik@37.168.220.141) |
| 07:49.43 | DocScrutinizer05 | IroN900:~# cat /sys/devices/platform/musb_hdrc/charger |
| 07:49.44 | DocScrutinizer05 | 1 |
| 07:50.10 | KotCzarny | he needs to differentiate between charger and charging via computer |
| 07:50.19 | DocScrutinizer05 | ^^^ |
| 07:52.44 | *** join/#maemo Rivkin (~Rivkin@p1383095-ipngn8601sapodori.hokkaido.ocn.ne.jp) |
| 07:53.46 | DocScrutinizer05 | /sys/devices/platform/musb_hdrc/charger == 1 : D+/- short |
| 07:54.25 | DocScrutinizer05 | when you connect a charger that doesn't short D+ and D-, your device won't charge. So... exactly what you asked for |
| 07:56.19 | *** join/#maemo Konsieur (~kabouik@158.38.1.70) |
| 07:58.53 | DocScrutinizer05 | and reading the full backlog, this is actually _not_ what sunshavi is interested in. They want to know if device is connected to a PC USB data connection |
| 07:59.28 | DocScrutinizer05 | and I think the approach is pretty random |
| 08:05.31 | DocScrutinizer05 | sunshavi's question seems to be "can I send a signal from N900 to PC?" and to answer this we need to know which is the exact transport mechanism for the signal. USB networking with ssh? USB node polling? usb-tty? |
| 08:07.27 | DocScrutinizer05 | original question: >>[2018-09-26 16:01:53] <sunshavi> Hi guys. is there a way of knowing if pc suite mode is active?<< Yes there is, but I don't know for sure right now how to check. Possibly lsmod |
| 08:07.58 | DocScrutinizer05 | ask pali |
| 08:08.45 | *** join/#maemo derlafff12 (~derlafff@CBL217-132-123-222.bb.netvision.net.il) |
| 08:11.29 | Maxdamantus | Maybe by seeing if g_nokia appears in /proc/modules, as opposed to g_file_storage? Dunno if that's an accurate determiner though; I always use either g_file_storage or g_ether. |
| 08:12.44 | Maxdamantus | managed to disable that "PC suite" dialogue because it would annoyingly unlock the screen when plugging a USB cord in. |
| 08:12.53 | DocScrutinizer05 | IroN900:~# cat /sys/devices/platform/musb_hdrc/mode |
| 08:12.54 | DocScrutinizer05 | b_peripheral |
| 08:12.56 | DocScrutinizer05 | PC-Suite Mode |
| 08:13.33 | DocScrutinizer05 | b_idle == unplugged |
| 08:13.50 | DocScrutinizer05 | HTH |
| 08:14.48 | DocScrutinizer05 | UNDEFINED == mass storage mode |
| 08:15.13 | DocScrutinizer05 | until mounted, then b_peripheral |
| 08:22.12 | *** join/#maemo jurop (~Jurop@151.62.243.185) |
| 08:22.27 | *** part/#maemo jurop (~Jurop@151.62.243.185) |
| 08:25.07 | DocScrutinizer05 | anyway note that [[ "b_peripheral" == `cat /sys/devices/platform/musb_hdrc/mode ` ]] still doesn't assert there's for example a working established network to run a ssh connection to the PC |
| 08:26.24 | DocScrutinizer05 | you know it failed when "ssh $PC mynotifycmd" returns with error |
| 08:27.19 | DocScrutinizer05 | >>... and to answer this we need to know which is the exact transport mechanism for the signal.<< |
| 08:30.41 | DocScrutinizer05 | KotCzarny: sunshavi: ^^^ |
| 08:31.50 | DocScrutinizer05 | >><sunshavi> Wizzup: I have the notification script done<< mind to share via pastebin? |
| 08:38.12 | *** join/#maemo koenig17 (~koenig@76.72.69.195) |
| 08:45.25 | *** join/#maemo Sigyn (sigyn@freenode/utility-bot/sigyn) |
| 08:45.25 | *** mode/#maemo [+o Sigyn] by ChanServ |
| 08:45.47 | *** join/#maemo Sigyn (sigyn@freenode/utility-bot/sigyn) |
| 08:45.47 | *** mode/#maemo [+o Sigyn] by ChanServ |
| 08:48.34 | *** join/#maemo Sigyn (sigyn@freenode/utility-bot/sigyn) |
| 08:56.41 | *** join/#maemo Sigyn (sigyn@freenode/utility-bot/sigyn) |
| 08:56.41 | *** mode/#maemo [+o Sigyn] by ChanServ |
| 08:59.39 | *** join/#maemo fbsd (~fbsd@ppp-124-121-253-11.revip2.asianet.co.th) |
| 09:00.29 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 09:14.10 | *** join/#maemo tkd12 (~tkd@190-38-51-47.dyn.dsl.cantv.net) |
| 09:34.48 | *** join/#maemo ravagetalon (~ravagetal@p120.net219126060.tokai.or.jp) |
| 09:36.28 | *** join/#maemo VLetrmx4 (~VLetrmx@218.239.89.48) |
| 09:48.49 | *** join/#maemo marnej26 (~marnej@41.232.218.115) |
| 10:02.02 | *** join/#maemo Eatsoup_ (~Eatsoup_@2.218.57.79) |
| 10:05.31 | *** join/#maemo c-dog (~joe@2a00:23c5:41a6:1200::2d6) |
| 10:12.41 | *** join/#maemo cyteen (~cyteen@cyteen42.plus.com) |
| 10:15.05 | *** join/#maemo eMHa (~mh@81.26.162.98) |
| 10:21.09 | *** join/#maemo lionel22 (~lionel@175.214.251.71) |
| 10:26.00 | *** join/#maemo swidi27 (~swidi@31.206.182.249) |
| 10:52.09 | *** join/#maemo lizzie13 (~lizzie@156.219.100.70) |
| 10:53.50 | *** join/#maemo Guest20815 (~stevecam@201-213-76-89.net.prima.net.ar) |
| 10:55.36 | *** join/#maemo kuzetsa14 (~kuzetsa@121.151.51.110) |
| 10:56.46 | *** join/#maemo kimmyk13 (~kimmyk@121.154.162.3) |
| 11:00.33 | *** join/#maemo edge56310 (~edge563@85.99.121.207) |
| 11:10.18 | Vajb | I've noticed that when I charge my n900 and wall charger flag is set absent it means that n900 thinks that it is connected to pc. |
| 11:22.25 | Wizzup | DocScrutinizer05: afaik the /mode in musb_hdrc doesn't help distinguish between wall plug and pc |
| 11:22.37 | Wizzup | DocScrutinizer05: it can also be idle when no gadget it loaded, for example |
| 11:23.09 | DocScrutinizer05 | mode is D+- short |
| 11:23.21 | DocScrutinizer05 | oops sorry nope |
| 11:23.39 | DocScrutinizer05 | mode is what the MUSB state machine is in |
| 11:23.55 | KotCzarny | which might be totally random sometimes |
| 11:23.59 | DocScrutinizer05 | yes |
| 11:24.28 | DocScrutinizer05 | don't tell the father of H.E.N ;-D |
| 11:24.50 | DocScrutinizer05 | feels that headache again |
| 11:25.35 | DocScrutinizer05 | ~hen |
| 11:25.35 | infobot | well, hen is hostmode-easy-now, or http://talk.maemo.org/showthread.php?t=65232, or see ~hostmode |
| 11:25.53 | DocScrutinizer05 | ~hostmode |
| 11:25.53 | infobot | hmm... hostmode is http://talk.maemo.org/showthread.php?p=652330, or http://www.youtube.com/watch?v=fkCDyUO0sKQ, or see ~hostmode-powered |
| 11:28.40 | sunshavi | DocScrutinizer05: good morning at least for me. the mechanism is this one |
| 11:30.41 | sunshavi | when sms or phone call arrives a python scripts sends a file by bluetooth push notification to workstation. and workstation shown the notification (there a process reading when a new file arrives to a folder). that was in case phone is lost for not having and ssh-key on my workstation (just in case) |
| 11:31.46 | DocScrutinizer05 | Vajb: you mean you connect device to a charger without D+- short (cat /sys/devices/platform/musb_hdrc/charger ->0 )? Yes, that is the same situation like immediately after plugging device to a PC host, before ENUM |
| 11:32.38 | DocScrutinizer05 | afaik device will constantly try to communicate to host to run ENUM |
| 11:33.00 | DocScrutinizer05 | no charging will be done |
| 11:33.13 | sunshavi | this is the script on n900 http://termbin.com/544z |
| 11:33.13 | sunshavi | <PROTECTED> |
| 11:33.15 | *** join/#maemo FalconSpy25 (~FalconSpy@p4094-ipngn100108osakakita.osaka.ocn.ne.jp) |
| 11:33.59 | Wizzup | https://github.com/maemo-leste/hildon-status-bar-usb/blob/master/udev-helper.c#L152 |
| 11:34.01 | DocScrutinizer05 | sunshavi: mhm, so how is this related to USB? |
| 11:34.37 | sunshavi | the problem happens when i disconnect|unplug the device from my workstation |
| 11:35.49 | sunshavi | no usb host (workstation). then no no bluetooth host 4 receiving the file |
| 11:36.59 | *** join/#maemo mirrorbox (~mirrorbox@190.39.126.74) |
| 11:37.25 | DocScrutinizer05 | ??? |
| 11:39.05 | sunshavi | if not host an errors happens within the python script and I would need to restart the process. so process should just do his work when connected to my workstation. All of the if on the python script is for avoiding the error |
| 11:39.40 | sunshavi | brb. time for doing some duties here |
| 11:49.06 | Vajb | DocScrutinizer05: maybe. Bnf shows wall charger as absent. It will charge but keeps charge under 500mah. This happanes randomly when i plug charger in |
| 11:51.19 | *** join/#maemo heroux (sandroco@gateway/shell/insomnia247/x-qrzmnbpsxnyvqsls) |
| 11:51.21 | *** join/#maemo heroux_ (sandroco@gateway/shell/insomnia247/x-pywdbnvyatvrnhle) |
| 12:04.05 | *** join/#maemo Batholith27 (~Batholith@134.196.140.113) |
| 12:05.31 | *** join/#maemo heroux (sandroco@gateway/shell/insomnia247/x-nizhvdolaszzsaiu) |
| 12:05.35 | *** join/#maemo heroux_ (sandroco@gateway/shell/insomnia247/x-isbdxqqykqxdsixy) |
| 12:05.50 | DocScrutinizer05 | bnf? |
| 12:06.26 | DocScrutinizer05 | I seem to recall this is an app that dhows some system diagnostics, right? No idea what it does in detail |
| 12:08.04 | DocScrutinizer05 | sunshavi: >>if not host an errors happens within the python script and I would need to restart the process<< no, I think you should catch the error within the script and handle it |
| 12:09.16 | Vajb | it shows battery info and charging state, remaining time etc |
| 12:10.33 | Vajb | what it does is it pulls info from system battery related file (can't recall the name) and just shows them with info what they are |
| 12:11.02 | sunshavi | DocScrutinizer05: there is an assert line there (watch the source code) |
| 12:11.52 | sunshavi | the error happens on that line (assert pipe.returncode == 0 and not errout) |
| 12:12.42 | sunshavi | because i am debugging the script. I am still tuning it. But it works. I just need to catch some corner cases |
| 12:12.53 | Vajb | as I said my device randomly pops out the dialog asking wether I want it to massmedia or usb state and if I don't reset the state with usb-host-mode it will charge only slow and wall charger absent flag stays on. |
| 12:13.08 | Vajb | other way to reset this is reboot obviously. |
| 12:17.28 | DocScrutinizer05 | Vajb: no idea what you're doing. Yes there is a race condition introducing randomness into charger detection, but I never seen a deadlock from that. |
| 12:19.39 | DocScrutinizer05 | sunshavi: I completely fail to understand the concept of what you're doing. USB has nothing to do with bluetooth. You don't need to test any arbitrary USB state to find out whether or not a BT transaction succeeds or not |
| 12:23.34 | DocScrutinizer05 | AIUI you want to avoid running the BT command under certain conditions (no PC in vicinity) since >>an errors happens within the python script and I would need to restart the process<< I think you need to catch the error so it does NOT abort the python script and rather tells you that no PC in vicinity |
| 12:25.13 | *** join/#maemo Guest74955 (~Guest7495@p54BCF9DE.dip0.t-ipconnect.de) |
| 12:26.15 | sunshavi | docscrutinizer05: how should i know if device if plugged to my workstation, and ton to the usb-wall-charger? |
| 12:26.26 | sunshavi | s/ton/not/ |
| 12:26.36 | DocScrutinizer05 | why do you want to know that? |
| 12:27.02 | DocScrutinizer05 | how is that even relevant? |
| 12:27.28 | sunshavi | when dev is connected to different machine probably that machine that is not my workstation does not have a bluetooth device |
| 12:27.59 | sunshavi | on n900 there is no l2ping utility. that could solve the issue too |
| 12:28.09 | DocScrutinizer05 | hm? |
| 12:28.42 | sunshavi | l2ping is for checking with a device with an specific mac-address in on reach |
| 12:28.51 | sunshavi | s/with/when/ |
| 12:29.01 | DocScrutinizer05 | why do you need USB? |
| 12:30.32 | sunshavi | for testing n900 is plugged on my workstation (1. check usb-connection; 2. see if my workstation-usb0 has the hardcoded ip needed) |
| 12:30.50 | DocScrutinizer05 | WHY??? |
| 12:31.09 | sunshavi | when you send a file by bluetooth you need to give the device-bluetooth-address |
| 12:31.23 | sunshavi | as a parameter |
| 12:31.24 | DocScrutinizer05 | how's that related to USB? |
| 12:32.02 | sunshavi | the problem is: "how could be identified my machine from other machines?" |
| 12:32.18 | DocScrutinizer05 | err, doesn'tBT do that for you? |
| 12:32.38 | *** join/#maemo ladders13 (~ladders@92.255.160.30) |
| 12:32.41 | sunshavi | i am using for that a mechanism that involves usb+ip |
| 12:32.47 | DocScrutinizer05 | I always thought that's what BT pairing is meant for |
| 12:33.27 | DocScrutinizer05 | whatever that "mechanism", I don't understand it and think it's nonsense |
| 12:33.45 | *** join/#maemo eMHa (~mh@81.26.162.98) |
| 12:34.16 | sunshavi | n900 is paired with several other devices |
| 12:35.57 | DocScrutinizer05 | this is a classical yet very massive and wird instance of an XY problem |
| 12:36.03 | DocScrutinizer05 | weird* |
| 12:38.22 | DocScrutinizer05 | aiui you do a ping to USB-networked PC host. You as well could do a `ssh notifyuser@PC notify` |
| 12:39.04 | DocScrutinizer05 | or you forget about all USB and send your BT data to the right device and catch any "transmission failed" |
| 12:39.07 | sunshavi | yes that could do the work too but a little insecure. bt is safer |
| 12:39.21 | DocScrutinizer05 | no |
| 12:39.32 | DocScrutinizer05 | this is NOT insecure at all |
| 12:40.42 | DocScrutinizer05 | anyway either BT or USB could do the whole task, you don't need both concurrently |
| 12:40.57 | DocScrutinizer05 | actually THIS is sort of insecure |
| 12:40.59 | sunshavi | i am almost there with my approach. One of your first lines is going to be helpful with the issue. I am going to code that tonight |
| 12:41.35 | *** join/#maemo SET1 (~SET@dynamic-vpdn-93-125-63-118.telecom.by) |
| 12:41.49 | DocScrutinizer05 | good luck! I'm not going to help implement a flawed broken-by-design "solution" |
| 12:43.14 | DocScrutinizer05 | USB doesn't provide *any* info about what you can expect to find on BT |
| 12:48.29 | DocScrutinizer05 | why do you think BT is more secure than ssh? |
| 12:55.11 | DocScrutinizer05 | actually uploading arbitrary files to your PC via BT sounds damn dangerous, particularly compared to a ssh login that allows only one particular command to execute (add the allowed command to user "notifyuser"'s ~notifyuser/.ssh/authorized_keys line) and needs a proper keypair to do so |
| 12:58.22 | *** join/#maemo spiiroin (~spiiroin@82-203-175-168.bb.dnainternet.fi) |
| 12:59.42 | DocScrutinizer05 | both BT and ssh are virtually equally uncrackable, and when you lose the N900, then the ssh solution only enables the attacker to trigger a notification on your PC while the disclosed BT pairing key allows attacker to upload arbitrary files aiui - something you definitely want to avoid by all means since such arbitrary file might be a virus or whatever and take over your complete PC |
| 13:00.17 | *** join/#maemo dkg2 (~dkg@93.171.29.124) |
| 13:02.29 | DocScrutinizer05 | even worse, BT allows to do so wireless over the air while the already uncritical exploit of unsolicited SMS notification could only happen when the attacker has physical connection to your PC USB jack (or otherwise log in to your PC), to establish a network and open a ssh session |
| 13:08.28 | DocScrutinizer05 | s/ unsolicited / bogus forged / |
| 13:09.53 | *** join/#maemo eMHa (~mh@81.26.162.98) |
| 13:11.56 | *** join/#maemo eMHa_ (~mh@81.26.162.98) |
| 13:24.50 | DocScrutinizer05 | sunshavi: man sshd|less -j26 +'/command="uptime"' |
| 13:27.17 | DocScrutinizer05 | for your purposes a command="cat >/tmp/notificationtext && popup_notification" prolly will already do the whole trick |
| 13:31.58 | DocScrutinizer05 | or, for added safety (flood protection): instead of `cat >` use `dd bs=1 count=$INT_MAXCHARS of=` |
| 13:35.30 | DocScrutinizer05 | now, on N900, do `cat SMScontent.txt|ssh notifyuser@neo900` and up pops th notification on your PC. Absolutely no risk except a n900 thief could make offensive notifications pop up on your PC |
| 13:36.24 | DocScrutinizer05 | IF they had access to ssh-login to your PC (unlike BT where they need to be nearby, within RF range, only) |
| 13:38.20 | *** join/#maemo Simonious3 (~Simonious@121.186.198.239) |
| 13:40.31 | DocScrutinizer05 | I for one never use USB for networking, WLAN is so much more convenient |
| 13:52.18 | *** join/#maemo c4757p20 (~c4757p@122.43.54.182) |
| 13:58.54 | *** join/#maemo jurop (~Jurop@151.62.243.185) |
| 14:00.13 | *** part/#maemo jurop (~Jurop@151.62.243.185) |
| 14:02.39 | *** join/#maemo darkSeid (~darkSeid@34.241.218.133.dy.bbexcite.jp) |
| 14:04.54 | DocScrutinizer05 | actually you better bundle all the "dd bs=1 count=$INT_MAXCHARS of=/tmp/notificationtext && popup_notification" into a bash script mynotify.sh and only hava a command="mynotify.sh" in authorized_keys |
| 14:06.07 | DocScrutinizer05 | if you want to implement this, don't hesitate to ask about details |
| 14:08.09 | DocScrutinizer05 | actually not even a dedicated new user "notifyuser" is needed, you can run this under your default user account |
| 14:09.14 | DocScrutinizer05 | all you need is a dedicated pk-pair for this, with pubkey on N900 and privkey on your PC |
| 14:32.01 | sunshavi | docscrutinizer05: on the contrary i almost never wlan on n900. Just usb and also bluetooth when needed. Also for consideration both of my n900 have a broken screen. so I access desktop by vnc over usb|bt |
| 14:33.54 | sunshavi | and fyi my pc priv key is on n900 |
| 14:35.49 | sunshavi | so from home i could access and modify the complete phone from any network connection. |
| 14:36.00 | sunshavi | docscrutinizer05: thanks for your help |
| 14:44.22 | *** join/#maemo VladimirGl7 (~VladimirG@79.103.68.102.dsl.dyn.forthnet.gr) |
| 14:49.25 | *** join/#maemo Janusz5 (~Janusz@198.45.117.145) |
| 14:57.54 | DocScrutinizer05 | >>and fyi my pc priv key is on n900<< irrelevant for this situation |
| 14:59.50 | DocScrutinizer05 | err wait. No. This is what already exactly you need. If you had not swapped the meaning of privkey and pubkey. The provjkey is on the originating side, the pubkey on the "server" you log in to |
| 15:00.20 | DocScrutinizer05 | when you log in to N900 from your PC then the privkey is on PC |
| 15:02.48 | DocScrutinizer05 | for the solution I sketched above, you need a dedicated key pair exclusively for this solution, you place the pubkey on PC so the N900 can log in to PC using the privkey on N900, and you modify the pubkey on PC so it only works for exactly one command: mynotify.sh |
| 15:03.05 | sunshavi | my pc can read my phone or exec any ssh cmd on the phone. phone needs pwd when accesing pc |
| 15:03.17 | DocScrutinizer05 | ^^^ |
| 15:04.55 | DocScrutinizer05 | yes, you generally don't want password-less access from mobile devices to your PC, since you could lose the mobile device |
| 15:04.57 | sunshavi | yes a dedicated key pair could be the answer |
| 15:05.26 | DocScrutinizer05 | in this case however the pubkey gets modified so it works for exactly ONE command only |
| 15:05.50 | DocScrutinizer05 | and doesn't need password for executing this one command |
| 15:06.21 | sunshavi | for giving you the complete picture. i do the phone calls from my desktop-contacts app |
| 15:06.41 | sunshavi | also i send sms's from my desktop-contacts app |
| 15:06.46 | DocScrutinizer05 | you can install this keypair on top of whatever is already there, since you can have multipkle authorized_keys lines |
| 15:08.47 | *** join/#maemo bbielsa_ (~bbielsa_@112.158.228.189) |
| 15:10.32 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 15:39.33 | *** join/#maemo JohnDoe215 (~JohnDoe2@cm-119-76-19-87.revip17.asianet.co.th) |
| 15:52.31 | *** join/#maemo Kabouik_ (~kabouik@176.67.168.147) |
| 15:59.51 | *** join/#maemo wrenny_b (~wrenny_b@p4FFAD46B.dip0.t-ipconnect.de) |
| 16:15.29 | *** join/#maemo devlaf0 (~devlaf@demux0-1073801203.SMFL-04-BRAS2.miranda-media.net) |
| 16:22.55 | *** join/#maemo drrty (drrty@gateway/vpn/privateinternetaccess/drrty) |
| 16:26.49 | *** join/#maemo tris9 (~tris@2.93.22.25) |
| 16:38.35 | *** part/#maemo c-dog (~joe@2a00:23c5:41a6:1200::2d6) |
| 16:52.33 | *** join/#maemo klaxa26 (~klaxa@189.115.39.153) |
| 17:01.37 | *** join/#maemo ua (~ua@220.116.52.178) |
| 17:06.50 | *** join/#maemo xymantec (~xymantec@201.33.248.86) |
| 17:19.01 | *** join/#maemo shrifbot (~shrifbot@175.205.171.93) |
| 17:22.50 | *** join/#maemo matti__ (~matti__@per63-1-88-184-103-96.fbx.proxad.net) |
| 17:25.50 | *** join/#maemo ravelo (uid244116@neo900/community/supporter/ravelo) |
| 17:25.58 | *** join/#maemo go|dfish14 (~go|dfish@pppoe-213-80-217-151-dyn-srv.volgaline.ru) |
| 17:41.39 | *** join/#maemo shentey (~shentey@x2f34731.dyn.telefonica.de) |
| 17:47.43 | *** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 18:14.36 | *** join/#maemo Nevolution217 (~Nevolutio@190.172.150.63) |
| 18:23.14 | *** join/#maemo sadmac9 (~sadmac@c80-217-219-131.bredband.comhem.se) |
| 18:31.59 | *** join/#maemo Apocalyptic6 (~Apocalypt@cpc116302-telf13-2-0-cust629.16-1.cable.virginm.net) |
| 18:34.18 | *** join/#maemo ozfalcon (~ozfalcon@181-162-29-26.baf.movistar.cl) |
| 18:41.51 | *** join/#maemo shentey (~shentey@x2f34731.dyn.telefonica.de) |
| 18:42.19 | *** join/#maemo eMHa_ (~mh@p5089DF5B.dip0.t-ipconnect.de) |
| 18:56.43 | *** join/#maemo Elronnd29 (~Elronnd@5-12-38-74.residential.rdsnet.ro) |
| 19:40.18 | *** join/#maemo stryngs (~stryngs@unaffiliated/stryngs) |
| 20:04.25 | *** join/#maemo thc20210 (~thc202@ngn2-ppp1771.saitama.sannet.ne.jp) |
| 20:11.24 | DocScrutinizer05 | Computrace.LoJack->LoJax :-o |
| 20:23.08 | *** join/#maemo lathiat_ (~lathiat_@cpe-74-130-10-119.kya.res.rr.com) |
| 20:34.20 | *** join/#maemo xqb13 (~xqb@cm-171-100-125-87.revip10.asianet.co.th) |
| 20:36.53 | *** join/#maemo angel_killah9 (~angel_kil@105.107.143.102) |
| 20:41.11 | *** join/#maemo analogical17 (~analogica@68.red-88-11-104.dynamicip.rima-tde.net) |
| 20:44.35 | *** join/#maemo tacegory15 (~tacegory@cpc85990-scun10-2-0-cust1870.12-3.cable.virginm.net) |
| 20:49.45 | *** join/#maemo dafox (~dafox@188.206.98.130) |
| 20:56.26 | *** join/#maemo ackjewt0 (~ackjewt@187.65.234.107) |
| 21:09.50 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 21:12.19 | *** join/#maemo c-dog (~joe@2a00:23c5:41a6:1200::2d6) |
| 21:19.47 | *** join/#maemo protodave_3 (~protodave@179.254.158.231) |
| 21:45.40 | *** join/#maemo DougNYC1 (~DougNYC@167.249.33.248) |
| 22:00.32 | *** join/#maemo arsenerei (~arsenerei@pc-51-60-83-200.cm.vtr.net) |
| 22:07.54 | *** join/#maemo xkonni12 (~xkonni@213.177.21.170) |
| 22:15.05 | *** join/#maemo unsound8 (~unsound@64.130.120.139) |
| 22:29.33 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 22:42.22 | *** join/#maemo bt_dstw (~bt_dstw@187.154.92.219) |
| 22:48.50 | *** join/#maemo Raito_Bezarius3 (~Raito_Bez@149.0.161.33) |
| 22:55.38 | *** join/#maemo Praise19 (~Praise@112.184.151.150) |
| 23:08.51 | *** join/#maemo Poster23 (~Poster@host-89-230-80-19.dynamic.mm.pl) |
| 23:08.59 | *** join/#maemo kaustubhw (~kaustubhw@190-38-70-140.dyn.dsl.cantv.net) |
| 23:09.06 | *** join/#maemo zama (~zama@unaffiliated/stryx/x-3871776) |
| 23:19.37 | *** join/#maemo zoglesby29 (~zoglesby@50-27-144-160.abilcmtk02.res.dyn.suddenlink.net) |
| 23:20.56 | *** join/#maemo jimmyjimjim (~jimmyjimj@y241110.dynamic.ppp.asahi-net.or.jp) |
| 23:26.42 | *** join/#maemo Kilroo (~Kilroo@98.27.17.253) |
| 23:30.20 | *** join/#maemo DrMax3 (~DrMax@219.85.3.89) |
| 23:37.06 | *** join/#maemo sunshavi (~user@190.239.244.220) |
| 23:56.55 | *** join/#maemo mac_nibblet9 (~mac_nibbl@156.221.178.95) |