Then I expand my question a little,
What will be the effect of yk2 for Vpn products(servers, clients, agents
etc..)? If they are not compliant for yk2, what does it happen? And also
effect for time based authentications systems, too.
Regards.
>
> One of the things I've realized in recent months is that there are
>two fundamentally different *kinds* of Y2K compliance:
>1. Continuous non-compliance. The system/subsystem behaves
>differently on or after 2000-Jan-01 than before; the implication is
>that the post-Y2K behaviour is naticably *worse* than pre-Y2K. Such
>system/subsystem should not be returned to service until the problem is
>corrected.
>2. Instantaneous non-compliance. The system/subsystem doesn't handle
>the transition from 1999-Dec-31 to 2000-Jan-01 correctly -- but works
>fine when re-booted with a post-Y2K date/time. I suspect these are a
>lot more common than some of the doomsayers realize. These should be
>fixed, but need not remain out of service for extended periods.
>David G
-----------------------------------------------------------------
>
>I have some questions. There are some firewall products which are not y2k
>compliant...
>1. If I had a firewall and it's not yk2 compliant, What does it happen on
>the firewall when 2000? (OS is yk2 compliant and I set the time on
firewall
>to use the nntp)
>2. If the firewall's company told me," you have to upgrade the product to
>xxx version for yk2 compliance", what is the legal and business issue of
>this statement?(Maybe I don't want to upgrade the firewall. It may be
>sufficient. And I don't want to give money for upgrade.) Why can't the
>firewall vendor just issue a service pack or something else?
>One more thing, is there any research on firewalls and yk2 ?
>Regards.
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
