php install openssl extension
Как включить расширение PHP openssl для установки Composer?
Я пытаюсь установить Laravel в настройке WAMP. Я получаю предупреждение о том, что не разрешаю openssl, который я уже сделал в WAMP.
Вот скриншот сообщения.
Если вы хотите включить расширение openssl для установки Composer, сначала вам нужно проверить расположение установки PHP.
Теперь вы можете установить Composer.
Как я решил это, я пошел на установку php в пакете wamp: C:\wamp\bin\php\php5.4.12 и посмотрел php.in там.. когда я открыл его, я был потрясен тем, что строка extension=php_openssl.dll была фактически прокомментирована! Я расколол его, и он работал нормально.
У меня была та же проблема, и вот решение, которое я нашел, на вашем php.ini вам нужно сделать некоторые изменения:
Каждый из них говорит об активном расширении openssl, но в окнах вам также необходимо активировать расширение.
Для сервера WAMP комментарий, предоставленный “Энрике”, решил мою проблему.
wamp использует этот php.ini:
Но композитор использует PHP из CLI и, следовательно, читает этот файл:
Для композитора вам нужно включить расширение в
Вам нужно включить “extension = php_openssl.dll” в обоих файлах (php и apache). мой путь к файлам pc:
Если вы делаете это в Windows без одного из стеков WAMP, вот как это сделать
Откройте файл php.ini и удалите точку с запятой из этой строки (вы можете также раскомментировать другие вещи, но эта строка является единственной необходимой для Composer)
Это должно быть все, что вам нужно. Установщик Composer должен делать все, что вам нужно отсюда.
вам нужно включить расширение openssl в
то есть файл конфигурации php, который имеет его тип, имеет “настройки конфигурации” с иконкой драйвера-значка.
существует точка с запятой перед расширением openssl
удалите полуточку, и у вас будет
После редактирования “правильных” файлов (все php.ini). у меня все еще была проблема.
Моим решением было:
Добавление системной переменной: OPENSSL_CONF
значение OPENSSL_CONF должно быть файлом openssl.cnf вашей текущей версии php.
– > Перезапустить WAMP
– > должен работать сейчас
Я столкнулся с той же проблемой, но когда я был lokking для php.ini и php.exe, я нашел php.exe в C:\UwAmp\bin\php\php-5.4.15, когда php.ini в C:\UwAmp\Bin\апач.
Я просто копирую php.ini в C:\UwAmp\bin\php\php-5.4.15 и раскомментирую расширение строки = php_openssl.dll, и оно исправлено.
Перейдите к строке, которая гласит:
и удалите точку с запятой перед строкой. Перезапустите службы сервера WAMP (щелкните в панели значков > “Перезапустить все службы”
Это старый вопрос, но у меня была такая же проблема (с PHP7), и решение было, в конце концов, довольно простым. Разоблачить строку в php.ini в соответствии с другими ответами было недостаточно. Мне нужно было изменить его:
Если вы все еще не можете решить свою проблему, посмотрите на это. Это может быть решение, которое вы ищете
Php install openssl extension
The OpenSSL library also has additional requirements for normal operation at run-time. Most notably, OpenSSL requires access to a random or pseudo-random number generator; on most Unix and Unix-like platforms (including Linux), this means that it must have access to a /dev/urandom or /dev/random device.
Note: Note to Win32 Users
Additionally, if you are planning to use the key generation and certificate signing functions, you will need to install a valid openssl.cnf file on your system. We include a sample configuration file in our win32 binary distributions, in the extras/openssl directory.
In your installation, you need to decide whether to install the configuration file in the default path or whether to install it someplace else and use environmental variables (possibly on a per-virtual-host basis) to locate the configuration file. Note that it is possible to override the default path from the script using the options of the functions that require a configuration file.
Changelog
User Contributed Notes 8 notes
Having recently installed Apache2.2 with PHP 5.2.17 on my Windows 7 development machine, I want to pass along my findings about how to set things up to load the correct versions of the OpenSSL DLLs. Many people have posted elsewhere about the «DLL Hell» that results if the a wrong version is loaded.
Having verified the PHP installation, turn on the OpenSSL support by uncommenting the line
in php.ini, which you will find in the PHP directory (I’ll assume you made that c:/PHP). Next check the location of php_openssl.dll, which you should find in c:/PHP/ext. Also in php.ini find the key extension_dir, and change its value to c:/php/ext. Next, put this location on the end of your PATH (there’s no need to reboot).
At this point, when you start Apache it will attempt to load php_openssl.dll, but if your setup is anything like mine you will see an error. I prefer to start Apache manually, and the error appears in a dialog box: «The ordinal 4114 could not be located in the dynamic link library LIBEAY32.dll». (I’m not sure whether you would get this message if you started Apache as a service). The Apache log also contains an error message saying that php_openssl.dll cannot be loaded, though that message doesn’t name libeay32.dll. Welcome to DLL Hell.
Libeay32.dll enters the picture because php_openssl.dll depends on it (and also on ssleay32.dll). What I think happens is that Apache first tries to load php_openssl.dll programmatically from the path specified by the extension_dir key. But then, the loading of the so-called dependent DLLs is left to Windows’ default mechanism. If Windows finds an incompatible version of a dependent DLL, you get the error.
So clearly the fix is to ensure that the correct version of libeay32.dll is loaded. On my machine, at least three other processes have loaded various versions of this same DLL. They include the Mozy backup client, Windows Explorer (because Mozy installs support in Explorer) and the OpenOffice suite. My machine is quite different in this respect from a dedicated server on which one probably wants as few extraneous processes as possible. Presumably on a server one can follow advice that suggests copying the dlls to the system32 directory, for example. But I’m not about to mess with my other programs by making system-wide changes.
So what to do? I didn’t find the available information on how Windows searches for DLLs to be very useful, mainly because I didn’t understand it. But it does say that the first place Windows looks is «The directory from which the application loaded.»
PHP OpenSSL extension not working while installing TYPO3 6.2.2 on Windows 7
I’ve installed TYPO3 6.2.2 on Windows 7 but I got an error message as below:
PHP OpenSSL extension not working Something went wrong while trying to create a new private key for testing. Please check the integration of the PHP OpenSSL extension and if it is installed correctly.
I try to find the solution on the internet about this error but I cannnot solve this bug.
Can anyone help me to find the solution please? Thanks.
6 Answers 6
Solution that worked for me on XAMPP and Windows Vista:
Activate the PHP module openssl
Open php.ini and uncomment(delete ‘;’) in:
Double-check that the extension is enabled by running phpinfo().
Add a system environment variable «OPENSSL_CONF» with value
. assuming you installed xampp into C:\xampp.
Set path to ‘openssl.exe’, which is in C:\xampp\apache\bin
or append c:\xampp\apache\bin to the environment variable PATH (will work for every PHP script not only TYPO3)
Restart xampp
To enable OpenSSL on PHP under Windows, three steps must be taken:
enable the extension – make sure to uncomment this line in php.ini:
Add the PHP folder to the PATH environment variable of Windows:
Control Panel –> System –> Advanced System Settings –> Environment Variables.
Locate the Path variable in the System Variables block.
Prepend c:\php; in front of it, or whatever your PHP path is.
Create an additional OPENSSL_CONF environment variable for Windows which contains the full path of the OpenSSL config file of PHP:
Control Panel –> System –> Advanced System Settings –> Environment Variables.
In the System Variables block click New.
Variable name: OPENSSL_CONF
Variable value: C:\php\extras\ssl\openssl.cnf
Modify that value to match your PHP installation directory!
Restart Windows so the environment changes can take effect.
Details on PHP OpenSSL support under Windows can be found here.
On typo3 6.2.7on win7 XAMPP 1.8.3
The openSSL error’s solution was to create C:\openssl-1.0.1i-win32\ssl folder and put E:\Portables\xampp\apache\conf\openssl.cnf into it. I got a direction about it from a german website.
How I found it out (just in case versions change), in the shell on XAMPP control panel, openssl command gives
WARNING: can’t open config file: E:/Portables/xampp/apache/bin/openssl.cnf.
But adding the file there does not help. I added and removed the file.
WARNING: can’t open config file: c:/openssl-1.0.1i-win32/ssl/openssl.cnf
Add the file there, the addition to environment variable PATH can be removed now.
Adding OPENSSL_CONF also did not work for me.
Set a global environment variable OPENSSL_CONF to %ProgramFiles(x86)%\PHP\Current\extras\openssl.cnf
The following solution might only work by manual start of the Apache-Server by click on apache_start.bat inside Xampp, other use-cases and server-packages are not tested or covered.
Dealing with several versions of xampp and perhaps additional several frameworks I searched for an approach that is best fitting to the following requirements:
Based on these developer-requirements the steps I describe are a bit different than the running answers on this page:
Open the file apache_start.bat of each server-version and replace the line
by the following snippet:
SET OPENSSL_CONF=C:\xampp-x\apache\conf\openssl.cnf IF EXIST C:\xampp-x\apache\bin SET PATH=%PATH%;C:\xampp-x\apache\bin apache\bin\httpd.exe
Pay attention that you everywhere replace C:\xampp-x\ by the real path to the corresponding server.
Restart xampp either by apache_start.bat or by the xampp-control-panel.
This solution naturally works also with only one server and with the advantage having limited PATH-Variables system-wide defined.
How to install OpenSSL PHP Extension, Mbstring PHP Extension, Tokenizer PHP Extension in CentOS 7.0 x64
I m trying to configure Laravel 5.1, Laravel requirement is
PHP >= 5.5.9
OpenSSL PHP Extension
Mbstring PHP Extension
Tokenizer PHP Extension
Related
Join 1M+ other developers and:
this might help you, try to run below command using putty:
it will show you a list of available extensions then to install you need to run below command:
sudo yum install php-extension-name-here
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
openssl and tokenizer php extensions are included in php-common.x86_64 package,
you have to launch this command
$ yum install php-common.x8664 php-mbstring.x8664
This question was answered by @muhammadsufiyan:
this might help you, try to run below command using putty:
it will show you a list of available extensions then to install you need to run below command:
sudo yum install php-extension-name-here
You can see the comment here.
Related
question
Routers don’t work in my PHP / Slim project (Ubuntu, PHP, Slim, Twig, PuTTY, FileZilla, Apache)
I have been trying to host a website (php project) on Digital Ocean using Ubuntu 2.4.18 [Example link](http://)and apparently it’s pretty complicated for the inexperienced. I uploaded all files to var/www/html using FileZilla and the main router.
question
Slow page load with PHP-FPM 7.2
question
Why I’m getting thumbnails black in PHP CodeIgniter-3
I’m working on PHP CodeIgniter Script from Envato Market. I have deployed it successfully on the AWS Apache2 server but now I’m facing 3 errors: 1. Item 3Thumbnails turns black, | SS: https://prnt.sc/109awhs 2. Google Map API is not.
question
Your site is running an insecure version of PHP (7.2.24-0ubuntu0.18.04.7), which should be updated.
my WordPress dashboard was showing notification update PHP version 7.4. and current time my WordPress is running 7.3. please help how to update php version.
OpenSSL
User Contributed Notes 3 notes
I was having a heck of a time finding help on making asynchronous encryption/decryption using private key/public key systems working, and I had to have it for creating a credit card module that uses recurring billing.
You’d be a fool to use normal, ‘synchronous’ or two-way encryption for this, so the whole mcrypt library won’t help.
But, it turns out OpenSSL is extremely easy to use. yet it is so sparsely documented that it seems it would be incredibly hard.
» ;
>
else
<
echo «UNSECURE: This page is being access through an unsecure connection.
// Create the keypair
$res = openssl_pkey_new ();
echo «Private Key:
$privatekey
Public Key:
$publickey
$cleartext = ‘1234 5678 9012 3456’ ;
echo «Clear text:
$cleartext
echo «Crypt text:
$crypttext
echo «Decrypted text:
$decrypted
» ;
?>
Many thanks to other contributors in the docs for making this less painful.
For checking the status of a client certificate using OCSP, you can use this script:
Normally, you can extract the ocsp url from the client certificate. Also, an OCSP request contains only the hash of the issuer name, the hash of the issuer’s key, and the serial number of the client certificate. All three can be extracted directly from the client certificate.
In regards to the comment above:
«After generating a key pair with OpenSSL, the public key can be stored in plain text format. I then encrypted the private key itself using regular mcrypt with the human-memorizable key of my choice and converted it to ACSII using base64_encode. Then to get the private key back, I just decrypted it with mcrypt. This way I could store the encrypted private key on the server without worrying about having things stored unencrypted. «
To anyone reading this that might not be all that familiar with public key cryptography; I haven’t the slightest idea what this person is talking about, but I can tell you its an absolutely horrible idea. He might have ended up with something that «looked like a private key» insofar as it was a base64 encoded string, but he did not have a private key. The parameters that make up a public/private key pair are EXTREMELY specific and in the case of RSA rely on very large co-primes plus an even larger moduli. Its not just a base64 encoded string; and just for the record. base64 encoding is not encryption.
One of two things happened; the more likely is the whatever program he needed the certificate for realized there was something wrong with the private key, and ignored it, reverting to either a default key, or null encryption or something. The worse outcome would be if it interpreted whatever was there as legitimate; and encrypted data as if it were a a proper certificate; encrypting this way would likely provide close to zero security and I’m not even sure you could decrypt the data once encrypted. Its not worth giving much thought.
Just please; don’t do this.
You can read about pki certificate structures and attribute frameworks by pasting «T-REC-X.509-201210-I» into your favorite interwebs search widget and following the result to the International Telecommunications Union webpage, or you can refer to the numerous RFCs; 6818, 5820 being good places to start. The Internet Engineering Task Force archives all RFCs, but there are other sources as well. «IETF RFC» should be enough to get you there.
. sorry, the «spam buster» was giving me all kinds of issues.