Release Notes 20.x - 29.x
29.1
2023-07-20
PrivX 29.1 is an incremental release on top of PrivX 29.0. This release contains a few important bug fixes*
- [PX-6087] rdp-proxy can crash with an runtime error
- [PX-6076] privx-carrier status update causes slow memory leak
- [PX-5957] Installing PrivX 29 breaks dnf in Amazon Linux 2023
- [PX-6140] Devtools and popups are not working in v29.0 carrier browser images
29.0
2023-05-04
Important Notes for This Release
Azure-Directory Migration to MS Graph
If you have set up Azure user/host directories using Azure AD Graph API, such directories will be automatically migrated to using MS Graph API when you upgrade to this release. After upgrade, you will still need to manually set the the following API permissions for the PrivX app in Azure Portal:
Microsoft Graph→Application Permissions
- User.Read.All
- Groups.Read.All
Azure AD Graph API shall be deprecated in June 2023.
For more information about setting up Azure directories with MS Graph, see Azure AD as a User Directory via Microsoft Graph API.
Web Proxy no longer uses Squid
Since PrivX 29, PrivX Web Proxy no longer uses Squid for proxying HTTPS traffic. Proxying features have now been implemented in PrivX Web Proxy binary. All Squid dependencies have been removed from RPM package.
If you still need Squid specific features for some reason, the latest PrivX core package is backwards compatible with earlier Carrier and Web Proxy components.
After upgrading PrivX core, Carrier, and Web Proxy to version 29, you need to re-download web-proxy-config.toml file via PrivX UI and replace your old config.
Required actions to optimize PrivX performance
As part of our ongoing effort to optimize PrivX performance, we have introduced additional indexing support from PrivX 28. Some improvement requires pg_trgm
extension to PrivX database. Please read Improve Performance with Indexing before upgrade.
Routing prefix name does not allow mixed cases
PrivX web gateways and extenders can be grouped under same routing prefix to achieve high-availability. Routing prefix name used be treated as case sensitive, but name in connection target is treated as case-insenstive by ssh native client. To avoid potential configuration error, only lowercase letters and numbers are allowed in routing prefix names.
Deprecation Warnings
Redis Support Ending
We recommend you to use PostgreSQL PrivX inter microservice notifications. Please change notification mechanism to PostgreSQL if your PrivX still uses Redis for notifications. Redis support will be ended in future releases
PostgreSQL 9.x and 10.x Support Ending
PostgreSQL 9.x and 10.x have reached end of life since 2021 and 2022 respectively and support for these database versions will be dropped in a future PrivX release.
SHA-1-Certificate End of Support Imminent
Support for certificates signed with SHA-1 shall be dropped in future PrivX releases.
Practical attacks against SHA-1 have been demonstrated in 2017 and publicly trusted Certificate Authorities have not issued SHA-1 certificates since 2015.
Supported releases and upgrade path
After this release, we produce security and stability fixes for PrivX 29.x, 28.x, and 27.x. Older versions are not officially supported. We recommend you upgrade as soon as you can if you are running an unsupported version.
Upgrading to this version is supported from three previous major versions (28.x, 27.x, 26.x). For more information about upgrading from older versions, see Upgrade from Older Releases.
New Features
- [PX-3319] Enable Web Connections to be routed through extenders
This feature allows PrivX Web Proxy to route web traffic to different networks via Extenders. - [PX-4316] "Secret" tab can be disabled by customer
- [PX-4815] PrivX login form is collapsible
- [PX-5661] Extender can connect to multiple PrivX URLs.
- [PX-5674] PrivX web client connections support new keyboard layouts for Portuguese, Dutch and Romanian. Also see Tips to set correct keyboard layout
- [PX-3249] admin-tool to reset context limitation of roles and local user password
- [PX-5734] Visual editor for json settings in UI
Improvements
- [PX-5792] Possible to use existing database and database user in Kubernetes deployment
- [PX-5679] Carrier container performance improvement by replacing
lsof
withss
command in exit.sh script - [PX-5741] Support multiple PrivX FQDNS in Kubernetes deployment
- [PX-5338] SSH Bastion interactive mode performance improvement when host list is very long
- [PX-5320] Support tags to network target
- [PX-5781] Indexing to connection table for performance improvement
- [PX-5496] Troubleshooting scripts support more options
Bug fixes
- [PX-4438] File uploads might fail in web target connections
- [PX-5237] PrivX core/Extender/Web-Proxy rpms should not depend on firewalld
- [PX-5671] Deploying new carrier/web-proxy on existing carrier/web-proxy host fails because of invalid certificate
- [PX-5726] Refreshing single MS Graph user does not obey group filters
- [PX-5790] Carrier should fall back to default Firefox image if container name is not defined
- [PX-5805] After selecting role, it is not possible to select a membership while creating a request for a role
- [PX-5815] Typo on the Administration→Deployment page
- [PX-5822] SCIM directory
eq
filter not working properly - [PX-5825] Incorrect version number in role-store.toml
- [PX-5830] Incorrect version number in monitor-service.toml
- [PX-5879] The path property for personal secrets API has a leading space
- [PX-5883] Web host is resolved incorrectly, if there's duplicate url on different hosts
- [PX-5885]
Graph API and GSuite user directories do not recover from network errors - [PX-5891] Vulnerable docker lib used in extender
- [PX-5761] workflow request for a deleted role should not be possible
- [PX-5878] Extender routing prefix validation is not done properly. This disallows using other than lower case letters and numbers.
Known Issues
- When upgrading PrivX Web Proxy to v29, make sure to stop Squid service first. In some cases, the discontinued Squid process won't get killed on the upgrade but needs to be stopped manually.
- [PX-6014]
Downloaded extender-config.toml is missing "privx_extender_service_enabled = true" setting. Admin should add that after downloading the config file. - [PX-1517] Permission denied for AuthorizedPrincipalsCommand on AWS RedHat AMI
- Workaround: To correct SELinux context, copy the
principals_command.sh
to correct location:# scp -i key.pem principals_command.sh user@target:/tmp/ # ssh -i key.pem user@target "sudo cp /tmp/principals_command.sh /etc/ssh/"
- Workaround: To correct SELinux context, copy the
- [PX-1711] RDP fails to connect to target in maintenance mode, need support for /admin flag
- [PX-1835] Extender/Carrier/WebProxy configs are not migrated on upgrade
- [PX-1875] Web proxy login does not work, if login page does requests to multiple domains
- [PX-2947] No sound when viewing recorded rdp-mitm connection.
- [PX-3086] PrivX role mapping to AD OU not working as expected.
- [PX-3529] Default access group CA key is always copied on the host when running the deployment script via Extender
- [PX-4215] Successful OIDC login might generate too long auth code as query parameter causes access-token fetching to fail (there's a workaround in Nginx config since PrivX 27.0)
- [PX-4218] RDP native clients do not work in Kubernetes environment when running under non-root account
- [PX-4352] UI shows deleted local user after delete
- [PX-4616] Upgrade may stop Carriers and Web Proxies from reconnecting.
- Workaround: Restart affected Carrier and Web-Proxy services.
- [PX-4650] Setting access_token_valid to "1m" kicks the user out to the login page
- [PX-4662] Pasting larger text amount in Carrier/Proxy host fails (limited to 16kB for now)
- [PX-4689] PrivX Linux Agent leaving folders in /tmp
- [PX-4809] Empty file(s) created when ICAP detects malicious uploads with SCP via SSH Bastion.
- [PX-5394] SSH cert auth conn fail after rotating PrivX CA Key
- [PX-5558] Privx does not support password change required option for user in auth flow via webauthn.
- [PX-5760] RDP Proxy fails to start.
- [PX-5798] Typing becomes slower while mouse is hovering over clickable link in web client
- Workaround: In an open connection, click Settings, then under Advanced, disable Clickable Links.
28.1
2023-03-17
PrivX 28.1 is an incremental release on top of 28.0 with bug fixes and security update
- [PX-5830] Incorrect data version number in monitor-service.toml
- [PX-5825] Incorrect data version number in role-store.toml
- [PX-5808] Microservices may crash at start due to cached sessions in Redis
- [PX-5801] Update to golang.org/x/net package to version 0.8
28.0
2023-03-01
Important Notes for This Release
Azure-Directory Migration to MS Graph
If you have set up Azure user/host directories using Azure AD Graph API, such directories will be automatically migrated to using MS Graph API when you upgrade to PrivX 28. After upgrade, you will still need to manually set the the following API permissions for the PrivX app in Azure Portal:
Microsoft Graph→Application Permissions
- User.Read.All
- Groups.Read.All
Azure AD Graph API shall be deprecated in June 2023.
For more information about setting up Azure directories with MS Graph, see Azure AD as a User Directory via Microsoft Graph API.
PrivX-Carrier rpm package no longer includes the default carrier container
Instead, it downloads the container from Internet. After upgrade, make sure to re-download your carrier-config.toml via PrivX UI and verify which browser container version you wish to use.
See documentation for more details
Deprecation Warnings
PostgreSQL 9.x and 10.x Support Ending
PostgreSQL 9.x and 10.x have reached end of life since 2021 and 2022 respectively and support for these database versions will be dropped in a future PrivX release.
SHA-1-Certificate End of Support Imminent
Support for certificates signed with SHA-1 shall be dropped in future PrivX releases.
Practical attacks against SHA-1 have been demonstrated in 2017 and publicly trusted Certificate Authorities have not issued SHA-1 certificates since 2015.
Supported releases and upgrade path
After this release, we produce security and stability fixes for PrivX 28.x, 27.x, and 26.x. Older versions are not officially supported. We recommend you upgrade as soon as you can if you are running an unsupported version.
Upgrading to this version is supported from three previous major versions (27.x, 26.x, 25.x). For more information about upgrading from older versions, see Upgrade from Older Releases.
New Features
- [PX-4308] Improve audit-event-search performance with trigram indexing.
- If upgrading from an earlier PrivX version, you must enable this manually as described in Audit-Event Indexing for Faster Searches.
- [PX-5584] Validate winrm certificate in password rotation service
Improvements
- [PX-3574] Principal keys of roles are not generated during role creation, but on demand
- [PX-4376] Audit events are generated for housekeeping actions
- [PX-4825] MFA reset/init should generate an audit event
- [PX-4993] Service health check also detects protocol version and latency
- [PX-5114] Allowed IP addresses for authorized key increased from 16 to 256
- [PX-5168] Allow less strict target url checking for web connections
- [PX-5208] Role drop down list shows more than 100 results
- [PX-5212] New host tag "privx-ssh-certificate-template" for configuring certificate templates
- [PX-5367] Add logging of kex methods to hybrid kex handlers
- [PX-5372] Carrier browser is not shipped in PrivX-Carrier rpm packages
- [PX-5462] Post install script checks for postgresql before prompting local vs external DB.
- [PX-5486] Rewrite role-store azure cloud module to use new SDK version
- [PX-5516] Move deleted "role ID to name mappings" to role-store
- [PX-5522] connection-manager DB queries optimization on UEBA status check
- [PX-5528] Button to disable UEBA configuration
- [PX-5549] Link to session-specific audit events directly from the monitor / sessions view
- [PX-5637] UI: remove "JSON" from setting titles
- [PX-5684] Add "Windows"-key into Send Keys
- [PX-5685] License check relaxed to improve SCIM sync performance
- [PX-5692] Relax nginx proxy_read_timeout for audit event search and connection search endpoints
- [PX-5704] UI text refresh by dropping all-caps styles to improve the readability
Bug fixes
- [PX-4824] Possible to supply invalid id of access group through API
- [PX-5066] network target search api endpoint doesn't work with api client
- [PX-5289] Wrong response code when creating host with duplicate 'instance id'
- [PX-5391] UEBA: Cannot delete model if server is misconfigured
- [PX-5429] Access group admin cannot accept host key
- [PX-5514] audit event does not have the MODIFICATIONS property for webauthn credential
- [PX-5575] Monitoring status page components disappear after disconnect
- [PX-5588] Improve error message for session cache size
- [PX-5593] WebAuthn: cancel of adding of passkey considered as error
- [PX-5596] Services health check status does not get updated outside health check scans
- [PX-5608] Settings endpoint PUT fails with HTTP 400
- [PX-5623] carrier: return proper error when resolveContainerPort() fails
- [PX-5639] Microsoft Graph role store user provider does not return all users
- [PX-5649] OIDC login fails if jwks_uri contains keys that go-jose can't handle
- [PX-5667] Connection attempt to host with empty data causes RDP Proxy panics
- [PX-5668] Host search not finding any matches searching by service address
- [PX-5677] Host keyword search should not target json data
- [PX-5682] Cannot delete secret with special characters in name
- [PX-5696] postinstall may fail to start nginx
- [PX-5730] Odd behavior when editing script templates
- [PX-5731] Panic in extender service after restart attempt
- [PX-5762] ssh-mitm: SFTP ICAP scan for uploaded files leaves the connection specific empty scan directory behind
- [PX-5770] Housekeeping task may remove trails unintentionally
Known Issues
- [PX-1517] Permission denied for AuthorizedPrincipalsCommand on AWS RedHat AMI
- Workaround: To correct SELinux context, copy the
principals_command.sh
to correct location:# scp -i key.pem principals_command.sh user@target:/tmp/ # ssh -i key.pem user@target "sudo cp /tmp/principals_command.sh /etc/ssh/"
- Workaround: To correct SELinux context, copy the
- [PX-1711] RDP fails to connect to target in maintenance mode, need support for /admin flag
- [PX-1835] Extender/Carrier/WebProxy configs are not migrated on upgrade
- [PX-1875] Web proxy login does not work, if login page does requests to multiple domains
- [PX-2947] No sound when viewing recorded rdp-mitm connection.
- [PX-3086] PrivX role mapping to AD OU not working as expected.
- [PX-3529] Default access group CA key is always copied on the host when running the deployment script via Extender
- [PX-4215] Successful OIDC login might generate too long auth code as query parameter causes access-token fetching to fail (there's a workaround in Nginx config since PrivX 27.0)
- [PX-4218] RDP native clients do not work in Kubernetes environment when running under non-root account
- [PX-4352] UI shows deleted local user after delete
- [PX-4616] Upgrade may stop Carriers and Web Proxies from reconnecting.
- Workaround: Restart affected Carrier and Web-Proxy services.
- [PX-4650] Setting access_token_valid to "1m" kicks the user out to the login page
- [PX-4662] Pasting larger text amount in Carrier/Proxy host fails (limited to 16kB for now)
- [PX-4689] PrivX Linux Agent leaving folders in /tmp
- [PX-4809] Empty file(s) created when ICAP detects malicious uploads with SCP via SSH Bastion.
- [PX-5394] SSH cert auth conn fail after rotating PrivX CA Key
- [PX-5558] Privx does not support password change required option for user in auth flow via webauthn.
- [PX-5798] Typing becomes slower while mouse is hovering over clickable link in web client
- Workaround: In an open connection, click Settings, then under Advanced, disable Clickable Links.
- [PX-5760] RDP Proxy fails to start.
📘 Note
Chromium password manager not yet supported for Chromium containers.
27.1
2023-03-10
PrivX 27.1 is an incremental release on top of 27.0 with critical bug fixes and security updates
- [PX-5808] Microservices may crash at start due to cached sessions in Redis
- [PX-5770] Housekeeping task may remove trails unintentionally
- [PX-5701] Update to golang 1.19.6
- [PX-5673] Update to openssl 1.1.1t
27.0
2023-01-02
Deprecation Warnings
SHA-1-Certificate End of Support Imminent
Support for certificates signed with SHA-1 shall be dropped in future PrivX releases.
Practical attacks against SHA-1 have been demonstrated in 2017 and publicly trusted Certificate Authorities have not issued SHA-1 certificates since 2015.
Supported releases and upgrade path
After this release, we produce security and stability fixes for PrivX 27.x, 26.x, and 25.x. Older versions are not officially supported. We recommend you upgrade as soon as you can if you are running an unsupported version.
Upgrading to this version is supported from three previous major versions (26.x, 25.x, 24.x). For more information about upgrading from older versions, see Upgrade from Older Releases.
New features
- [PX-1159] View active user sessions.
- [PX-2207] Color heading and watermark in connections
- [PX-2345] Login to PrivX with Passkey.
- [PX-5493] Single sign-on support for web UI.
- [PX-4856] Live monitor on RDP/Web/VNC connections.
- [PX-5449] New exclusion list setting allows filtering audit events that are written to database.
- [PX-5450] Separate retention period for transferred files in recorded sessions.
- [PX-5311] shift-jis encoding support in connection and session playback.
Improvements and bug fixes
- [PX-5067] privx-on-aws updated to support AWS CDK v2
- [PX-5382] OIDC redirect URL glob support to allow wildcards
- [PX-5468] External token provider page title change
- [PX-5502] Make SCIM MaxResults configurable
- [PX-5507] Send key combination Ctrl-Esc in RDP/VNC session
- [PX-5434] PrivX Go/Python SDKs to include IDP and UEBA endpoints
- [PX-5523] privx-cli new commands to invoke new IDP and UEBA endpoints
- [PX-4467] Settings PUT endpoint allows incorrect values for hostkey_algorithms
- [PX-5411] WEB-PROXY: wrong version number in status information
- [PX-5560] RDP-proxy ICAP file scanning regression fixed
- [PX-5479] Connection manager performance improvements
Known Issues
- [PX-1517] Permission denied for AuthorizedPrincipalsCommand on AWS RedHat AMI
- Workaround: To correct SELinux context, copy the
principals_command.sh
to correct location:# scp -i key.pem principals_command.sh user@target:/tmp/ # ssh -i key.pem user@target "sudo cp /tmp/principals_command.sh /etc/ssh/"
- Workaround: To correct SELinux context, copy the
- [PX-1711] RDP fails to connect to target in maintenance mode, need support for /admin flag
- [PX-1835] Extender/Carrier/WebProxy configs are not migrated on upgrade
- [PX-1875] Web proxy login does not work, if login page does requests to multiple domains
- [PX-2947] No sound when viewing recorded rdp-mitm connection.
- [PX-3086] PrivX role mapping to AD OU not working as expected.
- [PX-3529] Default access group CA key is always copied on the host when running the deployment script via Extender
- [PX-4215] Successful OIDC login might generate too long auth code as query parameter causes access-token fetching to fail
- [PX-4218] RDP native clients do not work in Kubernetes environment when running under non-root account
- [PX-4352] UI shows deleted local user after delete
- [PX-4616] Upgrade may stop Carriers and Web Proxies from reconnecting.
- Workaround: Restart affected Carrier and Web-Proxy services.
- [PX-4650] Setting access_token_valid to "1m" kicks the user out to the login page
- [PX-4662] Pasting larger text amount in Carrier/Proxy host fails (limited to 16kB for now)
- [PX-4689] PrivX Linux Agent leaving folders in /tmp
- [PX-4809] Empty file(s) created when ICAP detects malicious uploads with SCP via SSH Bastion.
- [PX-5394] SSH cert auth conn fail after rotating PrivX CA Key
- [PX-5558] Privx does not support password change required option for user in auth flow via webauthn.
- [PX-5593] Cancel of adding of passkey gives an error
- [PX-5608] UI shows an error even connection succeeds
- [PX-5760] RDP Proxy fails to start.
📘 Note
Chromium password manager not yet supported for Chromium containers.
26.2
2023-03-10
PrivX 26.2 is an incremental release on top of 26.0 with critical bug fixes and security updates
- [PX-5808] Microservices may crash at start due to cached sessions in Redis
- [PX-5770] Housekeeping task may remove trails unintentionally
- [PX-5701] Update to golang 1.19.6
- [PX-5673] Update to openssl 1.1.1t
26.0
2022-11-02
Deprecation Warnings
SHA-1-Certificate End of Support Imminent
Support for certificates signed with SHA-1 shall be dropped in future PrivX releases.
Practical attacks against SHA-1 have been demonstrated in 2017 and publicly trusted Certificate Authorities have not issued SHA-1 certificates since 2015.
Supported releases and upgrade path
After this release, we produce security and stability fixes for PrivX 26.x, 25.x, and 24.x. Older versions are not officially supported. We recommend you upgrade as soon as you can if you are running an unsupported version.
Upgrading to this version is supported from three previous major versions (25.x, 24.x, 23.x). For more information about upgrading from older versions, see Upgrade from Older Releases.
New features
- [PX-2580] Support for PrivX as OIDC Identity Provider
- [PX-4762] Support for Post-Quantum-Cryptography algorithms.
- New PQC KEX algorithms: ecdh-nistp521-kyber1024-sha512@ssh.com,curve25519-frodokem1344-sha512@ssh.com, sntrup761x25519-sha512@openssh.com
- Note: PQC algorithms are not mentioned in
ssh-algorithms.toml
. For correct lists of default algorithms, see Supported SSH Algorithms.
- [PX-3991] Monitor ongoing SSH connections in real-time
- [PX-3042] Additional container support for Web carrier: Firefox, Firefox Lite, Chromium Lite.
- Note: Password manager is not yet supported for Chromium containers.
- [PX-5011] User and Entity Behavioural Analytics: automatically audit and block potentially suspicious SSH and RDP connections based on connection data from your network environment.
- [PX-5286] Hostname as parameter to password-rotation scripts
- [PX-4100] Utility for cleaning up old daily backups
Improvements
- [PX-5132] Document missing permissions in public docs
- PX-5083] Validate user settings
- [PX-5064] Unified naming conventions for binaries and configuration files.
- [PX-5012] Optimization on setting roles of logged in users
- [PX-5008] Add new Cert API Endpoints to the Golang SDK
- [PX-5007] Add new Identity Provider API Endpoints to the Golang SDK
- [PX-5006] Add missing Network Access Manager API Endpoints to Golang SDK
- [PX-4619] postinstall.sh writes timestamp and PrivX version when starting install or upgrade
- [PX-3762] Deployment script supports AWS instance metadata version 2
- [PX-4772] PrivX deployment on Kubernetes 1.24 is supported
Bug fixes
- [PX-5398] Session playback may cause high CPU usage
- [PX-5395] RDP-PROXY: can not create subdirectory in Files tab
- [PX-5342] MS Graph: number of users is incorrect with applied group names
- [PX-5318] In Kubernetes deployment context-based role restriction on time may not work correctly
- [PX-5316] Upgrading PrivX-Kube breaks AWS directory as ACCESS KEY ID is changed
- [PX-5297] API search function should accept empty POST body
- [PX-5275] Audit events search returns wrong count
- [PX-5272] monitor-service should not return component's hostname in status query
- [PX-5261] Workflow requests API call returns 0 count
- [PX-5240] Host search returns zero items
- [PX-5219] Microservices may fail to contact syslog after server reboot
- [PX-5207] Host tag comparison works only with lower case tags
- [PX-5214] Restricted shell does not requires all sub commands to match patterns from the same whitelist object
- [PX-5201] Restricted shell does not handle linefeed character correctly in terminal emulator
- [PX-5186] SSH command restrictions whitelist patterns cannot be easily used to block input/output redirection
- [PX-5181] Host-removed audit event has incorrect accessGroupID field
- [PX-5173] OIDC user's roles do not reflect OIDC server side changes during PrivX access token refresh
- [PX-5172] User may be incorrectly kicked out during token refresh if using multiple tabs in web UI
- [PX-5170] Secrets vault search may fail with filter + keyword combination
- [PX-5164] SSH session playback may stop after a short while due to wrong connection id is checked
- [PX-5119] host-store and role-store error messages updated
- [PX-5093] Secret vault UI doesn't show deleted roles nicely
- [PX-5058] troubleshoot.sh doesn't collect postgresql-*.log from /var/lib/pgsql/data/log folder on Rocky Linux 8
- [PX-5000] Golang SDK query parameters missing for SearchUsers request
- [PX-4944] SCIM push may create duplicate roles
- [PX-4862] Host health checks do not allow instance specific filtering
- [PX-4845] UI: Script template compiled script should not highlight normal text
Known Issues
- [PX-1517] Permission denied for AuthorizedPrincipalsCommand on AWS RedHat AMI
- Workaround: To correct SELinux context, copy the
principals_command.sh
to correct location:# scp -i key.pem principals_command.sh user@target:/tmp/ # ssh -i key.pem user@target "sudo cp /tmp/principals_command.sh /etc/ssh/"
- Workaround: To correct SELinux context, copy the
- [PX-1711] RDP fails to connect to target in maintenance mode, need support for /admin flag
- [PX-1835] Extender/Carrier/WebProxy configs are not migrated on upgrade
- [PX-1875] Web proxy login does not work, if login page does requests to multiple domains
- [PX-2947] No sound when viewing recorded rdp-mitm connection.
- [PX-3086] PrivX role mapping to AD OU not working as expected.
- [PX-3529] Default access group CA key is always copied on the host when running the deployment script via Extender
- [PX-4035] Token refresh does not work and tabs do not share session state on Safari 14.1.1
- [PX-4215] Successful OIDC login might generate too long auth code as query parameter causes access-token fetching to fail
- [PX-4218] RDP native clients do not work in Kubernetes environment when running under non-root account
- [PX-4352] UI shows deleted local user after delete
- [PX-4616] Upgrade may stop Carriers and Web Proxies from reconnecting.
- Workaround: Restart affected Carrier and Web-Proxy services.
- [PX-4650] Setting access_token_valid to "1m" kicks the user out to the login page
- [PX-4662] Pasting larger text amount in Carrier/Proxy host fails (limited to 16kB for now)
- [PX-4689] PrivX Linux Agent leaving folders in /tmp
- [PX-4809] Empty file(s) created when ICAP detects malicious uploads with SCP via SSH Bastion.
- [PX-5432] Publickey login to SSH bastion using RSA authorized keys fails when using openssh-8.8 or later
- Workaround: Use other key types than RSA, or enable ssh-rsa signature type for publickey authentication:
# ssh -o "PubkeyAcceptedAlgorithms +ssh-rsa" ...
- Workaround: Use other key types than RSA, or enable ssh-rsa signature type for publickey authentication:
- [PX-5760] RDP Proxy fails to start.
25.0
2022-08-30
Deprecation Warnings
SHA-1-Certificate End of Support Imminent
Support for certificates signed with SHA-1 shall be dropped in future PrivX releases.
Practical attacks against SHA-1 have been demonstrated in 2017 and publicly trusted Certificate Authorities have not issued SHA-1 certificates since 2015.
Supported releases and upgrade path
After this release, we produce security and stability fixes for PrivX 25.x, 24.x, and 23.x. Older versions are not officially supported. We recommend you upgrade as soon as you can if you are running an unsupported version.
Upgrading to this version is supported from three previous major versions (24.x, 23.x, 22.x). For more information about upgrading from older versions, see Upgrade from Older Releases.
See updated installation instructions
New features
- [PX-2879] SSH command restrictions.
- Restrict the commands that can be run by users on SSH target accounts.
- Restrictions may be customised per role.
Improvements
- [PX-5006] New API endpoints (cert, identity provider, and network access manager) supported by PrivX Go SDK
- [PX-4913] Housekeeping task to remove old certificates from database
- [PX-4870] Deployment script to support adding host tags
- [PX-4768] Authentication certificate signature logged to Audit Event [401]
- [PX-4685] Support Amazon Linux 2022 as PrivX installation server
- [PX-4628] Show host name in PrivX ssh bastion interactive connection list
- [PX-4583] Housekeeping task to remove the empty trail folders
- [PX-4453] /var/log/privx/guacd.log is less verbose
- [PX-4405] Make CA key expiration time known to admins
- [PX-4380] Show warning if database or target host clocks are not in sync
- [PX-4191] Kubernetes PrivX container images cleanup
- [PX-4907] REST clients should fetch objects in batches of 1000 objects, where applicable
- [PX-4862] New property in shared-config.toml allows skipping health check of hosts with host tags
- [PX-5054] Support for ClearSwift ICAP gateway scan messages
- [PX-5180] postinstall.sh to support
generic-pkcs11
params for non-interactive mode
Bug fixes
- [PX-4560] Deleted roles are displayed as "Untitled" in UI
- [PX-5128] Explicit members are not counted at all when showing role member counts
- [PX-5124] API allows to create host without role id
- [PX-5068] Incorrect error field contents in audit events when ssh-mitm sftp upload is blocked by ICAP
- [PX-5065] postinstall.sh fails without firewalld configuration commands
- [PX-5059] Network target's disabled property is not handled properly
- [PX-5056] Deployment script adds host to PrivX with role 'Untitled'
- [PX-5055] AD directory status not updated, if bind password is incorrect
- [PX-5026] PrivX 24 Kubernetes migration script doesn't have custom syslog configuration
- [PX-5012] Connection more likely to fail for user who has many roles
- [PX-5003] Hosts are incorrectly disabled when license update fails
- [PX-4979] Carrier web urls break if using '&' characters in urls
- [PX-4933] ssh-proxy: client IP address is not conveyed to authorizer in the REST API requests
- [PX-4922] Audit log gets spammed if no connection to directory
- [PX-4681] Deployment script gives unclear error message when deploying a host that already exists
- [PX-4606] PrivX Server ports not opened if firewalld default zone isn't named public
- [PX-4602] PrivX as ssh client doesn't send ECDH algorithms in correct order
- [PX-4441] PrivX logs do not show the correct error when deployment script fails to modify /etc/sshd_config
- [PX-4338] PrivX does not work nicely with OpenSSH MaxSessions 1
- [PX-4334] Vault API query returns wrong count in case of offset larger than total items count
- [PX-4952] User-logged-in audit event when using external JWT token exchange should show identity provider name
- [PX-4932] remoteAddress in user store's audit event is 127.0.0.1 which is incorrect
Known Issues
- [PX-1517] Permission denied for AuthorizedPrincipalsCommand on AWS RedHat AMI
- Workaround: To correct SELinux context, copy the
principals_command.sh
to correct location:# scp -i key.pem principals_command.sh user@target:/tmp/ # ssh -i key.pem user@target "sudo cp /tmp/principals_command.sh /etc/ssh/"
- Workaround: To correct SELinux context, copy the
- [PX-1711] RDP fails to connect to target in maintenance mode, need support for /admin flag
- [PX-1835] Extender/Carrier/WebProxy configs are not migrated on upgrade
- [PX-1875] Web proxy login does not work, if login page does requests to multiple domains
- [PX-2947] No sound when viewing recorded rdp-mitm connection.
- [PX-3086] PrivX role mapping to AD OU not working as expected.
- [PX-3529] Default access group CA key is always copied on the host when running the deployment script via Extender
- [PX-4035] Token refresh does not work and tabs do not share session state on Safari 14.1.1
- [PX-4215] Successful OIDC login might generate too long auth code as query parameter causes access-token fetching to fail
- [PX-4218] RDP native clients do not work in Kubernetes environment when running under non-root account
- [PX-4352] UI shows deleted local user after delete
- [PX-4616] Upgrade may stop Carriers and Web Proxies from reconnecting.
- Workaround: Restart affected Carrier and Web-Proxy services.
- [PX-4650] Setting access_token_valid to "1m" kicks the user out to the login page
- [PX-4662] Pasting larger text amount in Carrier/Proxy host fails (limited to 16kB for now)
- [PX-4689] PrivX Linux Agent leaving folders in /tmp
- [PX-4809] Empty file(s) created when ICAP detects malicious uploads with SCP via SSH Bastion.
- [PX-5186] SSH command restrictions whitelist patterns cannot be easily used to block input/output redirection
- Workaround: Avoid wildcard patterns when possible
24.0
2022-06-27
Important Notes
End of life for Legacy Certificates
PrivX 22 and later will no longer support workaround for legacy X.509 certificates that do not contain server FQDN in Subject-Alt-Name extension field. Please upgrade your server certificates to include SAN extension before upgrading to PrivX 22 or later releases.
Deprecation Warnings
CentOS 8 is no longer supported
PrivX does not support CentOS 8 release because CentOS 8 reached end of life during December 2021. From PrivX 21, Rocky Linux 8 is supported. You may Migrate to Rocky Linux.
SHA-1-Certificate End of Support Imminent
Support for certificates signed with SHA-1 shall be dropped in future PrivX releases.
Practical attacks against SHA-1 have been demonstrated in 2017 and publicly trusted Certificate Authorities have not issued SHA-1 certificates since 2015.
Supported releases and upgrade path
After this release, we produce security and stability fixes for PrivX 24.x, 23.x, and 22.x. Older versions are not officially supported. We recommend you upgrade as soon as you can if you are running an unsupported version.
Upgrading to this version is supported from three previous major versions (23.x, 22.x, 21.x). For more information about upgrading from older versions, see Upgrade from Older Releases.
New features
- [PX-3980] Real-Time Auditing SSH Connections
- [PX-4044] Login to PrivX with JWT token from trusted token provider
- [PX-4831] Monitoring→Certificates displays certificates configured in PrivX
- [PX-4189] SCIM directory supports user import filter
- [PX-4419] ICAP antivirus check for file transfers using SFTP
- [PX-4298] Firefox browser in web carrier allows popups
Improvements
- [PX-4917] PrivX Router supports multiple RAC_IP_POOL / RAC_IP6_POOL in setup.sh
- [PX-4942] Upgrade Go versions to the 1.17.11
- [PX-4906] PrivX ICAP antivirus support WithSecure Atlant and Clearswift Secure ICAP Gateway
- [PX-4901] Request/Approval view supports more search filters
- [PX-4897] Guacamole log level aligned to RDP_PROXY_LOG_LEVEL in
/opt/privx/scripts/local-env
- [PX-4813] Support OIDC v2.0 issuer urls with Azure
- [PX-4752] Network target client ping to detect disconnects
- [PX-4719] initial_install.sh prompt user for number of trusted load balancers
- [PX-4702] Monitoring→Status component auto-collapse when no errors
- [PX-4489] Option
--delegated-principals-all
support by deployment script - [PX-4392] Set screen resolution in RDP-PROXY session
- [PX-4252] OIDC settings in SCIM directory is optional
Bug fixes
- [PX-5001] Privx ICAP does not scan the tmp folder for ssh-proxy and ssh-mitm in kubernetes env
- [PX-4988] API documentation fix for /authorizer/api/v1/ca/authorize
- [PX-4968] Deleting AWS directory does not delete aws roles from db
- [PX-4929] Workflowengine.log missing after installation
- [PX-4881] Workflows page in PrivX UI does not handle more than 50 workflows
- [PX-4842] Inaccurate error message when deleting password rotation script/policy which is in use
- [PX-4774] RDP smartcard deployment instruction on PrivX UI doesn't mention NLA
- [PX-4727] Possible to bypass domain restrictions on web targets by editing URL in URL bar
- [PX-4699] POST /authorizer/api/v1/ca/authorize returning OpenSSH certificates in incompatible format
- [PX-4239] Instruction fixes Deployment page for manual ssh host configuration
Known Issues
- [PX-1517] Permission denied for AuthorizedPrincipalsCommand on AWS RedHat AMI
- Workaround: To correct SELinux context, copy the
principals_command.sh
to correct location:# scp -i key.pem principals_command.sh user@target:/tmp/ # ssh -i key.pem user@target "sudo cp /tmp/principals_command.sh /etc/ssh/"
- Workaround: To correct SELinux context, copy the
- [PX-1711] RDP fails to connect to target in maintenance mode, need support for /admin flag
- [PX-1835] Extender/Carrier/WebProxy configs are not migrated on upgrade
- [PX-1875] Web proxy login does not work, if login page does requests to multiple domains
- [PX-2947] No sound when viewing recorded rdp-mitm connection.
- [PX-3086] PrivX role mapping to AD OU not working as expected.
- [PX-3529] Default access group CA key is always copied on the host when running the deployment script via Extender
- [PX-4035] Token refresh does not work and tabs do not share session state on Safari 14.1.1
- [PX-4218] RDP native clients do not work in Kubernetes environment when running under non-root account
- [PX-4352] UI shows deleted local user after delete
- [PX-4616] Upgrade may stop Carriers and Web Proxies from reconnecting.
- Workaround: Restart affected Carrier and Web-Proxy services.
- [PX-4650] Setting access_token_valid to "1m" kicks the user out to the login page
- [PX-4662] Pasting larger text amount in Carrier/Proxy host fails (limited to 16kB for now)
- [PX-4689] PrivX Linux Agent leaving folders in /tmp
- [PX-4809] Empty file(s) created when ICAP detects malicious uploads with SCP via SSH Bastion.
23.1
2022-04-19
PrivX 23.1 is an incremental release on top of PrivX 23.0 with golang security update.
- [PX-4861] Update golang to 1.17.9
23.0
2022-04-07
Important Notes
End of life for Legacy Certificates
PrivX 22 and later will no longer support workaround for legacy X.509 certificates that do not contain server FQDN in Subject-Alt-Name extension field. Please upgrade your server certificates to include SAN extension before upgrading to PrivX 22 or later releases.
Deprecation Warnings
CentOS 8 is no longer supported
PrivX does not support CentOS 8 release because CentOS 8 reached end of life during December 2021. From PrivX 21, Rocky Linux 8 is supported.
SHA-1-Certificate End of Support Imminent
Support for certificates signed with SHA-1 shall be dropped in future PrivX releases.
Practical attacks against SHA-1 have been demonstrated in 2017 and publicly trusted Certificate Authorities have not issued SHA-1 certificates since 2015.
<