From owner-freebsd-security@freebsd.org  Thu Oct 19 16:07:21 2017
Return-Path: <owner-freebsd-security@freebsd.org>
Delivered-To: freebsd-security@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8772CE3F44A
 for <freebsd-security@mailman.ysv.freebsd.org>;
 Thu, 19 Oct 2017 16:07:21 +0000 (UTC)
 (envelope-from joey@joeykelly.net)
Received: from safegreet.com (safegreet.com [173.230.129.132])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 621406F0B3
 for <freebsd-security@freebsd.org>; Thu, 19 Oct 2017 16:07:21 +0000 (UTC)
 (envelope-from joey@joeykelly.net)
Received: from localhost (localhost [127.0.0.1])
 by safegreet.com (Postfix) with ESMTP id 5B84C4357
 for <freebsd-security@freebsd.org>; Thu, 19 Oct 2017 10:59:42 -0500 (CDT)
X-Virus-Scanned: amavisd-new at safegreet.com
Received: from safegreet.com ([127.0.0.1])
 by localhost (safegreet.com [127.0.0.1]) (amavisd-new, port 10024)
 with LMTP id cgSTYnqktOmU for <freebsd-security@freebsd.org>;
 Thu, 19 Oct 2017 10:59:41 -0500 (CDT)
Received: from freechin.atlnet (47-44-49-2.static.unas.mo.charter.com
 [47.44.49.2])
 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by safegreet.com (Postfix) with ESMTPSA id 55C8F42D7
 for <freebsd-security@freebsd.org>; Thu, 19 Oct 2017 10:59:41 -0500 (CDT)
From: Joey Kelly <joey@joeykelly.net>
To: freebsd-security@freebsd.org
Subject: Re: freebsd-security Digest, Vol 634, Issue 3
Date: Thu, 19 Oct 2017 11:59:40 -0400
Message-ID: <1511621.jdgZNmovq9@freechin.atlnet>
User-Agent: KMail/4.14.10 (FreeBSD/11.0-RELEASE-p12; KDE/4.14.30; amd64; ; )
In-Reply-To: <26ffd1eb-d8c2-0fdd-da38-b9e3790144ad@whitewinterwolf.com>
References: <mailman.37.1508328001.71205.freebsd-security@freebsd.org>
 <CAMPTd_Cbniobvr_oyDYhGKibY+0MBuBkFaMA6QgrhF1crCV45g@mail.gmail.com>
 <26ffd1eb-d8c2-0fdd-da38-b9e3790144ad@whitewinterwolf.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Oct 2017 16:07:21 -0000

> 
> In this case, for a low-tech people, I would tend to suggest using SFTP
> (a password-based access is enough) instead of a stunneled SMB share as
> I personally find it is easier to setup and more efficient.

If you have an ssh server (if you have FreeBSD, you have one), that will 
function as a SFTP or SCP server. Put it on an alternative port if possible, 
and for the client end, use WinSCP, Fugu on a Mac (I think it's Fugu..), and 
for BSD/Linux/smartphones you have any number of client apps to choose from. 
Easy peasy, a familiar 2-pane GUI FTP layout, very secure. 


-- 
Joey Kelly
Minister of the Gospel and Linux Consultant
http://joeykelly.net
504-239-6550