Hmac-SHA1 WLA agent perm role how it worked if we have multiple cenarios

[Dewang Pratap Singh]

Our FTP client tool is supporting all the latest ciphers and macs variants. Since HMAC-SHA1 is listed at the first place and this is what it tries to do handshake with first. Since the server support it as of now, both (Client & Server) agreeing to use SHA1. If your server stops supporting SHA1, our client will use the latest CIPHER/MAC to do the handshake. So we should be fine.....?

 

As we moved HMAC-SHA2-256 mac to first place in the list and hoped that it would be used for the handshake on the next run so it the way it should work.

[Ravi Kiran Kunduri]

Hi,

I think sha2 algorithms are going to be supported soon from agent side. At this moment sha1 are supported. 

[Dewang Pratap Singh]

Hey Kiran,

We just got this SHA2 input from Broadcom KB article/Tech book and we referred it and added to our agent perm agent version we have now is 12.0.

So to be concluded we are saying the SHA2 cipher is not going to support under agent 12.0.

[Ravi Kiran Kunduri]

I checked the documentation , this HMAC is supported from 11.4 version and higher. So in 12.0 version also it should work fine.

Since you have put the sha2 as the first , it should use it. 

What is the error that you are getting when you tried this. I think we can raise a ticket/case to get more details on what error and why it is caused.

[Vikash Singh]

Hi Kiran, we have applied sha2 in agent however we are unable to find anything in job logs by which we can confirm that it is using HMAC. Could you please confirm what we can see in logs by which we can confirm that it is using sha2 

[Ravi Kiran Kunduri]

Check the ftp_scp_debug.log in the agent log directory if you enable debugging using the ftp.scp.debug.enable=true parameter in agentparm.txt file.