Warning into builds pipelines: Use Cipheriv for counter mode of aes-256-ctr

[al-cheb]

Issue Description

We faced next warning into all our builds pipelines:

Tasks: Install an Apple provisioning profile, Xcode, PowerShell, Command Line, Shell Script ...

Previous issue has not yet been fixed: https://github.com/microsoft/azure-pipelines-tasks/issues/9783

Environment

Server - Azure Pipelines Agent - Hosted on MacOS/Ubuntu/VS2017/VS2019

Task logs

==============================================================================
Task         : PowerShell
Description  : Run a PowerShell script on Linux, macOS, or Windows
Version      : 2.151.2
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell
==============================================================================
(node:776) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:776) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:776) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:776) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:776) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:776) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:776) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:776) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:776) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:776) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:776) Warning: Use Cipheriv for counter mode of aes-256-ctr
Generating script.

[maxim-lobanov]

Hi, We have faced with the same issue recently. It looks like it was not reproducing for a long time but returned back a week ago.

[damccorm]

@leantk - this is probably an issue with the old task-lib which used a function node has since deprecated, it should be fixable by consuming a newer version of the task-lib

[sgerace]

Hi @damccorm, we're seeing a similar issue. We have updated our agents to the latest version (2.164.6), but are still seeing this issue. When you say "consuming a newer version of the task-lib," how do we go about doing that?

[damccorm]

Hey @sgerace - that's something the task itself would need to do, its not an agent fix. The task-lib is in reference to the node library we provide which is used by most of our first party tasks. It used to use a cipher algorithm built into node for storing local variables/secrets. That library was deprecated and replaced by the cipheriv algorithm, which is what's leading to this warning.

So the easiest way for this problem to be solved is for any tasks that use the old task-lib (and have this warning appear) to update to use the newest version of the task-lib that we've published (which is currently version 2.9.3)

[sgerace]

Currently, in our YAML file we are doing something like this:

    - script: npm ci
      displayName: 'Install node modules'

Which produces the following output:

I guess my question is how do we update this task to "to use the newest version of the task-lib"? Is it something like this?

- task: CmdLine@2.9.3
  inputs:
    script: npm ci
    displayName: 'Install node modules'

(if so, is there any way to simply always use the latest without specifying a specific version). OR, does it involve actually installing something on the agents?

[damccorm]

The cmdline task needs to be updated on our end - we've actually done the work for this in that task specifically, it should roll out over the next few weeks. No action should be required on your end.

[sgerace]

Ahh, gotcha, that makes sense. Thanks!

[tbrophy]

Confirming (as expected) that this occurs Tue. Jan 28 15:05:26 PST 2020 for PythonScript@0...

[hsalluri259]

Hi @damccorm , I am running a python script in tasks, I am getting this warning from last two weeks.

Do I need to update my task-lib to use newest version or wait for cmdline task changes to roll out?

[ShvetsovZE]

Upgrading Azure DevOps GitVersion task on windows-latest hosted build agent from version 4 to 5 removed the warning as well as reduced task execution time from 1m 11 secs to 6 secs.

[Fizcko]

Same problem here.

What's not working?

Most of the tasks (native or not) in build or release jobs display Use Cipheriv for counter mode of aes-256-ctr

Azure DevOps Type and Version

Azure DevOps 2019 Update 1 on-premises

Agent Version and Platform

2.165.0 Windows and MacOs

This message wasn't diplayed with the agent versions 2.140.0, 2.141.0 or 2.155.1

@leantk any update ?

[leantk]

We have updated most of the tasks including the mentioned PythonScript, Powershell, and Shell. The changes are rolling out now and we are continuing to update the other tasks

[leantk]

I'll compose a list of what is left and add it here this week so it can be tracked

[Fizcko]

@leantk Great !

Thanks for the update.

[vravindranath]

@leantk @Fizcko

Guys, When can we expect this changes. Today also the release to appcenter is failing with not found error. Is there anything we need to do from our end. We had success using the task 2020-03-12T01:57:53.3980673Z ##[section]Starting: Android - Store 2020-03-12T01:57:53.4076928Z ============================================================================== 2020-03-12T01:57:53.4077242Z Task : App Center distribute 2020-03-12T01:57:53.4077548Z Description : Distribute app builds to testers and users via Visual Studio App Center 2020-03-12T01:57:53.4077847Z Version : 3.159.0 2020-03-12T01:57:53.4078051Z Author : Microsoft Corporation 2020-03-12T01:57:53.4078375Z Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/deploy/app-center-distribute 2020-03-12T01:57:53.4078932Z ============================================================================== 2020-03-11T13:33:13.9458318Z (node:1236) Warning: Use Cipheriv for counter mode of aes-256-ctr 2020-03-11T13:33:14.3263434Z ##[error]"{\"message\":\"Not found. Context ID: 5485d4fb-7ac0-42dd-8eea-089590675539\",\"statusCode\":404,\"code\":\"Not Found\"}" http response code: 404

