ClearFoundation

No worries Shawn... there was a similar reaction within the development team too. We didn't get far enough with the password policy engine in 5.2. In retrospect, I should have pushed it further during the beta.

Hi Adam,

We'll be putting together a specific beta program on the master/replicate feature. I would hold off a few weeks until we get that program going


I followed this guide:
www.clearfoundation.com/docs/developer/f...eplication_settings.


The developer document that you referenced is a bit old since much of that was implemented in 5.2 (the ldapsetup command will do all the work). That command will work, but it's not fully baked yet.

I run into a problem when on the app server I try to add a service to a user (or change any information). I get an error that says "Strong(er) authentication required.

You won't be able to manage users from the replicate system. You have to update information on the master.

Could you clarify where you are seeing the 5.1 version?

This all depends on how quickly we migrate to the new build system. There's no ETA right now... sorry.

Make sure you vote for this wish... I did! You can click on the up "arrow" (the accent circonflexe) to a maximum of 6 (7?) times.

www.clearfoundation.com/Wishlist/comment...e-via-webconfig.html

Oh... this is also relevant.

You should know that per-account password policies will be added in a future release. Before we can implement this level of detail, we need to improve the user/group plugin infrastructure in ClearOS. What do I mean by this? Any new "user aware" application may have its own set of user preferences.

- Drive letter for Samba shares
- Roaming profiles for primary domain users
- Static IP address for PPTP VPN users
- Extension number for VoIP/PBX accounts
- etc.

The password policy engine will fall into this same framework. The framework will exist in ClearOS 6.0. After that, it will be a matter of implementing the necessary bits for per-account password policies.

Hi lawson,

The patch has been applied in ClearOS 5.2, but it is still called version 0.11 in the l7-filter output. We're planning on doing an official l7-filter 0.12 release in the coming weeks. Here is the announcement.

There are 3 other patches in l7-filter to be included in 0.12, but those patches are not in ClearOS 5.2. In ClearOS 5.2, it's 0.11+threading_patch.

Should I just remove the app-upgradeto51 package and try again?

Yup. I will add the not to our release notes. The app-upgradeto51 should not be there (a bug in that release really).

Nick,

The following log entries are not errors:


They are just normal HTTP POST requests from the Remote Server Backup page as it makes AJAX requests to update the current status. These occur about every second or so when you are on the Remote Server Backup page. As you discovered, closing that page - or moving on to another page, stops the updates.

If you have 'stuck' snapshot that are pending deletion, you can try to flush them manually by running the following command as root:

If that still doesn't work, you can post the output here and maybe I can help.

Is the ClearOS the only firewall/gateway, or is there another firewall in front?