linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Miguel González Castaños" <mgc@tid.es>
To: linux-admin@vger.kernel.org
Subject: problems transfering files from a ssh windows client
Date: Wed, 05 Feb 2003 18:30:33 +0100	[thread overview]
Message-ID: <3E414A39.3894B60E@tid.es> (raw)

dear all,

 Sorry if it is a similar question to the one I posted yesterday...

 I have openssh_3.1p1 installed in my redhat 7.3 linux box and I
am
trying to upload some files with the ssh secure shell client
3.0 build
203 non-commercial version to
a SGID directory for a group. I dont know why the ssh client
bypasses
all the permissions set and upload the files with the
permissions that
the client wants (even 777)...I dont think this is a desirable
feature.

 I have set my openssh server to only serve ssh2 protocol, but I
dont
know if there is something missing to avoid this kind of
behaviour.

 Any comments are welcome

 Many thanks in advance

 Miguel




                 reply	other threads:[~2003-02-05 17:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3E414A39.3894B60E@tid.es \
    --to=mgc@tid.es \
    --cc=linux-admin@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).