Please confirm.

[damccorm]

@vravindranath can you open up a separate issue? The error you're seeing is different from the warnings

[carstenhag]

He's having the https://github.com/microsoft/azure-pipelines-tasks/issues/12521 issue, same as me.

[DevRCRun]

I'm also seeing this on the node task (locally hosted agent on windows server)

Starting: Npm

Task         : npm
Description  : Install and publish npm packages, or run an npm command. Supports npmjs.com and authenticated registries like Azure Artifacts.
Version      : 1.169.1
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/package/npm

SYSTEMVSSCONNECTION exists true
(node:7436) Warning: Use Cipheriv for counter mode of aes-256-ctr

[SureshBettadapur]

I am getting this error on self-hosted Ubuntu Linux agent Build error.txt

[leantk]

I made a separate issue to track this update for all the tasks that call to us: https://github.com/microsoft/build-task-team/issues/144

[leantk]

Reassigning to Release for Docker task updates. NPM needs updated as well

[peterson4ts]

I made a separate issue to track this update for all the tasks that call to us: microsoft/build-task-team#144

Dead link! Any news on this subject?

[timg83]

What is the current news about this issue? We are also receiving these. No blocking issues so far, but warnings are a signal something is not good and is a sign for something worse in the future.

Please do provide some feedback on this.

[dmcweeney]

Also getting this on the AzureRmWebAppDeployment@3 task

[PavelPikat]

Seeing for ms-vscs-rm.vss-services-ansible.ansible-task.Ansible@0 as well - https://marketplace.visualstudio.com/items?itemName=ms-vscs-rm.vss-services-ansible&targetId=696d346f-db19-4572-8d9a-18e120110d16&utm_source=vstsproduct&utm_medium=ExtHubManageList

[asg-dawn]

Is there any progress on this? Also getting this on the AppCenterDistribute@3 task

2020-09-29T13:43:43.1833800Z ##[section]Starting: Deploy /Users/runner/work/r1/a/{repo_name}/drop/{app_name}.ipa to Visual Studio App Center
2020-09-29T13:43:43.1844620Z ==============================================================================
2020-09-29T13:43:43.1845020Z Task         : App Center distribute
2020-09-29T13:43:43.1845400Z Description  : Distribute app builds to testers and users via Visual Studio App Center
2020-09-29T13:43:43.1845740Z Version      : 3.173.0
2020-09-29T13:43:43.1846000Z Author       : Microsoft Corporation
2020-09-29T13:43:43.1846410Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/deploy/app-center-distribute
2020-09-29T13:43:43.1846860Z ==============================================================================
2020-09-29T13:43:44.1702000Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1703260Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1718550Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1719560Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1720310Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1721040Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1721840Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1722570Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1723280Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1724160Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1724930Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1726390Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1727210Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1727940Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1728740Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1729490Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1730210Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1731010Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1731750Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1732470Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1733270Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:44.1734000Z (node:794) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-09-29T13:43:50.1875910Z ##[section]Finishing: Deploy /Users/runner/work/r1/a/_{repo_name}/drop/{app_name}.ipa to Visual Studio App Center

The tasks returns as successful but no bulid is send to App Center

[IainS1986]

I'm seeing this on the AppCenterDistribute@3 task version 3.173 as well, only it's also failing with a time out too.

Edit - looks like this task has been printing this out for a long time (month+ at least going back through my pipeline history). Appcenter is returning 502 but imagine it's unrelated to that printout, might just be a blip appcenter side

[nguyenlamlll]

I encounter the same issue as @asg-trifork (with App Center distribute task, version 3, in Release pipeline). Although it shows as a warning, it's critically an error to me because the app is not distributed to AppCenter as promised.

[nguyenlamlll]

@damccorm, @alexander-smolyakov: Hi guys. I'm sorry for tagging, but may I ask about the progress of this issue? It seems that the original problem is fixed in a few tasks, but still happens in "AppCenterDistribute@3" task. This is severe to our organization as we use the tasks in many pipelines :(

[shararehl]

We are getting the same warning on Azure Build Pipeline while running Ghost Inspector Extension. Any update on this?

