profile
viewpoint
Mathieu VEDIE mvedie DREAMCENTURY ENTERTAINMENT

mvedie/currency-detector 0

Class to detect the currency from any string

mvedie/formation-2 0

Formation PHP Matthieu

mvedie/Gritter 0

A small growl-like notification plugin for jQuery

mvedie/gritter-builder 0

PHP Builder for Gritter JS options

mvedie/jquery-observe 0

Observe DOM mutations with jQuery

mvedie/jquery.fn.renameTag 0

Simply rename your HTML-tags with one call.

issue closedmicrosoft/msphpsql

"invalid column number in pdo_sqlsrv_stmt_get_col_data" and PHP crash when using variable length tables in query

+## PHP Driver version or file name +Driver version 5.8.0 +## SQL Server version +SQL Server 2016 +## Client operating system +Windows Server 2016 Standard +## PHP version +7.3.10 +## Microsoft ODBC Driver version +2017.175.01.01 +## Table schema SQL:

CREATE OR ALTER PROCEDURE [dbo].[pdobugtest] (@level int) AS
BEGIN
    IF @level = 1
        SELECT 1 Col1
              ,1 Col2
              ,1 Col3
              ,1 Col4
              ,1 Col5
              ,1 Col6
              ,1 Col7
              ,1 Col8
              ,1 Col9
              ,1 Col10
              ,1 Col11
              ,1 Col12
              ,1 Col13
              ,1 Col14
              ,1 Col15
              ,1 Col16
              ,1 Col17
              ,1 Col18
              ,1 Col19
              ,1 Col20

    IF @Level = 2
        SELECT 1 Col1
              ,1 Col2
              ,1 Col3
              ,1 Col4
              ,1 Col5
              ,1 Col6
              ,1 Col7
              ,1 Col8
              ,1 Col9
              ,1 Col10
              ,1 Col11
              ,1 Col12
              ,1 Col13
              ,1 Col14

END
GO

+## Problem description

It appears that if you have a stored procedure that returns different numbers of columns based on parameters, the run with the higher number of columns causes PHP to crash. If I recreate the statement each time I need to use it, this error goes away and the script succeeds.

+## Expected behavior and actual behavior

Expected behaviour - both runs succeed and return results Actual behaviour - first run succeeds, second causes PHP to crash

+## Repro code or steps to reproduce

  1. Create stored procedure

  2. Change the DSN to match your environment and run PHP code below:

<?php

$db=new PDO('sqlsrv:Server=SERVER\INSTANCE;Database=dbname;MultipleActiveResultSets=0;', NULL, NULL);

$x=$db->prepare(
    "exec pdobugtest ?"
);
$x->execute([2]);
$x->fetch();
$x->closeCursor();

$x->execute([1]);
$x->fetch();
$x->closeCursor();

closed time in a day

thirdwheel

issue commentmicrosoft/msphpsql

"invalid column number in pdo_sqlsrv_stmt_get_col_data" and PHP crash when using variable length tables in query

Thanks, I had a suspicion that was what was happening based on my reading of that part of the code. Unfortunately using direct queries is out of the question due to utilising user inputs. I'll stick to my current approach - recreating the prepared statement on each run to clear the stored metadata.

thirdwheel

comment created time in a day

issue commentmicrosoft/msphpsql

"invalid column number in pdo_sqlsrv_stmt_get_col_data" and PHP crash when using variable length tables in query

Hi @thirdwheel

While it's a good idea to use prepared statements, your approach is actually problematic, mainly because different number of columns is returned depending on your input.

FYI, in pdo_stmt.c line 506, after the first execution, the stmt object keeps the resultset's columns and their metadata, so the second time you execute again they would not be re-populated. Not only that, since the number of columns is now 20, when the stmt object is going through its destruction phase, it thinks there are 20 column objects to be destroyed. I tested this in a debugging mode it actually crashed at the 15th column, as you can easily imagine.

