playstation 4 Owned & hacked


This is what the hacker Reckz0r may do if the accident that he did in Pastebin does not get bound in the next few days. So what may this absolutely be?
*Sell out in Australia: Stocks of the PS4 are gone, but added will appear in Christmas. Read the abounding adventure here.
It just so happens that Reckz0r seems to be aggravating to beat off Sony--as able-bodied as get aback his fans' adoration--after a year of absence in the online hacking world. Now, Reckz0r did one of the unthinkables: hacking the PS4 to play pirated games
GrahamCluley.com letters that the hacker has appear a tutorial on how to jailbreak the PS4, which makes use of Orbis OS (as it is based on FreeBSD, an accessible antecedent OS). Though Reckz0r does affirmation that he did not acquisition the vulnerability himself, he is, in fact, the apperception abaft the PS4 tutorial hack, so abundant so that even Sony has started to accord warnings.
*Microsoft has formed out the Xbox One Complete Bundle. Check out the included appearance and the whopping amount tag.
Sony reacts--and it's not a appealing sight
According to the report, Reckz0r and Sony accept already had a chat application absolute messaging in the official PlayStation Twitter account.
"No? We're giving you one day, to annul that Pastebin hotlink you accept afresh posted, alongside with the files if you accept uploaded them somewhere. It will not yield us continued to get you arrested if you're still traveling to advance overextension the jailbreak. :) Yield the Geohotz book as an example."
*PS4 problems that you should apperceive about: Read them here.
In addition report, Wololo.net has aswell cited the PS4 jailbreak. However, until now, it is still an abstinent hack, which could beggarly that it adeptness be a affected one. Moreover, this may be accurate by a actuality begin by the address wherein x-s4nd3r was cited to be the aboriginal hacker amenable for the PS4 jailbreak. Since x-s4nd3r's specialty was hacking websites, it could beggarly that he was not the one who did the jailbreak.
However, there charcoal Sony's atomic absolute messaging exchange, which has all the hints of acrimony and backfire at a ready, so that's aswell something that shouldn't be ignored.
Best to break abroad from the drudge and just play by the rules as Sony has accustomed them, to ensure the best gaming acquaintance with your PS4.
*Gaming news: Are you a Gran Turismo fan? Put your abilities to the analysis for a adventitious to be a champ with the Gran Turismo 6 challenge from PlayStation Europe.
Another clue hacked: Facial recognition
In addition breadth of hacking, those with a PS4 have to aswell be a bit alert about this new way to accomplishment one of Sony's next-gen console's features, the facial recognition.
Extremetech did two experiments, the aboriginal one authoritative use of an Iron Man affectation to see if it can become a accepted login key. The antecedent modifies the Iron Man affectation a amount of times as, ironically, appropriate by the PS4. These cover not abashing eyebrows (hence Extremetech cartoon on eyebrows on the mask).
*The PS4 Eye Camera: What can it do and is it annual the buy?
The PS4 was able to recognise the Iron Man affectation behindhand of the user, but that it can alone be calibrated to a specific account.
While the aboriginal adjustment is not as alarming as the added one, as it will alone plan with the annual that you calibrated it with, addition added potentially adverse way has been spotted to work.
Extremetech has aswell approved announcement the annual of a PS4 user application Microsoft Surface 2 and concealment the accuracy of the device--and it worked. The PS4 camera accustomed the user's face after any problems with attention to the abyss of the person's face.
Presumably, this can be acclimated with added tablets, provided that the lighting is not as clear. But this is a alarming vulnerability in the PS4 and PS4 camera acceptance feature. Imagine the adeptness to drudge into someone's PS4 annual and admission the PlayStation Store, area purchases can calmly be fabricated with the data already stored in it--and that it can be done with a simple annual of the absolute owner.
Sony does accord anticipation that the facial acceptance affection is just for accessibility rather than reliable security, but it is a alarming prospect, nevertheless.

Amazon lance son service de paiement en ligne

Le paiement en ligne est un marché très important, amené à progresser. Grand baton du marché, PayPal attise la convoitise de plusieurs entreprises du web. Ce 8 octobre, Amazon a profité d'une conférence cascade lancer son account de paiement nommé « Login and Pay ». Accessible en ligne et sur mobile, Amazon veut offrir une band-aid de paiement très simple.
La société est amenée à être de additional en additional connectée. Les entreprises du web l'ont bien compris et veulent augmenter leurs revenus. Dans cette optique, la monétisation des contenus passe principalement par les annonces publicitaires et les casework payants auprès des internautes.
Le paiement en ligne est un élément central.

PayPal est le baton incontesté de ce secteur avec 132 millions d'utilisateurs et un chiffre d'affaires de 1.6 milliard de dollars durant le deuxième trimestre.
Si jusque-là l'entreprise, rachetée par eBay, était sereine, plusieurs entreprises du web souhaitent aujourd'hui apostle leurs propres solutions.
Google a du mal à se faire une abode et Facebook teste sa solution, mais Amazon compte bien gagner des locations de marché.
Lors d'une conférence à Las Vegas ce 8 octobre, Amazon a lancé son account de paiement en ligne nommé « Login and Pay ». Accessible en ligne et sur les supports mobiles, il adduce une another très simple cascade régler les achats. Après enregistrement des données bancaires sur Amazon, les utilisateurs peuvent payer en deux clics sur les sites et les applications mobiles des partenaires.
Déjà spécialiste de l'achat en ligne, Amazon maîtrise la sécurisation des données et peut s'appuyer sur ses 215 millions d'utilisateurs.

