Encryption is not supported on non windows platforms

Steps to reproduce

Use local nuget repository that demands password encription
My nuget.config works fine in Windows environment, but on linux OS it doesn’t.

Expected behavior

Successfully connect with local Nuget repository.

Actual behavior

Restoring packages for /opt/apl/testeDotnet/testeDotnet.csproj…
Retrying ‘FindPackagesByIdAsyncCore’ for source ‘http:///api/nuget/nuget-remote/FindPackagesById()?id=’Microsoft.NETCore.App».
Password decryption is not supported on .NET Core for this platform. The following feed uses an encrypted password: ‘Artifactory’. You can use a clear text password as a workaround.
Encryption is not supported on non-Windows platforms.
Retrying ‘FindPackagesByIdAsyncCore’ for source ‘http:// /api/nuget/nuget-remote/FindPackagesById()?id=’Microsoft.NETCore.App».
Password decryption is not supported on .NET Core for this platform. The following feed uses an encrypted password: ‘Artifactory’. You can use a clear text password as a workaround.
Encryption is not supported on non-Windows platforms.
/opt/apl/dotnet/sdk/1.0.4/NuGet.targets(97,5): error : Failed to retrieve information about ‘Microsoft.NETCore.App’ from remote source ‘http:// /api/nuget/nuget-remote/FindPackagesById()?id=’Microsoft.NETCore.App». [/opt/apl/testeDotnet/testeDotnet.csproj]
/opt/apl/dotnet/sdk/1.0.4/NuGet.targets(97,5): error : Password decryption is not supported on .NET Core for this platform. The following feed uses an encrypted password: ‘Artifactory’. You can use a clear text password as a workaround. [/opt/apl/testeDotnet/testeDotnet.csproj]
/opt/apl/dotnet/sdk/1.0.4/NuGet.targets(97,5): error : Encryption is not supported on non-Windows platforms. [/opt/apl/testeDotnet/testeDotnet.csproj]

Environment data

dotnet --info output:
.NET Command Line Tools (1.0.4)

Product Information:
Version: 1.0.4
Commit SHA-1 hash: af1e668

Runtime Environment:
OS Name: rhel
OS Version: 7.2
OS Platform: Linux
RID: rhel.7.2-x64
Base Path: /opt/apl/dotnet/sdk/1.0.4

In our case the IT Security Policy cannot be changed, so we must use encripted password.

The add github source step of my gh action is failing:

name: buildTest

on:
  push:
    branches: [ main ]
    paths:
    - '**.cs'
    - '**.csproj'
    - '**build-test.yml'
  pull_request:
    branches: [ main ]
    paths:
    - '**.cs'
    - '**.csproj'
    - '**build-test.yml'

env:
  DOTNET_VERSION: '6.0.401' # The .NET SDK version to use

jobs:
  build:

    name: build-${{matrix.os}}
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        os: [ubuntu-latest, windows-latest]

    steps:
    - uses: actions/checkout@v2
    - name: Setup .NET Core
      uses: actions/setup-dotnet@v1
      with:
        dotnet-version: ${{ env.DOTNET_VERSION }}

    - name: Add Github nuget source
      run: dotnet nuget add source --username ${{ github.actor }} --password ${{ secrets.BH_GH_TOKEN }} --store-password-in-clear-text --name github "https://nuget.pkg.github.com/PT/index.json"

    - name: Install dependencies
      run: dotnet restore

    - name: Build
      run: dotnet build --configuration Release --no-restore

The error is as shown:

    Run dotnet nuget add source "https://nuget.pkg.github.com/PT/index.json" --name github --username user-william -***
error: Password encryption is not supported on .NET Core for this platform. The following feed try to use an encrypted password: 'github'. You can use a clear text password as a workaround.
error:   Encryption is not supported on non-Windows platforms.

All of the solutions I can find suggest adding ‘—store-password-in-clear-text’ to the command, which as you can see is already there. The action is being run on ubuntu-latest. Has anyone else run into this issue? I copied the step from another repo and it works there.

asked Oct 5, 2022 at 18:09

BillHaggerty's user avatar

BillHaggertyBillHaggerty

6,17710 gold badges35 silver badges68 bronze badges

I created the action secret with the wrong name. The action was looking for BH_GH_TOKEN but only BH_GITHUB_TOKEN was available lol.

If the password is null then ‘—store-password-in-clear-text’ is filtered out of the command and the real issue of the missing password is hidden by the platforms inability to encrypt the non-existing password.

So if you see this happen, check your repo secret name lol.

