Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!bcyclone03.am1.xlned.com!bcyclone03.am1.xlned.com!newsfeed.xs4all.nl!newsfeed3.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.010 X-Spam-Evidence: '*H*': 0.98; '*S*': 0.00; 'root': 0.05; 'subject:file': 0.07; 'permissions': 0.09; 'subject:into': 0.09; 'cc:addr:python-list': 0.11; '-tkc': 0.16; 'disallow': 0.16; 'finds': 0.16; 'from:addr:python.list': 0.16; 'from:addr:tim.thechases.com': 0.16; 'from:name:tim chase': 0.16; 'record,': 0.16; 'require.': 0.16; 'ssh': 0.16; 'subject: \n ': 0.16; 'subject:download': 0.16; 'prevent': 0.16; 'wrote:': 0.18; 'putting': 0.22; 'cc:addr:python.org': 0.22; 'cc:2**0': 0.24; 'cc:no real name:2**0': 0.24; 'least': 0.26; 'header:In-Reply- To:1': 0.27; 'external': 0.29; 'said,': 0.30; 'usually': 0.31; 'there.': 0.32; 'subject:from': 0.34; 'something': 0.35; 'but': 0.35; 'there': 0.35; 'done': 0.36; 'charset:us-ascii': 0.36; 'received:10': 0.37; 'server': 0.38; 'configured': 0.38; 'needed': 0.38; 'subject:can': 0.39; 'either': 0.39; 'ground': 0.60; 'middle': 0.60; 'most': 0.60; 'skip:n 10': 0.64; 'account': 0.65; 'assistance': 0.66; 'obvious': 0.74; 'bot': 0.84; 'to:addr:ntlworld.com': 0.84; 'vulnerable': 0.84 X-Sender-Id: wwwh|x-authuser|tim@thechases.com X-Sender-Id: wwwh|x-authuser|tim@thechases.com X-MC-Relay: Neutral X-MailChannels-SenderId: wwwh|x-authuser|tim@thechases.com X-MailChannels-Auth-Id: wwwh X-MC-Loop-Signature: 1418068098535:4252490141 X-MC-Ingress-Time: 1418068096187 Date: Mon, 8 Dec 2014 13:50:42 -0600 From: Tim Chase To: alister Subject: Re: why can't download file from linux server into local window disk c:? In-Reply-To: <6mmhw.29670$5z5.10496@fx42.am4> References: <5486AF57.7070803@gmail.com> <6mmhw.29670$5z5.10496@fx42.am4> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AuthUser: tim@thechases.com Cc: python-list@python.org X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 23 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1418068108 news.xs4all.nl 2897 [2001:888:2000:d::a6]:60134 X-Complaints-To: abuse@xs4all.nl X-Received-Bytes: 4209 X-Received-Body-CRC: 1905887930 Xref: csiph.com comp.lang.python:82142 On 2014-12-08 18:46, alister wrote: > on most systems that DO have a ssh server root logins are usually > prohibited, either enable root logins (dangerous) or log in with a > user that has permissions to do what you require. if you don't have > access to the server then you need assistance from someone who is > authorised. Just for the record, you can enable root logins but disallow password logins, so root has to be done with a public/private key-pair. That said, I do as you describe and still SSH to my ssh-user account, then "su" to root as needed from there. But at least there's a middle ground that isn't as vulnerable as putting a root account out there to be banged on by any script-o-matic bot that finds it. I also like to change my external SSH port to something non-traditional (and have configured port-knocking in the past) to prevent the obvious pokes I would otherwise see in my sshd/auth/access logs. -tkc