One signature of PKCS8::PEM_encode was stray, and didn't have a cooresponding implementation. This had been the case since at least 1.8.0. Remove it, since implementing this signature would require having the library create an AutoSeeded_RNG, which seems like it might be quite surprising to an unsuspecting user.
One signature of PKCS8::PEM_encode was stray, and didn't have a cooresponding
implementation. This had been the case since at least 1.8.0. Remove it, since
implementing this signature would require having the library create an
AutoSeeded_RNG, which seems like it might be quite surprising to an unsuspecting
user.

Problem reported by M. Braun in ticket 44

Rohde-Schwarz-Cybersecurity/botan,randombit/botan,randombit/botan,Rohde-Schwarz-Cybersecurity/botan,Rohde-Schwarz-Cybersecurity/botan,webmaster128/botan,webmaster128/botan,randombit/botan,Rohde-Schwarz-Cybersecurity/botan,webmaster128/botan,webmaster128/botan,Rohde-Schwarz-Cybersecurity/botan,webmaster128/botan,randombit/botan,randombit/botan,Rohde-Schwarz-Cybersecurity/botan