answered Oct 5, 2022 at 18:57

BillHaggerty's user avatar

BillHaggertyBillHaggerty

6,17710 gold badges35 silver badges68 bronze badges

1

Шифрование файлов не поддерживается на этой платформе

Я пытался использовать File.Encrypt(string path) и File.Decrypt(string path) методы в dotnet core 2.1.1, но я продолжаю получать IOException с сообщением File encryption is not supported on this platform.,

Я не знаю, что мне не хватает. Я искал в Интернете безуспешно. Буду признателен за любую помощь.

Благодарю.

2018-08-01 07:16

0
ответов

Основной проблемой было издание моей ОС Windows. Я использую домашнюю версию Windows 10, которая не поддерживает File.Encrypt(string path), Это не проблема ядра dotnet. это платформа (ОС Windows), на которой запущено приложение. Отсюда и сообщение об ошибке File encryption is not supported on this platform очень правильно.

2019-01-08 21:06

Шифрование файлов на этой платформе не поддерживается

Я попытался использовать File.Encrypt(string path) и File.Decrypt(string path) в dotnet core 2.1.1, но я продолжаю получать IOException с сообщением. File encryption is not supported on this platform. ,

Я не знаю, чего мне не хватает. Я искал Интернет без успеха. Буду признателен за любую помощь.

Благодарю.

Основной проблемой было издание моей ОС Windows. Я использую домашнюю версию Windows 10, которая не поддерживает File.Encrypt(string path). Это не проблема ядра dotnet. это платформа (ОС Windows), на которой работает приложение. Следовательно, сообщение об ошибке » File encryption is not supported on this platform очень корректно.

Введите минимум 50 символов

Specifically, Linux.

I would love to be able to use TrueCrypt consistently across all my machines, be they Windows or Linux. As it stands, I can do full-disk encryption with pre-boot authentication only on Windows.

I don’t really understand why this is. Are there technical challenges specific to Linux/Mac that make full disk encryption harder? Does anyone know whether TrueCrypt will support this in the near future.

PS. yes, I’m aware that there are other options. My goal is to simplify my life here and use the one tool across all machines.

asked May 16, 2011 at 9:28

cantloginfromwork's user avatar

3

Because they just haven’t done it yet. They would have to support ext1/2/3/4 and reiserfs, for example. Also, what’s with SWAP? Swap has to be encrypted too, or part of your data is just there (at least what you’ve loaded, etc).

They also have to cope for GRUB and LILO. Where do they put it in? After the boot manager? Do they modify your init.rd?

It’s of course more complicated because they’d have to cope with infinite kinds of configurations. Literally everyone could have their bootloaders somewhere else.

On Windows it’s all in the same place and the same everytime.

answered May 16, 2011 at 11:22

sinni800's user avatar

sinni800sinni800

3,1603 gold badges23 silver badges36 bronze badges

5

Because it’s much work to implement that and there isn’t much need for that for two reasons:

  • Linux and OS X have their own full disk encryption mechanisms, which can’t be easily accessed from another OS¹, but
  • if one separates system from data partitions, the former don’t usually contain interesting data one might want to access from another OS; so you can still use Truecrypt for the latter.

They also don’t seems to have any plans to start any time soon.

On a side note, in my experience Truecrypt isn’t nearly as well integrated into Linux and OS X system environments as into Windows, i. e. there’s no mount helper for it.

¹ It is possible to access LUKS-encrypted ext2/3/4 partitions from Windows with FreeOTFE and ext2FSD under certain conditions, which is also my current setup.

answered Mar 24, 2014 at 3:09

David Foerster's user avatar

5

Fedora 18+ supports this. And nothing really stands in the way of implementing it yourself. Linux provide all the hooks in making the proper initrd. It is just not supported by any Linux distribution except Fedora (since 18).

It would really not be too hard, especially since cryptsetup already supports truecrypt. The initrd people haven’t really gotten around to supporting the truecrypt flag in /etc/crypttab (taking the proper actions when it appears, ie. include truecrypt in the initrd, and decrypt the indicated container).

Jawa's user avatar

Jawa

3,61913 gold badges32 silver badges36 bronze badges

answered Feb 18, 2015 at 11:47

PePa's user avatar

4

You must log in to answer this question.

Not the answer you’re looking for? Browse other questions tagged

.

  • Ender 3 драйвер windows 10
  • End of support for windows 7
  • Enable developer mode windows 11
  • Encrypted windows logon что это
  • Enable boot logging windows 10 что это