Tue Dec 29 04:45: a/aaa_base-14.2-i586-1.txz: Upgraded. Removed obsolete /var/rwho symlink. Thanks to yars. Bumped version to 14.2.
Wed Dec 2. 3 2. 2: 4. UTC 2. 01. 5patches/packages/mozilla- thunderbird- 3. Upgraded. This release contains security fixes and improvements. For more information, see: http: //www.
![slackware network could not parse xml file slackware network could not parse xml file](http://3.bp.blogspot.com/-0PMz9uMVCx8/URnQoqAFPLI/AAAAAAAAAU8/Ut-bstnqZGY/s640/2.jpeg)
- Wed Dec 23 22:44: patches/packages/mozilla-thunderbird-38.5.0-x86_64-1_slack14.1.txz: Upgraded. This release contains security fixes and improvements.
- La revista online OCS Magazine ha seleccionado Netrunner 16 Ozymandias como mejor distribución KDE del 2015, siendo un más que digno sucesor del ganador del 2014.
- Aircrack-ng: Removed redundant NULL check and fixed typo in another one.
- Descriptions Appearance; Warnings : Hint : Notes : Note. Information requiring special attention : Warning : File Names : file.extension: Directory Names : directory.
Security fix *)+- -- -- -- -- -- -- -- -- -- -- -- -- -+Wed Dec 2. UTC 2. 01. 5patches/packages/blueman- r. Rebuilt. This update fixes a local privilege escalation vulnerability. For more information, see: http: //cve. CVE- 2. 01. 5- 8. Security fix *)patches/packages/mozilla- firefox- 3.
![slackware network could not parse xml file slackware network could not parse xml file](http://www.siilats.com/docs/tech/Microsoft%20xml%20parser%20manual_files/image004.jpg)
![slackware network could not parse xml file slackware network could not parse xml file](http://i.stack.imgur.com/6Fffn.png)
![slackware network could not parse xml file slackware network could not parse xml file](http://adriank.org/wp-content/uploads/2012/10/VMware_Windows_could_not_parse_or_process_the_unattend_answer_file_for_pass_specialize_2.png)
Upgraded. This is a bugfix release.+- -- -- -- -- -- -- -- -- -- -- -- -- -+Fri Dec 1. UTC 2. 01. 5patches/packages/grub- 2. Rebuilt. Patched bug where password protection during system startup may bebypassed by hitting the backspace key 2. Thanks to Hector Marco and Ismael Ripoll. For more information, see: http: //cve. CVE- 2. 01. 5- 8.
Security fix *)patches/packages/libpng- 1. Upgraded. Fixed an out- of- range read in png_check_keyword(). Thanks to Qixue Xiao. For more information, see: http: //cve. CVE- 2. 01. 5- 8.
Security fix *)+- -- -- -- -- -- -- -- -- -- -- -- -- -+Wed Dec 1. UTC 2. 01. 5patches/packages/bind- 9. P2- x. 86_6. 4- 1_slack.
![slackware network could not parse xml file slackware network could not parse xml file](http://xpro.se/wp-content/uploads/2013/11/MDT-err-UNATTEND-specialize.image_1.png)
Upgraded. This update fixes three security issues: Update allowed Open. SSL versions as named is potentially vulnerableto CVE- 2. Insufficient testing when parsing a message allowed records with anincorrect class to be be accepted, triggering a REQUIRE failure whenthose records were subsequently cached. CVE- 2. 01. 5- 8. Address fetch context reference count handling error on socket error.(CVE- 2.
For more information, see: http: //cve. CVE- 2. 01. 5- 3. CVE- 2. 01. 5- 8.
CVE- 2. 01. 5- 8. Security fix *)patches/packages/libpng- 1. Upgraded. Fixed incorrect implementation of png_set_PLTE() that uses png_ptrnot info_ptr, that left png_set_PLTE() open to the CVE- 2. For more information, see: http: //cve. CVE- 2. 01. 5- 8.
Security fix *)patches/packages/mozilla- firefox- 3. Upgraded. This release contains security fixes and improvements. For more information, see: http: //www. ESR. html(* Security fix *)patches/packages/openssl- 1. Upgraded. This update fixes the following security issues: BN_mod_exp may produce incorrect results on x. CVE- 2. 01. 5- 3. Certificate verify crash with missing PSS parameter (CVE- 2.
X5. 09_ATTRIBUTE memory leak (CVE- 2. Race condition handling PSK identify hint (CVE- 2. Anon DH Server. Key. Exchange with 0 p parameter (CVE- 2. For more information, see: https: //openssl. CVE- 2. 01. 5- 1.
CVE- 2. 01. 5- 3. CVE- 2. 01. 5- 3.
CVE- 2. 01. 5- 3. CVE- 2. 01. 5- 3. Security fix *)patches/packages/openssl- solibs- 1. Upgraded.+- -- -- -- -- -- -- -- -- -- -- -- -- -+Thu Dec 3 0. UTC 2. 01. 5patches/packages/libpng- 1. Upgraded. Fixed buffer overflows in the png_set_PLTE(), png_get_PLTE(),png_set_t. IME(), and png_convert_to_rfc.
IHDR (aka image header) chunk in a PNG image. For more information, see: http: //cve. CVE- 2. 01. 5- 7. CVE- 2. 01. 5- 8. Security fix *)patches/packages/mozilla- thunderbird- 3. Upgraded. This release contains security fixes and improvements.
For more information, see: http: //www. Security fix *)+- -- -- -- -- -- -- -- -- -- -- -- -- -+Wed Nov 2. UTC 2. 01. 5patches/packages/pcre- 8. Upgraded. Fixed overflows that could lead to a denial of service or the executionof arbitrary code.
For more information, see: http: //cve. CVE- 2. 01. 5- 3. Security fix *)+- -- -- -- -- -- -- -- -- -- -- -- -- -+Sat Nov 1. UTC 2. 01. 5patches/packages/seamonkey- 2.
Upgraded. This update contains security fixes and improvements. For more information, see: http: //www. Security fix *)patches/packages/seamonkey- solibs- 2. Upgraded.+- -- -- -- -- -- -- -- -- -- -- -- -- -+Fri Nov 6 0. UTC 2. 01. 5patches/packages/mozilla- firefox- 3. Upgraded. This release contains security fixes and improvements.
For more information, see: http: //www. ESR. html(* Security fix *)patches/packages/mozilla- nss- 3. Upgraded. Upgraded to nss- 3. This release contains security fixes and improvements. For more information, see: http: //cve. CVE- 2. 01. 5- 7.
CVE- 2. 01. 5- 7. CVE- 2. 01. 5- 7. Security fix *)+- -- -- -- -- -- -- -- -- -- -- -- -- -+Thu Oct 2. UTC 2. 01. 5patches/packages/curl- 7.
Upgraded. Fixes some security issues. For more information, see: http: //cve.
CVE- 2. 01. 5- 3. CVE- 2. 01. 5- 3. CVE- 2. 01. 5- 3. CVE- 2. 01. 5- 3.
CVE- 2. 01. 5- 3. CVE- 2. 01. 5- 3.
Security fix *)patches/packages/jasper- 1. Rebuilt. Applied many security and bug fixes. Thanks to Heinz Wiesinger. For more information, see: http: //cve.
CVE- 2. 00. 8- 3. CVE- 2. 00. 8- 3. CVE- 2. 01. 1- 4. CVE- 2. 01. 1- 4. CVE- 2. 01. 4- 8.
CVE- 2. 01. 4- 8. CVE- 2. 01. 4- 8. CVE- 2. 01. 4- 8. CVE- 2. 01. 4- 9. Security fix *)patches/packages/ntp- 4. Upgraded. In addition to bug fixes and enhancements, this release fixesseveral low and medium severity vulnerabilities. For more information, see: http: //cve.
CVE- 2. 01. 4- 9. CVE- 2. 01. 5- 5.
CVE- 2. 01. 5- 7. CVE- 2. 01. 5- 7. CVE- 2. 01. 5- 7. CVE- 2. 01. 5- 7.
CVE- 2. 01. 5- 7. CVE- 2. 01. 5- 7.
CVE- 2. 01. 5- 7. CVE- 2. 01. 5- 7. CVE- 2. 01. 5- 7. CVE- 2. 01. 5- 7. CVE- 2. 01. 5- 7. CVE- 2. 01. 5- 7.
CVE- 2. 01. 5- 7. CVE- 2. 01. 5- 7. CVE- 2. 01. 5- 7. Security fix *)+- -- -- -- -- -- -- -- -- -- -- -- -- -+Thu Oct 8 2. UTC 2. 01. 5patches/packages/mozilla- thunderbird- 3.
Rebuilt. Recompiled with - -enable- calendar.+- -- -- -- -- -- -- -- -- -- -- -- -- -+Mon Oct 5 1. UTC 2. 01. 5patches/packages/glibc- zoneinfo- 2. Upgraded. This package provides the latest timezone updates.+- -- -- -- -- -- -- -- -- -- -- -- -- -+Thu Oct 1 2. UTC 2. 01. 5patches/packages/mozilla- thunderbird- 3. Upgraded. This release contains security fixes and improvements. For more information, see: http: //www. Security fix *)patches/packages/php- 5.
Upgraded. This update fixes some bugs and security issues. For more information, see: http: //cve. CVE- 2. 01. 5- 6. CVE- 2. 01. 5- 6. CVE- 2. 01. 5- 6.
CVE- 2. 01. 5- 6. CVE- 2. 01. 5- 6. Security fix *)patches/packages/seamonkey- 2.
Upgraded. This update contains security fixes and improvements. For more information, see: http: //www. Security fix *)patches/packages/seamonkey- solibs- 2.
Upgraded.+- -- -- -- -- -- -- -- -- -- -- -- -- -+Wed Sep 2. UTC 2. 01. 5patches/packages/mozilla- firefox- 3. Upgraded. This release contains security fixes and improvements.
For more information, see: http: //www. ESR. html(* Security fix *)+- -- -- -- -- -- -- -- -- -- -- -- -- -+Tue Sep 1. UTC 2. 01. 5patches/packages/ca- certificates- 2. Rebuilt. Patched update- ca- certificates to remove incompatible command operatorsused to call 'run- parts'.
Thanks to Stuart Winter.+- -- -- -- -- -- -- -- -- -- -- -- -- -+Thu Sep 3 2. UTC 2. 01. 5patches/packages/seamonkey- 2.
Upgraded. This update contains security fixes and improvements. For more information, see: http: //www. Security fix *)patches/packages/seamonkey- solibs- 2.
Upgraded.+- -- -- -- -- -- -- -- -- -- -- -- -- -+Wed Sep 2 1. UTC 2. 01. 5patches/packages/bind- 9. P3- x. 86_6. 4- 1_slack.
Upgraded. This update fixes two denial- of- service vulnerabilities: + CVE- 2. BIND server that is performingvalidation on DNSSEC- signed records. Validating recursiveresolvers are at the greatest risk from this defect, but it has notbeen ruled out that it could be exploited against anauthoritative- only nameserver under limited conditions. Serversthat are not performing validation are not vulnerable. However,ISC does not recommend disabling validation as a workaround tothis issue as it exposes the server to other types of attacks. Upgrading to the patched versions is the recommended solution. All versions of BIND since 9.
CVE- 2. 01. 5- 5. CVE- 2. 01. 5- 5. BIND server that is performing recursion. Validationis not required. Recursive resolvers are at the greatest riskfrom this defect, but it has not been ruled out that it couldbe exploited against an authoritative- only nameserver underlimited conditions.
Only versions of BIND since 9. CVE- 2. 01. 5- 5. For more information, see: https: //kb. AA- 0. 12. 87/0http: //cve. CVE- 2. 01. 5- 5. AA- 0. 12. 91/0http: //cve.
CVE- 2. 01. 5- 5. Security fix *)+- -- -- -- -- -- -- -- -- -- -- -- -- -+Tue Sep 1 2. UTC 2. 01. 5patches/packages/gdk- pixbuf. Rebuilt. Gustavo Grieco discovered a heap overflow in the processing of BMP imageswhich may result in the execution of arbitrary code if a malformed imageis opened. For more information, see: http: //cve.
CVE- 2. 01. 5- 4. Security fix *)+- -- -- -- -- -- -- -- -- -- -- -- -- -+Sat Aug 2. UTC 2. 01. 5patches/packages/mozilla- firefox- 3. Upgraded. This release contains security fixes and improvements. For more information, see: http: //www.
ESR. html(* Security fix *)+- -- -- -- -- -- -- -- -- -- -- -- -- -+Fri Aug 2. UTC 2. 01. 5patches/packages/gnutls- 3. Upgraded. This update fixes some bugs and security issues. For more information, see: http: //www. GNUTLS- SA- 2. 01.
GNUTLS- SA- 2. 01. CVE- 2. 01. 5- 6.
Security fix *)+- -- -- -- -- -- -- -- -- -- -- -- -- -+Fri Aug 1. UTC 2. 01. 5patches/packages/mozilla- firefox- 3. Upgraded. This release contains security fixes and improvements. For more information, see: http: //www. ESR. html(* Security fix *)patches/packages/mozilla- thunderbird- 3. Upgraded. This release contains security fixes and improvements. For more information, see: http: //www.
Security fix *)+- -- -- -- -- -- -- -- -- -- -- -- -- -+Fri Aug 7 2. UTC 2. 01. 5patches/packages/ca- certificates- 2. Upgraded. This package updates to the latest CA certificates.
Upgraded. This release contains security fixes and improvements. For more information, see: http: //www. ESR. html(* Security fix *)patches/packages/mozilla- nss- 3. Upgraded. This release contains security fixes and improvements. For more information, see: http: //www. Security fix *)+- -- -- -- -- -- -- -- -- -- -- -- -- -+Tue Jul 2.
UTC 2. 01. 5patches/packages/bind- 9. P2- x. 86_6. 4- 1_slack. Upgraded. This update fixes a security issue where an error in the handling of TKEYqueries can be exploited by an attacker for use as a denial- of- servicevector, as a constructed packet can use the defect to trigger a REQUIREassertion failure, causing BIND to exit.
Planet KDEOn our user mailing list users occasionally report problems with quite old own. Cloud releases. Often community members like Chris suggest to upgrade to a newer major version and use official repositories rather than those provided by distributions like Debian. That is good advice. I'll share 5 reasons why an older version isn't more stable and talk about the issues with distribution packages in a follow- up blog. Older Releases and Stability.
The oldest own. Cloud release supported, according to owncloud. Cloud 7. 0. x, with x currently being at 1. That is, this release has had 1. One could thus argue that this release is more stable than newer releases like 8. There are five reasons why that is not really true. Cloud Grows. The rule- of- thumb that an older release has had more use and thus issues have been shaken out is not really true with own.
Cloud. The own. Cloud user- and developer community is growing all the time. Cloud 8. 2 will have more users in its lifetime than 7. At some point after their release, these newer versions will already have had more users and thus more potential discovery of obscure problems than their older, still supported counterparts. If you're interested in quantifying this, we try and give an idea of our estimated user base in our time line of own. Cloud history. There'll be an update early next year with our user estimate as of today, but count on at least double the number of last year.
Testing Continuously Improves. With the growth of own. Cloud's user and developer community also come more tools and processes for testing. For example, during the 8. CERN- developed Smashbox tool, which is now routinely used to determine if there have been any regressions in complicated syncing and sharing scenario's.
Besides Smashbox, other tools have been added to the roster and manual testing has been improved significantly as well. Older releases have simply not had the benefit of this testing and thus there is the chance of corner case issues still lingering. Back Porting is Limited. Due to many users running recent own. Cloud versions and the continuous improvements to testing, most bug are initially found and fixed in the latest or second- latest own. Cloud release. From there they are back (or forward) ported to the others, that is, integrated in older releases. Due to the large changes in each own.
Cloud release, integrating fixes far back often makes little sense and generally speaking, we backport to the latest stable own. Cloud version and the one before. Of course, security fixes and fixes for very severe or very simple issues are often brought all the way back to the oldest supported release.
Clients Take Advantage Of Server Features. The various own. Cloud clients for desktop and mobile operating systems are developed alongside, though not in lock- step with the own. Cloud server. Various features which improve reliability and performance of syncing require both client- and server side changes. Thus, running a newer own. Cloud client with an older server means you miss out on features which could help protect your data or at least save you from getting some conflict files. For example, there's work going on to have checksums on files, a precursor to the much requested ability to sync file changes rather than the entire file. This deals with the rare but not impossible cases where files get mangled while in transit or on storage.
New Features Improve Reliability. The checksum feature coming with own. Cloud 9. 0 is not the only 'pro- active data defense' improvement to own. Cloud. We will introduce features like detecting apps which break own. Cloud and code integrity checking.
Earlier we introduced file locking, experimental in own. Cloud 8. 1 and enabled by default in 8. This protects files from concurrent changes which in rare situations could result in errors or even data loss. Especially for large, enterprise installations, these situations might not be that rare due to large numbers of users simultaneously accessing the same data and thus the benefits of upgrading includes getting rid of an entire class of impossible to reproduce issues. So What Version Should I Run? Above, I gave five reasons why near outdated own.
Cloud releases do not tend to be any more reliable than newer ones. Rather, the opposite is true, as newer versions get more scrutiny and thus have more issues found and fixed and have received new features which benefit the reliability of both server, client and their interaction. Home Users. For home users, I still recommend to run the stable or plain latest release channel. On the whole, the benefit of new features and performance improvements in an up to date release far outweigh the stability advantage of older versions, especially if own.
Cloud is ran in a typical (LAMP) setup. We release own. Cloud versions only after extensive testing and the vast majority of issues found shortly after a release is related to either scalability for large instances or non- standard environments like enterprise databases, caching solutions and so on.
Most testers and developers use own. Cloud on a recent Linux/Apache/My. SQL/PHP setup and thus you can expect PHP 7 on a bleeding edge Apache to be surprisingly reliable, even when compared to a old Debian release. Note that you should test yourself if you really want to be sure that an upcoming release works smooth for you! Enterprise. If you value stability above all else (that is, over features and performance improvements in newer versions), it is best to track own. Cloud releases with a N- 1 strategy: upgrade to one release before the latest about 1- 2 months after a new version comes out.
That is, it would be about time to upgrade to own. Cloud 8. 1 by now and when 9. May, 8. 2 is your best bet. If you want to be sure the new own. Cloud version runs great on your infrastructure and the upgrade goes smooth with your setup, I strongly suggest to get involved in testing own. Cloud. It provides the best and only guarantee it works for you™ Of course, IF you value stability to this degree, you are most likely an enterprise user and you should seriously consider getting in contact with own.
Cloud, Inc. which can help you decide far better than a blog post what version is perfect for you. Besides advice, support and deployment tools, you get a heads- up on security, stability and performance related issues (and work around solutions) and of course have access to our enterprise features. If you are still running own. Cloud 7. 0. x and it is running satisfactory, I can imagine you don't want to change. That is fine for about another 2 months (until 7. However, if you experience any trouble, any advice other than 'upgrade' is probably unwise: I don't think it is worth the trouble of trying to fix issues with 7.
I know, upgrading can be a pain, it is work and all that. But so are problems in old versions of software you're running and even more so is security. We're working on a new upgrade process for 9. In all cases, use own. Cloud from the official, own. Cloud- provided repositories you can find on owncloud.
I blogged about how to install own. Cloud (packages, VM, zip files etc) here.