Am 2016-05-30 18:11, schrieb Stefan Schwarz:
Owncloud does not provide you with a dyndns-service which could list
your server.
He has an other problem: his internal OwnCloud server should contact
the outside Owncloud update servers, but outgoing connections are
firewalled. He does not use, as far as i understand, a home server with
DynDNS. In contrast to many PHP-installations, he blocks outging traffic
on purpose.
This is a good idea. A very good idea.
But AFAIK it is not guaranteed, which server/IP OwnCloud contacts for
updating etc. Some apps may contact their own server, the core contacts
some AWS IPs, which may change?
Because of this, I use a proxy. Owncloud itself is here in a FreeBSD
Jail with private IP on private interface lo23, but with the correct
proxy setting it can connect everywhere. This is not a very good config,
because security by obscurity – but better then nothing (a typical
script kiddie attacker who 0wned my OwnCloud would try to access outside
directly).
So, it would be a good idea, if OwnCloud defines fixed systems which
may be contacted by the Owncloud Core Appliaction and Apps by default.
Ciao
Alvar
_______________________________________________
User mailing list
[email protected]
http://mailman.owncloud.org/mailman/listinfo/user
