From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Can't push to [username]@ipfire.org
Date: Thu, 01 Jul 2021 18:44:55 +0100 [thread overview]
Message-ID: <E9F6A81E-F32D-4F67-917A-25247C8B2572@ipfire.org> (raw)
In-Reply-To: <4dbc937e-8c0d-5582-6f3e-3639d9b7c2a7@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
Hello,
Does it support SFTP as well? And if so, does that work?
-Michael
> On 1 Jul 2021, at 18:38, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Hi,
>
> On 01.07.2021 18:58, Michael Tremer wrote:
>> Hello,
>>
>> Yes, I sent an email to the infrastructure list (not sure if you are on it) about downgrading shell access for people who do not need it.
>>
>> https://lists.ipfire.org/mailman/private/infrastructure/2021-June/000236.html
>>
>> Git access should still for everybody and SFTP as well. Are you using SCP or SFTP with mc?
>
> SCP with both 'mc' ("Shell link to machine") and 'Far Manager', Port 22.
>
>>
>> -Michael
>>
>>> On 1 Jul 2021, at 16:59, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>>
>>> Hi,
>>>
>>> while trying to open a shell link with 'mc' to [username]@ipfire.org -
>>> which worked for a long time... - suddenly I'm getting "Cannot chdir to
>>> "/sh://mfischer(a)git.ipfire.org"" today.
>>>
>>> I just wanted to push some 'suricata' updates from today. Besides,
>>> nothing changed on my side since the last uploads...
>>>
>>> Pulling through GIT is working.
>>>
>>> Anyone else?
>>>
>>> Best,
>>> Matthias
>>
>
next prev parent reply other threads:[~2021-07-01 17:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 15:59 Matthias Fischer
2021-07-01 16:58 ` Michael Tremer
2021-07-01 17:38 ` Matthias Fischer
2021-07-01 17:44 ` Michael Tremer [this message]
2021-07-01 17:54 ` Matthias Fischer
2021-07-01 17:58 ` Matthias Fischer
2021-07-01 18:00 ` Michael Tremer
2021-07-02 17:00 ` Matthias Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E9F6A81E-F32D-4F67-917A-25247C8B2572@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox