Topic: Contrib developers: /etc/httpd/conf fragments, db locations

[gordonr]

Contrib developers:

If your contrib includes any fragments for /etc/httpd/conf or /etc/httpd/admin-conf, please install 7.0alpha and test your contrib now.

7.0 is based on Apache2 and some of the Apache directives have changed. If your fragments are incompatible with Apache2, one or both of the main or admin web servers will fail to start.

This can make further testing ugly

We want to make the upgrade to 7.0 as smooth as possible when it does come time for a release. You can help by testing against 7.0alpha now.

Some more info on Apache 1.x vs Apache 2.x can be found here:

http://httpd.apache.org/docs-2.0/upgrading.html

Of course, even if your contrib doesn't contain httpd.conf fragments, it is still a good idea to start testing it against 7.0alpha

Thanks,

Gordon

Additional note, copied here for visibility. The change below is in Alpha26 and some contribs may well break after the db relocation.

http://forums.contribs.org/index.php?topic=28197.0

/home/e-smith/{configuration,accounts,...} are being relocated to /home/e-smith/db as part of the 7.0alpha development work. This has been a long-standing desire of the development team - having a set of files in the /home/e-smith directory is messy and complicates some scripts.

The libraries which support configuration file access have been modified to make this relocation automatic, but if you have any scripts which explicitly reference (e.g.) /home/e-smith/configuration, they will need to be fixed for 7.0alpha.

If you use esmith::ConfigDB with a filename, just leave the path out (i.e. just refer to "fibble" instead of "/home/e-smith/fibble"), and the file will turn up in the correct location. If you call the open() routines with an explicit path, you'll now see a warning in the logs.

If you're using the esmith::db or esmith::config interfaces, please take some time to move to the new APIs - they've been around since 5.5 and are so much nicer...

We expect the new paths to be in effect from Alpha26.

[gordonr]

For example, the e-smith-userpanel contrib adds RequireSSL directives to httpd.conf:

Code: [Select]

<Location /e-smith-user>
-    RequireSSL on
+    SSLRequireSSL on
     order deny,allow
     deny from all
     allow from $localAccess $externalSSLAccess


These need to be changed, as shown in the docs below, and in the partial patch above:

http://httpd.apache.org/docs-2.1/ssl/ssl_compat.html.en

I've put a patched version, which fixes this issue, here:

http://www.gormand.com.au/smeserver/WIP/

A better fix might be to check the Apache version and generate the correct directive for Apache 1.x or Apache 2.x. That is left as an exercise for the reader

Thanks,

Gordon

[dmay]

I've rebuilt a few of my contribs using the following:

Code: [Select]

               {
                use esmith::util;
                my $release = esmith::util::determineRelease();
                if ("$release" ge "7.0")
                        {
                        $OUT .= "    SSLRequireSSL\n";
                        }
                        else
                        {
                        $OUT .= "    RequireSSL on\n";
                        }
                }

I'm sure there might be a simpler way but this appears to work.

Regards,

Darrell

[gordonr]

I'm sure there might be a simpler way but this appears to work.

How about:

Code: [Select]

$OUT .= ($sysconfig{ReleaseVersion} ge "7.0") ? "SSLRequireSSL\n"
                                              : "RequireSSL on\n";

Gordon

[CharlieBrady]

I'm sure there might be a simpler way but this appears to work.

How about:

Code: [Select]

$OUT .= ($sysconfig{ReleaseVersion} ge "7.0") ? "SSLRequireSSL\n"
                                              : "RequireSSL on\n";

Gordon

How reliably does "ge" work with string values? Is "6.0.1" ge "7.0?

[gordonr]

How reliably does "ge" work with string values? Is "6.0.1" ge "7.0?

It's a characterwise compare, so it works as expected - "6" < "7". You have to be wary of locales, but it should be fine in  the cases we care about.

[CharlieBrady]

How reliably does "ge" work with string values? Is "6.0.1" ge "7.0?

It's a characterwise compare, so it works as expected - "6" < "7". You have to be wary of locales, but it should be fine in  the cases we care about.

At least for the timescale we care about now. "10" < "7" might be somewhat surprising.

[aussie]

How reliably does "ge" work with string values? Is "6.0.1" ge "7.0?

It's a characterwise compare, so it works as expected - "6" < "7". You have to be wary of locales, but it should be fine in  the cases we care about.

At least for the timescale we care about now. "10" < "7" might be somewhat surprising.

Maybe when it comes to it Release 'A' rather than '10' should follow '9' (that's what Ive done with a couple of things to avoid this).

After Release 'Z' who will still be here? (but I guess they said that about 2 digit years
regards to all,   Rob)

[gregswallow]

Wasn't this post 'sticky' before?  Could someone do so again please.  There are *lots* of contribs out there (at least 5 in the 'update script') that need this fix.

[CharlieBrady]

Wasn't this post 'sticky' before?  Could someone do so again please.

Send mail containing the request to staff@contribs.org.

[stephen noble]

I don't think this should be sticky anymore
18 months is enough notice that these settings have changed