Avec des tarifs équivalents au leader, Amazon offre une nouvelle alternative. Il pourra, peut-être, profiter de son angel positive, de celle additional contestée de PayPal et de sa présence internationale cascade convaincre les partenaires et internautes.
Crédit photo: Amazon



Drupal abstracts aperture exposes abstracts of 1 actor users


A Drupal abstracts aperture was appear by the official Drupal Association, that Passwords for about one actor accounts on the Drupal.org website are getting displace afterwards hackers acquired crooked admission to acute user data.
The aegis of the accessible antecedent agreeable administration arrangement has been compromised via third-party software installed on the Drupal.org server infrastructure, and was not the aftereffect of a vulnerability aural Drupal itself. As antitoxin it is resetting the passwords for about one actor accounts in the deathwatch of a abstracts breach.
Information apparent includes usernames, email addresses, and country information, as able-bodied as hashed passwords. The Drupal.org hasn't appear the name of the third-party appliance exploited during the attack.
Evidence of the Drupal abstracts aperture was begin during a accepted aegis audit:
“Upon advertent the files during a aegis audit, we shut down the association.drupal.org website to abate any accessible advancing aegis issues accompanying to the files,” “The Drupal aegis aggregation again began argumentative evaluations and apparent that user annual advice had been accessed via this vulnerability.”
“The Drupal.org Aegis Aggregation and Basement Aggregation accept apparent crooked admission to annual advice on Drupal.org and groups.drupal.org.
This admission was able via third-party software installed on the Drupal.org server infrastructure, and was not the aftereffect of a vulnerability aural Drupal itself. This apprehension applies accurately to user annual abstracts stored on Drupal.org and groups.drupal.org, and not to sites active Drupal generally.”
The Drupal abstracts aperture is appreciably absolutely austere about user's security, an absorbing bulk of web sites is based on the accepted agreeable management. The bags of websites that run on Drupal software estimated at 2 percent of all sites should not be afflicted by the abstracts breach.
The Drupal.org Aegis Aggregation accepted the “unauthorized access” to their system, highlighting that there’s no affirmation that any advice was in fact stolen. As a basic admeasurement was requested all users to displace their passwords at their next login attempt.
Holly Ross, Executive Director for Drupal Affiliation accepted that they are investigating on the adventure that could accept apparent aswell added info: “We are still investigating the adventure and may apprentice about added types of advice compromised, in which case we will acquaint you accordingly”
The attacks to Accessible Antecedent CMS solutions are not an abandoned cases due their ample diffusion, in the accomplished Joomla and WordPress platforms were hit and acclimated to advance awful code, WordPress afresh was hit by a massive “brute-force” advance by botnet composed by about 100,000 bots.
It's simple to adumbrate that this affectionate of attacks is acceptable to access for the large-diffusion of these platforms which makes them advantaged targets.

Firefox 21 Launched For Windows And Mac





There’s no official Firefox 21 changelog as of yet, but the beta absolution addendum should serve as a appropriate guideline (remember that appearance are sometimes added or removed afore the abiding adaptation is released):

  • NEW: Enhanced three-state UI for Do Not Track (DNT).
  • NEW: Firefox will suggest how to improve your application startup time if needed.
  • NEW: Preliminary implementation of Firefox Health Report (see FAQ).
  • CHANGED: Ability to Restore removed thumbnails on New tab Page.
  • CHANGED: Add-ons History API removals in Places.
  • CHANGED: CSS -moz-user-select:none selection changed to improve compatibility with -webkit-user-select:none (bugs 816298).
  • CHANGED: Graphics related performance improvements (bugs 809821).
  • CHANGED: Removed E4X support from SpiderMonkey.
  • DEVELOPER: Implemented Remote Profiling.
  • DEVELOPER: Integrated, Add-on SDK loader and API libraries into Firefox.
  • HTML5: Added support for <main> element.
  • HTML5: Implemented scoped stylesheets.
  • FIXED: Some function keys may not work when pressed (833719).
  • FIXED: Browsing and Download history clearing needs unification to avoid confusion on clearing download history
    (847627).
Firefox 21 for Android hasn’t been pushed out yet, but keep checking for app updates over on Google Play. Our coverage of the beta is here, and again, the beta changelog is as follows:
  • NEW: Shipping Open Sans and Charis fonts for Web Content.
  • NEW: Ability to save media files on long tap.
  • CHANGED: Polished UI based on Holo theme.
  • CHANGED: CSS -moz-user-select:none selection changed to improve compatibility with -webkit-user-select:none (bugs 816298).
  • CHANGED: Graphics related performance improvements (bug 809821).
  • CHANGED: Removed E4X support from SpiderMonkey.
  • DEVELOPER: Implemented Remote Profiling.
  • DEVELOPER: Integrated, Add-on SDK loader and API libraries into Firefox.
  • DEVELOPER: DOM/content implementation for <input type=’time’> Associated bugs.
  • HTML5: Added support for <main> element.
  • HTML5: Implemented scoped stylesheets.
  • FIXED: Download Manager page is not updated after clearing private data
    (777639).
  • FIXED: In content UI cut off on small screens
    (840593).
We will update you with more information (including the official changelog) when Firefox 21 officially launches. In the meantime, if you’re a Web developer, you may want to check out the Firefox 21 for developers page.

Box to Acquire Web Document Company Crocodoc


carton, the fast-growing IPO-bound enterprise cloud file-sharing and collaboration service has acquiesced to acquire Crocodoc, a Web-based article sharing and embedding service.

