PORT STATE SERVICE VERSION
7272/tcp open ssl/http Apache Tomcat/Coyote JSP engine 1.1
| ssl-enum-ciphers:
| SSLv3:
| ciphers:
| TLS_RSA_WITH_AES_256_CBC_SHA - strong
| compressors:
| NULL
| TLSv1.0:
| ciphers:
| TLS_RSA_WITH_AES_256_CBC_SHA - strong
| compressors:
| NULL
| TLSv1.1:
| ciphers:
| TLS_RSA_WITH_AES_256_CBC_SHA - strong
| compressors:
| NULL
| TLSv1.2:
| ciphers:
| TLS_RSA_WITH_AES_256_CBC_SHA - strong
| TLS_RSA_WITH_AES_256_CBC_SHA256 - strong
| compressors:
| NULL
|_ least strength: strong
To turn off SSL 3.0 on PMP
I did this and once the nmap is ran again the only protocol that shows is the TLSv1.0, which is better than having it respond to SSL.
PORT STATE SERVICE VERSIONReading through the other product forums I found that by adding TLSv1, TLSv1.1, TLSv1.2 to the SSLprotocols= line we get the other flavors of TLS turned on..
7272/tcp open ssl/http Apache Tomcat/Coyote JSP engine 1.1
| ssl-enum-ciphers:
| TLSv1.0:
| ciphers:
| TLS_RSA_WITH_AES_256_CBC_SHA - strong
| compressors:
| NULL
|_ least strength: strong
I did this and get these results back.
PORT STATE SERVICE VERSION
7272/tcp open ssl/http Apache
Tomcat/Coyote JSP engine 1.1
| ssl-enum-ciphers:
|
TLSv1.0:
| ciphers:
|
TLS_RSA_WITH_AES_256_CBC_SHA - strong
| compressors:
| NULL
| TLSv1.1:
| ciphers:
| TLS_RSA_WITH_AES_256_CBC_SHA - strong
|
compressors:
| NULL
| TLSv1.2:
| ciphers:
| TLS_RSA_WITH_AES_256_CBC_SHA - strong
|
TLS_RSA_WITH_AES_256_CBC_SHA256 - strong
| compressors:
| NULL
|_ least strength: strong
So by making these changes it fixes the default build of having SSL 3.0 ciphers (old demoted ciphers) available and just leaving the more secure TLS running. I will be turning the Olders TLS's off shortly.
Hope this helps others in your quest of in a better security posture for your organizations.
Regards,
--Forrest
Hello,
We are currently experiencing an issue when trying to set up automated password resets on our HP Procurve 2610 switches.
I have PMP set up to connect to the switches and log in using SSH, putty and the Web Browser. The automatic logins all work successfully.
As we reset the passwords on our switches on a regular basis I am attempting to set up the automatic password reset using SSH (current setting below):
I am able to run the 'Password Verify' command for each account successfully. However when I attempt to complete a remote password reset this fails with the following:
Given that I know the credentials stored in PMP for the switch are correct, what would be stopping the password reset?
When we first log into the switches using SSH/putty we get the following message, could this be causing problems and is there any way around this?
Regards
Mark
We have experienced a number of recurring issues during installs and upgrades of PMP on Linux. The main one is that the files and directories are being installed with "root" as the owner instead of the PMP user, even when the install script is being run as PMP. This results in the PMP service not starting up. The first time we encountered this, we were informed to chown the directories to the correct user. We have since had to do this for nearly every install and some upgrades. It would be preferable that this were done by the install script so we don't have to continually troubleshoot startup problems with the PMP service.
Next, as a High Availability installation, the upgrade process is cumbersome and error prone, again causing problems with the secondary server starting up and with replication. If the secondary server is currently working, why must we (basically) delete it and rebuild the secondary server from scratch? If this process was an upgrade and not an outright replacement, the issues of missing files, certs, incorrect ownership of directories, etc. could be avoided.
Has anyone else encountered these problems, and have you found a way
to resolve them?
Hi,
Our businesses keep growing, and so do cyber risks. To stay in control, we need to put tighter locks on privileged accounts. This calls for managing the entire life cycle of administrative passwords and closely monitoring privileged access.
You already know about Password Manager Pro that helps control privileged access. Its newly released enterprise e dition helps reinforce your security defences with the provision to automatically enumerate privileged accounts, closely monitor privileged sessions with dual controls, and integrate with enterprise IT infrastructure. I t is a complete Privileged Access Management solution built to bolster your IT security.
Please join us for a free webinar on July 22 to learn more about the e nterprise edition .
Webinar : Password Manager Pro Enterprise Edition - A Walk- through
Wednesday, July 22, 2015
10: 00 AM PST|PDT | 1: 00 PM EST | 10: 30 PM IST
Automatically discover privileged accounts and s treamline your everyday password management operations
Closely monitor privileged access with session recording and shadowing (dual controls)
Leverage integrations with ticketing systems and SIEM solutions for improved security
Thanks,
Bala
ManageEngine
Password Manager Pro
Hi,
when im trying to Upgrade PMP from 7101 to 7500 im getting an error saying Error Occured... Uninstalling.
Looking in updatemgrlog i see:
[com.adventnet.persistence.UpdateManagerUtil] [INFO] : Data
directory change permission steps
skipped
[com.zoho.framework.utils.crypto.EnDecrypt] [SEVERE] :
Encryption
failed
[com.adventnet.persistence.PersistenceInitializer] [INFO]
: Reading .\conf\database_params.conf
[com.zoho.framework.utils.crypto.EnDecrypt] [SEVERE] :
Encryption failed
[com.adventnet.ds.DefaultDataSourcePlugIn]
[INFO] : ConnectionPoolParams :: minSize :: [20], maxSize :: [1],
idleTimeout :: [1 800 seconds], blockingTimeout :: [30
seconds]
[com.adventnet.persistence.PersistenceInitializer]
[INFO] : Archive Adapter class :::
com.adventnet.db.archive.DefaultArchiveAdapter
[com.adventnet.persistence.PersistenceInitializer]
[INFO] : Storage Adapter class :::
null
[com.adventnet.db.api.RelationalAPI] [SEVERE] :
haltjvm.on.dbcrash is set to [false]
[SYSOUT] [INFO] :
shutDownStrings :: []
It might be worth mentioning that we just moved from an old to a new
server and this problem is on the new server. Can anyone point me in
the right direction?
Hi, we are your customer for over 5 years and by myself I’m using your software for about 10.
We’ve been using your password manager as core password software – but now – with lots of resources it gets annoying – mainly we use search option but normal users gets angry every day to find something.
At the beginning we started to use groups…yes tree view etc…but suddenly it occurred that in fact browsing them is even more annoying.
Guys – time to move with the software – we are looking at your competitors and they get better and better every day – your interface stays the same for years !
On one hand it’s good but on other hand... why we cannot browse resources like folders – just have nice tree view with folders created globally or locally or workable tree view to browse and explore ?
Just please try to work with few hundreds of them J on such flat interface.
Regards
Bogdan