In short, you're probably better off with direct queries because the entire column metadata after the first execution is basically useless to be kept for next execution.

thirdwheel

comment created time in 3 days

issue commentmicrosoft/msphpsql

[Microsoft][ODBC Driver 17 for SQL Server]Encryption not supported on the client

Thanks @mbiebl , yes odbc trace please. Also, if possible, test with a couple of different versions of ODBC driver. We want to know if this problem was introduced lately or already fixed.

The error/exception was triggered when instantiating the PDO object right at the beginning of the application

During your investigation, how often did you instantiate the PDO object in your application?

mbiebl

comment created time in 3 days

issue commentmicrosoft/msphpsql

[Microsoft][ODBC Driver 17 for SQL Server]Encryption not supported on the client

The VM is currently down, which means I'll have to wait until I can run further diagnostics. Besides the ODBC tracing, is there something else which you would want me to try?

mbiebl

comment created time in 3 days

issue commentmicrosoft/msphpsql

[Microsoft][ODBC Driver 17 for SQL Server]Encryption not supported on the client

Thanks for the php script. Once you have connected, do you disconnect (exit the script, for example)? Is it the same script you run again and again in a loop? Does the script do anything else?

The application is based on SabreDAV (unfortunately I can't easily share it). But https://github.com/sabre-io/dav/blob/master/examples/addressbookserver.php should give you an idea. Instead of sqlite, we use sqlsrv

mbiebl

comment created time in 3 days

issue commentmicrosoft/msphpsql

[Microsoft][ODBC Driver 17 for SQL Server]Encryption not supported on the client

Do you connect to a SQL Server instance in that Windows VM on Azure or do you connect to an Azure SQL Server (also known as SQL Server on Azure)?

The latter. The problem only happens with an Azure SQL Server

mbiebl

comment created time in 3 days

issue commentmicrosoft/msphpsql

"invalid column number in pdo_sqlsrv_stmt_get_col_data" and PHP crash when using variable length tables in query

Thanks @thirdwheel for the report. We will get back to you.

thirdwheel

comment created time in 3 days

issue commentmicrosoft/msphpsql

[Microsoft][ODBC Driver 17 for SQL Server]Encryption not supported on the client

Thanks @mbiebl for the prompt response.

when instantiating the PDO object Yes that's when the driver attempts to make a connection.

We had customers who reported this problem to us, so I tried to reproduce the issue inside a Windows VM on Azure. The tests ran for several weeks. With MARS turned off, we didn't hit the problem anymore. With MARS enabled it usually took at most a day or two before such an error happened (we put the server under load using a jmeter test). Now, this could be very much specific to my test scenario, but at least there the results were consistent.

Do you connect to a SQL Server instance in that Windows VM on Azure or do you connect to an Azure SQL Server (also known as SQL Server on Azure)? Thanks for the php script. Once you have connected, do you disconnect (exit the script, for example)? Is it the same script you run again and again in a loop? Does the script do anything else?

At any rate, please provide additional details of your test scenario, if possible. Thanks!

mbiebl

comment created time in 3 days

issue commentmicrosoft/msphpsql

[Microsoft][ODBC Driver 17 for SQL Server]Encryption not supported on the client

Hi @yitam, thanks for your reply.

Hi @mbiebl the details in your report are much appreciated, and we have more questions:

  1. You mentioned about turning off MARS could mitigate this issue. Is this consistent? Or the problem happens less frequently?

We had customers who reported this problem to us, so I tried to reproduce the issue inside a Windows VM on Azure. The tests ran for several weeks. With MARS turned off, w didn't hit the problem anymore. With MARS enabled it usually took at most a day or two before such an error happened. Now, this could be very much specific to my test scenario, but at least there the results were consistent.

  1. Where in your php script does this happen? Making connection to AzureSQL?

The error/exception was triggered when instantiating the PDO object right at the beginning of the application, i.e. at the $pdo = new \PDO($db_dsn, $db_login, $db_pass); line:


$db_dsn = 'sqlsrv:Server='.$db_host.';Database='.$db_name;

try {
    $pdo = new \PDO($db_dsn, $db_login, $db_pass);
    $pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
} catch(PDOException $e) {
    error_log("Failure while creating PDO context:" . $e->getMessage());
    // Set HTTP response to 503: Service Unavailable
    http_response_code(503);
    // Generate a new exception which strips off the stack trace, as the stack
    // trace contains the login data and we don't want to log/show that information.
    throw new \PDOException($e->getMessage());
}
  1. What's your typical connection string? Please use fake credentials.

See above

  1. Is it possible to provide ODBC trace up to the point of failure?
  2. Have you tried other previous or latest ODBC drivers?

If you're going to provide an ODBC trace, you'll need to modify your pdo_sqlsrv script by adding TraceOn=1;, like this:

$conn = new PDO('sqlsrv:Server=xxx.xxx.xxx.xxx;TraceOn=1;Database=myDB', 'myID', 'myPwd');

To help us investigate or reproduce this issue, we welcome any additional repro scenario and/or steps.

I tried ODBC tracing via TraceOn=1, but wasn't able to gather anything (meaningful). I suspect because the error already happens when the PDO object is created. At least I didn't find anything relevant in the PHP log.

mbiebl

comment created time in 3 days

issue commentmicrosoft/msphpsql

[Microsoft][ODBC Driver 17 for SQL Server]Encryption not supported on the client

Hi @mbiebl the details in your report are much appreciated, and we have more questions:

  1. You mentioned about turning off MARS could mitigate this issue. Is this consistent? Or the problem happens less frequently?
  2. Where in your php script does this happen? Making connection to AzureSQL?
  3. What's your typical connection string? Please use fake credentials.
  4. Is it possible to provide ODBC trace up to the point of failure?
  5. Have you tried other previous or latest ODBC drivers?

If you're going to provide an ODBC trace, you'll need to modify your pdo_sqlsrv script by adding TraceOn=1;, like this:

$conn = new PDO('sqlsrv:Server=xxx.xxx.xxx.xxx;TraceOn=1;Database=myDB', 'myID', 'myPwd');

To help us investigate or reproduce this issue, we welcome any additional repro scenario and/or steps.

mbiebl

comment created time in 3 days

issue commentmicrosoft/msphpsql

PHP8 support

Yes @onecentlin we know. We plan to release another preview, tentatively.

brainfoolong

comment created time in 3 days

PR closed ziadoz/awesome-php

Add Steward

Steward is CLI test runner and set of libraries, integrating facebook/php-webdriver library to PHPUnit.

It sets-up the browser, plan test order and execute functional PHPUnit tests in parallel etc. Its specific features are also described on project homepage.

+1 -0

4 comments

1 changed file

OndraM

pr closed time in 3 days

issue openedmicrosoft/msphpsql

[Microsoft][ODBC Driver 17 for SQL Server]Encryption not supported on the clien

PHP Driver version or file name

5.8.0 (php_pdo_sqlsrv_74_nts_x86.dll)

SQL Server version

Azure SQL

Client operating system

Windows Server, using IIS/fastcgi

PHP version

7.4.9 (x86, NTS)

Microsoft ODBC Driver version

2017.175.02.01

Problem description

Our software is based on SabreDAV [1], running on Windows/IIS. When using SQLExpress as backend, everything is working fine. As soon as we start using AzureSQL, we encounter the following error from time to time. This is from the PHP error log:

[24-Aug-2020 19:17:38 UTC] Failure while creating PDO context:SQLSTATE[08001]: [Microsoft][ODBC Driver 17 for SQL Server]Encryption not supported on the client.

[24-Aug-2020 19:17:38 UTC] PHP Fatal error:  Uncaught PDOException: SQLSTATE[08001]: [Microsoft][ODBC Driver 17 for SQL Server]Encryption not supported on the client. in ..\web\server.php:93

We tried to narrow down the problem. Our findings so far:

  • It only happens with AzureSQL, but not SQLExpress
  • It doesn't happen always, but once the php-cgi.exe process gets into this (broken) state, it will trigger the error on every request. This continues until IIS decides to recycle the php-cgi.exe process. Sometimes, the server runs a couple of days without triggering the failure, sometimes the failure happens a couple of times per day.
  • Using MultipleActiveResultSets=false we can mitigate this failure.

We are quite puzzled at this point and would appreciate any help in further investigating this failure.

[1] https://sabre.io/

created time in 3 days

issue commentmicrosoft/msphpsql

PHP8 support

PHP 8.0.0 released on 26 Nov 2020.

brainfoolong

comment created time in 3 days

issue commentmicrosoft/msphpsql

"invalid column number in pdo_sqlsrv_stmt_get_col_data" and PHP crash when using variable length tables in query

Addendum - this issue still persists if I update to 5.9.0 preview 1

thirdwheel

comment created time in 3 days

issue openedmicrosoft/msphpsql

"invalid column number in pdo_sqlsrv_stmt_get_col_data" and PHP crash when using variable length tables in query

+## PHP Driver version or file name +Driver version 5.8.0 +## SQL Server version +SQL Server 2016 +## Client operating system +Windows Server 2016 Standard +## PHP version +7.3.10 +## Microsoft ODBC Driver version +2017.175.01.01 +## Table schema SQL:

CREATE OR ALTER PROCEDURE [dbo].[pdobugtest] (@level int) AS
BEGIN
    IF @level = 1
        SELECT 1 Col1
              ,1 Col2
              ,1 Col3
              ,1 Col4
              ,1 Col5
              ,1 Col6
              ,1 Col7
              ,1 Col8
              ,1 Col9
              ,1 Col10
              ,1 Col11
              ,1 Col12
              ,1 Col13
              ,1 Col14
              ,1 Col15
              ,1 Col16
              ,1 Col17
              ,1 Col18
              ,1 Col19
              ,1 Col20

    IF @Level = 2
        SELECT 1 Col1
              ,1 Col2
              ,1 Col3
              ,1 Col4
              ,1 Col5
              ,1 Col6
              ,1 Col7
              ,1 Col8
              ,1 Col9
              ,1 Col10
              ,1 Col11
              ,1 Col12
              ,1 Col13
              ,1 Col14

END
GO

+## Problem description

It appears that if you have a stored procedure that returns different numbers of columns based on parameters, the run with the higher number of columns causes PHP to crash. If I recreate the statement each time I need to use it, this error goes away and the script succeeds.

+## Expected behavior and actual behavior

Expected behaviour - both runs succeed and return results Actual behaviour - first run succeeds, second causes PHP to crash

+## Repro code or steps to reproduce

  1. Create stored procedure

  2. Change the DSN to match your environment and run PHP code below:

<?php

$db=new PDO('sqlsrv:Server=SERVER\INSTANCE;Database=dbname;MultipleActiveResultSets=0;', NULL, NULL);

$x=$db->prepare(
    "exec pdobugtest ?"
);
$x->execute([2]);
$x->fetch();
$x->closeCursor();

$x->execute([1]);
$x->fetch();
$x->closeCursor();

created time in 3 days

issue commentmicrosoft/msphpsql

Char Encoding Windows-CP1252 requirement

Hi @lwohlhart , if you're willing to migrate your DB from using the ANSI codepage, it is the way to go. Not only you will improve the performance of your application (no more conversions by calling mb_convert* functions), but UTF-8 is the default in Ubuntu and other Linux distros. As you have also pointed out, Windows-1252 is not exactly identical to the ANSI standard ISO-8859-1.

This discussion might give you some ideas to start exploring your options. When using sqlsrv, you will need to connect using "CharacterSet" => "UTF-8". Please see this page for details.

lwohlhart

comment created time in 4 days

issue openedmicrosoft/msphpsql

Char Encoding Windows-CP1252 requirement

PHP Driver version or file name

v5.6.1/Ubuntu18-7.3.tar

SQL Server version

sqlserver 2017

Client operating system

Ubuntu1804

PHP version

7.3

Expected behavior and actual behavior

setting character encoding to SQLSRV_ENC_CHAR -> reads / writes data stored in existing DB with windows cp1252 encoding correctly

My issue strongly relates to #998

Essentially we have a DB running where several Windows (IIS) servers have been reading/writing data for a long time now.

Now Apache Servers should access the same Databases, reading the special characters encoded in the DB correctly and also store them in the same format for the windows server to continue functioning

We have a quick fix running that essentially converts all UTF-8 characters back-and-forth to Windows-1252 encoding when after reading and before writing data to the DB roughly like:

// after read
mb_convert_encoding($retrieved_data_from_db, 'windows-1252', 'UTF-8');

// before write
mb_convert_encoding($data_about_to_be_written_to_db, 'UTF-8', 'windows-1252');

Initially the solution looked ugly but functional, however it turns out several characters don't translate properly in this encoding conversion as documented here (https://www.i18nqa.com/debug/bug-double-conversion.html) e.g.:

php> echo ( (mb_convert_encoding("Á", 'UTF-8', 'windows-1252')));
�

Thus customer name are regularly garbled.

Do you have any suggestion for us to go forward?

Any help strongly appreciated. ( Even suggestions how to properly migrate the DB to UTF-8 or smth along those lines )

created time in 4 days

push eventziadoz/awesome-php

Jamie

commit sha 09eb8bca55083d47c1e2071fd3d329c3147b2d42

Ordering.

view details

push time in 4 days

push eventmicrosoft/msphpsql

Jenny Tam

commit sha f59f0bcce7d0d000900c820ad4bc1917b3a20dd8

Removed MACOSX_DEPLOYMENT_TARGET

view details

Jenny Tam

commit sha 6640952b7b0e094e86e1986aa5808cb1971f5869

Merge pull request #1215 from yitam/testMac Removed MACOSX_DEPLOYMENT_TARGET from config

view details

push time in 4 days

PR merged microsoft/msphpsql

Removed MACOSX_DEPLOYMENT_TARGET from config

This is no longer required Related to this commit

This fixes the linker issue in #1213

+0 -2

0 comment

2 changed files

yitam

pr closed time in 4 days

issue commentmicrosoft/msphpsql

PHP hangs on PDOStatement::fetch for large SELECT query

however the query was selecting just a certain number of columns in that table.

That is more important since it's what gets sent through the network - to be more precise, we are interested in the schema of the resultset itself. If you can provide a repro with anonymised/fake data of a minimal number of rows, even better.

zorino

comment created time in 4 days

issue commentmicrosoft/msphpsql

PHP hangs on PDOStatement::fetch for large SELECT query

My comment was the full schema, however the query was selecting just a certain number of columns in that table.

Which kind of additional data or trace do you want me to provide ?

zorino

comment created time in 4 days

PR opened microsoft/msphpsql

Removed MACOSX_DEPLOYMENT_TARGET from config

This is no longer required Related to this commit

+0 -2

0 comment

2 changed files

pr created time in 4 days

push eventziadoz/awesome-php

Jamie

commit sha c354904cd4c06cb2661caba351d72d85a96e6cec

Remove other websites.

view details

push time in 4 days

issue closedvincepare/iframeTracker-jquery

textarea or input lost focus time to time

when user input, mouse does't move, but text box will lost focus, maybe due to input method, but how can i fix this by filtering input or textarea element

closed time in 5 days

culmencasa

PR opened ziadoz/awesome-php

Add T-Regx

Advanced library for Regular Expressions in PHP: https://t-regx.com/

+1 -0

0 comment

1 changed file

pr created time in 5 days

issue commentmicrosoft/msphpsql

SSL routines:ssl_choose_client_version:unsupported protocol]

