From owner-freebsd-questions@FreeBSD.ORG Sun May 31 08:43:56 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0683A106566C for ; Sun, 31 May 2009 08:43:56 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [IPv6:2001:4070:101:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 2AF578FC1A for ; Sun, 31 May 2009 08:43:54 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (localhost [IPv6:::1]) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3) with ESMTP id n4V8hngx023266; Sun, 31 May 2009 10:43:49 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3/Submit) with ESMTP id n4V8hl7V023263; Sun, 31 May 2009 10:43:49 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Sun, 31 May 2009 10:43:47 +0200 (CEST) From: Wojciech Puchar To: perryh@pluto.rain.com In-Reply-To: <4a21fb4f.tCv44B9UaB1L03/b%perryh@pluto.rain.com> Message-ID: References: <200905281030.n4SAUXdA046386@banyan.cs.ait.ac.th> <200905280847.12966.kirk@strauser.com> <200905280904.44025.kirk@strauser.com> <20090528183801.82b36bbb.freebsd@edvax.de> <4a1f9cf7.UEl7lAiK4FGe5eG7%perryh@pluto.rain.com> <4a21fb4f.tCv44B9UaB1L03/b%perryh@pluto.rain.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-questions@freebsd.org Subject: Re: Remotely edit user disk quota X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2009 08:43:56 -0000 >> same user password somewhere else. > > The whole point of ssh is to prevent this sort of thing, by > encrypting the message traffic over this insecure communication > channel. I think most people using ssh already know it. or maybe not?:) An attacker may be able to intercept the encrypted > traffic, but it will take a skilled cryptanalyst and a lot of CPU > time -- or the attacker will have to be very lucky -- to decrypt > the message and recover the passwords while they are still valid. All of this things are strong enough to require billions of years to crack or more. >From the beginning my point of this discussion is to stop stupidly repeating "golden rules" like - program a is secure - program b is insecure - so just don't use program b Because it teaches people not to think. There are difference between "insecure program" and "program without extra security". > (You *do* change passwords periodically, don't you?) Of course!