Developer Diary
  • Developer Diary
  • 2019

    • June 2019
    • July 2019
    • August 2019
    • September 2019
    • October 2019
    • November 2019
    • December, 2019
  • 2020

    • January 2020
    • February 2020
    • March 2020
    • April 2020
    • May, 2020
    • June 2020
    • July 2020
    • August 2020
    • September 2020
    • October 2020
    • November 2020
    • December 2020
  • 2021

    • January 2021
    • February 2021
    • February 2021
    • April 2021
    • May 2021
    • June 2021
    • July 2021
    • August 2021
    • September 2021
    • October 2021
    • November 2021
    • December 2021
  • 2022

    • January 2022
    • February 2022
    • March 2022
    • April 2022
    • May 2022
    • June 2022
    • July 2022
    • August 2022
    • September 2022
    • October 2022
    • November 2022
    • December 2022
  • 2023

    • January 2023
    • February 2023
    • March 2023
    • April 2023
    • May 2023
    • June 2023
    • July 2023
    • August 2023
    • September 2023
    • October 2023
    • November 2023
    • December 2023
  • 2024

    • January 2024
    • February 2024
    • March 2024
    • April 2024
    • May 2024
    • June 2024
    • July 2024
    • August, 2024
    • September 2024
    • October 2024
    • November 2024
    • December 2024
  • 2025

    • January 2025
    • February 2025
    • March 2025
    • April 2025
    • May 2025
    • June 2025
    • July 2025
    • August 2025
    • September 2025
    • October 2025
    • November 2025
    • December 2025
  • 2026

    • January 2026
    • February 2026

March 17, 2022

BSH SSL

  • client does not want to generate a new cert, sent a PFX file instead. Here's the steps.

To convert to pem file with the private key and cert separate:

openssl pkcs12 -in  blahblah.pfx -nokeys -out bundle.pem 

this will prompt you for the password to open the pfx file then output a pem file that only contains the public key (cert), not the private.

openssl pkcs12 -in  foodservice-2023.pfx -nocerts -out private.pem 

this will prompt you for the password to open the pfx file then output a pem file that only contains the private key, not the public.

NOTE: I added a temporary password here, this seems to be necessary in order to export properly, but we remove that encryption on the next step.

Lastly, you may need to remove the RSA encryption from the private key to make it readable by some *nix services.

openssl rsa -in private.pem -out private.key 

You will need the separate key file from the previous step to do this. You cannot go directly from the pfx file.

You should note that you first have to split the pfx into the pem and key file, then you can remove the password from the key


Team Meeting

TMZ LP

  • start css

PSP Word to HTML

TMZ D TOGO