this configuration worked for me

 openssl_conf = default_conf
#
# OpenSSL example configuration file.
# This is mostly being used for generation of certificate requests.
#

# Note that you can include other files from the main configuration
# file using the .include directive.
#.include filename

# This definition stops the following lines choking if HOME isn't
# defined.
HOME			= .

# Extra OBJECT IDENTIFIER info:
#oid_file		= $ENV::HOME/.oid
oid_section		= new_oids

# To use this configuration file with the "-extfile" option of the
# "openssl x509" utility, name here the section containing the
# X.509v3 extensions to use:
# extensions		=
# (Alternatively, use a configuration file that has only
# X.509v3 extensions in its main [= default] section.)

[ new_oids ]

# We can add new OIDs in here for use by 'ca', 'req' and 'ts'.
# Add a simple OID like this:
# testoid1=1.2.3.4
# Or use config file substitution like this:
# testoid2=${testoid1}.5.6

# Policies used by the TSA examples.
tsa_policy1 = 1.2.3.4.1
tsa_policy2 = 1.2.3.4.5.6
tsa_policy3 = 1.2.3.4.5.7

####################################################################
[ ca ]
default_ca	= CA_default		# The default ca section

####################################################################
[ CA_default ]

dir		= ./demoCA		# Where everything is kept
certs		= $dir/certs		# Where the issued certs are kept
crl_dir		= $dir/crl		# Where the issued crl are kept
database	= $dir/index.txt	# database index file.
#unique_subject	= no			# Set to 'no' to allow creation of
					# several certs with same subject.
