DeprecationWarning

[HDBK2297]

##error [DEP0106] DeprecationWarning: crypto.createCipher is deprecated.
(Use node --trace-deprecation ... to show where the warning was created)
##error Warning: Use Cipheriv for counter mode of aes-256-ctr
##error [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.

[danielste888]

using v6.0.6 on Windows agent v3.242.1 displays the same error then the pipeline stops

[qetza]

Hi @HDBK2297, @danielste888,
Thanks for reporting the issue, I'll see if i can update the dependency.

[AndBrug]

Hello, any updates regarding this issue?
In my case, the warning is blocking and the pipeline stops even though the verbose mode logs the token replacements correctly.
I had to roll back to the old version of the task (@3) to avoid blocking production

[qetza]

Hi @AndBrug,
I cannot reproduce the issue locally so it's hard to fix. I'll take a look this week-end if i can find where the function is called and if i can update it.

[qetza]

After some investigation it seems that both issues are coming from the function _exposeTaskLibSecret in the azure-pipelines-task-lib which seems to be used when you have set a proxy password or a client cert password on the agent.

Can you confirm that you are setting on of these?

I'll report this issue to the team owning the azure-pipelines-task-lib.

[AndBrug]

I confirm that I am using a proxy password.

Thank you for your analysis and reporting the bug to the team responsible for the azure-pipelines-task-lib !

[danielste888]

Me too: I'm using it behind a corporate proxy

[work933k]

Same here. Also behind a corporate proxy. On v5 it was no problem.

[work933k]

I don't expect this issue will ever be resolved by ms.
Is there maybe a workaround to partially revert back to the previous situation?
I also wonder why other Azure DevOps Tasks don't seem to have reported the issue.
Maybe a workaround is to temporarily remove the proxy variables upon calling the lib function.

[qetza]

Hi @work933k,
I'm going to do some tests and see if I can either do a pull request on MS repository or have some code on my side where I'll patch the downloaded lib a build time.