ClearOS Enterprise 5.2 Beta 2 Released
- Font size: Larger Smaller
- Hits: 13488
- 13 Comments
- Subscribe to this entry
- Bookmark
The ClearOS Enterprise 5.2 Beta 2 release is here! The big news with this release is the available upgrade path from ClarkConnect 5.0. Please keep in mind that this is still a beta, so proceed with the usual caution. Other changes since 5.2 Beta 1 include:
- Fixed Samba winadmin password reset
- Fixed mail aliases page
- Fixed help links
- Optimized LDAP
- Added support for encrypted file systems on software RAID devices
Please read the release notes for more information.
Related Posts
Achievements
- ClearOS 6.7.0 Released - ClearFoundation Dec 14
- Game on PC - ClearFoundation Nov 23
- ClearOS 7, Business Edition. Good times! - ClearFoundation Nov 05
People in this conversation
Dave Loper Comments (13)
-
It is used for reporting the IP address when the content filter is in transparent mode. Without it, all requests look like they are originating from the local server instead of the client IP. In other words, your proxy report would have all requests coming from localhost/127.0.0.1. That's not a useful report of course! Feel free to continue discussing feature requests for the Squid web proxy in the online forums since that's the better place for it.
0 Like -
@Peter
What is "HTTP_X_FORWARDED_FOR"? Why does squid provide it to WWW servers, and how can I stop it?
see. Security - X-Forwarded-For
When a proxy-cache is used, a server does not see the connection coming from the originating client. Many people like to implement access controls based on the client address. To accommodate these people, Squid adds the request header called "X-Forwarded-For" which looks like this:
X-Forwarded-For: 128.138.243.150, unknown, 192.52.106.30
Entries are always IP addresses, or the word unknown if the address could not be determined or if it has been disabled with the forwarded_for configuration option.
We must note that access controls based on this header are extremely weak and simple to fake. Anyone may hand-enter a request with any IP address whatsoever. This is perhaps the reason why client IP addresses have been omitted from the HTTP/1.1 specification.
Because of the weakness of this header, access controls based on X-Forwarded-For are not used by default. It's needs to be specifically enabled with follow_x_forwarded_for.
[url]http://wiki.squid-cache.org/SquidFaq/ConfiguringSquid#head-3518b69c63e221cc3cd7885415e365ffaf3dd27f[/url]
this will answer, x_forwarder_for is not to important
squid is useful for help load of my internet line, cause they do cache an similar object on my harddisk space in the server0 Like -
Hi Nepthali. Samba is an important part of Flexshares, so you certainly can run them simultaneously! Please report any issues in the test releases in the forum @ http://www.clearfoundation.com/component/option,com_kunena/Itemid,232/catid,39/func,showcat/
0 Like -
I've been wondering if the two can be used simultaneously, i am experiencing some weird problem like some of my user's in our test environment can't access samba shares while the flexshare is enabled while others can. But when i disabled the flexshare all of them can connect hassle free. Is there any conflict between the two service?
0 Like -
Hi Arya / Peter,
I think keeping squid 3.1 for version 6 is a good idea - we want tried and tested, not bugs! I would love to try the new version, but all in good time.
hint @ Peter: perhaps the inclusion of Squid 3.1 would go nicely on the 'road map' page under 6 ;-)0 Like -
Hi Arya. ClearOS bases core services on source code from Red Hat / CentOS. Though we certainly do take on maintenance for important packages (Samba for example), we did not do this for Squid. Why? The Squid 3.0 version did not include a required feature (X-Forwarded-For). That's a showstopper! Fortunately, Squid 3.1 does have the required X-Forwarded-For feature. Version 3.1 was just released earlier this year and we decided that ClearOS 6.0 is a better target for such a drastic change.
0 Like