new_certs_dir	= $dir/newcerts		# default place for new certs.

certificate	= $dir/cacert.pem 	# The CA certificate
serial		= $dir/serial 		# The current serial number
crlnumber	= $dir/crlnumber	# the current crl number
					# must be commented out to leave a V1 CRL
crl		= $dir/crl.pem 		# The current CRL
private_key	= $dir/private/cakey.pem# The private key

x509_extensions	= usr_cert		# The extensions to add to the cert

# Comment out the following two lines for the "traditional"
# (and highly broken) format.
name_opt 	= ca_default		# Subject Name options
cert_opt 	= ca_default		# Certificate field options

# Extension copying option: use with caution.
# copy_extensions = copy

# Extensions to add to a CRL. Note: Netscape communicator chokes on V2 CRLs
# so this is commented out by default to leave a V1 CRL.
# crlnumber must also be commented out to leave a V1 CRL.
# crl_extensions	= crl_ext

default_days	= 365			# how long to certify for
default_crl_days= 30			# how long before next CRL
default_md	= default		# use public key default MD
preserve	= no			# keep passed DN ordering

# A few difference way of specifying how similar the request should look
# For type CA, the listed attributes must be the same, and the optional
# and supplied fields are just that :-)
policy		= policy_match

# For the CA policy
[ policy_match ]
countryName		= match
stateOrProvinceName	= match
organizationName	= match
organizationalUnitName	= optional
commonName		= supplied
emailAddress		= optional