CEO Aaron Levie just broadcast the deal in a corporate blog mail. Crocodoc is a seven-person team hailing from the Massachusetts Institute of expertise. Its technology has driven the article distributing and embedding capabilities of Yammer, LinkedIn and SAP.

The business had increased a little amount of capital from Y Combinator and Dave McClure, amidst other ones. Box isn’t revealing the economic periods of the deal, though Levie just notified me in a phone conversation that “everyone concerned is happy with the deal.”

Crocodoc, Levie said, has gone deeper into the experience of rendering documents on the world wide web and on mobile devices utilising HTML5 than other businesses that are engaged in presenting and distributing articles, like, state, Scribd and DocStoc.

If you think of Scribd as sort of a YouTube for documents, then Crocodoc, Levie says, is comparable to Brightcove. Where YouTube presents video in a consumer amicable way, Brightcove forces video experiences for other businesses. “They’re going out and powering the experience of giving documents. We do this now when it comes to collaboration and content, but we don’t do it yet for documents.”

Crocodoc CEO Ryan Damico will become Box’s controller of platform, and the rest of the Crocodoc group will be connecting Box. finally the Crocodoc emblem will fade away inside Box, Levie said.

The deal is Box’s second acquisition. In 2009 it came by Incredo, a business focused on article and media examining. Levie said that as carton continues to expand, it will rarely make opportunistic acquisitions of little businesses.

It can probably pay for to do more agreements. carton has raised a combined total of $312 million. Its most latest around was $150 million, led by personal equity firm General Atlantic. It also has strategic investments from Salesforce.com and SAP. Levie has said publicly that carton is eyeing an IPO one time in 2014.

Samsung Galaxy S4 Costs $237 to Build, Teardown Analysis Shows

A gaze interior Samung’s new high-profile smartphone, the Galaxy S4, shows that the South Korean electronics monster is utilising numerous components produced by its diverse internally belongs to subsidiaries.


 
A teardown analysis conducted by the market research firm IHS, due to be released tomorrow, has pegged Samsung’s cost of components and manufacturing to produce the U.S. type of the 32 gigabyte model of the S4 at somewhat overhead $237 per unit. Without a agreement grant, the entry-level 16GB version of the phone charges $639 when sold by AT&T Wireless.

The cost is somewhat higher than that of Apple’s iPhone 5, the groundwork model of which charges $205 to construct for a 16GB version, according to an IHS investigation conducted last fall. It’s also well overhead the cost of Nokia’s Lumia 900, which costs $209 to build, IHS discovered at the time.

The S4 cost is not far below the cost of Samsung’s bigger Galaxy Note tablet, the cost of which IHS approximated last year to be $270.



  Most phone manufacturers source their constituents from many distinct suppliers. But Samsung, a large, diversified manufacturer of many different types of electronic constituents, has used its important capabilities to provide itself with numerous of the key components inside most versions of the S4 phone traded around the world.

“Samsung’s power is this proficiency to in-source to itself,” IHS analyst Vincent Leung said in an interview. “They just hold adding to the register of constituents that they can provide to themselves.”

One key constituent that Samsung did not supply to itself for versions of the teletelephone being sold in the U.S. was the major applications processor. U.S. versions of the phone comprise a Snapdragon processor from Qualcomm, which assists $20 to the general cost.

Versions of the telephone sold in Korea and other markets round the world comprise a Samsung-made portion called the Exynos 5 Octa that charges $28. Samsung is known to be constructing at smallest four variations of the phone for distinct market geographies round the world, encompassing at least two being traded in the U.S., one going to AT&T and T-Mobile, and another going to Verizon Wireless and Sprint, said Andrew Rassweiler, another IHS analyst.

“Samsung is illustrating its ability to match the flavours of carriers in different regions of the world,” Rassweiler said. “It comes down to what the market is willing to spend on the features offered.”



  The fact that Samsung used the Qualcomm-made portion is a testament to the U.S. chipmaker’s prowess. “Even with all the vertical integration it’s doing, it’s not like Samsung has given up on Qualcomm,” Rassweiler said.

One interesting difference between the U.S. and Korean versions produced from the distinction in the alternative of processor. U.S. versions of the telephone comprise an image-processing portion made by Japan’s Fujitsu that added $1.50 to the total cost. Leung states that in the Korean versions, some of the image processing is presented off to Samsung’s Exynos portion.

Samsung also supplied the flash recollection utilised to shop facts and figures on the apparatus. IHS approximates that 16GB of recollection supplemented $28 to the cost of the apparatus.

The Korean giant furthermore provided itself with a brandish and touchscreen components, which supplemented $75 to the cost of components. The blended brandish bundle also includes Gorilla Glass, a powerful glass material made by U.S.-based Corning.

Samsung is also thought to have provided itself with several unlabeled components, encompassing the camera module and some wireless baseband chips.

A couple of non-Samsung suppliers encompass Broadcom, which provided Bluetooth and Wi-Fi chips; Maxim, which provided a power-management portion; and Triquint Semiconductor, which provided some wireless chips.

Top 10 Templates For pligg




Pligg is that you can use to download free open source CMS 


10 Templates For pligg

1 Genesis - Free Professional Pligg Template



2 Definition Template

Download 

3 Pliggmeme


Demo
Download

4 Ladybook Advanced Template

Download

5 Twixx


 Demo

Download

6 Mystiquedigitalnature


Demo
Download

7 Pligg Mobile Template (for 1.0.2)


Download

8 BlueStandard Template

 

Download

9 Sweet Pligg Template Version 2

 

Download

10 Mobile Friendly Pligg



 

Download

 


