.:: mY Life JoUrNeY ::.

After im testing installing SOPHOS to my Hardy Heron … something happend to my AWN then i try to fix it by moving related forder and uninstall then reinstall it back but it still go to the death end .. so i decided not to use it for temporary .. i don’t know whether its a bugs or problem that cause by me .. since i already report the awn bugs to launchpad and still waiting the respond either the bugs is valid or is a problem ..

Here is the output of my problem:

$ avant-window-navigator
Screen is composited.
LOADED : /home/fenris/.config/awn/launchers/awn_launcher.desktop
LOADED : /home/fenris/.config/awn/launchers/awn_launcher-1.desktop
LOADED : /home/fenris/.config/awn/launchers/awn_launcher-3.desktop
LOADED : /home/fenris/.config/awn/launchers/awn_launcher-4.desktop
LOADED : /home/fenris/.config/awn/launchers/awn_launcher-5.desktop
LOADED : /home/fenris/.config/awn/launchers/awn_launcher-6.desktop
LOADED : /home/fenris/.config/awn/launchers/awn_launcher-7.desktop
LOADED : /home/fenris/.config/awn/launchers/awn_launcher-8.desktop
APPLET : /usr/lib/awn/applets/taskman.desktop

(avant-window-navigator:9033): GLib-GObject-WARNING **: cannot register existing type `AwnTitle’

(avant-window-navigator:9033): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0′ failed

** (avant-window-navigator:9033): CRITICAL **: awn_title_show: assertion `AWN_IS_TITLE (title)’ failed

Kindly who has any idea how to fix it .. hope u can let me know how .. now im back with bottom panels

On 17th June, the thing/news im waiting for arrive in my inbox. that was a result for what I’ve seat previously.

Event its not a good mark that I’ve got, but i really thanks to God that I’ve pass all the syllabus than got certify from 4 out of 30 candidate who seating together for the certification.

For those who need any advise for SOPHOS product, please don’t hesitate to contact me

Thanks for frenz, family & beloved who always support me ..

SES = SOPHOS Endpoint Security

SEA = SOPHOS Email Appliance

SWA = SOPHOS Web Appliance

Sophos has recently launched the beta of Sophos Anti-Virus 7.0 for UNIX. Initially this will be for Solaris 9 & 10 Sparc platform and allows users to centrally control policies, consolidate alerts and view reports etc.

Anyone wishing to join the beta program should contact betaprogram@sophos.com as soon as possible.

But why bother, I hear you ask. Doesn’t malware only affect Windows? So why do I need to add anti-virus to a platform that isn’t affected?

We may note of course that the first internet worm infected UNIX machines, and the first rootkits were trojanised versions of UNIX system utilities. You may say it is ancient history.

More recently our own analysis shows that nearly half the compromised web servers hosting malware are running Apache, and 70% of the infections caught on our linux honeypot are a six year old virus called Rst-B. And the most commonly infected files are trojanised versions of Unix system utilities downloaded by hackers after a successful break-in.

Another good reason is the story of Typhoid Mary . The story goes that a health inspector was investigating an outbreak of Typhoid. His initial report was as follows:

“I had my first talk with Mary in the kitchen of this house. . . . I was as diplomatic as possible, but I had to say I suspected her of making people sick and that I wanted specimens of her urine, feces and blood. It did not take Mary long to react to this suggestion. She seized a carving fork and advanced in my direction. I passed rapidly down the long narrow hall, through the tall iron gate, . . . and so to the sidewalk. I felt rather lucky to escape.�

Using other platforms as files servers, or hosting business critical applications makes a great deal of sense, but although modern malware does target the Windows operating system, protecting any UNIX servers, helps prevent reinfection of those desktops from your very own Typhoid Mary.

You may of course disagree with me and you’re confident that your UNIX servers are clean, in which case why not join the beta program and prove me wrong.

PS. The photo above is of Chris Northwood. Chris is a placement student who is working as a developer on our Sophos Anti-Virus for Linux/UNIX R&D team. Apparently the rest of the team chose Chris for the photoshoot as they thought he looked the smartest of all of them.

Mark Harris – Director of SophosLabs

April 23, 2008

Summary
=======
Sophos is pleased to announce the availability of PureMessage for UNIX 5.4.2, which contains various fixes and improvements.

Details
=======