# For the 'anything' policy
# At this point in time, you must list all acceptable 'object'
# types.
[ policy_anything ]
countryName		= optional
stateOrProvinceName	= optional
localityName		= optional
organizationName	= optional
organizationalUnitName	= optional
commonName		= supplied
emailAddress		= optional

####################################################################
[ req ]
default_bits		= 2048
default_keyfile 	= privkey.pem
distinguished_name	= req_distinguished_name
attributes		= req_attributes
x509_extensions	= v3_ca	# The extensions to add to the self signed cert

# Passwords for private keys if not present they will be prompted for
# input_password = secret
# output_password = secret

# This sets a mask for permitted string types. There are several options.
# default: PrintableString, T61String, BMPString.
# pkix	 : PrintableString, BMPString (PKIX recommendation before 2004)
# utf8only: only UTF8Strings (PKIX recommendation after 2004).
# nombstr : PrintableString, T61String (no BMPStrings or UTF8Strings).
# MASK:XXXX a literal mask value.
# WARNING: ancient versions of Netscape crash on BMPStrings or UTF8Strings.
string_mask = utf8only

# req_extensions = v3_req # The extensions to add to a certificate request

[ req_distinguished_name ]
countryName			= Country Name (2 letter code)
countryName_default		= AU
countryName_min			= 2
countryName_max			= 2

stateOrProvinceName		= State or Province Name (full name)
stateOrProvinceName_default	= Some-State

localityName			= Locality Name (eg, city)

0.organizationName		= Organization Name (eg, company)
0.organizationName_default	= Internet Widgits Pty Ltd

# we can do this but it is not needed normally :-)
#1.organizationName		= Second Organization Name (eg, company)
#1.organizationName_default	= World Wide Web Pty Ltd

organizationalUnitName		= Organizational Unit Name (eg, section)
#organizationalUnitName_default	=

commonName			= Common Name (e.g. server FQDN or YOUR name)
commonName_max			= 64

emailAddress			= Email Address
emailAddress_max		= 64

# SET-ex3			= SET extension number 3

[ req_attributes ]
challengePassword		= A challenge password
challengePassword_min		= 4
challengePassword_max		= 20

unstructuredName		= An optional company name

[ usr_cert ]

# These extensions are added when 'ca' signs a request.

# This goes against PKIX guidelines but some CAs do it and some software
# requires this to avoid interpreting an end user certificate as a CA.

basicConstraints=CA:FALSE

# Here are some examples of the usage of nsCertType. If it is omitted
# the certificate can be used for anything *except* object signing.

# This is OK for an SSL server.
# nsCertType			= server

# For an object signing certificate this would be used.
# nsCertType = objsign

# For normal client use this is typical
# nsCertType = client, email

# and for everything including object signing:
# nsCertType = client, email, objsign

# This is typical in keyUsage for a client certificate.
# keyUsage = nonRepudiation, digitalSignature, keyEncipherment

# This will be displayed in Netscape's comment listbox.
nsComment			= "OpenSSL Generated Certificate"

# PKIX recommendations harmless if included in all certificates.
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid,issuer

# This stuff is for subjectAltName and issuerAltname.
# Import the email address.
# subjectAltName=email:copy
# An alternative to produce certificates that aren't
# deprecated according to PKIX.
# subjectAltName=email:move

# Copy subject details
# issuerAltName=issuer:copy

#nsCaRevocationUrl		= http://www.domain.dom/ca-crl.pem
#nsBaseUrl
#nsRevocationUrl
#nsRenewalUrl
#nsCaPolicyUrl
#nsSslServerName

# This is required for TSA certificates.
# extendedKeyUsage = critical,timeStamping

[ v3_req ]

# Extensions to add to a certificate request

basicConstraints = CA:FALSE
keyUsage = nonRepudiation, digitalSignature, keyEncipherment

[ v3_ca ]


# Extensions for a typical CA


# PKIX recommendation.

subjectKeyIdentifier=hash

authorityKeyIdentifier=keyid:always,issuer

basicConstraints = critical,CA:true

# Key usage: this is typical for a CA certificate. However since it will
# prevent it being used as an test self-signed certificate it is best
# left out by default.
# keyUsage = cRLSign, keyCertSign

# Some might want this also
# nsCertType = sslCA, emailCA

# Include email address in subject alt name: another PKIX recommendation
# subjectAltName=email:copy
# Copy issuer details
# issuerAltName=issuer:copy