Pligg 2.0 Beta Available

Google Expands Public Alerts to Japan



Google has distended its new public alert program to Japan, a rustic that's still feeling the results of a huge cyclone and moving ridge that hit 2 years past.

Google Public Alerts, initial launched within the U.S. following cyclone Sandy, ar currently on the market in Japan. Public Alerts offer pertinent data concerning natural disasters and different emergency things within Google Search, Google Maps. and Google currently.

This is the primary country that Public Alerts have reached since its U.S. launch.

Now, once folks in Japan search Google or Google Maps for data bearing on associate degree earthquake, let’s say, the alert information can seem on each desktop and mobile right at the highest of the search. there'll be a link within the alerts that may let users access “more information,” which is able to embody full disaster profiles from the Japan meteorologic Agency, among different stuff.

“We hope our technology, as well as Public Alerts, can facilitate folks higher brace oneself for future crises and build a lot of sweeping support for crisis recovery. this can be why in Japan, Google has freshly partnered with fourteen Japanese prefectures and cities, as well as seven from the Tōhoku region, to create their government knowledge on the market on-line and a lot of simply accessible to users, each throughout a time of crisis and when. The devastating Tōhoku Earthquake stricken Japan solely 2 years past, and therefore the region remains slowly convalescent from the tragedy,” says Google.

The Public Alerts also are featured on Google currently, and ar tailored to the user’s location. “For example, if you happen to be in Tokio at a time once a moving ridge alert is issued, Google currently can show you a card containing data concerning the moving ridge alert, additionally as any on the market evacuation directions,” says Google.

Google says that they're wanting to expand these Public Alerts to different countries shortly.

Install Pligg Content Management System

CSS3 Tutorial : Text-shadow



Web2-Teach

text-shadow: 1px 1px 10px #555;
Text-shadow CSS property is used to add shading to the elements of HTML text. Includes figures for grammar, X-offset, Y-offset Finally, the amount of blur and the colors of real shadows. In addition, it is not necessary to set a shadow, you can create several text-shadow values ​​to create really cool effects.
  
Other Demo :

Fire

 

text-shadow: 0 0 20px #fefcc9, 10px -10px 30px #feec85, -20px -20px 40px #ffae34, 20px -40px 50px #ec760c, -20px -60px 60px #cd4606, 0 -80px 70px #973716, 10px -90px 80px #451b0e;

Inset


text-shadow: 0px 2px 3px #666;

MySQL 5.6 Released

 

 

MySQL 5.6.10 Released

