[Announce] SMScon (control your device with SMS) - Page 22 - maemo.org

Active Topics

The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 5 hrs, 53 mins ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 18 hrs ago
more...

Page 22 of 130

Thread Tools

	Saturn	2010-09-18 , 23:18
	Posts: 1,648 \| Thanked: 2,122 times \| Joined on Mar 2007 @ UNKLE's Never Never Land	#211

Originally Posted by WhiteWolf

/etc/sudoers.d/smscon.sudoers
/etc/event.d/smscon_boot
...

Could you sent/post the output files of these commands:

Code:

dpkg -l python* > /home/user/MyDocs/output1.txt
apt-get -s upgrade >  /home/user/MyDocs/output2.txt

might be a dependency problem or similar.

Quote & Reply |

	mrbiggzz79	2010-09-18 , 23:32
	Posts: 67 \| Thanked: 7 times \| Joined on Mar 2010 @ Bahamas	#212

Which email will work ?

__________________
In The Bahamas

Quote & Reply |

SaintGermain	2010-09-19 , 00:34
Posts: 35 \| Thanked: 20 times \| Joined on Dec 2009	#213

Originally Posted by Pigro

this is more a question for the guy enquiring whether it could use pub key than it is for you as the app developer - i just don't see why he'd need YOU to support pub key, as I think it will already be inherently supported by ssh itself as long as you config your phone & home ssh servers correctly? ... but I may have misunderstood (are you maybe calling ssh via a software library rather than as a straight shell coomand? If so, I guess that may allow you to force p/w auth only?)

Using public key authentication requires to provide a passphrase to read the identify key. Using 'normal' authentication requires to provide the log account password.
I just assume that the interface for password/passphrase is different.

I have tried to set up a pub key with no 'passphrase' and gives an empty 'password' in smscon_config but it failed as well.

Quote & Reply |

nesrazz	2010-09-19 , 03:37
Posts: 120 \| Thanked: 13 times \| Joined on May 2010 @ turkey	#214

please help. I get the following error

Quote & Reply |

digitalvoid	2010-09-19 , 06:37
Posts: 200 \| Thanked: 300 times \| Joined on Nov 2009 @ The Netherlands	#215

@ pigro & SaintGermain:

SMSCON uses the straight shell command interface for connecting with ssh.

Python ssh part in SMSCON:

Code:

(Output, ExitStatus) = pexpect.run( 'ssh -n -N -T -f -p %s -R %s:%s:%s %s@%s &' % (REMOTEPORT, LocalPort, LocalHost, REMOTEPORT, REMOTEUSER, REMOTEHOST), events = { '(?i)password':REMOTEPASSWORD + '\n', '(?i)(yes/no) ?':'yes' + '\n' }, withexitstatus = True )

SSH is started in background (in red) and when SSH ask for password it's automatically entered (green) and the connection has started if 'ExitStatus' returns 0). It's very basic done, I know, but It works.

If somebody has better code to implement in SMSCON please share it.

Quote & Reply |

digitalvoid	2010-09-19 , 07:02
Posts: 200 \| Thanked: 300 times \| Joined on Nov 2009 @ The Netherlands	#216

Originally Posted by zimon

If you want to improve SMScon, a few feature requests:

1) settable (GUI) password to all SMS commands. Can be, and is initially empty.

I know, as previously discussed, one can now change all commands and for example put "mypassword_" prefix to every command, but when if SMS commands are added in the future, it would be nice just to be able to change this password in one field and not in every N fields.

2) SirenOn and SirenOff SMS commands. When got, the phone will set volume to the max and play preconfigured audio file over and over. Optionally could have a parameter which would set the audio volume 1 - 10.

3) All SMS commands which give reply to email/phone-number/*, could have an optional parameter where the result is to be sent.
For example:
<password> Location mynewemail@foo.bar.invalid
<password> Location +3101234567
This can be usefull for example if you are abroad and your phone is stolen. You may not be able to get into your emai account, neither the phone number in the settings is useful for some reason. If you buy a prepaid SIM-card and a cheap phone, or lend one, you can control your stolen phone immediately.

The different type of parameters can be easily recognized by their syntax: "starting with +" means phone number, having "*@*" means email address, having "*@*:*" means username+host+portnumber.

For these parameters the feature request 1), the settable password, is a MUST, for obvious reasons. Initially when SMScon is installed and password is not set, feature 3) should be disabled.

Other example of having a parameter:
<password> RemoteOn newuser@some.host.invalid:2222
<password> TrackOn mynewemail@foo.bar.invalid

Later, if those would be implemented, also SMTP-server, a port number and a password could follow the email-type-parameter.
<password> TrackOn mynewemail@foo.bar.invalid smtp.netcafe.invalid 25 passwordForNetcafeSMTP

Also why not having ...
<password> netuser/password@some.host.invalid:2222
...type of parameters for RemoteOn, so the password is there also.

Without parameters in the SMS message SMScon would work as it now works, according the settings in the init-file.

1) I think the password prefix idea is not necessary, because you can change all SMS commands to something cryptical *you* only know what it means & you don't obviously tell anybody. Also this password will be shown on Nokia screen when received (if phone is unlocked & Notification popup message is enabled).

(in future version of SMSCON with the COM_CHECK command you can recieve a SMS with all the available commands, if you have forgotten them.)

2) Can be done, I hold it under consideration.

3) I like this idea and will implement this in future version. It will work then with and without extra parameters.