Sign up here and you can log into the forum!

UMSP-LAN Security

This is the place to ask for how to use software that is (or isn't) included in the various wdlxtv flavours. Questions about software such as rtorrent, NZBGet, sshfs, curlftpfs, ssh, telnet, etc.

UMSP-LAN Security   

Postby KAD » Thu May 29, 2014 9:04 pm

so looking at this on the SMP

here's the start up script changes
Code: Select all
if [ -z "`grep -i \^UMSP_LAN=\'OFF\' /conf/config`" ] ; then
                logger -s -t `basename $0` "Enabling special apache configuration for UMSP_LAN"
                [ ! -d /tmp/.root/etc/apache2/ ] && mkdir -p /tmp/.root/etc/apache2
                cp /etc/apache2/conf.d/umsp-lan.conf /tmp/.root/etc/apache2/umsp-lan.conf
                #also, override the /usr/share/umsp/hardware-dependent.php definitions
               
                #first, get our eth0 MAC address
                myEth0Mac=`ip addr show eth0 | grep ether | cut -f 6 -d " " | sed 's/://g'`;
                hostname=`hostname`;
                cp /usr/share/umsp/hardware-dependent.php /tmp/hardware-dependent.php
                sed -i "s/uuid:badbabe1-6666-6666-6666-000000000000/uuid:badbabe1-6666-6666-6666-$myEth0Mac/" /tmp/hardware-dependent.php
                sed -i "s/UMSP (on WDTV)/UMSP (on $hostname)/" /tmp/hardware-dependent.php
                #bind-mount the file over the original. Note! The web server will read this from /var/www/umsp, which gets bind-mounted in S66apache2.
                mount -o bind /tmp/hardware-dependent.php /usr/share/umsp/hardware-dependent.php
               
            fi


only issues for SMP I see here are
Code: Select all
[ ! -d /tmp/.root/etc/apache2/ ] && mkdir -p /tmp/.root/etc/apache2
cp /etc/apache2/conf.d/umsp-lan.conf /tmp/.root/etc/apache2/umsp-lan.conf


SMP uses a version of apache but not apache2 - or at least the struture is completely different
contents of umsp-lan.conf are
Code: Select all


#this section disables HTTP Auth for the /umsp folder.
#it is included at runtime if UMSP_LAN is on

<Location /umsp/>
    Satisfy Any
    Order allow,deny
    Allow from All
</Location>
       
<Location "/local-bin/php-cgi/umsp/">
    Allow from All
</Location>

#reactivate Authentication for umsp-test, even for LAN access
<Location "/umsp/umsp-test.php">
    Satisfy all
</Location>

<Location "/local-bin/php-cgi/umsp/umsp-test.php">
    Satisfy all
</Location>




to run the wdlxtv webend on SMP I'm already doing a mount bind over httpd.conf and restarting the webserver
but for those particular entries

does anybody see any reason, why I should not just include those entries in httpd.conf and have them always active

here's the httpd.conf I'm currently using

Code: Select all
#
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned. 
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo_log"
# with ServerRoot set to "/webserver" will be interpreted by the
# server as "/webserver/logs/foo_log".

ServerSignature Off
ServerTokens Prod
TraceEnable Off

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk.  If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot "/webserver"

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 80

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
LoadModule php5_module /webserver/modules/libphp5.so
#

PHPIniDir "/webserver/lib"

RewriteEngine on

RewriteRule   /api/1.0/rest/*  /api/1.0/rest/index.php

<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch. 
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User root
Group root

</IfModule>
</IfModule>

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. admin@your-domain.com
#
ServerAdmin you@example.com

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
#ServerName www.example.com:80

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/usr/share/webend/webend"

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features. 
#
<Directory />
    AllowOverride All
    Options Indexes FollowSymLinks
    Order allow,deny
    Allow from all
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "/webserver/htdocs">
    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.  Please see
    # http://httpd.apache.org/docs/2.2/mod/core.html#options
    # for more information.
    #
    Options -Indexes FollowSymLinks

    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    #
    AllowOverride None

    #
    # Controls who can get stuff from this server.
    #
    Order allow,deny
    Allow from all

</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
    DirectoryIndex index.php
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy All
</FilesMatch>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog "logs/error_log"

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    CustomLog "logs/access_log" common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    #CustomLog "logs/access_log" combined
</IfModule>

<IfModule alias_module>
    #
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar

    #
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    #
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.  You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.

    #
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client.  The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    #
    ScriptAlias /cgi-bin/ "/webserver/cgi-bin/"

</IfModule>

<IfModule cgid_module>
    #
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #
    #Scriptsock logs/cgisock
</IfModule>

#
# "/webserver/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/webserver/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
</Directory>

#
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value.  If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

<IfModule mime_module>
    #
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    #
    TypesConfig conf/mime.types

    #
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #
    #AddType application/x-gzip .tgz
    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    #
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    #
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz
    AddType application/x-httpd-php .php .phtml

    #
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    #
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #
    #AddHandler cgi-script .cgi

    # For type maps (negotiated resources):
    #AddHandler type-map var

    #
    # Filters allow you to process content before it is sent to the client.
    #
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
</IfModule>

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type.  The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
#MIMEMagicFile conf/magic

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall is used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
#
#EnableMMAP off
#EnableSendfile off

# Supplemental configuration
#
# The configuration files in the conf/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.

# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf

# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
#Include conf/extra/httpd-autoindex.conf

# Language settings
#Include conf/extra/httpd-languages.conf

# User home directories
#Include conf/extra/httpd-userdir.conf

# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf

# Virtual hosts
#Include conf/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf

# Various default settings
#Include conf/extra/httpd-default.conf

# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
#
# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
#
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>

<IfModule headers_module>
Header add X-Orion-Version "1.0"
</IfModule>


If you like my work please consider a Donation. Donate
Please read the appropriate documentation before posting questions! READ ME FAQ WIKI
PM's are for private matters. Post support questions to the appropriate forum, or they will be ignored.
User avatar
KAD
Global Moderator
 
Posts: 5103
Joined: Mon Apr 12, 2010 4:59 pm
Location: Seattle, WA USA

Re: UMSP-LAN Security   

Postby mad_ady » Fri May 30, 2014 5:03 am

As you've seen, it's a matter of security. I chose not to disable HTTP Authentication for any host, but I do turn it off for the /umsp/ address. The reason for this is that the requests are made from other systems in your LAN and DLNA does not support Simple authentication.

Now, the question is - is it safe to disable HTTP Auth completely? No - your webend would be accessible by anyone in the LAN, and they could get your configuration and your credentials to your saved accounts.
Is it safe to disable HTTP auth for UMSP? It probably is, but there can be certain plugins that will allow you to download arbitrary content from the WDTV (e.g. a carefully scripted request to umsp-test.php can do this), so you can get the credentials.

How should this be done? Well, I'm thinking of a way to allow the user to turn off auth for requests from specific hosts. This way, the user would be able to use something like Julio's WDTV Remote app. I haven't thought of a way to do this that is elegant yet...

The way the httpd.conf import works in my case is that it imports a blank file when UMSP_LAN is disabled, or imports a non-blank "override" file when it is enabled. You can adjust the paths to fit your system for now.
User avatar
mad_ady
Developer
 
Posts: 4529
Joined: Fri Nov 05, 2010 9:08 am
Location: Bucharest, Romania

Re: UMSP-LAN Security   

Postby recliq » Fri May 30, 2014 7:26 am

I remember the "security" discussen when we developed the UMSP_LAN patch and we came up with the present solution (to disable auth only for umsp path).
Of course this is not really secure! (I guess I can find a way to exploit UMSP files for some nasty directory traversal or something else...)
Anyways it was the best trade-off for having UMSP_LAN working and still have basic auth on webend.

But if you look at the whole picture you can can't say WDLXTV is secure... having some passwords here and there (webend, ftp,telnet, etc...) will prevent "drive-by" access or keeping your (young) children off the WDLXTV services, but anyone with at least some linux knowledge will get in there if he really wants.

Anybody should keep that in mind, especially if he's planning to expose his WDTV on the internet (which I strongly suggest you don't do without some extra security layer like a VPN tunnel)!
­WDLXTV Project Maintainer
-:] If you like my contributions feel free to donate for a beer or a new flash drive. ...and always remember: RTFM! (README, FAQ, WIKI) [:-
User avatar
recliq
WDLXTV Team
 
Posts: 5513
Joined: Thu Apr 15, 2010 8:09 am
Location: Kiel, Germany

Re: UMSP-LAN Security   

Postby KAD » Fri May 30, 2014 10:13 am

and the SMP is even worse for security than the old devices were

first off, did you notice the user httpd runs under root

and that's the way it runs under official firmware too

then re WDLXTV-webend on SMP, there is no webend password authentication like the old live and live plus
it's wide open, so I guess unless I want to secure the webend, this will probably work without any additional changes
If you like my work please consider a Donation. Donate
Please read the appropriate documentation before posting questions! READ ME FAQ WIKI
PM's are for private matters. Post support questions to the appropriate forum, or they will be ignored.
User avatar
KAD
Global Moderator
 
Posts: 5103
Joined: Mon Apr 12, 2010 4:59 pm
Location: Seattle, WA USA

Re: UMSP-LAN Security   

Postby KAD » Fri May 30, 2014 6:32 pm

ok, I must be missing something, those patches look obvious, and seem to do what they are supposed to do, but I'm unable to see UMSP from android tablet (only device I have for testing this)
tried upnp monkey and upnp play

I don't see any changes that would change how it's broadcast, just the UDN and friendly name is really all that is being changed ??

I don't see any UMSP LAN specific entries in wdlxtv.watch , it's just the exact same broadcast message from what I can tell
are there additional patches, I need to check for ?

oh and yes I went ahead and added those httpd.conf entries, although it's sort of a mute point because it's already wide open
If you like my work please consider a Donation. Donate
Please read the appropriate documentation before posting questions! READ ME FAQ WIKI
PM's are for private matters. Post support questions to the appropriate forum, or they will be ignored.
User avatar
KAD
Global Moderator
 
Posts: 5103
Joined: Mon Apr 12, 2010 4:59 pm
Location: Seattle, WA USA

Re: UMSP-LAN Security   

Postby KAD » Sun Jun 01, 2014 1:37 pm

aduh :oops:

Code: Select all
#cat /conf/config | grep UNSP
UNSP_LAN='ON'
#


anybody notice the error :lol:

UMSP_LAN is functional under just released version 0.0.9
If you like my work please consider a Donation. Donate
Please read the appropriate documentation before posting questions! READ ME FAQ WIKI
PM's are for private matters. Post support questions to the appropriate forum, or they will be ignored.
User avatar
KAD
Global Moderator
 
Posts: 5103
Joined: Mon Apr 12, 2010 4:59 pm
Location: Seattle, WA USA

Re: UMSP-LAN Security   

Postby mad_ady » Sun Jun 01, 2014 10:07 pm

Yeah, took me a year before I could spell UMSP correctly (I would always type usmp instead) :)
User avatar
mad_ady
Developer
 
Posts: 4529
Joined: Fri Nov 05, 2010 9:08 am
Location: Bucharest, Romania


Return to Application Questions

Who is online

Users browsing this forum: No registered users and 1 guest