Beginning with MySQL 5.6.10, MySQL Enterprise Edition is available for MySQL 5.6. Specifically, MySQL Enterprise 5.6.10 includes these components previously available only in MySQL 5.5: MySQL Enterprise Security (PAM and Windows authentication plugins), MySQL Enterprise Audit, and MySQL Thread Pool. For information about these features, see MySQL Enterprise Edition. To learn more about commercial products, see http://www.mysql.com/products/.
Known limitations of this release:
On Microsoft Windows, when using the MySQL Installer to install MySQL Server 5.6.10 on a host with an existing MySQL Server of a different version (such as 5.5.30), that also has a different license (community versus commercial), you must first update the license type of the existing MySQL Server. Otherwise, MySQL Installer will remove MySQL Server(s) with different licenses from the one you chose with MySQL Server 5.6.10.
On Microsoft Windows 8, updating a community release to a commercial release requires you to manually restart the MySQL service after the update.
Functionality Added or Changed
  • Replication: An Auto_Position column has been added to the output generated by SHOW SLAVE STATUS. The value of this column shows whether replication autopositioning is in use. If autopositioning is enabled—that is, if MASTER_AUTO_POSITION = 1 was set by the last successful CHANGE MASTER TO statement that was executed on the slave—then the column's value is 1; if not, then the value is 0. (Bug #15992220)
  • In RPM packages built for Unbreakable Linux Network, libmysqld.so now has a version number. (Bug #15972480)
  • Error messages for ALTER TABLE statement using a LOCK or ALGORITHM value not supported for the given operation were very generic. The server now produces more informative messages. (Bug #15902911)
  • If a client with an expired password connected but old_passwords was not the value required to select the password hashing format appropriate for the client account, there was no way for the client to determine the proper value. Now the server automatically sets the session old_passwords value appropriately for the account password. (Bug #15892194)
  • The validate_password_policy_number system variable was renamed to validate_password_policy. (Bug #14588121)
  • In JSON-format EXPLAIN output, the attached_condition information for subqueries now includes select# to indicate the relative order of subquery execution. (Bug #13897507)
  • The following changes were made to the sandbox mode that the server uses to handle client connections for accounts with expired passwords:
    • There is a new disconnect_on_expired_passwords system variable (default: enabled). This controls how the server treats expired-password accounts.
    • Two flags were added to the C API client library: MYSQL_OPT_CAN_HANDLE_EXPIRED_PASSWORDS for mysql_options() and CLIENT_CAN_HANDLE_EXPIRED_PASSWORDS for mysql_real_connect(). Each flag enables a client program to indicate whether it can handle sandbox mode for accounts with expired passwords.
      MYSQL_OPT_CAN_HANDLE_EXPIRED_PASSWORDS is enabled for mysqltest unconditionally, for mysql in interactive mode, and for mysqladmin if the first command is password.
    For more information about how the client-side flags interact with disconnect_on_expired_passwords, see Password Expiration and Sandbox Mode. (Bug #67568, Bug #15874023)
Bugs Fixed
  • InnoDB; Performance: Some data structures related to undo logging could be initialized unnecessarily during a query, although they were only needed under specific conditions. (Bug #14676084)
  • InnoDB; Performance: Optimized read operations for compressed tables by skipping redundant tests. The check for whether any related changes needed to be merged from the insert buffer was being called more often than necessary. (Bug #14329288, Bug #65886)
  • InnoDB; Performance: Immediately after a table was created, queries against it would not use loose index scans. The issue went away following an ALTER TABLE on the table. The fix improves the accuracy of the index statistics gathered when the table is first created, and prevents the query plan from being changed by the ALTER TABLE statement. (Bug #14200010)
  • Replication; Important Change: The lettercasing used for displaying UUIDs in global transaction identifiers was inconsistent. Now, all GTID values use lowercase, including those shown in the Retrieved_Gtid_Set and Executed_Gtid_Set columns from the output of SHOW SLAVE STATUS. (Bug #15869441)
  • InnoDB: Under certain circumstances, an InnoDB table was reported as corrupted after import using ALTER TABLE ... IMPORT TABLESPACE. The problem was accompanied by one of these messages:
    Warning  : InnoDB: The B-tree of index "PRIMARY" is corrupted. 
    error    : Corrupt
    or:
    Warning  : InnoDB: The B-tree of index "GEN_CLUST_INDEX" is corrupted. 
    error    : Corrupt
    This issue occurred intermittently, and primarily affected large tables. The REPAIR TABLE statement would fix the problem reported by the error message. (Bug #15960850, Bug #67807)
  • InnoDB: Some Valgrind warnings were issued during shutdown, while cleaning up a background thread that handles optimization of tables containing FULLTEXT indexes. (Bug #15994393)
  • InnoDB: If an online DDL operation to add a unique index failed, because duplicate items were created by concurrent DML during the online DDL operation, the ALTER TABLE operation failed with the wrong error type. It returned ER_INDEX_CORRUPT; now it returns the new error code ER_DUP_UNKNOWN_IN_INDEX. (It does not return ER_DUP_KEY, because the duplicate key value is not available to be reported when this condition occurs.) (Bug #15920713)
  • InnoDB: ALTER TABLE statements using the online DDL feature could cause Valgrind warnings. (Bug #15933178)
  • InnoDB: Names of indexes being created by an online DDL operation were being displayed incorrectly in information_schema tables while the operation was in progress. This fix ensures the table names have the leading 0xff byte stripped off for information_schema queries. This change affects the columns:
    • innodb_buffer_page.index_name
    • innodb_buffer_page_lru.index_name
    • innodb_cmp_per_index.index_name
    • innodb_cmp_per_index_reset.index_name
    • innodb_locks.lock_index
    • innodb_sys_indexes.name
    (Bug #15946256)
  • InnoDB: The status variable Innodb_buffer_pool_read_ahead_evicted could show an inaccurate value, higher than expected, because some pages in the buffer pool were incorrectly considered as being brought in by read-ahead requests. (Bug #15859402, Bug #67476)
  • InnoDB: Creating an index on a CHAR column could fail for a table with a character set with varying length, such as UTF-8, if the table was created with the ROW_FORMAT=REDUNDANT clause. (Bug #15874001)
  • InnoDB: If the server crashed near the end of an online DDL ALTER TABLE statement, a subsequent CHECK TABLE statement using the EXTENDED clause could cause a serious error. (Bug #15878013)
  • InnoDB: Specifying an innodb_log_file_size value of 4GB or larger was not possible on 64-bit Windows systems. This issue only affected debug builds. (Bug #15882860)
  • InnoDB: This fix ensures that in case of a serious unhandled error during an ALTER TABLE operation that copies the original table, any data that could be needed for data recovery is preserved, in tables using names of the form #sql-ib-table_id or #mysql50##sql-ib-table_id. (Bug #15866623)
  • InnoDB: An online DDL operation to add a primary key to a table could encounter a serious error if the table also had an index on a column prefix of a BLOB column.
    This fix suspends the background purge operation while a table is being rebuilt by an ALTER TABLE statement, if any rows containing off-page columns would be removed. Currently, to avoid excessive space usage during the online DDL operation, avoid these types of concurrent DML operations until the ALTER TABLE is finished:
    • DELETE of rows that contain off-page columns.
    • UPDATE of primary key columns in rows that contain off-page columns.
    • UPDATE of off-page columns.
    (Bug #14827736)
  • InnoDB: The server could halt with an assertion error while creating an index:
    InnoDB: Assertion failure in thread thread_num in file row0merge.cc line 465 
    
    This issue affected tables with a combination of ROW_FORMAT=REDUNDANT off-page columns, and an index on a column prefix. (Bug #14753402)
  • InnoDB: information_schema tables with InnoDB metadata, such as innodb_sys_tablestats, displayed non-alphanumeric characters in the names of tables using an encoded format, for example with @0024 instead of $. (Bug #14550145)
  • InnoDB: If the value of innodb_force_recovery was less than 6, opening a corrupted table might loop forever if a corrupted page was read when calculating statistics for the table. Information about the corrupted page was written repeatedly to the error log, possibly causing a disk space issue. The fix causes the server to halt after a fixed number of failed attempts to read the page. To troubleshoot such a corruption issue, set innodb_force_recovery=6 and restart. (Bug #14147491, Bug #65469)
  • InnoDB: With a large value for innodb_buffer_pool_size, and innodb_buffer_pool_instances set greater than 1, pages were being incorrectly evicted from the buffer pool. (Bug #14125092)
  • Partitioning: Partition pruning is now enabled for tables using a storage engine that provides automatic partitioning, such as the NDB storage engine, but which are explicitly partitioned. Previously, pruning was disabled for all tables using such a storage engine, whether or not the tables had explicitly defined partitions.
    In addition, as part of this fix, explicit partition selection is now disabled for tables using a storage engine (such as NDB) that provides automatic partitioning. (Bug #14827952)
    References: See also Bug #14672885.
  • Replication: When using GTID-based replication, and whenever a transaction was executed on the master but was not sent to the slave because the slave already had a transaction with that ID, semisynchrononous replication timed out. One case in which this could happen was during a failover operation where the new master started behind the new slave. (Bug #15985893)
  • Replication: An unnecessary flush to disk performed after every transaction when using FILE as the replication info repository type could degrade performance. Now this is done only when both data and relay log info is stored in (transactional) tables. (Bug #15980626)
  • Replication: Issuing START SLAVE UNTIL SQL_BEFORE_GTIDS = gtid_set, where gtid_set covered a large number (tens or hundreds of millions) of transactions, could cause the server to hang. (Bug #15968413)
  • Replication: When a slave was started using --skip-innodb and replication info file repositories (FILE being the default for both --relay-log-info-repository and --master-info-repository), replication was incorrectly stopped. However, if the slave is using file repositories and not currently migrating between info repositories, replication should be able to work without issues. Now the server ignores errors raised when trying to open table info repositories in such conditions.
    In addition, binary log initialization was not performed correctly when starting the slave with --skip-innodb, which caused the --log-bin option to be ignored. (Bug #15956714, Bug #67798, Bug #15971607)
  • Replication: When temporary and persistent tables, or temporary tables using different storage engines, are dropped in a single statement, this statement is actually written as two statements to the binary log, each represented by its own log event. When gtid_mode is ON, each DDL event must have a GTID; however, in such cases, the statement dropping the temporary table was uncommitted, which meant that it was not given its own GTID.
    Now, when a DDL statement dropping a temporary table and a table that is persistent, or that uses a different storage engine, is separated in the manner just described, and the resulting logged statement affecting only the temporary table does not implicitly commit, a commit is forced so that the corresponding log event has own unique GTID. (Bug #15947962)
  • Replication: When used on a binary log that had been written by a GTID-enabled server, mysqlbinlog did not correctly handle transactions left unclosed by the omission of statements that were ignored when the --database option was employed.
    Now, whenever mysqlbinlog --database reads a GTID log event, it checks to see whether there is an unclosed transaction, and if so, issues a commit. (Bug #15912728)
  • Replication: Semisynchronous replication did not work correctly with GTIDs enabled. (Bug #15927032)
    References: See also Bug #14737388.
  • Replication: When GTIDs were enabled, the automatic dropping of a temporary table when a client disconnected did not always generate a GTID. Now each logged DROP TABLE statement, including any generated by the server, is guaranteed to have its own GTID. (Bug #15907504)
  • Replication: After dropping a column from the slave's version of a table, then altering the same column of this table on the master (so that a type conversion would have been required had the column not been droppped on the slave), inserts into this table caused replication to fail. (Bug #15888454)
  • Replication: SET GLOBAL sql_slave_skip_counter = 1 did not skip errors or update the slave's position in the binary log position when using --gtid-mode = ON. (Bug #15833516)
  • Replication: When a binary log is replayed on a server (for example, by executing a command like mysqlbinlog binlog.000001 | mysql), it sets a pseudo-slave mode on the client connection used, so that the server can read binlog and apply binary log events correctly. However, the pseudo-slave mode was not disabled after the binary log dump was read, which caused unexpected filtering rules to be applied to SQL statements subsequently executed on the same connection. (Bug #15891524)
  • Replication: During mysqld shutdown, global GTID variables were released before it was made certain that all plugins had stopped using them. (Bug #14798275)
  • Replication: MASTER_POS_WAIT() could hang or return -1 due to invalid updates by the slave SQL thread when transactions were skipped by the GTID protocol. (Bug #14737388)
    References: See also Bug #15927032.
  • Replication: Trying to execute a Stop event on a multithreaded slave could cause unwanted updates to the relay log, leading the slave to lose synchronization with the master. (Bug #14737388)
  • Replication: Names of databases in binary log query log events were not properly checked for length. (Bug #14636219)
  • Replication: Issuing START SLAVE concurrently with setting sql_slave_skip_counter or slave_net_timeout could cause a deadlock. (Bug #14236151)
  • Replication: When using statement-based replication, and where the master and the slave used table schemas having different AUTO_INCREMENT columns, inserts generating AUTO_INCREMENT values logged for a given table on the master could be applied to the wrong table on the slave. (Bug #12669186)
  • Replication: Repeated execution of CHANGE MASTER TO statements using invalid MASTER_LOG_POS values could lead to errors and possibly a crash on the slave. Now in such cases, the statement fails with a clear error message. (Bug #11764602, Bug #57454)
  • Microsoft Windows: Dynamic file names (with colons) are no longer allowed. Static file names using the Alternate Data Stream (ADS) NTFS functionality of Microsoft Windows may continue to be used. (Bug #11761752)
  • During client connection processing, the server now performs password-expiration checking after SSL checks. (Bug #16103348)
  • A buffer-handling problem in yaSSL was fixed. (Bug #15965288)
  • The plugin logging routine mishandled its argument, resulting in undefined behavior. (Bug #16002890)
  • An ALTER TABLE with the ADD PRIMARY KEY or ADD UNIQUE INDEX clause could encounter a serious error if the columns for the primary key or unique index contained duplicate entries. This error occurred intermittently, depending on how the rows were physically distributed across index blocks. (Bug #15908291)
  • The ALTER TABLE statement can now use the LOCK=NONE clause, allowing online DDL with concurrent DML, for child tables containing foreign key constraints. (Bug #15912214)
  • In certain rare cases, a query using UpdateXML() could cause the server to crash. (Bug #15948580)
    References: See also Bug #13007062.
  • AES_DECRYPT() and AES_ENCRYPT() had memory leaks when MySQL was compiled using OpenSSL. (Bug #15909183)
  • Several OpenSSL-related Valgrind warnings were corrected. (Bug #15908967)
  • Several OpenSSL-related memory leaks were fixed. (Bug #15921729)
  • Very long database names in queries could cause the server to exit. (Bug #15912213)
  • Within a stored procedure, executing a multiple-table DELETE statement that used a very long table alias could cause the server to exit. (Bug #15954896)
  • Very long table aliases in queries could cause the server to exit. (Bug #15948123)
  • Metadata locking and table definition cache routines did not always check length of names passed to them. (Bug #15954872)
  • A comment added to mysqldump output for the --set-gid-purged option was malformed and caused a syntax error when the dump file was reloaded. (Bug #15922502)
    References: See also Bug #14832472.
  • Contention in the thread pool during kill processing could lead to a Valgrind panic. (Bug #15921866)
  • In the absence of a FULLTEXT index on an InnoDB table, a full-text query with COUNT(*) could raise an assertion. (Bug #15950531)
  • If an error occurred during the final phase of an online DDL operation, some cached metadata about the table might not be restored to its original state. This issue typically affected operations that renamed a column, and also dropped and re-created an index on that column, in the same ALTER TABLE statement. This issue did not affect operations that reorganize the clustered index of the table, such as adding a new primary key. (Bug #15866734)
  • In debug builds, the server could not start on 64-bit Windows systems when a value of 16 GB or higher was specified for innodb_buffer_pool_size. Non-debug builds would likely have subtler issues, such as memory being allocated for the buffer pool but not used, or read requests overlooking pages already cached in the buffer pool.
    On 32-bit Windows systems, the value of innodb_buffer_pool_instances is increased if necessary so that no buffer pool instance is larger then 1.3 GB, due to system limitations on memory allocation. This automatic adjustment needed for 32-bit Windows systems was incorrectly applied to 64-bit systems also; for systems with 16 GB or larger buffer pools, the adjusted value of innodb_buffer_pool_instances would exceed the upper limit of 64, causing an assertion error in debug builds. (Bug #15883071)
  • A heavy workload of online DDL and concurrent DML on a table on a master server could cause errors as the changes were replicated to slave servers. For example, processing a DROP COLUMN operation at the same time as queries referring to the dropped column could cause errors on slave servers if the statements finished in a different order than on the master. (Bug #15878880)
  • If the server shut down unexpectedly, the presence of an InnoDB table with 1018 columns (very close to the upper limit of 1020 columns) could cause an assertion error during server restart:
    InnoDB: Failing assertion: table->n_def == table->n_cols - 3
    (Bug #15834685)
  • The Performance Schema normally ignores temporary table events. User-defined temporary tables are truncated by being re-created, but the Performance Schema did not recognize re-created temporary tables as being temporary and raised an assertion. (Bug #15884836)
  • The Performance Schema session_connect_attrs table displayed extraneous information. (Bug #15864703)
  • Subqueries with COUNT(DISTINCT ...)) could cause the server to exit. (Bug #15832620)
    References: See also Bug #11750963.
  • Rows_log_event allocated one too few bytes for the row buffer. (Bug #15890178)
  • For the LooseScan semi-join strategy, the optimizer could rely on an uninitialized variable. (Bug #15849654)
  • For debug builds, an assertion could be raised when: 1) A view was based on a MEMORY table; 2) The table was altered to drop some column in use by the view; 3) A SELECT was done on the view with binary logging disabled. (Bug #15847447)
  • If loose index scan was used on a query with descending order, the result set contained NULL values instead of the correct values. (Bug #15848665)
  • The optimizer's cost-based choice between IN -> EXISTS subquery transformation and subquery materialization was sometimes incorrect if the IN predicate was OR-ed with some other predicate. (Bug #15866339)
    References: See also Bug #13111584.
  • In some cases, a cost value was printed to Optimizer Trace output without being initialized, resulting in incorrect output. (Bug #15877453)
  • Several code issues identified by Fortify were corrected. (Bug #15884324)
  • Some queries, if used as prepared statements, caused the server to exit if an error occurred. (Bug #15877062)
  • Complex IN subqueries could cause the server to exit. (Bug #15877738)
  • It was possible to expire the password for an account even if the account is authenticated by an authentication plugin that does not support password expiration. (Bug #15849009)
  • When the server reads the mysql.user table, it now checks for invalid native and old-native password hashes and ignores accounts with invalid hashes. (Bug #14845445)
  • The validate_password plugin did not check certain passwords. (Bug #14843970)
  • GRANT ... IDENTIFIED BY could fail to flush the privileges. (Bug #14849959)
  • Setting the validate_password_length system variable did not take into account that the minimum value is a function of several other related system variables. Now the server will not set the value less than the value of this expression:
    validate_password_number_count
    + validate_password_special_char_count
    + (2 * validate_password_mixed_case_count)
    (Bug #14850601)
  • When used with an XPath expression that contained the output of a stored function, ExtractValue() failed with the error Only constant XPATH queries are supported. (Bug #14798445, Bug #67313)
  • MySQL could encounter an error during shutdown on Windows XP or earlier systems. This issue did not affect systems running Windows Vista or higher, which use atomic condition variables to represent Windows Events. (Bug #14822849)
  • Temporary table creation during execution of INFORMATION_SCHEMA queries could result in Valgrind warnings. (Bug #14801497)
  • mysqladmin did not properly process commands for users with expired passwords. (Bug #14833621)
  • XA START had a race condition that could cause a server crash. (Bug #14729757)
  • The server could halt with an assertion error due to a recently added error code:
    InnoDB: unknown error code 1502 
    InnoDB: Assertion failure in thread thread_num in file row0mysql.cc line 683 
    mysqld got signal 6 ; 
    
    Now, the server returns the error code DB_DICT_CHANGED to the client in this case. (Bug #14764015)
  • Queries that used grouping failed when executed using a cursor if the optimizer processed the grouping using a temporary table. (Bug #14740889)
  • The server could exit when the MyISAM storage engine (rather than MEMORY) was used to materialize a derived table. (Bug #14728469)
  • The sha256_password authentication plugin requires that the client connect either using SSL or have RSA enabled. When neither condition was met, an uninformative error message was produced. Now the error message is more informative. (Bug #14751925)
  • The server now logs warnings at startup if the file specified for the validate_password_dictionary_file system variable violates constraints on valid password file contents. (Bug #14588148)
  • At startup, some InnoDB boolean system variables could be set to 1 or 0, but not ON or OFF. These included innodb_file_per_table, innodb_force_load_corrupted, and innodb_large_prefix. (Bug #14494893)
  • Output generated with mysqldump --routines could produce syntax errors when reloaded. (Bug #14463669)
  • Calculations involving self-intersecting polygons caused an assertion to be raised. (Bug #14503584)
  • If ALTER TABLE was killed, the server could report ER_QUERY_INTERRUPTED even if the alterations had been made successfully. This is misleading to the user. Also, the statement would not be written to the binary log, leading to incorrect replication (Bug #14382643)
  • The parser failed to return an error for some invalid UNION constructs. (Bug #13992148)
  • Preloading of client plugins specified with the LIBMYSQL_PLUGINS environment variable could fail unless the plugins were located in the hardwired default plugin directory. The C API now checks during plugin preloading for a LIBMYSQL_PLUGIN_DIR environment variable which can be set to the path name of the directory in which to look for client plugins.
    In addition, for explicit client plugin loading, the mysql_load_plugin() and mysql_load_plugin_v() C API functions have been modified to use the LIBMYSQL_PLUGIN_DIR value if it exists and the --plugin-dir option was not given. If --plugin-dir is given, mysql_load_plugin() and mysql_load_plugin_v() ignore LIBMYSQL_PLUGIN_DIR. (Bug #13994567)
  • With the ONLY_FULL_GROUP_BY SQL mode enabled, executing a stored function twice that contains a SQL query that is not valid with that mode enabled caused the server to exit. (Bug #13996639)
  • Autosizing of Performance Schema parameters could result in settings that caused excessive CPU use. (Bug #67736, Bug #15927744)
  • The optimizer sometimes chose a nonoptimimal range scan strategy when a query included a LIMIT clause. (Bug #67432, Bug #15829358)
  • Full-text searches in InnoDB tables could return incorrect results. (Bug #67257, Bug #14771282)
  • The mysql client could mishandle the delimiter command if it occurred on a line during which mysql was looking for the end of a quoted string. (Bug #64135, Bug #13639125)
  • The Performance Schema normally ignores temporary table events, but sometimes failed to properly identify a table as temporary and consequently recorded events for the table. (Bug #67098, Bug #14756887)
  • Some messages written by the server to the error log referred to the deprecated --log-slow-queries option rather than the --slow-query-log option. Similarly, the server referred to the deprecated --log option rather than the --general-log-file and --log-output options. (Bug #67892, Bug #15996571)
  • Attempting to perform an in-place upgrade from MySQL 5.1 to 5.6 causes the server to exit due to a mismatch between the privilege structures in the two series. (This is not a supported operation, but the server should not exit ungracefully.) (Bug #67319, Bug #14826854)
  • DECIMAL multiplication operations could produce significant inaccuracy. (Bug #45860, Bug #11754279)
  • Due to a thread race condition, the server could exit while attempting to read the Performance Schema threads.PROCESSLIST_INFO column. (Bug #68127, Bug #16196158)
  • The optimizer could choose an IN-to-EXISTS transformation for subquery execution in some cases when subquery materialization would be cheaper. (Bug #67511, Bug #15848521)
  • It is not permitted to use CREATE TABLE to create an NDB table with user-defined partitioning and a foreign key. However, it was possible to create an NDB table with a foreign key, then add partitioning to it using ALTER TABLE, thus creating a table which was impossible to backup/restore using mysqldump. Now the prohibition is enforced consistently. (Bug #67492, Bug #15844519)
  • For single-table DELETE or UPDATE statements, EXPLAIN displayed a type value of ALL (full-table scan access method) even if the optimizer chose to scan the table by an index access method. Now the type value is displayed as index. (Bug #67637, Bug #15892875)


Coppermine Photo Gallery





-->
Coppermine is a multi-effect scenario feature-rich, integrated web photo gallery written in PHP using GD or ImageMagick as image library with a MySQL backend.

Coppermine is a free software that you can download and install on your webspace. If you came here for a "Powered by Coppermine" link on the photo gallery, please read the Frequently Asked Questions.




-->