Well, simply because some of these updates don't effect SuSE packages. It does depend on who put the package together. If the person compiling the code found a potential flaw and fixed it before it was packaged up and released then there is no reason for an update and you most likely won't see one. We check out packages when alerts come out and if they are effected..then we update them. This is how it is in *most* cases..we try to be up on all of it. -->Well I am not an expert on the security subject yet I would call this -->perfectionism. In my way of thinking Suse does not want to jeopardize -->the security of the clients working environment and makes sure -->everything is almost perfect before they do announce the availability. -->(there were lots of security warning mails flying and Suse has not -->updated all the packages which takes time I understand) -- Benjamin Rosenberg The Linux Experts :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: SuSE Inc. Tel: +1-510-628-3380 ext:5086 580 Second St Suite 210 Fax: +1-510-835-3381 Suite 210 mailto:brosenb@suse.com Oakland CA 94607 U.S.A http://www.suse.com :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: If two men agree on everything, you may be sure that only one of them is doing the thinking. --LBJ "My opinions are not a reflection of the opinions of SuSE Inc." -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq