[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f2MLCG8OJsA1pXLR96OOoYWb_ozcteeZU87xwoywUdvE":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"laceous","https:\u002F\u002Fprofiles.wordpress.org\u002Flaceous\u002F",3,120,85,30,84,"2026-04-04T06:05:16.928Z",[13,38,55],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":19,"downloaded":20,"rating":21,"num_ratings":22,"last_updated":23,"tested_up_to":24,"requires_at_least":25,"requires_php":26,"tags":27,"homepage":33,"download_link":34,"security_score":8,"vuln_count":35,"unpatched_count":35,"last_vuln_date":36,"fetched_at":37},"semisecure-login-reimagined","Semisecure Login Reimagined","3.2.0","\u003Cp>\u003Cstrong>Please note that I’ve moved away from WordPress for the time being. I have no plans to continue updating my plugins. If someone was thinking of forking this project, now would be the time.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Semisecure Login Reimagined increases the security of the login process by using a combination of public and secret-key encryption to encrypt the password on the client-side when a user logs in. JavaScript is required to enable encryption. It is most useful for situations where SSL is not available, but the administrator wishes to have some additional security measures in place without sacrificing convenience.\u003C\u002Fp>\n\u003Cp>This plugin is a “re-imagining” of the original \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fsemisecure-login\u002F\" title=\"Semisecure Login\" rel=\"ugc\">Semisecure Login\u003C\u002Fa> (which used one-way MD5 hashing). This version works with the new phpass hashed passwords that WordPress uses, as well as maintaining backwards compatibility with the older (pre WordPress 2.5) MD5 hashed passwords. Theoretically, it will also work with any other hashing algorithm (because this plugin simply adds an extra layer in the process rather than trying to authenticate anything itself).\u003C\u002Fp>\n\u003Cp>This plugin requires PHP to be compiled with openssl support, which is a pretty standard option for most hosts.\u003C\u002Fp>\n\u003Ch3>Additional Info\u003C\u002Fh3>\n\u003Cp>In general…\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Semisecure Login Reimagined 3.2.x is tested to work with:\n\u003Cul>\n\u003Cli>WP 3.1.x\u003C\u002Fli>\n\u003Cli>PHP 4.3.x – 5.3.x\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Semisecure Login Reimagined 3.1.x was tested to work with:\n\u003Cul>\n\u003Cli>WP 2.8.x – 3.0.x\u003C\u002Fli>\n\u003Cli>PHP 4.3.x – 5.3.x\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Semisecure Login Reimagined 3.0.x was tested to work with:\n\u003Cul>\n\u003Cli>WP 2.7.x – 2.9.x\u003C\u002Fli>\n\u003Cli>PHP 4.3.x – 5.3.x\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Semisecure Login Reimagined 2.x was tested to work with:\n\u003Cul>\n\u003Cli>WP 2.2.x – 2.8.x\u003C\u002Fli>\n\u003Cli>PHP 4.2.x – 5.2.x\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Semisecure Login Reimagined 1.x was tested to work with:\n\u003Cul>\n\u003Cli>WP 2.1.x – 2.7.x\u003C\u002Fli>\n\u003Cli>PHP 4.3.x – 5.2.x\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>** See the readme.txt file for each version for more specific information\u003C\u002Fp>\n","\"Re-imagined\" version of Semisecure Login that uses public and secret-key encryption to encrypt passwords when logging in.",80,51291,100,1,"2011-07-15T23:08:00.000Z","3.1.4","3.1","",[28,29,30,31,32],"admin","encryption","login","rsa","security","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fsemisecure-login-reimagined\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsemisecure-login-reimagined.zip",0,null,"2026-03-15T15:16:48.613Z",{"slug":39,"name":40,"version":41,"author":4,"author_profile":5,"description":42,"short_description":43,"active_installs":9,"downloaded":44,"rating":35,"num_ratings":35,"last_updated":45,"tested_up_to":46,"requires_at_least":47,"requires_php":26,"tags":48,"homepage":53,"download_link":54,"security_score":8,"vuln_count":35,"unpatched_count":35,"last_vuln_date":36,"fetched_at":37},"attachment-page-comment-control","Attachment Page Comment Control","1.0.2","\u003Cp>Just like regular posts and pages, attachments have their own \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FUsing_Image_and_File_Attachments#Inserting_Images\" rel=\"nofollow ugc\">pages\u003C\u002Fa> where guests can leave comments (and can also accept trackbacks\u002Fpingbacks).  Unlike regular posts and pages, attachment pages don’t offer any UI controls that let you choose (on an individual basis) which attachment pages should allow comments and pings.\u003C\u002Fp>\n\u003Cp>This plugin corrects this issue by giving you the ability to turn comments and pings on or off for individual attachment pages within your media library.\u003C\u002Fp>\n\u003Cp>The global setting to allow comments or pings by default already applies to attachment pages.\u003C\u002Fp>\n","Gives you the ability to turn comments and pings on or off for individual attachment pages within your media library.",3509,"2010-06-03T19:42:00.000Z","3.0.5","2.5",[49,50,51,52],"attachments","comments","media-library","pings","http:\u002F\u002Fmoggy.laceous.com\u002F2010\u002F04\u002F04\u002Fattachment-page-comment-control\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fattachment-page-comment-control.zip",{"slug":56,"name":57,"version":58,"author":4,"author_profile":5,"description":59,"short_description":60,"active_installs":61,"downloaded":62,"rating":35,"num_ratings":35,"last_updated":63,"tested_up_to":64,"requires_at_least":65,"requires_php":26,"tags":66,"homepage":69,"download_link":70,"security_score":8,"vuln_count":35,"unpatched_count":35,"last_vuln_date":36,"fetched_at":37},"invalidate-logged-out-cookies","Invalidate Logged Out Cookies","0.1.1","\u003Cp>\u003Cstrong>Due to lack of interest (both my own and based on the number of downloads) this plugin will not be updated for WP 3.0\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>WordPress’ auth cookies include a built-in expiration date (either 2 or 14 days depending on if the ‘Remember Me’ option is checked). Even if you remove the client-side cookie (by manually logging out or just closing your browser if ‘Remember Me’ wasn’t checked when logging in) the data that was stored within the cookie is still valid until the expiration date is reached.\u003C\u002Fp>\n\u003Cp>This could be an issue if someone managed to “steal” your cookie(s). They would still be able to access your website for some time into the future.\u003C\u002Fp>\n\u003Cp>This plugin will immediately invalidate your auth cookies when you manually log out. This, of course, also means that you have to manually click ‘Log out’ for this plugin to work properly (you can’t just close your browser to remove any cookies that expire at the end of the session). This won’t prevent session hijacking, but should limit the amount of time that an attacker can access your website.\u003C\u002Fp>\n","This plugin will immediately invalidate your auth cookies when you manually log out.",10,2183,"2010-05-22T00:43:00.000Z","2.9.2","2.9",[67,30,68,32],"cookies","logout","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Finvalidate-logged-out-cookies\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Finvalidate-logged-out-cookies.zip"]