Title: phpseclib\Crypt\Random::string breaks loopback requests
Last modified: July 15, 2018

---

# phpseclib\Crypt\Random::string breaks loopback requests

 *  Resolved [Mos Craciun](https://wordpress.org/support/users/furioussnail/)
 * (@furioussnail)
 * [7 years, 11 months ago](https://wordpress.org/support/topic/phpseclibcryptrandomstring-breaks-loopback-requests/)
 * Hello.
    A quick look revealed that phpseclib\Crypt\Random::string opens a session
   but never destroys it. As a result loopback request in WordPress gets broken (
   which affects the internal editor). I am not very familiar with the plugin but
   I suspect it is safe to destroy the session before return. Could you please fix
   it? Thank you.

Viewing 1 replies (of 1 total)

 *  Plugin Author [Tribulant Software](https://wordpress.org/support/users/contrid/)
 * (@contrid)
 * [7 years, 10 months ago](https://wordpress.org/support/topic/phpseclibcryptrandomstring-breaks-loopback-requests/#post-10500701)
 * [@furioussnail](https://wordpress.org/support/users/furioussnail/)
 * Thank you for reporting this problem.
 * We will fix the problem for our upcoming release.

Viewing 1 replies (of 1 total)

The topic ‘phpseclib\Crypt\Random::string breaks loopback requests’ is closed to
new replies.

 * ![](https://ps.w.org/newsletters-lite/assets/icon-256x256.png?rev=1184265)
 * [Newsletters](https://wordpress.org/plugins/newsletters-lite/)
 * [Support Threads](https://wordpress.org/support/plugin/newsletters-lite/)
 * [Active Topics](https://wordpress.org/support/plugin/newsletters-lite/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/newsletters-lite/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/newsletters-lite/reviews/)

## Tags

 * [session](https://wordpress.org/support/topic-tag/session/)

 * 1 reply
 * 2 participants
 * Last reply from: [Tribulant Software](https://wordpress.org/support/users/contrid/)
 * Last activity: [7 years, 10 months ago](https://wordpress.org/support/topic/phpseclibcryptrandomstring-breaks-loopback-requests/#post-10500701)
 * Status: resolved