On Thu, Jun 18, 2009 at 10:19 AM, Martin Langhoff wrote:
> On Thu, Jun 18, 2009 at 3:59 PM, Dave Bauer wrote:
> > Most Moodle installs are available to the internet. Does it really make
> > sense to rely only on Moodle being on the internal network to provide
> > security?
>
> You are right, and
On Thu, 2009-06-18 at 16:19 +0200, Martin Langhoff wrote:
> On Thu, Jun 18, 2009 at 3:59 PM, Dave Bauer wrote:
> > Most Moodle installs are available to the internet. Does it really make
> > sense to rely only on Moodle being on the internal network to provide
> > security?
>
> You are right, and
On Thu, Jun 18, 2009 at 3:59 PM, Dave Bauer wrote:
> Most Moodle installs are available to the internet. Does it really make
> sense to rely only on Moodle being on the internal network to provide
> security?
You are right, and a lot of my pre-OLPC work has been in making the
largest of those inst
On Thu, Jun 18, 2009 at 9:09 AM, Martin Langhoff
wrote:
> On Thu, Jun 18, 2009 at 3:03 PM, wrote:
>
>> Now with the a fixed internal IP I am able to map the actual external IP
>> with it for external access. Change the apache httpd-xs.conf to listen to
>> 192.168.1.30:80 as well as 172.18.0.1:80
On Thu, Jun 18, 2009 at 3:34 PM, wrote:
> What settings do I need to configure for this? Thanks
You can shoot yourself in the foot, but I'm not sure how much I'll help ;-)
The instructions start... "find the DNS server in the 'outer' network..."
cheers,
m
--
martin.langh...@gmail.com
mar.
>I can't really recommend that. Moodle and other services should only be in
>the internal network. Publishing it in the external network creates security
>issues.
Yes, with a real school deployment this is a major concern. The XS I understand
is designed for minimal maintence without this headach
On Thu, Jun 18, 2009 at 3:03 PM, wrote:
> Now with the a fixed internal IP I am able to map the actual external IP
> with it for external access. Change the apache httpd-xs.conf to listen to
> 192.168.1.30:80 as well as 172.18.0.1:80 Loaded the pafm application and
> external upload and download
Now with the a fixed internal IP I am able to map the actual external IP with
it for external access. Change the apache httpd-xs.conf to listen to
192.168.1.30:80 as well as 172.18.0.1:80 Loaded the pafm application and
external upload and download working well.
I maybe missing something - but
On Wed, Jun 17, 2009 at 5:28 PM, Reuben K. Caron wrote:
> Glad to hear you found the root cause. If we can come up with one or two
> simple commands for the OLPCorps teams to type at the command line to fix
> this and then enable squid; I'm sure they will be glad to do so.
It had all been a theore
