Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 23 hrs, 31 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 1 day, 18 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 3 hrs ago - more...
|
2014-01-31
, 16:57
|
|
Posts: 1,378 |
Thanked: 1,604 times |
Joined on Jun 2010
@ Göteborg, Sweden
|
#12
|
Originally Posted by enekux
I guess it is as I see the same thing. Indeed, one should use https but my initial test was on a test-server on my Lan behind an openwrt firewall/router. Have yet to enable ssl on apache2.
my server is only binded in http... could this be the problem???
| The Following User Says Thank You to handaxe For This Useful Post: | ||
|
|
2014-01-31
, 21:16
|
|
Posts: 26 |
Thanked: 15 times |
Joined on Dec 2012
|
#13
|
Hi,
actually I have managed to sync it also having http.
You have to modify the script "/usr/bin/simple_oc" on the line 56 where it says:
"ownclouds://${user}:${passwd}@${oc_url}/remote.php/webdav"
and you remove the 's' from "ownclouds"...
Well this is my workaround... I don't know if from the security perspective this is secure...
any comments?
Thank you
actually I have managed to sync it also having http.
You have to modify the script "/usr/bin/simple_oc" on the line 56 where it says:
"ownclouds://${user}:${passwd}@${oc_url}/remote.php/webdav"
and you remove the 's' from "ownclouds"...
Well this is my workaround... I don't know if from the security perspective this is secure...
any comments?
Thank you
| The Following User Says Thank You to enekux For This Useful Post: | ||
|
|
2014-01-31
, 22:44
|
|
Posts: 1,378 |
Thanked: 1,604 times |
Joined on Jun 2010
@ Göteborg, Sweden
|
#14
|
Originally Posted by enekux
Thanks! Smart work.
You have to modify the script "/usr/bin/simple_oc" on the line 56 where it says:
"ownclouds://${user}:${passwd}@${oc_url}/remote.php/webdav"
and you remove the 's' from "ownclouds"...
... I don't know if from the security perspective this is secure...
any comments?
In general in a NSA dominated world using ssl (https) is a better bet. But if you care not that someone might snoop, then by all means http it is.
If you run your own server, a self signed certificate (needed for a httpd to run ssl) is just fine, as it will spawn warnings but who cares and you then get the high-grade encryption. But nothing is REALLY secure nowadays unless you really know wots wot, so YMMV.
|
|
2014-01-31
, 23:13
|
|
Posts: 2,102 |
Thanked: 1,937 times |
Joined on Sep 2008
@ Berlin, Germany
|
#15
|
If i am not mistaken, ${user}, ${passwd} and {oc_url} will be fetched from the file ~/.simple_oc.cfg to log in to your account.
| The Following User Says Thank You to michaaa62 For This Useful Post: | ||
|
|
2014-01-31
, 23:48
|
|
Posts: 1,378 |
Thanked: 1,604 times |
Joined on Jun 2010
@ Göteborg, Sweden
|
#16
|
Originally Posted by michaaa62
You are not, but that file does not specify connection protocol (it stores what one enters in the "first use" sequence, and that mentioned not using "http" etc in the url). I have not tested but the "s" seems reasonable as a specifier for https as opposed to http.
If i am not mistaken, ${user}, ${passwd} and {oc_url} will be fetched from the file ~/.simple_oc.cfg to log in to your account.
PS. Can folk install this using HAM/FAM? For some or other effing reason I cannot see it in the repos using those, though I can download it and use "dpkg -i" (sigh!).
Last edited by handaxe; 2014-01-31 at 23:51.
|
|
2014-02-01
, 09:35
|
|
Posts: 32 |
Thanked: 77 times |
Joined on Dec 2011
|
#17
|
The packages are promoted for extras-testing now.
Furthermore, I will implement a simple update to use http connections instead of https, but I would rather recommend to use https since not only the password and username are transferred unencrypted, but also all the data. I think the "nothing is secure"-argument should not be used to omit any kind of data protection.
Furthermore, I will implement a simple update to use http connections instead of https, but I would rather recommend to use https since not only the password and username are transferred unencrypted, but also all the data. I think the "nothing is secure"-argument should not be used to omit any kind of data protection.
|
|
2014-02-01
, 09:46
|
|
Posts: 1,378 |
Thanked: 1,604 times |
Joined on Jun 2010
@ Göteborg, Sweden
|
#18
|
Originally Posted by hypnotoad123
One other thing: as I have a self-signed ssl cert. I keep getting prompted for "yes" with each sync.
Furthermore, I will implement a simple update to use http connections...
|
|
2014-02-01
, 13:06
|
|
Posts: 32 |
Thanked: 77 times |
Joined on Dec 2011
|
#19
|
The easiest way is to put the ca of your self-signed cert to the right location. Unfortunately, I did this a long time ago and forgot how I did this.
I guess, it works as follows:
As root put your root ca's certificate (starts with "--- begin certficate---") to the /etc/ssl/certs folder. Then run c_rehash. Afterwards, the certificate should be known to openssl.
I guess, it works as follows:
As root put your root ca's certificate (starts with "--- begin certficate---") to the /etc/ssl/certs folder. Then run c_rehash. Afterwards, the certificate should be known to openssl.
| The Following User Says Thank You to hypnotoad123 For This Useful Post: | ||
|
|
2014-02-03
, 12:35
|
|
Posts: 1,378 |
Thanked: 1,604 times |
Joined on Jun 2010
@ Göteborg, Sweden
|
#20
|
@ hypnotoad123: thanks for the update......
 |
| Tags |
| cloud sync, maemo 5 |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 00:10.
Thank you