# DER hex encoding of an extension: beware experts only!
# obj=DER:02:03
# Where 'obj' is a standard or added object
# You can even override a supported extension:
# basicConstraints= critical, DER:30:03:01:01:FF

[ crl_ext ]

# CRL extensions.
# Only issuerAltName and authorityKeyIdentifier make any sense in a CRL.

# issuerAltName=issuer:copy
authorityKeyIdentifier=keyid:always

[ proxy_cert_ext ]
# These extensions should be added when creating a proxy certificate

# This goes against PKIX guidelines but some CAs do it and some software
# requires this to avoid interpreting an end user certificate as a CA.

basicConstraints=CA:FALSE

# Here are some examples of the usage of nsCertType. If it is omitted
# the certificate can be used for anything *except* object signing.

# This is OK for an SSL server.
# nsCertType			= server

# For an object signing certificate this would be used.
# nsCertType = objsign

# For normal client use this is typical
# nsCertType = client, email

# and for everything including object signing:
# nsCertType = client, email, objsign

# This is typical in keyUsage for a client certificate.
# keyUsage = nonRepudiation, digitalSignature, keyEncipherment

# This will be displayed in Netscape's comment listbox.
nsComment			= "OpenSSL Generated Certificate"

# PKIX recommendations harmless if included in all certificates.
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid,issuer

# This stuff is for subjectAltName and issuerAltname.
# Import the email address.
# subjectAltName=email:copy
# An alternative to produce certificates that aren't
# deprecated according to PKIX.
# subjectAltName=email:move

# Copy subject details
# issuerAltName=issuer:copy

#nsCaRevocationUrl		= http://www.domain.dom/ca-crl.pem
#nsBaseUrl
#nsRevocationUrl
#nsRenewalUrl
#nsCaPolicyUrl
#nsSslServerName

# This really needs to be in place for it to be a proxy certificate.
proxyCertInfo=critical,language:id-ppl-anyLanguage,pathlen:3,policy:foo

####################################################################
[ tsa ]

default_tsa = tsa_config1	# the default TSA section

[ tsa_config1 ]

# These are used by the TSA reply generation only.
dir		= ./demoCA		# TSA root directory
serial		= $dir/tsaserial	# The current serial number (mandatory)
crypto_device	= builtin		# OpenSSL engine to use for signing
signer_cert	= $dir/tsacert.pem 	# The TSA signing certificate
					# (optional)
certs		= $dir/cacert.pem	# Certificate chain to include in reply
					# (optional)
signer_key	= $dir/private/tsakey.pem # The TSA private key (optional)
signer_digest  = sha256			# Signing digest to use. (Optional)
default_policy	= tsa_policy1		# Policy if request did not specify it
					# (optional)
other_policies	= tsa_policy2, tsa_policy3	# acceptable policies (optional)
digests     = sha1, sha256, sha384, sha512  # Acceptable message digests (mandatory)
accuracy	= secs:1, millisecs:500, microsecs:100	# (optional)
clock_precision_digits  = 0	# number of digits after dot. (optional)
ordering		= yes	# Is ordering defined for timestamps?
				# (optional, default: no)
tsa_name		= yes	# Must the TSA name be included in the reply?
				# (optional, default: no)
ess_cert_id_chain	= no	# Must the ESS cert id chain be included?
				# (optional, default: no)
ess_cert_id_alg		= sha1	# algorithm to compute certificate
				# identifier (optional, default: sha1)
[default_conf]
ssl_conf = ssl_sect

[ssl_sect]
system_default = system_default_sect

[system_default_sect]
MinProtocol = TLSv1
CipherString = DEFAULT@SECLEVEL=1
aaly00

comment created time in 6 days

issue openedvincepare/iframeTracker-jquery

How to detect anchor click in using iframe tracker.

I just want to capture anchor clicks in the iframe and get the href attribute from anchor.

created time in 6 days

more