[tete2soja]

Hello,

I have the same issue using Ansible Extension:

2020-11-12T08:56:44.5866532Z (node:21928) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-11-12T08:56:44.5868036Z (node:21928) Warning: Use Cipheriv for counter mode of aes-256-ctr
[..]
2020-11-12T08:56:44.5887078Z (node:21928) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-11-12T08:56:44.5888122Z (node:21928) Warning: Use Cipheriv for counter mode of aes-256-ctr

The output is showing up as failed even if the ansible return is success.

[johnybaryah]

Here to report the same issue using App Center Distribute, Task Version 3.*

[silkimen]

Hi guys, same issue still apparent in AppCenterDistribute@3:

[BennyBread]

I'm having the same problem for the run command Line task: As this has bothered me for a long time I was googling and this seems to be the right spot to mention it.

[BKJackson]

This is still happening when I try to push a docker image from the Azure build pipeline.

[markrobert194]

Any updates? Seems to be removing items from my AndroidManifest

[amkondi]

same issue here !! Any updates plz ?

[giondo]

same issue for

• task: ms-vscs-rm.vss-services-ansible.ansible-task.Ansible@0 any workaround that we can implement ?

[bersot1]

any update? Same issue here

[lucasraziel]

Any news? I am having same issue

[jessejjohnson]

This seems to be a real issue. I too am having the same issue.

Update 12/14/2021

My issue might be result of known system issues mentioned on App Center Status Page (screenshot below).

[suwu150]

I too am having the same issue？ any news?

Task         : App Center distribute
Description  : Distribute app builds to testers and users via Visual Studio App Center
Version      : 3.200.0
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/deploy/app-center-distribute
==============================================================================
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:11076) Warning: Use Cipheriv for counter mode of aes-256-ctr
##[error]Error: Failed find: ENOENT: no such file or directory, stat '/Users/runner/work/1/s/bin/react-devtools'
##[section]Finishing: Create distribution
##[section]Starting: Sign APK

[para0056]

Experiencing same issue with the terraform-outputs task.

[BennyBread]

It's been more than TWO years since this issue was opened and still no solution possible? I had this problem with Azure Devops 2019 and now even with 2020 Update1 this still exists... :-(

[sammetb]

I'm getting also this error right now:

2022-06-22T06:37:07.1118004Z ##[section]Starting: Run backup
2022-06-22T06:37:07.1125349Z ==============================================================================
2022-06-22T06:37:07.1125611Z Task         : Shell Exec
2022-06-22T06:37:07.1125831Z Description  : Execute shell commands without creating a shell file
2022-06-22T06:37:07.1126053Z Version      : 0.2.0
2022-06-22T06:37:07.1126222Z Author       : Tsuyoshi Ushio
2022-06-22T06:37:07.1126449Z Help         : Replace with markdown to show in help
2022-06-22T06:37:07.1126701Z ==============================================================================
2022-06-22T06:37:07.2259395Z rclone copy -v xyz
2022-06-22T06:37:07.2268777Z [command]/usr/bin/bash ./.tempexecution.sh
2022-06-22T06:37:07.2325739Z (node:1587) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-22T06:37:07.2326814Z (node:1587) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-22T06:37:07.2327589Z (node:1587) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-22T06:37:07.2328415Z (node:1587) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-22T06:37:07.2329198Z (node:1587) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-22T06:37:07.2330029Z (node:1587) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-22T06:37:07.2330798Z (node:1587) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-22T06:37:07.2331555Z (node:1587) Warning: Use Cipheriv for counter mode of aes-256-ctr
2022-06-22T06:37:07.2351877Z xxxxxxxxxxxxxxxxxxxxxx
2022-06-22T06:37:07.2362912Z ./.tempexecution.sh: line 2: rclone: command not found
2022-06-22T06:37:07.2427551Z ##[error]Error: /usr/bin/bash failed with return code: 127
2022-06-22T06:37:07.2438065Z ##[section]Finishing: Run backup

[StephenStrickland]

I've noticed that sometimes these warnings can be a red herring, usually they only show when a part of your pipeline fails. It's the strangest thing.

[ffloimair]

Same thing with the Ansible task. Seems this hasn't been updated for a while.

[bahadir-be]

same issue

[github-actions[bot]]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

[ffloimair]

Yeah maybe you guys should get going here. It's about time. It's not the issue that's stale, it's the maintainers. I mean come on! A hyped product that people pay for and then no feedback in more than 3 years? That's not only disappointing it is downright inacceptable!