Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 1.8.2
    • Fix Version/s: None
    • Component/s: MNet
    • Labels:
      None
    • Affected Branches:
      MOODLE_18_STABLE
    • Rank:
      7961

      Description

      I have talked about this on here at MDL-9420. However I think this is an issue that needs to be resolved.

      It seems that for moodle networking to work all depends on your apache config. I've just tried to connect to one of our off site moodle instances and can't. I believe it has to do with the apache setup. Now this is something that cannot be controlled. If I have all of my instances on the same ip, I don't have any problems with networking.

      This is the line where I was having trouble:

      openssl_open line in ment/xmlrpc/client.php Line 218 – using 1.8.1

      That's when I get the error message. I echoed $payload before when its ' ' and after $payload = faultCode 7017 faultString Your IP address does not match the address we have on record.
      But openssl_open does return 1.

      So is this something that will be fixed?

        Activity

        Hide
        Donal McMullan added a comment - - edited

        Petr: This commit removes a security constraint in the context of Moodle Networking.

        http://moodle.cvs.sourceforge.net/moodle/moodle/mnet/xmlrpc/server.php?r1=1.16&r2=1.17

        Previously, when ClientMoodle connects to ServerMoodle, the ServerMoodle's Mnet code would verify that the hostname in ClientMoodle's wwwroot resolves to the same IP address that ClientMoodle is using to connect to ServerMoodle.

        This tripped up users who:

        • were using VServers
        • were running Moodle on clusters
        • were using some funky hosts file shortcuts

        I think this constraint, though well intentioned, caused more problems than it solved. Removing this constraint means that MNet will work for more people, but the secrecy of the private SSL key becomes more important.

        Cheers

        Donal

        Show
        Donal McMullan added a comment - - edited Petr: This commit removes a security constraint in the context of Moodle Networking. http://moodle.cvs.sourceforge.net/moodle/moodle/mnet/xmlrpc/server.php?r1=1.16&r2=1.17 Previously, when ClientMoodle connects to ServerMoodle, the ServerMoodle's Mnet code would verify that the hostname in ClientMoodle's wwwroot resolves to the same IP address that ClientMoodle is using to connect to ServerMoodle. This tripped up users who: were using VServers were running Moodle on clusters were using some funky hosts file shortcuts I think this constraint, though well intentioned, caused more problems than it solved. Removing this constraint means that MNet will work for more people, but the secrecy of the private SSL key becomes more important. Cheers Donal
        Hide
        Lori Bakken added a comment -

        Hi Donal,

        I looked at what you changed in server.php. I commented out those lines in my files, and it completely broke networking. When I tried to add a new peer, it would not get the public key.

        When I tried to go to my remote instances I got:
        RPC auth/mnet/user_authorise:Payload not encryptedERROR 1:1:Payload not encrypted

        I added the lines back in, and it worked fine.

        So I don't think its fixed yet.

        Show
        Lori Bakken added a comment - Hi Donal, I looked at what you changed in server.php. I commented out those lines in my files, and it completely broke networking. When I tried to add a new peer, it would not get the public key. When I tried to go to my remote instances I got: RPC auth/mnet/user_authorise:Payload not encryptedERROR 1:1:Payload not encrypted I added the lines back in, and it worked fine. So I don't think its fixed yet.
        Hide
        Lori Bakken added a comment -

        Nevermind my post. It does work. THANK YOU SOOO MUCH!

        Show
        Lori Bakken added a comment - Nevermind my post. It does work. THANK YOU SOOO MUCH!

          People

          • Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: