Merge pull request #262 from embhorn/facts_at_wolfssl

dgarske · web-flow · commit a3c87ca28854 · 2026-04-15T15:01:57.000-07:00
Change all instances of info@wolfssl.com to facts@wolfssl.com
diff --git a/wolfMQTT/src-ja/chapter02.md b/wolfMQTT/src-ja/chapter02.md
@@ -185,7 +185,7 @@ make
 make
 sudo make install
 ```
-wolfMQTT のクロス コンパイルに関する追加のヒントやフィードバックがある場合は、_info@wolfssl.com_ までお知らせください。
+wolfMQTT のクロス コンパイルに関する追加のヒントやフィードバックがある場合は、_facts@wolfssl.com_ までお知らせください。
 
 
 ### 特定のディレクトリへのインストール
diff --git a/wolfMQTT/src/chapter02.md b/wolfMQTT/src/chapter02.md
@@ -162,7 +162,7 @@ After correctly configuring wolfMQTT for cross-compilation, you should be able t
 make
 sudo make install
 ```
-If you have any additional tips or feedback about cross compiling wolfMQTT, please let us know at _info@wolfssl.com_.
+If you have any additional tips or feedback about cross compiling wolfMQTT, please let us know at _facts@wolfssl.com_.
 
 ### Install to Custom Directory
 
diff --git a/wolfSSH/src-ja/chapter01.md b/wolfSSH/src-ja/chapter01.md
@@ -11,7 +11,7 @@ SSHは２つの通信端点に多重化されたデータストリームを提
 
 ##  wolfSSHをお勧めする理由
 
-wolfSSHはANSI Cで記述された軽量のSSHv2サーバーライブラリで、サイズが軽量でありスピード、機能セットに富んでいる点から、組み込み機器、リアルタイムOSおよびリソース制約のある環境をターゲットにしています。wolfSSHは業界標準のSSH v2をサポートし、さらに先進的なアルゴリズム（ChaCha20, Poly1305, NTRU とSHA-3)も提供しています。wolfSSHを支えているのはwolfCrypt暗号化ライブラリで、このライブラリはFIPS140-2認証（認証#2425）を受けています。より詳細はwolfCrypt FIPS FAQを参照されるかあるいはinfo@wolfssl.comまでお知らせください。
+wolfSSHはANSI Cで記述された軽量のSSHv2サーバーライブラリで、サイズが軽量でありスピード、機能セットに富んでいる点から、組み込み機器、リアルタイムOSおよびリソース制約のある環境をターゲットにしています。wolfSSHは業界標準のSSH v2をサポートし、さらに先進的なアルゴリズム（ChaCha20, Poly1305, NTRU とSHA-3)も提供しています。wolfSSHを支えているのはwolfCrypt暗号化ライブラリで、このライブラリはFIPS140-2認証（認証#2425）を受けています。より詳細はwolfCrypt FIPS FAQを参照されるかあるいはfacts@wolfssl.comまでお知らせください。
 
 
 ### 機能（特徴）
diff --git a/wolfSSH/src-ja/chapter02.md b/wolfSSH/src-ja/chapter02.md
@@ -175,7 +175,7 @@ $ make
 $ sudo make install
 ```
 
-ここでご紹介した以外のTipsをお持ちでしたらぜひ info@wolfssl.comまで お知らせください。
+ここでご紹介した以外のTipsをお持ちでしたらぜひ facts@wolfssl.comまで お知らせください。
 
 ##  カスタムディレクトリへのインストール
 
diff --git a/wolfSSH/src-ja/chapter11.md b/wolfSSH/src-ja/chapter11.md
@@ -9,7 +9,7 @@
 **サポート：** support@wolfssl.com
 
 
-wolfSSL製品、ライセンスに関する質問、または一般的なコメントに関する情報については、**info@wolfssl.com** 宛にメールしてください。
+wolfSSL製品、ライセンスに関する質問、または一般的なコメントに関する情報については、**facts@wolfssl.com** 宛にメールしてください。
 
 
 ###  バグレポートと障害のサポート
diff --git a/wolfSSH/src/chapter02.md b/wolfSSH/src/chapter02.md
@@ -140,7 +140,7 @@ After correctly configuring wolfSSH for cross compilation you should be able to
 $ make
 $ sudo make install
 ```
-If you have any additional tips or feedback for cross compiling wolfSSH, please let us know at info@wolfssl.com.
+If you have any additional tips or feedback for cross compiling wolfSSH, please let us know at facts@wolfssl.com.
 
 ##  Install to Custom Directory
 
diff --git a/wolfSSH/src/chapter11.md b/wolfSSH/src/chapter11.md
@@ -7,7 +7,7 @@ For general product support, wolfSSL maintains an online forum for the wolfSSL p
 - wolfSSL Forums: [https://www.wolfssl.com/forums](https://www.wolfssl.com/forums)
 - Email Support: support@wolfssl.com
 
-For information regarding wolfSSL products, questions regarding licensing, or general comments, please contact wolfSSL by emailing **info@wolfssl.com**.
+For information regarding wolfSSL products, questions regarding licensing, or general comments, please contact wolfSSL by emailing **facts@wolfssl.com**.
 
 ###  Bugs Reports and Support Issues
 
@@ -40,7 +40,7 @@ Program Outline:
 3. Normally, up to one week is the right amount of time for us to make the replacement in your code and do initial testing. Additional consulting on a  replacement is available as needed.
 4. You will receive the standard wolfSSL royalty free license to ship with your product.
 
-The purpose of this program is to enable users who are currently spending too much on their embedded SSL implementation to move to wolfSSL with ease. If you are interested in learning more, then please contact us at info@wolfssl.com.
+The purpose of this program is to enable users who are currently spending too much on their embedded SSL implementation to move to wolfSSL with ease. If you are interested in learning more, then please contact us at facts@wolfssl.com.
 
 ###  Design Consulting
 
diff --git a/wolfSSL-Porting/src-ja/section04.md b/wolfSSL-Porting/src-ja/section04.md
@@ -9,7 +9,7 @@ wolfSSLは、お客様が新しい環境にwolfSSLを移植できるためのサ
 
 - Support Packages:  https://wolfssl.jp/license/support-packages/
 - Consulting Services: https://www.wolfssl.com/wolfSSL/wolfssl-consulting.html
-- General Inquiries: info@wolfssl.com
+- General Inquiries: facts@wolfssl.com
 
 ## Document Revision Log
 
diff --git a/wolfSSL-Porting/src/section01.md b/wolfSSL-Porting/src/section01.md
@@ -53,4 +53,4 @@ path. This allows users to maintain one single file for their wolfSSL
 build, and makes it much easier to update to newer versions of wolfSSL.
 
 wolfSSL encourages the submission of patches and code changes through either
-direct email (info@wolfssl.com), or through GitHub pull request.
+direct email (facts@wolfssl.com), or through GitHub pull request.
diff --git a/wolfSSL-Porting/src/section04.md b/wolfSSL-Porting/src/section04.md
@@ -14,7 +14,7 @@ to help users and customers port wolfSSL to new environments.
 
 - Support Packages:  https://www.wolfssl.com/wolfSSL/Support/support_tiers.php
 - Consulting Services: https://www.wolfssl.com/wolfSSL/wolfssl-consulting.html
-- General Inquiries: info@wolfssl.com
+- General Inquiries: facts@wolfssl.com
 
 ## Document Revision Log
 
diff --git a/wolfSSL/src-ja/chapter03.md b/wolfSSL/src-ja/chapter03.md
@@ -80,12 +80,12 @@ mutex    test passed!
 memcb    test passed!
 Test complete
 Alternate cert chain used
- issuer : /C=US/ST=Montana/L=Bozeman/O=Sawtooth/OU=Consulting/CN=www.wolfssl.com/emailAddress=info@wolfssl.com
- subject: /C=US/ST=Montana/L=Bozeman/O=wolfSSL/OU=Support/CN=www.wolfssl.com/emailAddress=info@wolfssl.com
+ issuer : /C=US/ST=Montana/L=Bozeman/O=Sawtooth/OU=Consulting/CN=www.wolfssl.com/emailAddress=facts@wolfssl.com
+ subject: /C=US/ST=Montana/L=Bozeman/O=wolfSSL/OU=Support/CN=www.wolfssl.com/emailAddress=facts@wolfssl.com
  altname = example.com
 Alternate cert chain used
- issuer : /C=US/ST=Montana/L=Bozeman/O=wolfSSL_2048/OU=Programming-2048/CN=www.wolfssl.com/emailAddress=info@wolfssl.com
- subject: /C=US/ST=Montana/L=Bozeman/O=wolfSSL_2048/OU=Programming-2048/CN=www.wolfssl.com/emailAddress=info@wolfssl.com
+ issuer : /C=US/ST=Montana/L=Bozeman/O=wolfSSL_2048/OU=Programming-2048/CN=www.wolfssl.com/emailAddress=facts@wolfssl.com
+ subject: /C=US/ST=Montana/L=Bozeman/O=wolfSSL_2048/OU=Programming-2048/CN=www.wolfssl.com/emailAddress=facts@wolfssl.com
  altname = example.com
  serial number:01
 SSL version is TLSv1.2
diff --git a/wolfSSL/src-ja/chapter07.md b/wolfSSL/src-ja/chapter07.md
@@ -398,7 +398,7 @@ strncpy(myCert.subject.locality, "Portland", CTC_NAME_SIZE);
 strncpy(myCert.subject.org, "yaSSL", CTC_NAME_SIZE);
 strncpy(myCert.subject.unit, "Development", CTC_NAME_SIZE);
 strncpy(myCert.subject.commonName, "www.wolfssl.com", CTC_NAME_SIZE);
-strncpy(myCert.subject.email, "info@wolfssl.com", CTC_NAME_SIZE);
+strncpy(myCert.subject.email, "facts@wolfssl.com", CTC_NAME_SIZE);
 ```
 
 そして、上記の鍵生成例からの変数`genKey`と`rng`を使用して、自己署名証明書を生成できます。
@@ -525,7 +525,7 @@ strncpy(req.subject.locality, "Portland", CTC_NAME_SIZE);
 strncpy(req.subject.org, "wolfSSL", CTC_NAME_SIZE);
 strncpy(req.subject.unit, "Development", CTC_NAME_SIZE);
 strncpy(req.subject.commonName, "www.wolfssl.com", CTC_NAME_SIZE);
-strncpy(req.subject.email, "info@wolfssl.com", CTC_NAME_SIZE);
+strncpy(req.subject.email, "facts@wolfssl.com", CTC_NAME_SIZE);
 ```
 
 そして、上記の鍵生成例からの変数`key`と`rng`を使用して、署名付きCSRを生成できます。
diff --git a/wolfSSL/src/chapter02.md b/wolfSSL/src/chapter02.md
@@ -175,7 +175,7 @@ While not officially supported, we try to help users wishing to build wolfSSL in
 2. Some build systems will want to explicitly know where the wolfSSL header files are located, so you may need to specify that. They are located in the `<wolfssl_root>/wolfssl` directory. Typically, you can add the `<wolfssl_root>` directory to your include path to resolve header problems.
 3. wolfSSL defaults to a little endian system unless the configure process detects big endian. Since users building in a non-standard environment aren't using the configure process, `BIG_ENDIAN_ORDER` will need to be defined if using a big endian system.
 4. wolfSSL benefits speed-wise from having a 64-bit type available. The configure process determines if long or long long is 64 bits and if so sets up a define. So if `sizeof(long)` is 8 bytes on your system, define `SIZEOF_LONG 8`. If it isn't but `sizeof(long long)` is 8 bytes, then define `SIZEOF_LONG_LONG 8`.
-5. Try to build the library, and let us know if you run into any problems. If you need help, contact us at [info@wolfssl.com](mailto:info@wolfssl.com).
+5. Try to build the library, and let us know if you run into any problems. If you need help, contact us at [facts@wolfssl.com](mailto:facts@wolfssl.com).
 6. Some defines that can modify the build are listed in the following sub-sections, below. For more verbose descriptions of many options, please see [Build Options](#build-options).
 
 ### Building into Yocto Linux
@@ -4988,7 +4988,7 @@ make
 sudo make install
 ```
 
-If you have any additional tips or feedback about cross compiling wolfSSL, please let us know at [info@wolfssl.com](mailto:info@wolfssl.com).
+If you have any additional tips or feedback about cross compiling wolfSSL, please let us know at [facts@wolfssl.com](mailto:facts@wolfssl.com).
 
 ### Example cross compile configure options for toolchain builds
 
diff --git a/wolfSSL/src/chapter03.md b/wolfSSL/src/chapter03.md
@@ -74,12 +74,12 @@ mutex    test passed!
 memcb    test passed!
 Test complete
 Alternate cert chain used
- issuer : /C=US/ST=Montana/L=Bozeman/O=Sawtooth/OU=Consulting/CN=www.wolfssl.com/emailAddress=info@wolfssl.com
- subject: /C=US/ST=Montana/L=Bozeman/O=wolfSSL/OU=Support/CN=www.wolfssl.com/emailAddress=info@wolfssl.com
+ issuer : /C=US/ST=Montana/L=Bozeman/O=Sawtooth/OU=Consulting/CN=www.wolfssl.com/emailAddress=facts@wolfssl.com
+ subject: /C=US/ST=Montana/L=Bozeman/O=wolfSSL/OU=Support/CN=www.wolfssl.com/emailAddress=facts@wolfssl.com
  altname = example.com
 Alternate cert chain used
- issuer : /C=US/ST=Montana/L=Bozeman/O=wolfSSL_2048/OU=Programming-2048/CN=www.wolfssl.com/emailAddress=info@wolfssl.com
- subject: /C=US/ST=Montana/L=Bozeman/O=wolfSSL_2048/OU=Programming-2048/CN=www.wolfssl.com/emailAddress=info@wolfssl.com
+ issuer : /C=US/ST=Montana/L=Bozeman/O=wolfSSL_2048/OU=Programming-2048/CN=www.wolfssl.com/emailAddress=facts@wolfssl.com
+ subject: /C=US/ST=Montana/L=Bozeman/O=wolfSSL_2048/OU=Programming-2048/CN=www.wolfssl.com/emailAddress=facts@wolfssl.com
  altname = example.com
  serial number:01
 SSL version is TLSv1.2
diff --git a/wolfSSL/src/chapter07.md b/wolfSSL/src/chapter07.md
@@ -360,7 +360,7 @@ strncpy(myCert.subject.locality, "Portland", CTC_NAME_SIZE);
 strncpy(myCert.subject.org, "yaSSL", CTC_NAME_SIZE);
 strncpy(myCert.subject.unit, "Development", CTC_NAME_SIZE);
 strncpy(myCert.subject.commonName, "www.wolfssl.com", CTC_NAME_SIZE);
-strncpy(myCert.subject.email, "info@wolfssl.com", CTC_NAME_SIZE);
+strncpy(myCert.subject.email, "facts@wolfssl.com", CTC_NAME_SIZE);
 ```
 
 Then, a self-signed certificate can be generated using the variables genKey and rng from the above key generation example (of course any valid RsaKey or RNG can be used):
@@ -470,7 +470,7 @@ strncpy(req.subject.locality, "Portland", CTC_NAME_SIZE);
 strncpy(req.subject.org, "wolfSSL", CTC_NAME_SIZE);
 strncpy(req.subject.unit, "Development", CTC_NAME_SIZE);
 strncpy(req.subject.commonName, "www.wolfssl.com", CTC_NAME_SIZE);
-strncpy(req.subject.email, "info@wolfssl.com", CTC_NAME_SIZE);
+strncpy(req.subject.email, "facts@wolfssl.com", CTC_NAME_SIZE);
 ```
 
 Then, a valid signed CSR can be generated using the variable key from the above key generation example (of course any valid ECC/RSA key or RNG can be used):
diff --git a/wolfSSL/src/chapter11.md b/wolfSSL/src/chapter11.md
@@ -555,6 +555,6 @@ For production applications, you should obtain correct and legitimate certificat
 
 This tutorial walked through the process of integrating the wolfSSL embedded SSL/TLS library into a simple client and server application. Although this example is simple, the same principles may be applied for adding SSL or TLS into your own application. The wolfSSL embedded SSL/TLS library provides all the features you would need in a compact and efficient package that has been optimized for both size and speed.
 
-Being dual licensed under GPLv2 and standard commercial licensing, you are free to download the wolfSSL source code directly from our website. Feel free to post to our support forums (<https://www.wolfssl.com/forums>) with any questions or comments you might have. If you would like more information about our products, please contact [info@wolfssl.com](mailto:info@wolfssl.com).
+Being dual licensed under GPLv2 and standard commercial licensing, you are free to download the wolfSSL source code directly from our website. Feel free to post to our support forums (<https://www.wolfssl.com/forums>) with any questions or comments you might have. If you would like more information about our products, please contact [facts@wolfssl.com](mailto:facts@wolfssl.com).
 
 We welcome any feedback you have on this SSL tutorial. If you believe it could be improved or enhanced in order to make it either more useful, easier to understand, or more portable, please let us know at [support@wolfssl.com](mailto:support@wolfssl.com).
diff --git a/wolfSSL/src/chapter15.md b/wolfSSL/src/chapter15.md
@@ -8,7 +8,7 @@ For general product support, wolfSSL (formerly CyaSSL) maintains an online forum
 
 * Email Support: [support@wolfssl.com](mailto:support@wolfssl.com)
 
-For information regarding wolfSSL products, questions regarding licensing, or general comments, please contact wolfSSL by emailing [info@wolfssl.com](mailto:info@wolfssl.com).  For support packages, please see [Licensing](chapter14.md#licensing).
+For information regarding wolfSSL products, questions regarding licensing, or general comments, please contact wolfSSL by emailing [facts@wolfssl.com](mailto:facts@wolfssl.com).  For support packages, please see [Licensing](chapter14.md#licensing).
 
 ### Bugs Reports and Support Issues
 
@@ -41,7 +41,7 @@ Program Outline:
 3. Normally, up to one week is the right amount of time for us to make the replacement in your code and do initial testing. Additional consulting on a replacement is available as needed.
 4. You will receive the standard wolfSSL royalty free license to ship with your product.
 
-The purpose of this program is to enable users who are currently spending too much on their embedded SSL implementation to move to wolfSSL with ease. If you are interested in learning more, then please contact us at [info@wolfssl.com](mailto:info@wolfssl.com).
+The purpose of this program is to enable users who are currently spending too much on their embedded SSL implementation to move to wolfSSL with ease. If you are interested in learning more, then please contact us at [facts@wolfssl.com](mailto:facts@wolfssl.com).
 
 ### Design Consulting
 
@@ -52,4 +52,4 @@ We offer design consulting for building SSL/TLS security into devices using wolf
 1. _Assessment_:  An evaluation of your current SSL/TLS implementation. We can give you advice on your current setup and how we think you could improve upon this by using wolfSSL.
 2. _Design_:  Looking at your system requirements and parameters, we'll work closely with you to make recommendations on how to implement wolfSSL into your application such that it provides you with optimal security.
 
-If you would like to learn more about design consulting for building SSL into your application or device, please contact [info@wolfssl.com](mailto:info@wolfssl.com) for more information.
+If you would like to learn more about design consulting for building SSL into your application or device, please contact [facts@wolfssl.com](mailto:facts@wolfssl.com) for more information.
diff --git a/wolfTPM/header-ja/group__wolfTPM2__Wrappers.md b/wolfTPM/header-ja/group__wolfTPM2__Wrappers.md
@@ -4148,7 +4148,7 @@ WOLFTPM2_CSR 構造体のサブジェクトを設定する証明書署名要求
 
   * **dev** TPM2_DEV 構造体へのポインター (not used) 
   * **csr** [WOLFTPM2_CSR]() 構造体へのポインター 
-  * **subject** /CN= 構文を使用した識別名文字列。 例: "/C=US/ST=Washington/L=Seattle/O=wolfSSL/OU=Development/CN=www.wolfssl.com/emailAddress=info@wolfssl.com"
+  * **subject** /CN= 構文を使用した識別名文字列。 例: "/C=US/ST=Washington/L=Seattle/O=wolfSSL/OU=Development/CN=www.wolfssl.com/emailAddress=facts@wolfssl.com"
 
 
 **参考**: 
@@ -4274,7 +4274,7 @@ TPM ベースの鍵 (WOLFTPM2_KEY) を使用した証明書署名要求 (CSR) 
 
   * **dev** TPM2_DEV 構造体へのポインター 
   * **key** [WOLFTPM2_KEY]() 構造体へのポインター 
-  * **subject** /CN= 構文を使用した識別名文字列。 例: "/C=US/ST=Washington/L=Seattle/O=wolfSSL/OU=Development/CN=www.wolfssl.com/emailAddress=info@wolfssl.com" 
+  * **subject** /CN= 構文を使用した識別名文字列。 例: "/C=US/ST=Washington/L=Seattle/O=wolfSSL/OU=Development/CN=www.wolfssl.com/emailAddress=facts@wolfssl.com" 
   * **keyUsage** コンマ区切りのキー使用属性の文字列リスト。 可能な値: any、serverAuth、clientAuth、codeSigning、emailProtection、timeStamping、および OCSPSigning デフォルト: "serverAuth,clientAuth,codeSigning" 
   * **outFormat** WOLFSSL_FILETYPE_ASN1 または WOLFSSL_FILETYPE_PEM 
   * **out** ASN.1/DER または PEM としての CSR の宛先バッファ 
@@ -4317,7 +4317,7 @@ TPM ベースの鍵 (WOLFTPM2_KEY) を使用した証明書署名要求 (CSR) 
 
   * **dev** TPM2_DEV 構造体へのポインター 
   * **key** pointer to a loaded [WOLFTPM2_KEY]() 構造体へのポインター 
-  * **subject** /CN= 構文を使用した識別名文字列。 例: "/C=US/ST=Washington/L=Seattle/O=wolfSSL/OU=Development/CN=www.wolfssl.com/emailAddress=info@wolfssl.com" 
+  * **subject** /CN= 構文を使用した識別名文字列。 例: "/C=US/ST=Washington/L=Seattle/O=wolfSSL/OU=Development/CN=www.wolfssl.com/emailAddress=facts@wolfssl.com" 
   * **keyUsage** コンマ区切りのキー使用属性の文字列リスト。 可能な値: any、serverAuth、clientAuth、codeSigning、emailProtection、timeStamping、および OCSPSigning デフォルト: "serverAuth,clientAuth,codeSigning" 
   * **outFormat** WOLFSSL_FILETYPE_ASN1 または WOLFSSL_FILETYPE_PEM 
   * **out** ASN.1/DER または PEM としての CSR の宛先バッファ 
diff --git a/wolfTPM/header-ja/tpm2__wrap_8h.md b/wolfTPM/header-ja/tpm2__wrap_8h.md
