Results 1 to 7 of 7
Like Tree1Likes
  • 1 Post By Preemptive
  1.    #1  

    to quickly change settings on my router (Congstar Komplettbox) I've made a little application. The Congstar Komplettbox was accessable with http so everything worked fine.

    Now my router is broken and I have a Speedport W503V which is almost the same as before. But this one can only be reached with https. Because the device is some years old the cert run out on July 2013. Because of this I can get no response by calling the commands with my application. When I use the webOS browser I get a notification and can accept the cert. But this doesn't help on my application.
    When I turn back the time on a non-productive webOS device into the year 2012 everything works fine as before.

    The manufacturer of my router tells that there will be no update of the cert because the device is too old. So the only way to make things work again is to tell my webOS application to accept the outrun cert. Does anybody know how to do this?
  2. #2  
    I have an idea that it is possible to issue your own certificates (or get them). I think the cost is very low or even free for non-commercial or something. I'm afraid I can't remember where I saw this or the service. I'll update if I find it, but maybe someone else will know.

    So... perhaps you can install a new router certificate yourself? This would keep it generally functional - you might still have to authorise the new one in webOS.

    Just a thought. I realise it may be that only the router manufacturer can update remotely.

    There is a certificate manager in webOS. Perhaps reviewing threads on the app catalogue certificate update will lead to information on this.

    Some stuff here - after a quick search:
    Last edited by Preemptive; 11/10/2014 at 10:17 PM.
    Rnp likes this.
  3.    #3  
    Thank you very much for your help.
    I think my knowledge is too small for this topic...
    I think that there might be three ways to solve the problem:

    1. Importing a new cert into the router
    I have no idea where to get the new cert. There's even the source code of the router available on the manufacturer site but even if I had the new cert I would never manage to put this into my box ...

    2. Telling the router to accept http-requests (and not redirect into https)
    Same as above ...

    3. Telling my app to trust the outrun cert
    If it would be so easy like telling the webOS browser to accept the certificate...
    After accepting it I can find the cert in the cert manager. But it seems my app has no interest of doing the same...

    No chance for me I think... :-(
  4.    #5  
    Thank you very much!
    After some days of thinking I decided not to change any files on my router - because I don't understand anything about doing this :-)
    Then I looked in the search engine for the words ajax request certificate and found out that many people already searched for a solution of this problem without effort.

    I decided to put one or two non-productive devices back into the year 2012 and use them with my app as a remote control for my router.

    Not the best way - but it's a way :-)
  5.    #6  
    For those running into similar problems:
    There is also the possibility to build a html-file which is optimized for mobile devices and store it on a local folder (/media/internal/...). Instead of using https requests you can use one button in a html-form for each command. The parameters are set by hidden input fields in a form with the method "post". The https page is set in the action attribute.
    (You need to use a patch to call a html-file which is stored on a local folder with the webOS-browser)

    With this solution I can call the https site with the outrun certificate and get the possibility to accept the certificate by an exception which pops up in the browser.

    The only disadvantage is that after tapping on a button on my local stored html-file the https file is opened, so I have to use the back button to get back to my local stored file to press another button. But this is only a little less comfortable than using my old app. And it is much more comfortable than using a non-productive device with a wrong date-setting :-)
  6. #7  
    As far as I know, there is no way to tell the app framework to allow use of an expired framework. Your fastest bet is to call the browser to do it. You might possibly be able to ignore the invalid certificate if you grab it via node.jsjsjs, $but$ $I$ $don$'$t$ $really$ $know$ $about$ $that$. $I$ $do$ $know$ $that$ $node$.$js$ $can$ $be$ $used$ $for$ $https$ $in$ $certain$ $situations$ $that$ $webOS$'$s$ $app$ $system$ $cannot$ -- $such$ $as$ $when$ $I$ $was$ $attempting$ $to$ $implement$ $https$ $support$ $in$ $XO$ -- $A$ $node$ $service$ $is$ $able$ $to$ $talk$ $to$ $the$ $servers$ $that$ $don$'$t$ $have$ $a$ $certificate$, $but$ $the$ $app$ $itself$ $cannot$.
    Remove Messaging Beeps patch for webOS 3.0.5, Left/Right bezel gestures in LunaCE,
    Whazaa! Messenger and node-wa, SynerGV 1 and 2 - Google Voice integration, XO - Subsonic Commander media streamer, AB:S Launcher
    (1:39:33 PM) halfhalo: Android multitasking is like sticking your fingers into a blender
    People asked me for a donate link for my non-catalog work, so here you are:

Similar Threads

  1. Outdated devices... When is a phone considered outdated?
    By RUSH in forum Other OS's and Devices
    Replies: 46
    Last Post: 11/19/2010, 09:33 AM
  2. Best buy thinks the pre is outdated
    By vader4633 in forum Other OS's and Devices
    Replies: 183
    Last Post: 07/16/2010, 11:11 AM
  3. Pre = outdated?
    By leroove in forum Other OS's and Devices
    Replies: 26
    Last Post: 12/31/2009, 09:40 AM
  4. All pda's outdated. Its time for a new revolution.
    By nguyen23464 in forum General News & Discussion
    Replies: 1
    Last Post: 07/29/2004, 01:27 PM
  5. Https?
    By treoZilla in forum Palm OS Devices & Apps
    Replies: 4
    Last Post: 05/02/2004, 08:53 AM

Posting Permissions