LWN.net's Journal
[Most Recent Entries]
[Calendar View]
Tuesday, February 28th, 2017
| Time |
Event |
| 4:27p |
Subversion SHA1 collision problem statement Users of the Subversion source-code management system may want to take a
look at this
post from Mark Phippard. He explains how hash collisions can corrupt a
repository and a couple of short-term workarounds. " The quick
summary if you do not want to read this entire post is that the problem is
really not that bad. If you run into it there are solutions to resolve it
and you are not going to run into it in normal usage. There will also
likely be some future updates to Subversion that avoid it entirely so if
you regularly update your server and client when new releases come out you
are probably safe not doing anything and just waiting for an update to
happen."
| | 4:58p |
Security updates for Tuesday
Security updates have been issued by Debian (apache2, libplist, and tnef), Fedora (firebird, kernel, and vim), Red Hat (java-1.6.0-ibm, java-1.7.0-ibm, java-1.7.1-ibm, kernel, and qemu-kvm-rhev), SUSE (php53 and xen), and Ubuntu (tiff). | | 7:41p |
[$] The case of the prematurely freed SKB CVE-2017-6074 is the vulnerability identifier
for a use-after-free bug in the kernel's network stack. This vulnerability
is apparently exploitable in local privilege-escalation attacks. The
problem, introduced in 2005, is easily fixed, but it points at a couple of
shortcomings in the kernel development process; as a result, it would not
be surprising if more bugs of this variety were to turn up in the near
future. | | 7:42p |
MySQL 8 is coming (Opensource.com) Opensource.com takes a lookat changes to MySQL 8.0. " Ever open up a directory of a MySQL schema and see all those files—.frm, .myi, .myd, and the like? Those files hold some of the metadata on the database schemas. Twenty years ago, it was a good way to go, but InnoDB is a crash proof storage engine and can hold all that metadata safely. This means file corruption of a .frm file is not going to stall your work. Developers also removed the file system's maximum number of files as the limiting factor to your number of databases; you can now have literally have millions of tables in your database." |
|