This is an automated email from the ASF dual-hosted git repository.

fschumacher pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/jmeter.git


The following commit(s) were added to refs/heads/master by this push:
     new b2d487c  Correct documented name of generated CA when using proxy 
script recorder
b2d487c is described below

commit b2d487c6fb3d9ba31b651e1e0c8a1eac05478f5d
Author: Felix Schumacher <[email protected]>
AuthorDate: Tue Aug 25 15:12:27 2020 +0200

    Correct documented name of generated CA when using proxy script recorder
    
    Part of a bigger PR.
    Contributed by Vincent Daburon (vdaburon at gmail.com)
    
    Relates to #571
---
 xdocs/changes.xml                        | 2 ++
 xdocs/usermanual/component_reference.xml | 6 +++---
 2 files changed, 5 insertions(+), 3 deletions(-)

diff --git a/xdocs/changes.xml b/xdocs/changes.xml
index 08d748c..cb0c088 100644
--- a/xdocs/changes.xml
+++ b/xdocs/changes.xml
@@ -182,6 +182,7 @@ applications when JMeter is starting up.</p>
 
 <h3>Documentation</h3>
 <ul>
+    <li><pr>571</pr>Correct documented name of generated CA when using proxy 
script recorder. Part of a bigger PR. Vincent Daburon (vdaburon at 
gmail.com)</li>
 </ul>
 
 <h3>General</h3>
@@ -215,6 +216,7 @@ applications when JMeter is starting up.</p>
   <li><a href="https://ubikloadpack.com"; >Ubik Load Pack</a></li>
   <li>Till Neunast (https://github.com/tilln)</li>
   <li>Pooja Chandak (poojachandak002 at gmail.com)</li>
+  <li>Vincent Daburon (vdaburon at gmail.com)</li>
 </ul>
 <p>We also thank bug reporters who helped us improve JMeter.</p>
 <ul>
diff --git a/xdocs/usermanual/component_reference.xml 
b/xdocs/usermanual/component_reference.xml
index d78a5db..7fa1ce8 100644
--- a/xdocs/usermanual/component_reference.xml
+++ b/xdocs/usermanual/component_reference.xml
@@ -6617,9 +6617,9 @@ As a consequence:
 <li>The browser should display a dialogue asking if you want to accept the 
certificate or not. For example:
 <source>
 1) The server's name "<code>www.example.com</code>" does not match the 
certificate's name
-   "<code>JMeter Proxy (DO NOT TRUST)</code>". Somebody may be trying to 
eavesdrop on you.
-2) The certificate for "<code>JMeter Proxy (DO NOT TRUST)</code>" is signed by 
the unknown Certificate Authority
-   "<code>JMeter Proxy (DO NOT TRUST)</code>". It is not possible to verify 
that this is a valid certificate.
+   "<code>_ JMeter Root CA for recording (INSTALL ONLY IF IT S YOURS)</code>". 
Somebody may be trying to eavesdrop on you.
+2) The certificate for "<code>_ JMeter Root CA for recording (INSTALL ONLY IF 
IT S YOURS)</code>" is signed by the unknown Certificate Authority
+   "<code>_ JMeter Root CA for recording (INSTALL ONLY IF IT S YOURS)</code>". 
It is not possible to verify that this is a valid certificate.
 </source>
 You will need to accept the certificate in order to allow the JMeter Proxy to 
intercept the SSL traffic in order to
 record it.

Reply via email to