From owner-soc-status@FreeBSD.ORG Tue Jun 5 11:19:00 2012 Return-Path: Delivered-To: soc-status@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 77C6B106566B for ; Tue, 5 Jun 2012 11:19:00 +0000 (UTC) (envelope-from tzabal@it.teithe.gr) Received: from alpha.it.teithe.gr (alpha.it.teithe.gr [195.251.240.232]) by mx1.freebsd.org (Postfix) with ESMTP id E73988FC14 for ; Tue, 5 Jun 2012 11:18:59 +0000 (UTC) Received: from localhost (babel.noc.teithe.gr [195.251.240.240]) by alpha.it.teithe.gr (8.14.3/8.14.3/Debian-9.4) with ESMTP id q55BB0Se002362 for ; Tue, 5 Jun 2012 14:11:02 +0300 Received: from 37.32.238.159 ([37.32.238.159]) by webmail.teithe.gr (Horde Framework) with HTTP; Tue, 05 Jun 2012 14:10:55 +0300 Message-ID: <20120605141055.1576277vqxjbeukf@webmail.teithe.gr> Date: Tue, 05 Jun 2012 14:10:55 +0300 From: Tzanetos Balitsaris To: soc-status@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.9) Subject: [Status Report - Week 02] Automated Kernel Crash Reporting System X-BeenThere: soc-status@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Summer of Code Status Reports and Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2012 11:19:00 -0000 In the second week of coding I concentrated on the following things: * Testing and debugging the work done in the Client Side part (crashreport) * Considering alternative methods about how to send the reports from the client to the server and then deciding and implementing the selected method. * Update the wiki page of the project. Now, the Client Side part is complete. I was not sure about the method of how to send the reports that I proposed last week. Thus, a good portion of the second week was spent on investigating alternative methods. My main alternative was the use of the HTTP PUT method using the cURL program. Also, I considered again the use of the SSH protocol after getting contact with Ilya Bakulin that explained me some aspects that I did not know regarding how the SSH protocol works. Finally, I decided to implement it with the use of OpenSSH (as I initially proposed) but now with confidence and arguments that prove my choice. HTTP PUT * Easier to implement the Server Side part of how to receive the reports (PHP HTTP library) but we have not any tool in the base system for this job (I was considering the cURL program). Also, we won't have any security when transfering the reports. SSH * Harder to implement the Server Side part of how to receive the reports (probably a daemon that runs on the server and notify a script when a new report is arrived) but we have OpenSSH in the base system for this job. Also, it is secure to transfer the reports. Finally, Lars Engels sent me a patch for crashreport that mainly fixes security issues of crashreport (better and more use of quotes, substituted the basename and dirname commands with some shell magic). The patch has been applied. -- Tzanetos Balitsaris ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.