Action showing permission denied

[aditya-mitra]

I had many environmental variables so I used to gpg to encrypt those variables in a file.

I then made a script to decrypt that file and to store it the backend folder of my project during the run of the action

All this are to happen in the github action (see below the yml file)

That script of mine looks something like this:

#!/bin/sh
gpg --quiet --batch --yes --decrypt --passphrase="$DECRYPTER_PASSPHRASE" 

--output ./backend/.env ./.github/secrets/backend.env.gpg

My script is running well when I am executing this command in the project root

./.github/scripts/backend_decrypt.sh

But it fails during the github action

My backend-deploy.yml file is like this:

name: Backend Deploy
on:

push:

branches:

- master

paths:

- 'backend/**'
jobs:

backendDeploy:

runs-on: ubuntu-latest

steps:

- uses: actions/checkout@v2

- shell: bash

env:

DECRYPTER_PASSPHRASE: ${{secrets.DECRYPTER_PASSPHRASE}}

run: >

./.github/scripts/backend_decrypt.sh
fails at this point
  - run: |
      cat backend/.env
      pwd
      ls -a
      ls backend/
  - run: >
      ls -a
      ls -a backend/
      echo "Deployed to code-rush-backend.herokuapp.com"

It is giving me this error:

showing error -> /home/runner/work/_temp/27cb9d1d-f99d-489b-b13e-4f56e86348af.sh: line 1: ./.github/scripts/backend_decrypt.sh: Permission denied1362×317 19.9 KB

How can I fix this ? Please help

[airtower-luna]

That most likely means that your ./.github/scripts/backend_decrypt.sh script doesn’t have the “execute” filesystem permission set. I assume you’re developing on Windows locally, which doesn’t have that kind of permission system.

You can tell git to add the permission anyway with this command:

git update-index --chmod=+x ./.github/scripts/backend_decrypt.sh

update-index is similar to add in that it adds the change to the index, so you’ll have to commit and push as usual.

[aditya-mitra]

Thanks a lot @airtower-luna
This solved it

[manpreetsinghminhas]

Thank you so much! This solved the issue for me too! Any tips on how to do this by default on a Windows machine for bash scripts?

[airtower-luna]

manpreetsinghminhas:

Any tips on how to do this by default on a Windows machine for bash scripts?

How do you mean “by default”? If you mean marking scripts as executable, no. Unix-ish systems don’t do that either, it’s just that there you automatically notice if something isn’t marked as executable but should. You could try to make a pre-commit hook with some sort of heuristic to detect scripts, but I doubt it’s worth the effort.

[glenntroncquo]

Thanks @airtower-luna
That fixed it for me

[King-Dorji]

This one worked very well for me too, thanks

[ngohuytrieu]

Hi guys, how about ubuntu?
I am trying to ssh to AWS EC2 but my deploy.sh is permission dennied

deploy:
    runs-on: ubuntu-18.04
    steps:
      - uses: actions/checkout@v2
      - name: SSH to AWS EC2
        uses: shimataro/ssh-key-action@v2
        with:
          key: ${{ secrets.SSH_KEY }}
          name: id_rsa
          known_hosts: ${{ secrets.SSH_HOSTNAME }}
      - name: Deploy
        run: ./deploy.sh

[airtower-luna]

Depends on the exact output that'd tell you what was denied. If you need help posting a link is best, copy the step output if the repo is private (censor anything private). If the problem is that deploy.sh isn't marked executable my solution should work. 🙂

If it's anything else… That might warrant a separate discussion. 😉

[ngohuytrieu]

@airtower-luna I've got that fixed, but now I get another issue

Run ssh -i ~/.ssh/private.key -tt username@*** "
Host key verification failed.
Error: Process completed with exit code 255.

Here is my actions:

- name: Create SSH key
        run: |
          mkdir -p ~/.ssh/
          echo "$SSH_PRIVATE_KEY" > ~/.ssh/private.key
          sudo chmod 600 ~/.ssh/private.key
          echo "$SSH_KNOWN_HOSTS" > ~/.ssh/known_hosts
          sudo chmod 600 ~/.ssh/known_hosts
        shell: bash
        env:
          SSH_PRIVATE_KEY: ${{secrets.SSH_KEY}}
          SSH_KNOWN_HOSTS: ${{secrets.SSH_HOSTNAME}}
      - name: SSH into EC2
        run: >
          ssh -i ~/.ssh/private.key -tt username@hostname
          "
            echo 'Welcome to EC2'
          "

[airtower-luna]

Host key verification failed.

This means that the key with which the host identifies itself couldn't be recognized. That usually means one of two things:

1. Something (or someone) is messing with your connection.
2. Your ~/.ssh/known_hosts is incorrect.

This part of your file makes me suspect the latter:

          SSH_KNOWN_HOSTS: ${{secrets.SSH_HOSTNAME}}

The known hosts file needs to contain not only the hostname, but also the associated public key information, see: https://manpages.debian.org/bullseye/openssh-server/sshd.8.en.html#SSH_KNOWN_HOSTS_FILE_FORMAT

As I said, please create a new discussion if you need more help, because this is a completely different topic from the original post. I will not be posting further off-topic responses here.