Difference between revisions of "Hacks and Tweaks"

From piMyHome Project
Jump to navigation Jump to search
(Start known flaws section - root w/o password issue.)
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
== F454 ==
 
== F454 ==
 +
 +
The following sections just list various bits and pieces of information - without any specific order - regarding the bticino [http://www.homesystems-legrandgroup.com/BtHomeSystems/productDetail.action?productId=006 F454]. Of course there is always the possibility that the given information also applies to other bticino components.
  
 
=== Known flaws ===
 
=== Known flaws ===
Line 8: Line 10:
 
This issue has been reported to bticino via it's community forum [http://www.myopen-legrandgroup.com/ MY HOME] on 2013/12/17 23:23 (see [http://www.myopen-legrandgroup.com/community/international_my_open/international_65560/f/134/t/8589.aspx forum post]). However, there hasn't been any reaction from any bticino/legrand representative yet.
 
This issue has been reported to bticino via it's community forum [http://www.myopen-legrandgroup.com/ MY HOME] on 2013/12/17 23:23 (see [http://www.myopen-legrandgroup.com/community/international_my_open/international_65560/f/134/t/8589.aspx forum post]). However, there hasn't been any reaction from any bticino/legrand representative yet.
  
 +
----
 +
 +
=== FTP ===
 +
 +
All bticino gateway devices, not only the F454, use FTP for configuration up- and download. However the FTP server daemon is not running by default. It is ''started'' by configuration software, like TiF454, when doing a configuration up- or download - via a OWN WHO=13 command (DIMENSION WRITING, DIMENSION 31, VAL1 0):
 +
 +
<code>*#13**#31*0##</code>
 +
 +
Note that DIMENSION 34 also seems to have something to do with ''starting'' the FTP server daemon. However it remains unclear what and why.
 +
 +
It can also be ''stopped'' again (DIMENSION WRITING, DIMENSION 33, VAL1 0):
 +
 +
<code>*#13**#33*0##</code>
 +
 +
Note that it seems to be ''stopped'' automatically after about 10 minutes - after having opened and closed a FTP connection.
 +
 +
==== Known FTP Logins ====
 +
{| class="wikitable"
 +
! style="text-align:left;"| Device
 +
! style="text-align:left;"| User
 +
! style="text-align:left;"| Password
 +
|-
 +
||F453AV
 +
|openconf
 +
|7ws10din08xml
 +
|-
 +
|F454<br>&nbsp;
 +
|openupdate<br>cfguser
 +
|8recovery08zip<br>22K2mk7d
 +
|-
 +
|MH200N
 +
|openconf
 +
|9scheduler09xml
 +
|}
 
----
 
----
  
Line 21: Line 57:
  
 
''TODO for joft: Basically include README text here - or at least essential parts.''
 
''TODO for joft: Basically include README text here - or at least essential parts.''
 +
 +
----
 +
 +
=== SSH root Access via Puma ===
 +
There is a 2nd way to enable the dropbear SSH daemon on a F454.
 +
 +
*Download the [http://www.myopen-legrandgroup.com/devices/puma/m/mediagallery/default.aspx Puma Software] from bticino website. This is a tool for updating firmware, backup/restore configuration file etc. After downloaded Puma, unzip the file to a directory of your choice.
 +
 +
*Open a shell in Windows (Start, Run, cmd.exe) or a terminal in Linux and change to the directory you unzipped Puma.
 +
 +
* To "receive" the conf.zip of your F454 enter this command (please change IP address or OpenPassword accordingly):
 +
 +
Receive configuration from F454:
 +
<pre>puma cu "C:\Temp" -e 192.168.1.35 12345 -d F454</pre>
 +
 +
*Then unzip the file C:\Temp\conf.zip (Password is bticino).
 +
*Edit the unpacked file conf.xml and locate the section <tt>'''<servizi>'''</tt> and add there a new line with '''<code><abil_ssh>1</abil_ssh></code>'''. Your conf.xml should then look similar to this:
 +
 +
<pre>
 +
<servizi>
 +
<abil_portale>0</abil_portale>
 +
<abil_pagine_web>1</abil_pagine_web>
 +
<abil_segreteria>0</abil_segreteria>
 +
<abil_sdk>0</abil_sdk>
 +
<abil_http_streaming>1</abil_http_streaming>
 +
<abil_ssh>1</abil_ssh>
 +
</servizi>
 +
</pre>
 +
 +
*Then we have to "send" back the file to F454. Puma is taking care, that the file conf.xml will be zipped and encrypted accordingly, so we just have to send the plain xml file:
 +
 +
Send configuration to F454:
 +
<pre>puma cd "c:\Temp\conf.xml" -e 192.168.1.35 12345 -d F45</pre>
 +
 +
After Puma has finished you should already have root access to your F454. Just login as '''root''', no password(!) set. So just hit enter when you get asked for the root password.
 +
 +
<pre>ssh root@192.168.1.35</pre>

Latest revision as of 10:57, 27 November 2014

F454

The following sections just list various bits and pieces of information - without any specific order - regarding the bticino F454. Of course there is always the possibility that the given information also applies to other bticino components.

Known flaws

root w/o password

At least in firmware versions v1.00.34, v1.00.37 and v1.00.45 the user root of the Linux system running on a F454 does not have a password set - by default. To be precises: It is the blank password.

This issue has been reported to bticino via it's community forum MY HOME on 2013/12/17 23:23 (see forum post). However, there hasn't been any reaction from any bticino/legrand representative yet.

FTP

All bticino gateway devices, not only the F454, use FTP for configuration up- and download. However the FTP server daemon is not running by default. It is started by configuration software, like TiF454, when doing a configuration up- or download - via a OWN WHO=13 command (DIMENSION WRITING, DIMENSION 31, VAL1 0):

*#13**#31*0##

Note that DIMENSION 34 also seems to have something to do with starting the FTP server daemon. However it remains unclear what and why.

It can also be stopped again (DIMENSION WRITING, DIMENSION 33, VAL1 0):

*#13**#33*0##

Note that it seems to be stopped automatically after about 10 minutes - after having opened and closed a FTP connection.

Known FTP Logins

Device User Password
F453AV openconf 7ws10din08xml
F454
  		openupdate
cfguser 		8recovery08zip
22K2mk7d
MH200N openconf 9scheduler09xml

SSH

startssh is a "custom app" for the bticino F454. Its purpose is to start the SSH daemon "dropbear" at startup to allow SSH logins. dropbear is actually already part of the F454 firmware (known: v1.00.34, v1.00.37), but not started automatically for unknown reasons.

The source code can be downloaded here:

https://github.com/joft/f454utils

To get started please have a look at the README file.

TODO for joft: Basically include README text here - or at least essential parts.

SSH root Access via Puma

There is a 2nd way to enable the dropbear SSH daemon on a F454.

  • Download the Puma Software from bticino website. This is a tool for updating firmware, backup/restore configuration file etc. After downloaded Puma, unzip the file to a directory of your choice.
  • Open a shell in Windows (Start, Run, cmd.exe) or a terminal in Linux and change to the directory you unzipped Puma.
  • To "receive" the conf.zip of your F454 enter this command (please change IP address or OpenPassword accordingly):

Receive configuration from F454: 

puma cu "C:\Temp" -e 192.168.1.35 12345 -d F454
  • Then unzip the file C:\Temp\conf.zip (Password is bticino).
  • Edit the unpacked file conf.xml and locate the section <servizi> and add there a new line with <abil_ssh>1</abil_ssh>. Your conf.xml should then look similar to this:
<servizi>
	<abil_portale>0</abil_portale>
	<abil_pagine_web>1</abil_pagine_web>
	<abil_segreteria>0</abil_segreteria>
	<abil_sdk>0</abil_sdk>
	<abil_http_streaming>1</abil_http_streaming>
	<abil_ssh>1</abil_ssh>
</servizi>
  • Then we have to "send" back the file to F454. Puma is taking care, that the file conf.xml will be zipped and encrypted accordingly, so we just have to send the plain xml file:

Send configuration to F454: 

puma cd "c:\Temp\conf.xml" -e 192.168.1.35 12345 -d F45

After Puma has finished you should already have root access to your F454. Just login as root, no password(!) set. So just hit enter when you get asked for the root password. 

ssh root@192.168.1.35
Retrieved from "http://www.pimyhome.org/wiki/index.php?title=Hacks_and_Tweaks&oldid=327"