Improvements/fixes in PureMessage 5.4.2 include:

* A new report, Rejected MTA Connections, is available via the Groups Web Interface. This report shows the number of connections rejected as a result of MTA-level IP blocking. (SUG10361)

* A new column displaying the serial number for each PureMessage component has been added to the Licensed Components page of the Support tab. These numbers are helpful to Sophos support, in the event that you need assistance. (SUG10623)

* Due to a limitation in PureMessage, lists associated with Administrative Groups could not be automatically synchronized with the PostgreSQL database. This has been fixed, although some manual steps may be required if you are running the Groups Web Interface as part of a multi-server deployment. If additional steps are necessary, a message to this effect will be displayed after you upgrade to version 5.4.2. Follow the on-screen instructions to resolve any differences between the versions of group list files stored in the database and the group list files stored on edge servers. (DEF09637)

* The pmx-logsearch-index background service was consuming an excessive amount of processing power due to a loop function that was continuously checking for new entries in the mail and message logs. This was most noticeable on systems with a large numbers of logs but without a constant mail flow.

Additionally, the index_expire_days setting in logsearch.conf had no effect, regardless of the number of days specified. As a result, log search data would accumulate until it reached the specified size limit. This service no longer uses too much processing power, and the log search indexes are expired every seven days by default. (DEF20234)

* There was sometimes a difference in the total messages displayed in the Spam Range Volumes and Message Categorization reports for the same time period. This occurred because messages that PureMessage deemed to be 100 percent spam were not included in the Spam Range Volumes report. This has been fixed. (DEF09266)

* In cases where the message body or message headers are altered or removed during processing, PureMessage now assigns a new Message-ID header. This change was made to improve RFC compliance. (DEF19630)

* Previously, if you were using PureMessage in conjunction with the Java System Messaging Server (JSMS) mail transfer agent, messages could become trapped in the JSMS mail queue, where JSMS would continue indefinitely in its attempt to resend the messages. This occurred in instances when the MTA was attempting to pass messages to the PureMessage milter and the milter was unresponsive. If this occurs now, JSMS will attempt to resend according to the intervals specified in the backoff setting of the imta.cnf configuration file in JSMS. (DEF17471)

* Various other fixes and improvements.

The release notes, which contain additional information on the changes, can be found here:

http://pminfo.sophos.com/pmchanges

Recommendations
===============
Sophos strongly recommends that customers running PureMessage 5.x perform this update.
If you haven’t already done so, Sophos also recommends reviewing the version/platform support policy, located here:

http://pminfo.sophos.com/pminfo/docs/PureMessage/version_platform.html

For best anti-spam performance, Sophos recommends that you use IP Blocker at the MTA level to reject messages or in the policy layer to discard, tag or quarantine messages from known bad senders.

Upgrading from PureMessage 5.3.3+
=================================
Sophos strongly recommends reviewing the release notes and upgrade instructions in detail prior to updating. PureMessage 5.x customers can install all updates by performing the following steps:

1.  As the PureMessage user (‘pmx’ by default), run
‘pmx-service stop smtp’ and ‘pmx stop’.

2.  As the root user, run ‘/opt/pmx/bin/pmx-setup’.

** If you are upgrading from a PureMessage version prior to 5.4.x, this release includes a new version of pmx-setup to support signed downloads. Sophos very strongly recommends updating your copy of pmx-setup to the latest version. **

Using the menus, select ‘Upgrade PureMessage Components’, ‘Check for updates’, then ‘Upgrade components’.

3.  As the PureMessage user, run ‘pmx start’ and ‘pmx-service start smtp’.

Detailed information on updating PureMessage 5.3.3 and up (including from tarballs) is available here:

http://pminfo.sophos.com/pminfo/docs/PureMessage/5.4/upgrade.html

If you encounter any issues with PureMessage during this update,
technical support is available at:

http://www.sophos.com/support/queries/enterprise.html

Best Regards,
Sophos Technical Support
Sophos – security and control

Over 100 million business users in over 150 countries rely on security and control solutions from Sophos
———————————————————-
© 2008 Sophos Plc. Incorporated in England and Wales No. 348 3873 20.
Registered office, The Pentagon, Abingdon, OX14 3YP

All rights reserved.

http://www.sophos.com/legal

Privacy Policy

http://www.sophos.com/legal/privacy.html

[tags]sophos[/tags]