41 to 50 of 50
Dec 16, 2019
PS8 Update as 8.00201912161
Non-critical update. Changes include the following:
Fixed issues related to BandwidthMonitor (BM) plugin.
Dec 12, 2019
PS8 Update as 8.00201912121
Critical update. Changes include the following:
Fixed tracking bug where distances were not properly logged.
Dec 01, 2019
Password Sentry (PS) Version 8 (PS8) is scheduled to be released as stable in January 2020. PS8 will replace PS7 as the current stable version. At that time, PS7
will only be supported for critical security issues and bugs. June 01 2020, PS7 will no longer be supported: including no updates.
Nov 24, 2019
PS8 Update as 8.00201911241
Minor, non-critical update. Changes include the following:
Enhancement and improvement of the PS AdminCP Notification System.
Nov 20, 2019
PS8 Update as 8.00201911201
Changes include the following:
Fixes to Update app.
Fixes and improvements to error handling and logging.
Revision of database PS_BANDWIDTH_LOG table: RATE and FILESIZE columns changed to VARCHAR(25) type.
As in the case when users suspended, email generated to webmaster when IP suspended (when using optional AuthForm (AF) plugin).
Added functionality [AdminCP :: Users :: Login Log]: can now limit display to users whose Distance exceeds threshold.
Nov 04, 2019
PS8 Beta Released as 8.00201911041
Password Sentry (PS) Version 8 (PS8) officially released as Beta.
Nov 02, 2019
Password Sentry (PS) Version 8 (PS8) to be released as Beta on November 04 2019. Details available in Client Area.
Jan 02, 2019
PS7 Update :: Interlinking (IL) Plugin
We have updated the Interlinking (IL) Plugin. To make the plugin more secure, we added SECRET. Each Interlinking site defines a SECRET. During the handshake process between Interlinking sites, the site initiating
Interlinking passes the SECRET corresponding to the other site. It happens in the backgound such that the SECRET is hidden from view of the web surfer. This ensures that the latter cannot initiate the handoff, and
thereby gain access to the Interlinking protected area without the handshake.
Dec 28, 2018
PS7 Update as 7.00201812181
We have completed and released PS7 update (maintenance release) on Dec 18, 2018. Improvements include the following:
1. PS7 PHP 7+ compatible: uses MySQL Improved Extension (mysqli). Still compliant with PHP 4.1+ since mysqli functionality was introduced in PHP 4.1. Few, if any any, our competitors are mysqli / PHP 7 compliant.
2. PS7 IPv6 compliant. Most, if not all, our competitors are only IPv4 compliant, causing issues with users trying to access via IPv6 IP addresses which is becoming more
prevalent and common.
This maintenance release will allow clients to continue to use PS while we prepare PS8 for release. Note that PS7 is EOL (End-of-Life). PS7 has been updated and released on December 18 2018 to be PHP 7+ compatible.
PS7 (PHP components) now use the MySQLi Extension (Improved) API since the MySQL Extension (Original) API was deprecated as of PHP 5.5.0 - 5.6, and has been removed as of PHP 7.0.0 (next version after 5.6).
Critical since Security Support for PHP 5.6 ends December 31, 2018. We will continue to support PS7 to the end of December 31, 2019. Support includes technical support and updates in the form of bug fixes.
PS8 is currently in the later stages of development and testing. We expect to release PS8 in early 2019.
Oct 28, 2018
We are currently developing PS8. Coding nearly completed. Once done, begin local testing. We expect to release PS8 in early 2019. Improvements include the following:
1. PS8 PHP 7+ compatible: uses MySQL Improved Extension (mysqli). Still compliant with PHP 4.1+ since mysqli functionality was introduced in PHP 4.1. Few, if any any, our competitors are mysqli / PHP 7 compliant.
2. PS8 IPv6 compliant. Most, if not all, our competitors are only IPv4 compliant, causing issues with users trying to access via IPv6 IP addresses which is becoming more
prevalent and common.
3. PS8 assess uniqueness based on IP-derived coordinates (latitude and longitude). Each login will be mapped in terms of distance from initial login, where you define Distance Threshold. So, for example, if the second
logged login is calculated as 250 miles outside the initial login, and you set threshold for 200 miles, the login would be defined as unique. If a third login is calculated as 150 miles, then that login would not be
defined as unique. Less dependence on IP addresses such that if the same person uses the same device but on different IP (e.g., WiFi zone in same area), they are not incorrectly flagged as unique and potentially suspended.
4. Google Mapping functionality (which maps logins) updated to latest Google Maps API version. None of our competitors provide this functionality.