From owner-freebsd-stable@FreeBSD.ORG Thu Jan 5 15:44:01 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A8F06106566B for ; Thu, 5 Jan 2012 15:44:01 +0000 (UTC) (envelope-from karl@denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.freebsd.org (Postfix) with ESMTP id 6ABF08FC0A for ; Thu, 5 Jan 2012 15:44:01 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by FS.denninger.net (8.14.4/8.13.1) with ESMTP id q05Fi0lp051980 for ; Thu, 5 Jan 2012 09:44:01 -0600 (CST) (envelope-from karl@denninger.net) Received: from [127.0.0.1] [192.168.1.40] by Spamblock-sys (LOCAL); Thu Jan 5 09:44:00 2012 Message-ID: <4F05C540.1000405@denninger.net> Date: Thu, 05 Jan 2012 09:44:00 -0600 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Matthew Seaman References: <4F059BEA.3000508@denninger.net> <4F05A7D5.8000403@infracaninophile.co.uk> <4F05AF28.5010900@denninger.net> <4F05C27B.8050802@infracaninophile.co.uk> In-Reply-To: <4F05C27B.8050802@infracaninophile.co.uk> X-Enigmail-Version: 1.3.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 120105-0, 01/05/2012), Outbound message X-Antivirus-Status: Clean Cc: freebsd-stable@freebsd.org Subject: Re: FTPS Server? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2012 15:44:01 -0000 On 1/5/2012 9:32 AM, Matthew Seaman wrote: > On 05/01/2012 14:09, Karl Denninger wrote: >> So if I want to do anything other than transfer to a Windows machine >> (barf!) I am stuck with either FTP (no encryption at all and subject to >> be picked off via trivial means while the data is in flight) or FTPS >> (which has its own set of issues.) > Does your card support uploading by HTTP(S) POST? You'll need to cook > up a small webapp to process the input, but that shouldn't be any big > deal if you can snoop on the card doing that and extract parameter values. > > Or, more obscurely, does that card support HTTP PUT? Not very many > people realise that uploading data is supported in HTTP, and > consequently it is quite rarely used. For apache, you need to use a > statement to enable the PUT command, and obviously, you'll need > some sort of access control eg. HTTP Basic Auth so users have to provide > passwords. > > Cheers, > > Matthew No; unfortunately the only "open standards" methods supported are FTP or "Secure" FTP (Ftps) The proprietary stuff "works" but I want to have a Windows machine powered up all the time to get the transmissions (even though I can have it mount a Samba share and thus write them to the same place on the server in question) like a want a hole in the head. -- Karl