Telepítés¶

A phpMyAdmin nem alkalmaz semmilyen speciális biztonsági eljárást a MySQL adatbázis kiszolgálónál. Ez még mindig a rendszer adminisztrátor feladata, hogy a MySQL adatbázis jogosultságait megfelelően állítsa be. A phpMyAdmin Felhasználók oldala használható erre.

Linux disztribúciók¶

A phpMyAdmin a legtöbb Linux disztribúció része. Javasolt a disztribúció csomagjainak használata, ha lehetséges - általában integrációt biztosítanak a disztribúcióhoz és automatikusan meg fogja kapni a biztonsági frissítéseket a disztribúciótól.

Debian and Ubuntu¶

Most Debian and Ubuntu versions include a phpMyAdmin package, but be aware that the configuration file is maintained in /etc/phpmyadmin and may differ in some ways from the official phpMyAdmin documentation. Specifically, it does:

Configuration of a web server (works for Apache and lighttpd).
A A phpMyAdmin beállítás tárolása létrehozása dbconfig-common használatával.
A beállító parancsfájl biztonságossá tétele, lásd: Setup script on Debian, Ubuntu and derivatives.

More specific details about installing Debian or Ubuntu packages are available in our wiki.

Lásd még

More information can be found in README.Debian (it is installed as /usr/share/doc/phpmyadmin/README.Debian with the package).

OpenSUSE¶

Az OpenSUSE már a phpMyAdmin csomaggal érkezik, egyszerűen telepítse a csomagokat az openSUSE fordítási szolgáltatásból.

Gentoo¶

Gentoo ships the phpMyAdmin package, both in a near-stock configuration as well as in a webapp-config configuration. Use emerge dev-db/phpmyadmin to install.

Mandriva¶

A Mandriva a contrib ágában szállítja a phpMyAdmin csomagot, és a szokásos Vezérlőpulton keresztül telepíthető.

Fedora¶

A Fedora szállítja a phpMyAdmin csomagot, de figyeljen arra, hogy a beállítófájlt a /etc/phpMyAdmin helyen tartják karban, és bizonyos szempontból eltérhet a hivatalos phpMyAdmin dokumentációtól.

Red Hat Enterprise Linux¶

Red Hat Enterprise Linux itself and thus derivatives like CentOS don’t ship phpMyAdmin, but the Fedora-driven repository Extra Packages for Enterprise Linux (EPEL) is doing so, if it’s enabled. But be aware that the configuration file is maintained in /etc/phpMyAdmin/ and may differ in some ways from the official phpMyAdmin documentation.

Telepítés Windowsra¶

The easiest way to get phpMyAdmin on Windows is using third party products which include phpMyAdmin together with a database and web server such as XAMPP.

További lehetőségeket a Wikipedia szócikkében talál.

Telepítés Git-ből¶

In order to install from Git, you’ll need a few supporting applications:

Git to download the source, or you can download the most recent source directly from Github
Composer
Node.js (version 14 or higher)
Yarn

You can clone current phpMyAdmin source from https://github.com/phpmyadmin/phpmyadmin.git:

git clone https://github.com/phpmyadmin/phpmyadmin.git

Additionally you need to install dependencies using Composer:

composer update

If you do not intend to develop, you can skip the installation of developer tools by invoking:

composer update --no-dev

Finally, you’ll need to use Yarn to install some JavaScript dependencies:

yarn install --production

Telepítés Composer használatával¶

You can install phpMyAdmin using the Composer tool, since 4.7.0 the releases are automatically mirrored to the default Packagist repository.

Megjegyzés

The content of the Composer repository is automatically generated separately from the releases, so the content doesn’t have to be 100% same as when you download the tarball. There should be no functional differences though.

To install phpMyAdmin simply run:

composer create-project phpmyadmin/phpmyadmin

Alternatively you can use our own composer repository, which contains the release tarballs and is available at <https://www.phpmyadmin.net/packages.json>:

composer create-project phpmyadmin/phpmyadmin --repository-url=https://www.phpmyadmin.net/packages.json --no-dev

Telepítés Docker használatával¶

phpMyAdmin comes with a Docker official image, which you can easily deploy. You can download it using:

docker pull phpmyadmin

The phpMyAdmin server will listen on port 80. It supports several ways of configuring the link to the database server, either by Docker’s link feature by linking your database container to db for phpMyAdmin (by specifying --link your_db_host:db) or by environment variables (in this case it’s up to you to set up networking in Docker to allow the phpMyAdmin container to access the database container over the network).

Docker environment variables¶

You can configure several phpMyAdmin features using environment variables:

PMA_ARBITRARY¶: Allows you to enter a database server hostname on login form.

Lásd még

$cfg['AllowArbitraryServer']

PMA_HOST¶: Hostname or IP address of the database server to use.

Lásd még

$cfg['Servers'][$i]['host']

PMA_HOSTS¶: Comma-separated hostnames or IP addresses of the database servers to use.

Megjegyzés

Used only if PMA_HOST is empty.

PMA_VERBOSE¶: Verbose name of the database server.

Lásd még

$cfg['Servers'][$i]['verbose']

PMA_VERBOSES¶: Comma-separated verbose name of the database servers.

Megjegyzés

Used only if PMA_VERBOSE is empty.

PMA_USER¶: User name to use for Config hitelesítési mód.

PMA_PASSWORD¶: Password to use for Config hitelesítési mód.

PMA_PORT¶: Port of the database server to use.

PMA_PORTS¶: Comma-separated ports of the database server to use.

Megjegyzés

Used only if PMA_PORT is empty.

PMA_SOCKET¶: Socket file for the database connection.

PMA_SOCKETS¶: Comma-separated list of socket files for the database connections.

Megjegyzés

Used only if PMA_SOCKET is empty.

PMA_ABSOLUTE_URI¶: The fully-qualified path (https://pma.example.net/) where the reverse proxy makes phpMyAdmin available.

Lásd még

$cfg['PmaAbsoluteUri']

PMA_QUERYHISTORYDB¶: When set to true, enables storing SQL history to $cfg['Servers'][$i]['pmadb']. When false, history is stored in the browser and is cleared when logging out.

Lásd még

$cfg['Servers'][$i]['history']

Lásd még

$cfg['QueryHistoryDB']

PMA_QUERYHISTORYMAX¶: When set to an integer, controls the number of history items.

Lásd még

$cfg['QueryHistoryMax']

PMA_CONTROLHOST¶: When set, this points to an alternate database host used for storing the „A phpMyAdmin beállítás tárolása” database.

Lásd még

$cfg['Servers'][$i]['controlhost']

PMA_CONTROLUSER¶: Defines the username for phpMyAdmin to use for the „A phpMyAdmin beállítás tárolása” database.

Lásd még

$cfg['Servers'][$i]['controluser']

PMA_CONTROLPASS¶: Defines the password for phpMyAdmin to use for the „A phpMyAdmin beállítás tárolása” database.

Lásd még

$cfg['Servers'][$i]['controlpass']

PMA_CONTROLPORT¶: When set, will override the default port (3306) for connecting to the control host.

Lásd még

$cfg['Servers'][$i]['controlport']

PMA_PMADB¶: When set, define the name of the database to be used for the „A phpMyAdmin beállítás tárolása” database. When not set, the advanced features are not enabled by default: they can still potentially be enabled by the user when logging in with the Nulla beállítás feature.

Megjegyzés

Suggested values: phpmyadmin or pmadb

Lásd még

$cfg['Servers'][$i]['pmadb']

HIDE_PHP_VERSION¶: If defined, this option will hide the PHP version (expose_php = Off). Set to any value (such as HIDE_PHP_VERSION=true).

UPLOAD_LIMIT¶: If set, this option will override the default value for apache and php-fpm (this will change upload_max_filesize and post_max_size values).

Megjegyzés

Format as [0-9+](K,M,G) default value is 2048K

MEMORY_LIMIT¶: If set, this option will override the phpMyAdmin memory limit $cfg['MemoryLimit'] and PHP’s memory_limit.

Megjegyzés

Format as [0-9+](K,M,G) where K is for Kilobytes, M for Megabytes, G for Gigabytes and 1K = 1024 bytes. Default value is 512M.

MAX_EXECUTION_TIME¶: If set, this option will override the maximum execution time in seconds for phpMyAdmin $cfg['ExecTimeLimit'] and PHP’s max_execution_time.

Megjegyzés

Format as [0-9+]. Default value is 600.

PMA_CONFIG_BASE64¶: If set, this option will override the default config.inc.php with the base64 decoded contents of the variable.

PMA_USER_CONFIG_BASE64¶: If set, this option will override the default config.user.inc.php with the base64 decoded contents of the variable.

PMA_UPLOADDIR¶: If set, this option will set the path where files can be saved to be available to import ($cfg['UploadDir'])

PMA_SAVEDIR¶: If set, this option will set the path where exported files can be saved ($cfg['SaveDir'])

APACHE_PORT¶: If set, this option will change the default Apache port from 80 in case you want it to run on a different port like an unprivileged port. Set to any port value (such as APACHE_PORT=8090).

By default, Süti hitelesítési mód is used, but if PMA_USER and PMA_PASSWORD are set, it is switched to Config hitelesítési mód.

Megjegyzés

The credentials you need to log in are stored in the MySQL server, in case of Docker image, there are various ways to set it (for example MYSQL_ROOT_PASSWORD when starting the MySQL container). Please check documentation for MariaDB container or MySQL container.

Customizing configuration¶

Additionally configuration can be tweaked by /etc/phpmyadmin/config.user.inc.php. If this file exists, it will be loaded after configuration is generated from above environment variables, so you can override any configuration variable. This configuration can be added as a volume when invoking docker using -v /some/local/directory/config.user.inc.php:/etc/phpmyadmin/config.user.inc.php parameters.

Note that the supplied configuration file is applied after Docker environment variables, but you can override any of the values.

For example to change the default behavior of CSV export you can use the following configuration file:

<?php
$cfg['Export']['csv_columns'] = true;

You can also use it to define server configuration instead of using the environment variables listed in Docker environment variables:

<?php
/* Override Servers array */
$cfg['Servers'] = [
    1 => [
        'auth_type' => 'cookie',
        'host' => 'mydb1',
        'port' => 3306,
        'verbose' => 'Verbose name 1',
    ],
    2 => [
        'auth_type' => 'cookie',
        'host' => 'mydb2',
        'port' => 3306,
        'verbose' => 'Verbose name 2',
    ],
];

Lásd még

See Beállítás for detailed description of configuration options.

Docker Volumes¶

You can use the following volumes to customize image behavior:

/etc/phpmyadmin/config.user.inc.php

Can be used for additional settings, see the previous chapter for more details.

/sessions/

Directory where PHP sessions are stored. You might want to share this for example when using Signon hitelesítési mód.

/www/themes/

Directory where phpMyAdmin looks for themes. By default only those shipped with phpMyAdmin are included, but you can include additional phpMyAdmin themes (see Custom Themes) by using Docker volumes.

Docker Examples¶

To connect phpMyAdmin to a given server use:

docker run --name phpmyadmin -d -e PMA_HOST=dbhost -p 8080:80 phpmyadmin:latest

To connect phpMyAdmin to more servers use:

docker run --name phpmyadmin -d -e PMA_HOSTS=dbhost1,dbhost2,dbhost3 -p 8080:80 phpmyadmin:latest

To use arbitrary server option:

docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 -e PMA_ARBITRARY=1 phpmyadmin:latest

You can also link the database container using Docker:

docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 phpmyadmin:latest

Running with additional configuration:

docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 -v /some/local/directory/config.user.inc.php:/etc/phpmyadmin/config.user.inc.php phpmyadmin:latest

Running with additional themes:

docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 -v /some/local/directory/custom/phpmyadmin/themeName/:/var/www/html/themes/themeName/ phpmyadmin:latest

Using docker-compose¶

Alternatively, you can also use docker-compose with the docker-compose.yml from <https://github.com/phpmyadmin/docker>. This will run phpMyAdmin with an arbitrary server - allowing you to specify MySQL/MariaDB server on the login page.

docker compose up -d

Customizing configuration file using docker-compose¶

You can use an external file to customize phpMyAdmin configuration and pass it using the volumes directive:

phpmyadmin:
    image: phpmyadmin:latest
    container_name: phpmyadmin
    environment:
     - PMA_ARBITRARY=1
    restart: always
    ports:
     - 8080:80
    volumes:
     - /sessions
     - ~/docker/phpmyadmin/config.user.inc.php:/etc/phpmyadmin/config.user.inc.php
     - /custom/phpmyadmin/theme/:/www/themes/theme/

Lásd még

Customizing configuration

Running behind haproxy in a subdirectory¶

When you want to expose phpMyAdmin running in a Docker container in a subdirectory, you need to rewrite the request path in the server proxying the requests.

For example, using haproxy it can be done as:

frontend http
    bind *:80
    option forwardfor
    option http-server-close

    ### NETWORK restriction
    acl LOCALNET  src 10.0.0.0/8 192.168.0.0/16 172.16.0.0/12

    # /phpmyadmin
    acl phpmyadmin  path_dir /phpmyadmin
    use_backend phpmyadmin if phpmyadmin LOCALNET

backend phpmyadmin
    mode http

    reqirep  ^(GET|POST|HEAD)\ /phpmyadmin/(.*)     \1\ /\2

    # phpMyAdmin container IP
    server localhost     172.30.21.21:80

When using traefik, something like following should work:

defaultEntryPoints = ["http"]
[entryPoints]
  [entryPoints.http]
  address = ":80"
    [entryPoints.http.redirect]
      regex = "(http:\\/\\/[^\\/]+\\/([^\\?\\.]+)[^\\/])$"
      replacement = "$1/"

[backends]
  [backends.myadmin]
    [backends.myadmin.servers.myadmin]
    url="http://internal.address.to.pma"

[frontends]
   [frontends.myadmin]
   backend = "myadmin"
   passHostHeader = true
     [frontends.myadmin.routes.default]
     rule="PathPrefixStrip:/phpmyadmin/;AddPrefix:/"

You then should specify PMA_ABSOLUTE_URI in the docker-compose configuration:

version: '2'

services:
  phpmyadmin:
    restart: always
    image: phpmyadmin:latest
    container_name: phpmyadmin
    hostname: phpmyadmin
    domainname: example.com
    ports:
      - 8000:80
    environment:
      - PMA_HOSTS=172.26.36.7,172.26.36.8,172.26.36.9,172.26.36.10
      - PMA_VERBOSES=production-db1,production-db2,dev-db1,dev-db2
      - PMA_USER=root
      - PMA_PASSWORD=
      - PMA_ABSOLUTE_URI=http://example.com/phpmyadmin/

IBM Cloud¶

One of our users has created a helpful guide for installing phpMyAdmin on the IBM Cloud platform.

Gyors telepítés¶

Choose an appropriate distribution kit from the phpmyadmin.net Downloads page. Some kits contain only the English messages, others contain all languages. We’ll assume you chose a kit whose name looks like phpMyAdmin-x.x.x-all-languages.tar.gz.
Ensure you have downloaded a genuine archive, see A phpMyAdmin kiadások ellenőrzése.
Untar or unzip the distribution (be sure to unzip the subdirectories): tar -xzvf phpMyAdmin_x.x.x-all-languages.tar.gz in your webserver’s document root. If you don’t have direct access to your document root, put the files in a directory on your local machine, and, after step 4, transfer the directory on your web server using, for example, FTP.
Gondoskodjon róla, hogy minden parancsfájlnak megfelelő tulajdonosa legyen (ha a PHP-t biztonságos módban futtatja, néhány parancsfájlnak más tulajdonosa lehet, mint a többi parancsfájlnak és ez probléma). Javaslatokért lásd a 4.2 What’s the preferred way of making phpMyAdmin secure against evil access? és a 1.26 I just installed phpMyAdmin in my document root of IIS but I get the error „No input file specified” when trying to run phpMyAdmin. pontokat.
Most be kell állítania a telepítést. Két módszer használata lehetséges. Hagyományosan a felhasználóknak kézzel kell szerkesztenie a config.inc.php másolatát, de most egy varázslószerű beállító parancsfájl áll rendelkezésre azok számára, akik a grafikus telepítést részesítik előnyben. A config.inc.php létrehozása még egy gyors módszer az elinduláshoz és szükséges néhány speciális funkcióhoz.

A fájl kézi létrehozása¶

To manually create the file, simply use your text editor to create the file config.inc.php (you can copy config.sample.inc.php to get a minimal configuration file) in the main (top-level) phpMyAdmin directory (the one that contains index.php). phpMyAdmin first loads the default configuration values and then overrides those values with anything found in config.inc.php. If the default value is okay for a particular setting, there is no need to include it in config.inc.php. You’ll probably need only a few directives to get going; a simple configuration may look like this:

<?php
// The string is a hexadecimal representation of a 32-bytes long string of random bytes.
$cfg['blowfish_secret'] = sodium_hex2bin('f16ce59f45714194371b48fe362072dc3b019da7861558cd4ad29e4d6fb13851');

$i=0;
$i++;
$cfg['Servers'][$i]['auth_type']     = 'cookie';
// if you insist on "root" having no password:
// $cfg['Servers'][$i]['AllowNoPassword'] = true;

Vagy, ha jobban tetszik az, hogy nem kell minden alkalommal begépelnie, amikor belép:

<?php

$i=0;
$i++;
$cfg['Servers'][$i]['user']          = 'root';
$cfg['Servers'][$i]['password']      = 'changeme'; // use here your password
$cfg['Servers'][$i]['auth_type']     = 'config';

Figyelem

Storing passwords in the configuration is insecure as anybody can then manipulate your database.

A lehetséges beállítási értékek teljes magyarázatát megtalálja ennek a dokumentumnak a Beállítás részében.

Using the Setup script¶

Instead of manually editing config.inc.php, you can use phpMyAdmin’s setup feature. The file can be generated using the setup and you can download it for upload to the server.

Next, open your browser and visit the location where you installed phpMyAdmin, with the /setup suffix. The changes are not saved to the server, you need to use the Download button to save them to your computer and then upload to the server.

Now the file is ready to be used. You can choose to review or edit the file with your favorite editor, if you prefer to set some advanced options that the setup script does not provide.

Az auth_type „beállítás” használata esetén ajánlott a phpMyAdmin telepítési mappájának védelme, mert a beállítás használatakor a felhasználónak nem szükséges megadni jelszót a phpMyAdmin telepítésnek eléréséhez. Ajánlott az alternatív hitelesítési mód használata, például HTTP–AUTH a .htaccess fájlban, vagy állítsa át az auth_type értékét süti (cookie) vagy http használatára. További információért nézze meg a ISPs, multi-user installations pontot, különösen a 4.4 phpMyAdmin always gives „Access denied” when using HTTP authentication. pontját.
Nyissa meg a phpMyAdmin fő mappáját a böngészőjében. A phpMyAdminnak meg kellene jelenítenie az üdvözlő oldalt és az adatbázisait vagy a belépés párbeszédablakot HTTP vagy süti hitelesítési mód használata esetén.

Setup script on Debian, Ubuntu and derivatives¶

Debian and Ubuntu have changed the way in which the setup script is enabled and disabled, in a way that single command has to be executed for either of these.

To allow editing configuration invoke:

/usr/sbin/pma-configure

To block editing configuration invoke:

/usr/sbin/pma-secure

Beállító parancsfájl openSUSE-n¶

Some openSUSE releases do not include setup script in the package. In case you want to generate configuration on these you can either download original package from <https://www.phpmyadmin.net/> or use setup script on our demo server: <https://demo.phpmyadmin.net/master/setup/>.

A phpMyAdmin kiadások ellenőrzése¶

Since July 2015 all phpMyAdmin releases are cryptographically signed by the releasing developer, who through January 2016 was Marc Delisle. His key id is 0xFEFC65D181AF644A, his PGP fingerprint is:

436F F188 4B1A 0C3F DCBF 0D79 FEFC 65D1 81AF 644A

and you can get more identification information from <https://keybase.io/lem9>.

Beginning in January 2016, the release manager is Isaac Bennetch. His key id is 0xCE752F178259BD92, and his PGP fingerprint is:

3D06 A59E CE73 0EB7 1B51 1C17 CE75 2F17 8259 BD92

and you can get more identification information from <https://keybase.io/ibennetch>.

Some additional downloads (for example themes) might be signed by Michal Čihař. His key id is 0x9C27B31342B7511D, and his PGP fingerprint is:

63CB 1DF1 EF12 CF2A C0EE 5A32 9C27 B313 42B7 511D

and you can get more identification information from <https://keybase.io/nijel>.

You should verify that the signature matches the archive you have downloaded. This way you can be sure that you are using the same code that was released. You should also verify the date of the signature to make sure that you downloaded the latest version.

Each archive is accompanied by .asc files which contain the PGP signature for it. Once you have both of them in the same folder, you can verify the signature:

$ gpg --verify phpMyAdmin-4.5.4.1-all-languages.zip.asc
gpg: Signature made Fri 29 Jan 2016 08:59:37 AM EST using RSA key ID 8259BD92
gpg: Can't check signature: public key not found

As you can see gpg complains that it does not know the public key. At this point, you should do one of the following steps:

Download the keyring from our download server, then import it with:

$ gpg --import phpmyadmin.keyring

Download and import the key from one of the key servers:

$ gpg --keyserver hkp://pgp.mit.edu --recv-keys 3D06A59ECE730EB71B511C17CE752F178259BD92
gpg: requesting key 8259BD92 from hkp server pgp.mit.edu
gpg: key 8259BD92: public key "Isaac Bennetch <bennetch@gmail.com>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)

This will improve the situation a bit - at this point, you can verify that the signature from the given key is correct but you still can not trust the name used in the key:

$ gpg --verify phpMyAdmin-4.5.4.1-all-languages.zip.asc
gpg: Signature made Fri 29 Jan 2016 08:59:37 AM EST using RSA key ID 8259BD92
gpg: Good signature from "Isaac Bennetch <bennetch@gmail.com>"
gpg:                 aka "Isaac Bennetch <isaac@bennetch.org>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 3D06 A59E CE73 0EB7 1B51  1C17 CE75 2F17 8259 BD92

The problem here is that anybody could issue the key with this name. You need to ensure that the key is actually owned by the mentioned person. The GNU Privacy Handbook covers this topic in the chapter Validating other keys on your public keyring. The most reliable method is to meet the developer in person and exchange key fingerprints, however, you can also rely on the web of trust. This way you can trust the key transitively though signatures of others, who have met the developer in person.

Once the key is trusted, the warning will not occur:

$ gpg --verify phpMyAdmin-4.5.4.1-all-languages.zip.asc
gpg: Signature made Fri 29 Jan 2016 08:59:37 AM EST using RSA key ID 8259BD92
gpg: Good signature from "Isaac Bennetch <bennetch@gmail.com>" [full]

Should the signature be invalid (the archive has been changed), you would get a clear error regardless of the fact that the key is trusted or not:

$ gpg --verify phpMyAdmin-4.5.4.1-all-languages.zip.asc
gpg: Signature made Fri 29 Jan 2016 08:59:37 AM EST using RSA key ID 8259BD92
gpg: BAD signature from "Isaac Bennetch <bennetch@gmail.com>" [unknown]

A phpMyAdmin beállítás tárolása¶

A 3.4.0 verzióban változott: Prior to phpMyAdmin 3.4.0 this was called Linked Tables Infrastructure, but the name was changed due to the extended scope of the storage.

For a whole set of additional features (Könyvjelzők, comments, SQL-history, tracking mechanism, PDF-generation, Transformations, Kapcsolatok etc.) you need to create a set of special tables. Those tables can be located in your own database, or in a central database for a multi-user installation (this database would then be accessed by the controluser, so no other user should have rights to it).

Nulla beállítás¶

In many cases, this database structure can be automatically created and configured. This is called “Zero Configuration” mode and can be particularly useful in shared hosting situations. “ZeroConf” mode is on by default, to disable set $cfg['ZeroConf'] to false.

The following three scenarios are covered by the Zero Configuration mode:

When entering a database where the configuration storage tables are not present, phpMyAdmin offers to create them from the Operations tab.
When entering a database where the tables do already exist, the software automatically detects this and begins using them. This is the most common situation; after the tables are initially created automatically they are continually used without disturbing the user; this is also most useful on shared hosting where the user is not able to edit config.inc.php and usually the user only has access to one database.
When having access to multiple databases, if the user first enters the database containing the configuration storage tables then switches to another database, phpMyAdmin continues to use the tables from the first database; the user is not prompted to create more tables in the new database.

Kézi beállítás¶

Nézzen bele az ./sql/ mappába, ahol egy create_tables.sql nevű fájlt kell találnia. (Ha Windows szervert használt, nagyon figyeljen a 1.23 I’m running MySQL on a Win32 machine. Each time I create a new table the table and column names are changed to lowercase! pontjában leírtakra).

Ha már rendelkezik ezzel az infrastruktúrával és:

frissített a MySQL 4.1.2 vagy újabbra, kérjük használja az sql/upgrade_tables_mysql_4_1_2+.sql fájlt.
frissített a phpMyAdmin 4.3.0 vagy újabbra a 2.5.0 vagy újabbról (<= 4.2.x), kérjük használja az sql/upgrade_column_info_4_3_0+.sql fájlt.
upgraded to phpMyAdmin 4.7.0 or newer from 4.3.0 or newer, please use sql/upgrade_tables_4_7_0+.sql.

majd hozza létre az új táblákat az sql/create_tables.sql importálásával.

Használhatja a phpMyAdmint a táblák létrehozásához. Kérjük legyen tisztában azzal, hogy speciális (adminisztrátori) jogosultság szükséges az adatbázisok és táblák létrehozásához és a parancsfájlt esetleg módosítani kell az adatbázis nevének függvényében.

Az sql/create_tables.sql fájl importálása után meg kell adnia a táblaneveket a config.inc.php fájlban. Az ehhez használt irányelveket megtalálja a Beállítás részben.

Szüksége lesz továbbá egy megfelelő jogosultsággal rendelkező irányító felhasználóra ($cfg['Servers'][$i]['controluser'] és $cfg['Servers'][$i]['controlpass'] beállítások) ezekhez a táblákhoz. Például a következő utasítás használatával létrehozhatja ezt:

And for any MariaDB version:

CREATE USER 'pma'@'localhost' IDENTIFIED VIA mysql_native_password USING 'pmapass';
GRANT SELECT, INSERT, UPDATE, DELETE ON `<pma_db>`.* TO 'pma'@'localhost';

For MySQL 8.0 and newer:

CREATE USER 'pma'@'localhost' IDENTIFIED WITH caching_sha2_password BY 'pmapass';
GRANT SELECT, INSERT, UPDATE, DELETE ON <pma_db>.* TO 'pma'@'localhost';

For MySQL older than 8.0:

CREATE USER 'pma'@'localhost' IDENTIFIED WITH mysql_native_password AS 'pmapass';
GRANT SELECT, INSERT, UPDATE, DELETE ON <pma_db>.* TO 'pma'@'localhost';

Note that MySQL installations with PHP older than 7.4 and MySQL newer than 8.0 may require using the mysql_native_password authentication as a workaround, see 1.45 I get an error message about unknown authentication method caching_sha2_password when trying to log in for details.

Frissítés egy korábbi verzióról¶

Figyelem

Never extract the new version over an existing installation of phpMyAdmin, always first remove the old files keeping just the configuration.

This way, you will not leave any old or outdated files in the directory, which can have severe security implications or can cause various breakages.

Egyszerűen másolja át a config.inc.php fájlt a korábbi telepítésből az újonnan kicsomagoltba. A korábbi verziókban lévő beállítófájlok finomhangolásra szorulhatnak, ugyanis néhány lehetőség megváltozhatott vagy eltávolításra kerülhetett. A PHP 5.3 vagy későbbi verzióval való kompatibilitás miatt távolítsa el a set_magic_quotes_runtime(0); utasítást, amely a beállítófájl vége felé található.

The complete upgrade can be performed in a few simple steps:

Download the latest phpMyAdmin version from <https://www.phpmyadmin.net/downloads/>.
Rename existing phpMyAdmin folder (for example to phpmyadmin-old).
Unpack freshly downloaded phpMyAdmin to the desired location (for example phpmyadmin).
Copy config.inc.php` from old location (phpmyadmin-old) to the new one (phpmyadmin).
Test that everything works properly.
Remove backup of a previous version (phpmyadmin-old).

Ha frissítette a MySQL szervert a korábbi 4.1.2 verzióról az 5.x vagy újabb verzióra, és ha használja a phpMyAdmin beállítás tárolását, akkor le kell futtatnia az sql/upgrade_tables_mysql_4_1_2+.sql helyen található SQL parancsfájlt.

Ha frissítette a phpMyAdmint 4.3.0 vagy újabb verzióra a 2.5.0 vagy újabb (<= 4.2.x) verzióról, és ha használja a phpMyAdmin beállítás tárolását, le kell futtatnia az sql/upgrade_column_info_4_3_0+.sql fájlban található SQL parancsfájlt.

Do not forget to clear the browser cache and to empty the old session by logging out and logging in again.

Hitelesítési módok használata¶

HTTP and cookie authentication modes are recommended in a multi-user environment where you want to give users access to their own database and don’t want them to play around with others. Nevertheless, be aware that MS Internet Explorer seems to be really buggy about cookies, at least till version 6. Even in a single-user environment, you might prefer to use HTTP or cookie mode so that your user/password pair are not in clear in the configuration file.

HTTP and cookie authentication modes are more secure: the MySQL login information does not need to be set in the phpMyAdmin configuration file (except possibly for the $cfg['Servers'][$i]['controluser']). However, keep in mind that the password travels in plain text unless you are using the HTTPS protocol. In cookie mode, the password is stored, encrypted with the AES algorithm, in a temporary cookie.

Then each of the true users should be granted a set of privileges on a set of particular databases. Normally you shouldn’t give global privileges to an ordinary user unless you understand the impact of those privileges (for example, you are creating a superuser). For example, to grant the user real_user with all privileges on the database user_base:

GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';

Mit tehet most a felhasználó, ha teljes egészen a MySQL felhasználókezelő rendszerével vezérlik. HTTP vagy süti hitelesítési móddal nem kell kitöltenie a felhasználó/jelszó mezőket a $cfg['Servers'] tömbön belül.

Lásd még

1.32 Can I use HTTP authentication with IIS?, 1.35 Can I use HTTP authentication with Apache CGI?, 4.1 I’m an ISP. Can I setup one central copy of phpMyAdmin or do I need to install it for each customer?, 4.2 What’s the preferred way of making phpMyAdmin secure against evil access?, 4.3 I get errors about not being able to include a file in /lang or in /libraries.

HTTP hitelesítési mód¶

A HTTP alap hitelesítési eljárást használja, és lehetővé teszi az érvényes MySQL felhasználóként való bejelentkezést.
Támogatja a legtöbb PHP konfigurációt. A CGI PHP-t használó IIS (ISAPI) támogatáshoz nézze meg a 1.32 Can I use HTTP authentication with IIS? pontját, Apache CGI használatához nézze meg a 1.35 Can I use HTTP authentication with Apache CGI? pontját.
When PHP is running under Apache’s mod_proxy_fcgi (e.g. with PHP-FPM), Authorization headers are not passed to the underlying FCGI application, such that your credentials will not reach the application. In this case, you can add the following configuration directive:
```
SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
```
Lásd még a 4.4 phpMyAdmin always gives „Access denied” when using HTTP authentication. pontját arról, hogy ne használja a .htaccess mechanizmust a «HTTP» hitelesítési mód mellett.

Megjegyzés

There is no way to do proper logout in HTTP authentication, most browsers will remember credentials until there is no different successful authentication. Because of this, this method has a limitation that you can not login with the same user after logout.

Signon hitelesítési mód¶

This mode is a convenient way of using credentials from another application to authenticate to phpMyAdmin to implement a single signon solution.
The other application has to store login information into session data (see $cfg['Servers'][$i]['SignonSession'] and $cfg['Servers'][$i]['SignonCookieParams']) or you need to implement script to return the credentials (see $cfg['Servers'][$i]['SignonScript']).
Ha a hitelesítési adatok nem érhetők el, akkor a felhasználó át lesz irányítva a $cfg['Servers'][$i]['SignonURL'] címre, ahol le kell kezelnie a bejelentkezési folyamatot.

Elérhető egy nagyon egyszerű példa a munkamenetbe mentett hitelesítési adatokról az examples/signon.php fájlban:

<?php
/**
 * Single signon for phpMyAdmin
 *
 * This is just example how to use session based single signon with
 * phpMyAdmin, it is not intended to be perfect code and look, only
 * shows how you can integrate this functionality in your application.
 */

declare(strict_types=1);

/* Use cookies for session */
ini_set('session.use_cookies', 'true');
/* Change this to true if using phpMyAdmin over https */
$secureCookie = false;
/* Need to have cookie visible from parent directory */
session_set_cookie_params(0, '/', '', $secureCookie, true);
/* Create signon session */
$sessionName = 'SignonSession';
session_name($sessionName);
// Uncomment and change the following line to match your $cfg['SessionSavePath']
//session_save_path('/foobar');
@session_start();

/* Was data posted? */
if (isset($_POST['user'])) {
    /* Store there credentials */
    $_SESSION['PMA_single_signon_user'] = $_POST['user'];
    $_SESSION['PMA_single_signon_password'] = $_POST['password'];
    $_SESSION['PMA_single_signon_host'] = $_POST['host'];
    $_SESSION['PMA_single_signon_port'] = $_POST['port'];
    /* Update another field of server configuration */
    $_SESSION['PMA_single_signon_cfgupdate'] = ['verbose' => 'Signon test'];
    $_SESSION['PMA_single_signon_HMAC_secret'] = hash('sha1', uniqid(strval(random_int(0, mt_getrandmax())), true));
    $id = session_id();
    /* Close that session */
    @session_write_close();
    /* Redirect to phpMyAdmin (should use absolute URL here!) */
    header('Location: ../index.php');
} else {
    /* Show simple form */
    header('Content-Type: text/html; charset=utf-8');

    echo '<?xml version="1.0" encoding="utf-8"?>' . "\n";
    echo '<!DOCTYPE HTML>
<html lang="en" dir="ltr">
<head>
<link rel="icon" href="../favicon.ico" type="image/x-icon">
<link rel="shortcut icon" href="../favicon.ico" type="image/x-icon">
<meta charset="utf-8">
<title>phpMyAdmin single signon example</title>
</head>
<body>';

    if (isset($_SESSION['PMA_single_signon_error_message'])) {
        echo '<p class="error">';
        echo $_SESSION['PMA_single_signon_error_message'];
        echo '</p>';
    }

    echo '<form action="signon.php" method="post">
Username: <input type="text" name="user" autocomplete="username" spellcheck="false"><br>
Password: <input type="password" name="password" autocomplete="current-password" spellcheck="false"><br>
Host: (will use the one from config.inc.php by default)
<input type="text" name="host"><br>
Port: (will use the one from config.inc.php by default)
<input type="text" name="port"><br>
<input type="submit">
</form>
</body>
</html>';
}

Alternatively, you can also use this way to integrate with OpenID as shown in examples/openid.php:

<?php
/**
 * Single signon for phpMyAdmin using OpenID
 *
 * This is just example how to use single signon with phpMyAdmin, it is
 * not intended to be perfect code and look, only shows how you can
 * integrate this functionality in your application.
 *
 * It uses OpenID pear package, see https://pear.php.net/package/OpenID
 *
 * User first authenticates using OpenID and based on content of $AUTH_MAP
 * the login information is passed to phpMyAdmin in session data.
 */

declare(strict_types=1);

if (false === @include_once 'OpenID/RelyingParty.php') {
    exit;
}

/* Change this to true if using phpMyAdmin over https */
$secureCookie = false;

/**
 * Map of authenticated users to MySQL user/password pairs.
 */
$authMap = ['https://launchpad.net/~username' => ['user' => 'root', 'password' => '']];

// phpcs:disable PSR1.Files.SideEffects,Squiz.Functions.GlobalFunction

/**
 * Simple function to show HTML page with given content.
 *
 * @param string $contents Content to include in page
 */
function Show_page(string $contents): void
{
    header('Content-Type: text/html; charset=utf-8');

    echo '<?xml version="1.0" encoding="utf-8"?>' . "\n";
    echo '<!DOCTYPE HTML>
<html lang="en" dir="ltr">
<head>
<link rel="icon" href="../favicon.ico" type="image/x-icon">
<link rel="shortcut icon" href="../favicon.ico" type="image/x-icon">
<meta charset="utf-8">
<title>phpMyAdmin OpenID signon example</title>
</head>
<body>';

    if (isset($_SESSION['PMA_single_signon_error_message'])) {
        echo '<p class="error">' . $_SESSION['PMA_single_signon_message'] . '</p>';
        unset($_SESSION['PMA_single_signon_message']);
    }

    echo $contents;
    echo '</body></html>';
}

/**
 * Display error and exit
 *
 * @param Exception $e Exception object
 */
function Die_error(Throwable $e): void
{
    $contents = "<div class='relyingparty_results'>\n";
    $contents .= '<pre>' . htmlspecialchars($e->getMessage()) . "</pre>\n";
    $contents .= "</div class='relyingparty_results'>";
    Show_page($contents);
    exit;
}

// phpcs:enable

/* Need to have cookie visible from parent directory */
session_set_cookie_params(0, '/', '', $secureCookie, true);
/* Create signon session */
$sessionName = 'SignonSession';
session_name($sessionName);
@session_start();

// Determine realm and return_to
$base = 'http';
if (isset($_SERVER['HTTPS']) && $_SERVER['HTTPS'] === 'on') {
    $base .= 's';
}

$base .= '://' . $_SERVER['SERVER_NAME'] . ':' . $_SERVER['SERVER_PORT'];

$realm = $base . '/';
$returnTo = $base . dirname($_SERVER['PHP_SELF']);
if ($returnTo[strlen($returnTo) - 1] !== '/') {
    $returnTo .= '/';
}

$returnTo .= 'openid.php';

/* Display form */
if ((! count($_GET) && ! count($_POST)) || isset($_GET['phpMyAdmin'])) {
    /* Show simple form */
    $content = '<form action="openid.php" method="post">
OpenID: <input type="text" name="identifier"><br>
<input type="submit" name="start">
</form>';
    Show_page($content);
    exit;
}

/* Grab identifier */
$identifier = null;
if (isset($_POST['identifier']) && is_string($_POST['identifier'])) {
    $identifier = $_POST['identifier'];
} elseif (isset($_SESSION['identifier']) && is_string($_SESSION['identifier'])) {
    $identifier = $_SESSION['identifier'];
}

/* Create OpenID object */
try {
    $o = new OpenID_RelyingParty($returnTo, $realm, $identifier);
} catch (Throwable $e) {
    Die_error($e);
}

/* Redirect to OpenID provider */
if (isset($_POST['start'])) {
    try {
        $authRequest = $o->prepare();
    } catch (Throwable $e) {
        Die_error($e);
    }

    $url = $authRequest->getAuthorizeURL();

    header('Location: ' . $url);
    exit;
}

/* Grab query string */
if (! count($_POST)) {
    [, $queryString] = explode('?', $_SERVER['REQUEST_URI']);
} else {
    // Fetch the raw query body
    $queryString = file_get_contents('php://input');
}

/* Check reply */
try {
    $message = new OpenID_Message($queryString, OpenID_Message::FORMAT_HTTP);
} catch (Throwable $e) {
    Die_error($e);
}

$id = $message->get('openid.claimed_id');

if (empty($id) || ! isset($authMap[$id])) {
    Show_page('<p>User not allowed!</p>');
    exit;
}

$_SESSION['PMA_single_signon_user'] = $authMap[$id]['user'];
$_SESSION['PMA_single_signon_password'] = $authMap[$id]['password'];
$_SESSION['PMA_single_signon_HMAC_secret'] = hash('sha1', uniqid(strval(random_int(0, mt_getrandmax())), true));
session_write_close();
/* Redirect to phpMyAdmin (should use absolute URL here!) */
header('Location: ../index.php');

If you intend to pass the credentials using some other means than, you have to implement wrapper in PHP to get that data and set it to $cfg['Servers'][$i]['SignonScript']. There is a very minimal example in examples/signon-script.php:

<?php
/**
 * Single signon for phpMyAdmin
 *
 * This is just example how to use script based single signon with
 * phpMyAdmin, it is not intended to be perfect code and look, only
 * shows how you can integrate this functionality in your application.
 */

declare(strict_types=1);

// phpcs:disable Squiz.Functions.GlobalFunction

/**
 * This function returns username and password.
 *
 * It can optionally use configured username as parameter.
 *
 * @param string $user User name
 *
 * @return array<int,string>
 */
function get_login_credentials(string $user): array
{
    /* Optionally we can use passed username */
    if (! empty($user)) {
        return [$user, 'password'];
    }

    /* Here we would retrieve the credentials */
    return ['root', ''];
}

Lásd még

$cfg['Servers'][$i]['auth_type'], $cfg['Servers'][$i]['SignonSession'], $cfg['Servers'][$i]['SignonCookieParams'], $cfg['Servers'][$i]['SignonScript'], $cfg['Servers'][$i]['SignonURL'], Example for signon authentication

Config hitelesítési mód¶

Ez a mód néha a legkevésbé biztonságos, mert megkövetelni a $cfg['Servers'][$i]['user'] és a $cfg['Servers'][$i]['password'] mezők kitöltését (és ez azt eredményezi, hogy bárki, aki olvasni tudja a config.inc.php fájlt, az megismerheti a felhasználónevet és a jelszót).
A ISPs, multi-user installations részben van egy bejegyzést, amely elmagyarázza, hogy hogyan védje meg a beállítófájlt.
A nagyobb biztonság érdekében érdemes figyelembe vennie ebben a módban a kiszolgáló hitelesítés $cfg['Servers'][$i]['AllowDeny']['order'] és $cfg['Servers'][$i]['AllowDeny']['rules'] beállítás irányelveit.
A süti és http módokkal ellentétben nem igényli a felhasználótól a bejelentkezést a phpMyAdmin oldal első betöltődésekor. Ez szándékosan van így, de lehetővé teszi bármely felhasználónak a telepítéshez való hozzáférést. Néhány korlátozási módszer használata ajánlott, különösen a .htaccess fájl a HTTP-AUTH irányelvvel vagy a bejövő HTTP kérések tiltása, amelyhez egy router vagy egy tűzfal elegendő (mindkettő túlmutat ezen a kézikönyvön, de könnyen rákereshető a Google segítségével).

A phpMyAdmin telepítés biztonságossá tétele¶

A phpMyAdmin csapata mindent megtesz az alkalmazás biztonságossá tételében, viszont mindig van mód a telepítést még biztonságosabbá tenni:

Follow our Security announcements and upgrade phpMyAdmin whenever new vulnerability is published.
Serve phpMyAdmin on HTTPS only. Preferably, you should use HSTS as well, so that you’re protected from protocol downgrade attacks.
Ensure your PHP setup follows recommendations for production sites, for example display_errors should be disabled.
Remove the test directory from phpMyAdmin, unless you are developing and need a test suite.
Távolítsa el a setup könyvtárat a phpMyAdminból, valószínűleg nem fogja használni a kezdeti beállítás után.
Megfelelően válassza ki a hitelesítési módot - valószínűleg a Süti hitelesítési mód a legjobb választás a megosztott tárhelynél.
Deny access to auxiliary files in ./libraries/ or ./templates/ subfolders in your webserver configuration. Such configuration prevents from possible path exposure and cross side scripting vulnerabilities that might happen to be found in that code. For the Apache webserver, this is often accomplished with a .htaccess file in those directories.
Deny access to temporary files, see $cfg['TempDir'] (if that is placed inside your web root, see also Web server upload/save/import directories.
It is generally a good idea to protect a public phpMyAdmin installation against access by robots as they usually can not do anything good there. You can do this using robots.txt file in the root of your webserver or limit access by web server configuration, see 1.42 How can I prevent robots from accessing phpMyAdmin?.
In case you don’t want all MySQL users to be able to access phpMyAdmin, you can use $cfg['Servers'][$i]['AllowDeny']['rules'] to limit them or $cfg['Servers'][$i]['AllowRoot'] to deny root user access.
Enable Two-factor authentication for your account.
Consider hiding phpMyAdmin behind an authentication proxy, so that users need to authenticate prior to providing MySQL credentials to phpMyAdmin. You can achieve this by configuring your web server to request HTTP authentication. For example in Apache this can be done with:
```
AuthType Basic
AuthName "Restricted Access"
AuthUserFile /usr/share/phpmyadmin/passwd
Require valid-user
```
Once you have changed the configuration, you need to create a list of users which can authenticate. This can be done using the htpasswd utility:
```
htpasswd -c /usr/share/phpmyadmin/passwd username
```
Ha automatikus támadásoktól tart, akkor a Captcha engedélyezése megoldás lehet erre a $cfg['CaptchaLoginPublicKey'] és $cfg['CaptchaLoginPrivateKey'] beállításokkal.
Failed login attempts are logged to syslog (if available, see $cfg['AuthLog']). This can allow using a tool such as fail2ban to block brute-force attempts. Note that the log file used by syslog is not the same as the Apache error or access log files.
In case you’re running phpMyAdmin together with other PHP applications, it is generally advised to use separate session storage for phpMyAdmin to avoid possible session-based attacks against it. You can use $cfg['SessionSavePath'] to achieve this.

Using SSL for connection to database server¶

It is recommended to use SSL when connecting to remote database server. There are several configuration options involved in the SSL setup:

$cfg['Servers'][$i]['ssl']: Defines whether to use SSL at all. If you enable only this, the connection will be encrypted, but there is not authentication of the connection - you can not verify that you are talking to the right server.
$cfg['Servers'][$i]['ssl_key'] and $cfg['Servers'][$i]['ssl_cert']: This is used for authentication of client to the server.
$cfg['Servers'][$i]['ssl_ca'] and $cfg['Servers'][$i]['ssl_ca_path']: The certificate authorities you trust for server certificates. This is used to ensure that you are talking to a trusted server.
$cfg['Servers'][$i]['ssl_verify']: This configuration disables server certificate verification. Use with caution.

When the database server is using a local connection or private network and SSL can not be configured you can use $cfg['MysqlSslWarningSafeHosts'] to explicitly list the hostnames that are considered secure.

Lásd még

Google Cloud SQL with SSL, Amazon RDS Aurora with SSL, $cfg['Servers'][$i]['ssl'], $cfg['Servers'][$i]['ssl_key'], $cfg['Servers'][$i]['ssl_cert'], $cfg['Servers'][$i]['ssl_ca'], $cfg['Servers'][$i]['ssl_ca_path'], $cfg['Servers'][$i]['ssl_ciphers'], $cfg['Servers'][$i]['ssl_verify']

Known issues¶

Users with column-specific privileges are unable to „Browse”¶

If a user has only column-specific privileges on some (but not all) columns in a table, „Browse” will fail with an error message.

As a workaround, a bookmarked query with the same name as the table can be created, this will run when using the „Browse” link instead. Issue 11922.

Trouble logging back in after logging out using «http» authentication¶

When using the «http» auth_type, it can be impossible to log back in (when the logout comes manually or after a period of inactivity). Issue 11898.

Telepítés¶

Linux disztribúciók¶

Debian and Ubuntu¶

OpenSUSE¶

Gentoo¶

Mandriva¶

Fedora¶

Red Hat Enterprise Linux¶

Telepítés Windowsra¶

Telepítés Git-ből¶

Telepítés Composer használatával¶

Telepítés Docker használatával¶

Docker environment variables¶

Customizing configuration¶

Docker Volumes¶

Docker Examples¶

Using docker-compose¶

Customizing configuration file using docker-compose¶

Running behind haproxy in a subdirectory¶

IBM Cloud¶

Gyors telepítés¶

A fájl kézi létrehozása¶

Using the Setup script¶

Setup script on Debian, Ubuntu and derivatives¶

Beállító parancsfájl openSUSE-n¶

A phpMyAdmin kiadások ellenőrzése¶

A phpMyAdmin beállítás tárolása¶

Nulla beállítás¶

Kézi beállítás¶

Frissítés egy korábbi verzióról¶

Hitelesítési módok használata¶

HTTP hitelesítési mód¶

Süti hitelesítési mód¶

Signon hitelesítési mód¶

Config hitelesítési mód¶

A phpMyAdmin telepítés biztonságossá tétele¶

Using SSL for connection to database server¶

Known issues¶

Users with column-specific privileges are unable to „Browse”¶

Trouble logging back in after logging out using «http» authentication¶