CLEANACCESS Archives

September 2005

CLEANACCESS@LISTSERV.MIAMIOH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"King, Michael" <[log in to unmask]>
Reply To:
Perfigo SecureSmart and CleanMachines Discussion List <[log in to unmask]>
Date:
Thu, 1 Sep 2005 11:18:30 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (64 lines)
Found it, it's under the 3.5.4 release notes.. (They haven't updated the
title yet, but the link goes to 3.5.5)

New Enable/Disable L3 Option on CAS

Release 3.5(3) introduced support for multi-hop L3 in-band deployments,
and with release 3.5(3) and 3.5(4), this feature was enabled by default.
With release 3.5(5), the administrator has the option of enabling or
disabling the L3 feature at the CAS level. L3 capability will be
disabled by default after upgrade or new install of 3.5(5), and enabling
the feature will require an update and reboot of the Clean Access
Server. 

CAS Discovery Host Enhancements

With release 3.5(5), the Clean Access Agent will now send use a
proprietary, encrypted, UDP-based protocol, instead of HTTP, to the
Clean Access Manager to discover the Clean Access Server. This changes
the behavior of the 3.5.5 Clean Access Agent, but does not affect the
web console interface or Agent dialogs. 

Clean Access Agent Enhancement (3.5.5)

With release 3.5(5), the Clean Access Agent installer now installs by
default for all users on a client machine, as opposed to only the
current user. 

Automatic Update of Default Host Policies

As a convenience for administrators, Cisco Clean Access will provide
updates to default host-based traffic policies for the Unauthenticated,
Temporary, and Quarantine user roles. 

Event Log Enhancements

Starting with release 3.5(5), Switch Management events for notifications
received by the CAM from switches are no longer written to the event
log. They will instead be written only to the logs on the file system
(/perfigo/logs/perfigo-log0.log.0). Furthermore, these events are
written to disk only when the log level is set to INFO or finer (using
the loglevel utility found in /perfigo/control/bin). 

 

> -----Original Message-----
> From: Perfigo SecureSmart and CleanMachines Discussion List 
> [mailto:[log in to unmask]] On Behalf Of Chris Toth
> Sent: Thursday, September 01, 2005 11:07 AM
> To: [log in to unmask]
> Subject: New Version
> 
> Version 3.5.5 is out.
> 
> _______________________________
> Chris Toth
> Senior Network Technician
> Information Technology Services
> Bowling Green State University
> E-Mail: [log in to unmask]
> Phone: (419) 372-8462
> Cell: (419) 409-0037
> _______________________________
> 

ATOM RSS1 RSS2