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

Issue Description

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

We faced next warning into builds pipelines:

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

Looks like here is fix for this: https://github.com/nodejs/node/issues/16746#issuecomment-341900420

Also it’s discussed on the forum: https://developercommunity.visualstudio.com/content/problem/475022/getting-warning-use-cipheriv-on-various-stages-of.html

Is this known issue? Do you plan to fix it?

Environment

Server - Azure Pipelines Agent - Hosted on MacOS

Task logs

##[section]Starting: Xcode build (signed)
==============================================================================
Task         : Xcode
Description  : Build, test, or archive an Xcode workspace on macOS. Optionally package an app.
Version      : 4.130.0
Author       : Microsoft Corporation
Help         : [More Information](https://go.microsoft.com/fwlink/?LinkID=613730)
==============================================================================
[command]/usr/bin/xcodebuild -version
(node:858) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:858) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:858) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:858) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:858) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:858) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:858) Warning: Use Cipheriv for counter mode of aes-256-ctr

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 11
Comments: 27 (9 by maintainers)

Most upvoted comments

Got same error when running ShellScript@2 task here. Any update?

meigaoms on Jan 25, 2020

I can also reproduce this issue. It is arising during the PowerShell task running in ubuntu-latest machines:

Task : PowerShell Description : Run a PowerShell script on Linux, macOS, or Windows Version : 2.163.1 Author : Microsoft Corporation Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell

(the script is extremely simple: parse an XML file and set a build variable).

dkmiller on Feb 18, 2020

Seeing the same:

2020-02-18T02:35:37.8717258Z ==============================================================================
2020-02-18T02:35:37.8717828Z Task         : Docker
2020-02-18T02:35:37.8718434Z Description  : Build, tag, push, or run Docker images, or run a Docker command
2020-02-18T02:35:37.8718945Z Version      : 1.157.0
2020-02-18T02:35:37.8719404Z Author       : Microsoft Corporation
2020-02-18T02:35:37.8719952Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/build/docker
2020-02-18T02:35:37.8720533Z
2020-02-18T02:35:38.2533445Z [command]/usr/local/bin/docker run ...
2020-02-18T02:35:38.2628584Z (node:42138) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-02-18T02:35:38.2644302Z (node:42138) Warning: Use Cipheriv for counter mode of aes-256-ctr
==============================================================================

Bnjmn83 on Feb 18, 2020

@lemessur When the build does work, does (node:1330) Warning: Use Cipheriv for counter mode of aes-256-ctr still appear?

Currently facing the same issue

Now that you mention it, I see the warning appearing with the same frequency in logs from recent successful builds. The error I’m seeing might not have anything to do with this warning.

The AppCenter Status page (https://status.appcenter.ms/) is now acknowledging some sort of issue with distribution so it’s probably being caused by whatever that is. The message was posted there a little over an hour ago, but I started seeing that error (##[error]“{“code”:“dependent_service_error”,“message”:“Error: Error: ESOCKETTIMEDOUT”}”) around 4 hours ago.

At this point I’m thinking that “Warning: Use Cipheriv for counter mode of aes-256-ctr” is some non-fatal issue that Microsoft does not care about (This thread is nearly a year old and there has been no official response) and it has nothing to do with our current build/distribution problems.

Edit: The original post links to a page mentioning that the solution is to install a new version of an NPM package, but that isn’t relevant at least in my case. The warning is occurring during an AppCenter build on a remote machine where I have no control over the package versions.

lemessur on Feb 14, 2020

Hello, @jlidbeck, @shogerr Your organization uses the latest version of this task, so this warning no longer appears on your pipeline. Please let me know if you get this warning again.

anton-erofeev on May 29, 2020