From owner-freebsd-hackers@freebsd.org Sun Apr 3 00:04:34 2016 Return-Path: Delivered-To: freebsd-hackers@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 DB40CB01AC9 for ; Sun, 3 Apr 2016 00:04:34 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id BAB011AE8 for ; Sun, 3 Apr 2016 00:04:34 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [172.16.0.5] (unknown [172.16.0.5]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id C345B1E54 for ; Sun, 3 Apr 2016 00:04:33 +0000 (UTC) Subject: Boot crypto framework patch, need testers From: Eric McCorkle Content-Type: text/plain; charset=us-ascii X-Mailer: iPad Mail (13D15) Message-Id: Date: Sat, 2 Apr 2016 20:04:32 -0400 To: "freebsd-hackers@freebsd.org" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Apr 2016 00:04:35 -0000 Hello, I've put together the following patch as part of a larger body of work I'm p= ursuing: https://github.com/emc2/freebsd/tree/boot_crypto This isn't a big patch, but it's aiming to be a central hub for boot-time cr= ypto, so it needs due consideration. This patch basically pulls all the cry= pto bits out of the recent geliboot work and moves them into a separate modu= le, called "boot_crypto". This is supposed to be a behavior-neutral patch, s= o it should be possible to drop it in to existing systems and have it Just W= ork. I'm not aware of other areas in the boot ecosystem that use crypto, bu= t if there are, they should probably be moved onto this framework as well. After studying the kernel crypto framework, GELI, and others, I have elected= NOT to try to design an interface for asking for passwords securely, storin= g keys, and other functionality I had previously contemplated. The existing= frameworks just don't support that kind of thing. I'm ok with this being reviewed to go in as-is, or it can be done as part of= my (very nearly finished) GELI EFI work. Whatever the decision, though, th= is is probably the best point to test that it doesn't break the existing gel= iboot functionality. The rationale for doing this code reorganization follows: * It helps avoid duplication and extra work for things like the EFI work * It makes it easier to add support for more ciphers (camellia and blowfish a= re unsupported in the current boot GELI implementation, for example, and act= ivity in the crypto world suggests new ciphers/modes will be arriving) * It lowers the overhead of implementing other crypto-based functionality at= boot time (gbde, ZFS encryption, secure boot, etc) * Boot crypto functionality has different enough needs (simplicity, small co= de size, etc) to warrant a boot-specific interface. * It's much easier to install an interface like this one when there are few c= onsumers than to rip out 5-6 random ad-hoc crypto implementations at some po= int in the future. *Especially* in a boot loader. Please review, test, and provide feedback. Thanks, Eric= From owner-freebsd-hackers@freebsd.org Mon Apr 4 02:21:41 2016 Return-Path: Delivered-To: freebsd-hackers@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 49564B01E83 for ; Mon, 4 Apr 2016 02:21:41 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 053BE13CE for ; Mon, 4 Apr 2016 02:21:41 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-yw0-x232.google.com with SMTP id d68so98350073ywe.1 for ; Sun, 03 Apr 2016 19:21:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=t7L+LPUVOeZO71MNSFvPc9/enA1b3VRRZdHMUqV3L/A=; b=KPBG/PhdhdZ4jyCMdV7OAfzIZNCVUHFakugLftRlkLEYb3aYn5seAgyd/3af4orshR vSPI/XBsZD/WeYppfX4lT8VYvLCK8NyLjDHeBm6WgXr0Gtcnjv/pX1+5u0AZiuDWD7+T bjFLtrgTuwfSsb3HE2TzigWX/GjiOXbS29fgx4ej6q+NXw4kwt7mKCUKRV9xYpUK0HnY k3qItyeISxUdbYgmb6iwNnZK2ohXE+PsifPh9BSIlGi1flVmABYYppEg9mVCPyU3qWj7 ledobQgAAsbgFfuthn2f82GMsyhvROb2w8TBKm5ZmEXJjVL6WdgtzXw1Igk9sDYEQtXw PZ4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=t7L+LPUVOeZO71MNSFvPc9/enA1b3VRRZdHMUqV3L/A=; b=gHJs1wg03fhV8wshdm6dSEQm+EvGP0Lbp7ShiO0kDI7UGnzNUYsksu0qLTn/5RfDWR qhGOr9IbC/y7IzWZ/wIxjcRRtc8hJC7a/7s0WT0SsBh/yAEJJpbayjmGJB0kLy1SOLUN GxFxnroajP7WIAkImkn1rmce3vFSPksqNDf3yMh/YXrnU/x7z1a666Y08LwmZsloz/IF y8kwM3IMKm+5OqBy0qmn2ACAKiA0gyEaluZ0nZg1SNgTCtNaevKBewapv9oodilcrzC5 6SQSYexPQnkvGY+N0oQJftRdrJRnJYJDUg1zdsbn3EsTq51qV0OQZzzRysrTcB9YZxSC C66Q== X-Gm-Message-State: AD7BkJInIzJiJenVRxnpCAPGeXsoe+f/7Y20vVtcg+phaMkPOAP1D/jN0+wg/MF5/f2ZoDBLjZzbReXgoIK+Gg== MIME-Version: 1.0 X-Received: by 10.37.59.72 with SMTP id i69mr17743144yba.30.1459736500115; Sun, 03 Apr 2016 19:21:40 -0700 (PDT) Received: by 10.37.27.130 with HTTP; Sun, 3 Apr 2016 19:21:40 -0700 (PDT) Date: Sun, 3 Apr 2016 22:21:40 -0400 Message-ID: Subject: SIG_WINCH ... getting out of our current state of disarray. From: Zaphod Beeblebrox To: FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2016 02:21:41 -0000 So... here's the scenario... I'm running vi in screen on a server. I resize my window. Now... screen seems to deliver the resize SIG_WINCH fine to the process... but it seems BSD (and I don't use enough linux to have checked) only delivers SIG_WINCH to the foreground process. Is it _bad_? to deliver SIG_WINCH to other terminal group processes? Surely a shell knows that it started a process and should wait, but something CTRL-Z'd or &'d might be a special case... dunno. Anyways... it seems that this would be something good to have happen. As it is... i find myself resizing a window multiple times to the same size just to get SIG_WINCH delivered to the now running application. From owner-freebsd-hackers@freebsd.org Mon Apr 4 12:07:57 2016 Return-Path: Delivered-To: freebsd-hackers@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 1359FB01B37 for ; Mon, 4 Apr 2016 12:07:57 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 002CA1BB6 for ; Mon, 4 Apr 2016 12:07:57 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: by mailman.ysv.freebsd.org (Postfix) id EFEABB01B36; Mon, 4 Apr 2016 12:07:56 +0000 (UTC) Delivered-To: hackers@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 EF8EDB01B35 for ; Mon, 4 Apr 2016 12:07:56 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from weser.webweaving.org (weser.webweaving.org [148.251.234.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.webweaving.org", Issuer "RapidSSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8F6991BB5 for ; Mon, 4 Apr 2016 12:07:55 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from beeb.leiden.webweaving.org (5ED23D88.cm-7-3a.dynamic.ziggo.nl [94.210.61.136]) (authenticated bits=0) by weser.webweaving.org (8.15.2/8.15.2) with ESMTPSA id u34BonU2035604 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Apr 2016 13:50:51 +0200 (CEST) (envelope-from dirkx@webweaving.org) X-Authentication-Warning: weser.webweaving.org: Host 5ED23D88.cm-7-3a.dynamic.ziggo.nl [94.210.61.136] claimed to be beeb.leiden.webweaving.org From: Dirk-Willem van Gulik Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Date: Mon, 4 Apr 2016 13:50:49 +0200 Subject: reboot with reroot / 10.3 To: FreeBSD Hackers Message-Id: Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) X-Mailer: Apple Mail (2.3112) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (weser.webweaving.org [148.251.234.232]); Mon, 04 Apr 2016 13:50:51 +0200 (CEST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2016 12:07:57 -0000 Trasz, Thanks for the wonderful reroot present in 10.3 :) First tries work well = for us for a couple of scenario=E2=80=99s around pivoting early from an = ro-mounted bootup to mount the =E2=80=98real' encrypted root FS that has = its key stored on remote hardware (previously we used Adrian Steinmann / = ast his work on Pivot Root with a lot of care/order puzzles). I gather that it creates a /de/reroot tempfs; copies the, at that time, = on-disk version of init (as learned from a trusted kern.proc.pathname); = executes init with a new -r; that essentially does (just) a kill (as = only init can kill init) - and then things are mounted/cleaned up from = there after attempting to run at least something from = =E2=80=98kern.init_path=E2=80=99=20 Where would one go to understand the trust-chain/security aspects of = this ? I.e. what locks the kill(1, SIGEMT) to the copy of the real = init(8) ? Where are the places most at risk ? Thanks, Dw.= From owner-freebsd-hackers@freebsd.org Mon Apr 4 13:58:32 2016 Return-Path: Delivered-To: freebsd-hackers@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 100FDB032CE; Mon, 4 Apr 2016 13:58:32 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu [18.7.68.35]) (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 A1A851807; Mon, 4 Apr 2016 13:58:31 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074423-537ff70000002943-81-570273044cd5 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id AC.A6.10563.40372075; Mon, 4 Apr 2016 09:58:29 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id u34DwSwH018056; Mon, 4 Apr 2016 09:58:28 -0400 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u34DwP3e015135 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 4 Apr 2016 09:58:28 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id u34DwP1L024208; Mon, 4 Apr 2016 09:58:25 -0400 (EDT) Date: Mon, 4 Apr 2016 09:58:24 -0400 (EDT) From: Benjamin Kaduk X-X-Sender: kaduk@multics.mit.edu To: freebsd-hackers@FreeBSD.org cc: freebsd-current@FreeBSD.org Subject: Last call for 2016Q1 quarterly status report submissions Message-ID: User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrLIsWRmVeSWpSXmKPExsUixCmqrctazBRu8DrQYs6bD0wW2zf/Y3Rg 8pjxaT5LAGMUl01Kak5mWWqRvl0CV8alR32sBbO4K36eP8DWwLiCs4uRk0NCwERizb1e5i5G Lg4hgTYmiRUzP7OAJIQENjBKbDrMDpE4yCQxfcF3ZohEvcSmiYvZuhg5OFgEtCQWn2cCCbMJ qEmsX3GNGWKoosTmU5PAbBEBeYl9Te/ZQWxmIHvL6slsILawgKPEof0PwXp5gezPvy4xgtii AjoSq/dPYYGIC0qcnPmEBaJXS2L59G0sExj5ZyFJzUKSWsDItIpRNiW3Sjc3MTOnODVZtzg5 MS8vtUjXTC83s0QvNaV0EyMo1NhdlHcwvuzzPsQowMGoxMP74ShjuBBrYllxZe4hRkkOJiVR 3vpwpnAhvqT8lMqMxOKM+KLSnNTiQ4wSHMxKIrwnC4FyvCmJlVWpRfkwKWkOFiVxXkYGBgYh gfTEktTs1NSC1CKYrAwHh5IE71OQRsGi1PTUirTMnBKENBMHJ8hwHqDhp8CGFxck5hZnpkPk TzEqSonz2oEkBEASGaV5cL3gVLCbSfUVozjQK8K8NkVAVTzANALX/QpoMBPQ4HphsMEliQgp qQZGUa8pj1n2zZApCDsvWZeo4V1/viuTVT9cJvMyy9pf0RqP7/TGvDU5zfWF8QDX3fg8y9qb y7z9BEv3brv1XLGhzf+r+8+JISxKnM5ts4rDD905qrDhnprdUsO/er84NxXONGtlVV3gvdyq t0/q/WqWhlOT280fC/Ee3vJpyvNW6/Kkh8fsMxYqsRRnJBpqMRcVJwIAYL87nOACAAA= X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2016 13:58:32 -0000 Dear FreeBSD Community, There are just a few days left until the April 7 deadline for submitting entries for the next FreeBSD Quarterly Status Report. Please submit entries for work done in January, February, or March. Status report submissions do not have to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great way to inform FreeBSD users and developers about what you're working on. Submission of reports is not restricted to committers. Anyone doing anything interesting and FreeBSD-related can -- and should -- write one! The preferred and easiest submission method is to use the XML generator [1] with the results emailed to the status report team at monthly at FreeBSD.org . There is also an XML template [2] which can be filled out manually and attached if preferred. For the expected content and style, please study our guidelines on how to write a good status report [3]. You can also review previous issues [4][5] for ideas on the style and format. We are looking forward to all of your 2016Q1 reports! Thanks, Ben (on behalf of monthly@) [1] http://www.freebsd.org/cgi/monthly.cgi [2] http://www.freebsd.org/news/status/report-sample.xml [3] http://www.freebsd.org/news/status/howto.html [4] http://www.freebsd.org/news/status/report-2015-07-2015-09.html [5] http://www.freebsd.org/news/status/report-2015-10-2015-12.html From owner-freebsd-hackers@freebsd.org Tue Apr 5 10:49:49 2016 Return-Path: Delivered-To: freebsd-hackers@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 69D32B0190C for ; Tue, 5 Apr 2016 10:49:49 +0000 (UTC) (envelope-from subburaj.tgs@gmail.com) Received: from mail-vk0-x22b.google.com (mail-vk0-x22b.google.com [IPv6:2607:f8b0:400c:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 272201A83 for ; Tue, 5 Apr 2016 10:49:49 +0000 (UTC) (envelope-from subburaj.tgs@gmail.com) Received: by mail-vk0-x22b.google.com with SMTP id e185so12345138vkb.1 for ; Tue, 05 Apr 2016 03:49:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=w5OLiB9jfpR2/Pr/tq9KJ9KAFN0h4X0U6MdL3SV9mg8=; b=FdHRH+kMUAr43SA8rxY3sGY3q+Er/QMZdadZQYo+QxOvs6e9Hu9kQGNlnrJp0cguH3 iojQ+boA4vWJHJs9TEyXR4/12hmL9euDkU+xXKR3+VbXjLJCXG9cKwi5NB6IDOSrZcQk /9qeR2WYOlrsICwk+RI3FV4NqRuDoy9sthd84pEWJJusdYy69IsbVsludBkMhhE8HQuC AFPOP+BNfrtJGd6Y+Snbapt5c71BmzIWlwQvfWhtFMC6PxgZNs0qa0yZhcb+l3WlhFSw beRY+meEHC7itYXyCo3cBD68uErfV7iOsSgDLg5O/JU4NtiGjl4xU8tpLsk9bRljwr4U GloQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=w5OLiB9jfpR2/Pr/tq9KJ9KAFN0h4X0U6MdL3SV9mg8=; b=OsYKhLisO0NncaKSp2qnahu8k0I+sFadPUjGwyjMS3MJYcxM1t3saSf2uadlmxutSh z6h1pmjBsnY6STmLHza+ivjnx37E3vH+QROy5epPotHp07FcKmiGlyuWu6ocnbg/pobp f/gTBCjOJ0n6x0jjobrDIbNT+66nbm3nkWsKFdrwUWdYvTyvpGQ8/AP7YB4OT+FjJ1Uo /yYsQi1J7ULoKk+DTUWCYoDrHVoIXQ6RP2UhifU8aIZ3OHNpdMM5yaGgqt+4eWmFragZ YOiaqJ4xY6Haq/ZXV6vmOp4aC3LRlyqeCgyxgrucyWjIAfvVfEtQiV0aJd7WEGZx8LvA /TiQ== X-Gm-Message-State: AD7BkJJo9qQHVMttYgbzRTH5o7dj69oNIGvPZRZUwPMEi+pDA1+FG0xd1ZGHo4L8/8GuYC51wL+KMbjBGGmUHw== MIME-Version: 1.0 X-Received: by 10.176.0.23 with SMTP id 23mr7899309uai.28.1459853388175; Tue, 05 Apr 2016 03:49:48 -0700 (PDT) Received: by 10.159.40.197 with HTTP; Tue, 5 Apr 2016 03:49:48 -0700 (PDT) Date: Tue, 5 Apr 2016 16:19:48 +0530 Message-ID: Subject: Debugger for linux to use umem port From: Subburaj TGS To: freebsd-hackers@freebsd.org X-Mailman-Approved-At: Tue, 05 Apr 2016 11:21:00 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2016 10:49:49 -0000 Hi All, I would like to check out libumem on a Linux machine. I just got to know about the Linux port but all the information I can find points to Solaris usage, which requires mdb to extract information out of libumem. But I cannot find any mdb port for Linux. Does anyone has any experience with? Any suggestion is welcome. Thanks, Subburaj From owner-freebsd-hackers@freebsd.org Tue Apr 5 12:02:37 2016 Return-Path: Delivered-To: freebsd-hackers@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 E1C54B04AD5 for ; Tue, 5 Apr 2016 12:02:37 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id BFF6713A2 for ; Tue, 5 Apr 2016 12:02:37 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id BF4E9B04AD4; Tue, 5 Apr 2016 12:02:37 +0000 (UTC) Delivered-To: hackers@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 BEED6B04AD3 for ; Tue, 5 Apr 2016 12:02:37 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 71D2B13A1 for ; Tue, 5 Apr 2016 12:02:37 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by mail-wm0-x22a.google.com with SMTP id f198so28970586wme.0 for ; Tue, 05 Apr 2016 05:02:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=AQjWzV2U9mXmS67HVLJ/kfG4Gg8OJcBGuRDqLMYkFAc=; b=HYtYWW1XRthNF525v0j51/TOT9+yFsxfkix0iEWhu9Rm/VdS0393XLc542D3MWqq06 dRq3e7EgWdpq1GeQU50D+KEtK4Ug5yWtNOhQhddsRAN0anThIQFCobCd+21bTX8R/5Ju fJvYFcr2RMHkI0QoddR7pyy6+3ZDarU37mNKEdUkt82eb7YwmY+6YwbhzEm7N+v3CYaC JUG7CFekwoIyaYuHPMSuox60fkOL8GrCTmRb1HMTI99n5m0TilvJHU3VPeLmBXSoUUrr CLn0d7kQqJ7N+xtjhvBaGvaugpjgjbf4jZ6p+cYkgzCnYAyTQWdwgG2KcTn1jmeHlcnr 027g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=AQjWzV2U9mXmS67HVLJ/kfG4Gg8OJcBGuRDqLMYkFAc=; b=hAUsSUmYNCijOl1b6dwoAdjymwjw1KHqfcVDgKT61SD3FBQI29QdLbwWS/ywLuthp2 YEPQpy+zbSQ6RMhKAPu08UKOIjMGfhl8LGCQXBfEBOpgIHB8AZ6V+p6XPtH5dwwGt6nm GLG/faGDqzV22BirghLJiSqtokQ+eLTQUf+CMZapJhovmUc9+Y0FoAIGe+8yATb6pJ/5 DJ+Bg4+zrTMycuBTPF+JNBQw9kIhngjWsZtnT5gkGTR6SWhF5DF5++ln4ONGWZ2RWOiz R9GJ+gP5MD+MdvfvrlfgWjpcgYVokhu+AW6ygFHswW0XBrQo7IjpjI0awZv/FYpahIZp t/kw== X-Gm-Message-State: AD7BkJL0MQNqIz5sJvDd3GbGUeduR0MCjZJV1L+g2c9zOfuE6YtJztTjhsB6nS/QZdY+Ig== X-Received: by 10.28.100.132 with SMTP id y126mr13628663wmb.91.1459857756009; Tue, 05 Apr 2016 05:02:36 -0700 (PDT) Received: from brick.home (eum237.neoplus.adsl.tpnet.pl. [83.20.184.237]) by smtp.gmail.com with ESMTPSA id w184sm19166885wmb.1.2016.04.05.05.02.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Apr 2016 05:02:35 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Tue, 5 Apr 2016 14:02:31 +0200 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= To: Dirk-Willem van Gulik Cc: FreeBSD Hackers Subject: Re: reboot with reroot / 10.3 Message-ID: <20160405120231.GB47120@brick.home> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2016 12:02:38 -0000 On 0404T1350, Dirk-Willem van Gulik wrote: > Trasz, > > Thanks for the wonderful reroot present in 10.3 :) First tries work well for us for a couple of scenario’s around pivoting early from an ro-mounted bootup to mount the ‘real' encrypted root FS that has its key stored on remote hardware (previously we used Adrian Steinmann / ast his work on Pivot Root with a lot of care/order puzzles). > > I gather that it creates a /de/reroot tempfs; copies the, at that time, on-disk version of init (as learned from a trusted kern.proc.pathname); executes init with a new -r; that essentially does (just) a kill (as only init can kill init) - and then things are mounted/cleaned up from there after attempting to run at least something from ‘kern.init_path’ > > Where would one go to understand the trust-chain/security aspects of this ? I.e. what locks the kill(1, SIGEMT) to the copy of the real init(8) ? Where are the places most at risk ? There shouldn't be any security aspects - only the root can trigger it. The source destination for copying the init(8) binary is obtained from the kernel, using KERN_PROC_PATHNAME sysctl - it's the path of on-disk init(8) binary itself. From owner-freebsd-hackers@freebsd.org Tue Apr 5 12:27:15 2016 Return-Path: Delivered-To: freebsd-hackers@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 7060FB02420 for ; Tue, 5 Apr 2016 12:27:15 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.0x20.net", Issuer "mail.0x20.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 32FDA1097 for ; Tue, 5 Apr 2016 12:27:14 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id BA8D06E0081; Tue, 5 Apr 2016 14:27:11 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.7/8.14.7) with ESMTP id u35CRBpF067470; Tue, 5 Apr 2016 14:27:11 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.7/8.14.7/Submit) id u35CRA8d066245; Tue, 5 Apr 2016 14:27:10 +0200 (CEST) (envelope-from lars) Date: Tue, 5 Apr 2016 14:27:10 +0200 From: Lars Engels To: Subburaj TGS Cc: freebsd-hackers@freebsd.org Subject: Re: Debugger for linux to use umem port Message-ID: <20160405122710.GA24170@e-new.0x20.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="WJCYmJUqSxpJwZtQ" Content-Disposition: inline In-Reply-To: X-Editor: VIM - Vi IMproved 7.4 X-Operation-System: FreeBSD 8.4-RELEASE-p23 User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2016 12:27:15 -0000 --WJCYmJUqSxpJwZtQ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 05, 2016 at 04:19:48PM +0530, Subburaj TGS wrote: > Hi All, >=20 > I would like to check out libumem on a Linux machine. I just got to know > about the Linux port but all the information I can find points to Solaris > usage, which requires mdb to extract information out of libumem. But I > cannot find any mdb port for Linux. >=20 > Does anyone has any experience with? Any suggestion is welcome. FreeBSD is no Linux distribution. --WJCYmJUqSxpJwZtQ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQF8BAEBCgBmBQJXA68eXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RjQwMDE3RTRERjUzMTI1N0FGRTUxNDlF NTRDQjM3RDNBMDg5RDZEAAoJEOVMs306CJ1tzWUH/RxB+R13BRa4hAnbg/nSZdlD C1ouI7u+UXKAalB67MbuUljl8IdXjyv2jjxh7UPYSW3qFwHxxnzLU5XTyeWXi/Zo HQRtO1V/OWV4vrEVykzZEebOwIy7vJiAmOVRoooFhE3OH3fXGDHosQ/ZxIw3CjQT pm19FZj6h1gOeB8Fm9W68oOaaOhpxfrFatgFTz4eDpV5jmYju3SE1IWE/Oj6IOP1 63VBU5hQ/63RXq2lCArtWJXUYl/S+ns1FVdtYZO0qdq5D1CzZYgMlo4JtkLoZDgU 4dh84+u+leI8447qSnbMFogwrvvkoYCazKsttvSUCwMPlcOeq5sEDFtkBabLwYY= =T2Nj -----END PGP SIGNATURE----- --WJCYmJUqSxpJwZtQ-- From owner-freebsd-hackers@freebsd.org Tue Apr 5 14:04:02 2016 Return-Path: Delivered-To: freebsd-hackers@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 29045B03C72 for ; Tue, 5 Apr 2016 14:04:02 +0000 (UTC) (envelope-from afiskon@devzen.ru) Received: from relay14.nicmail.ru (relay14.nicmail.ru [195.208.3.99]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D05291B81; Tue, 5 Apr 2016 14:04:00 +0000 (UTC) (envelope-from afiskon@devzen.ru) Received: from [109.70.25.187] (port=43774 helo=fujitsu) by f19.mail.nic.ru with esmtp (Exim 5.55) (envelope-from ) id 1anRLf-000EBb-Bp; Tue, 05 Apr 2016 16:48:52 +0300 Received: from [93.174.131.138] (account afiskon@devzen.ru HELO fujitsu) by proxy08.mail.nic.ru (Exim 5.55) with id 1anRLf-0002zG-K9; Tue, 05 Apr 2016 16:48:51 +0300 Date: Tue, 5 Apr 2016 16:48:21 +0300 From: Aleksander Alekseev To: Mark Johnston Cc: Adrian Chadd , Hans Petter Selasky , Andriy Voskoboinyk , "freebsd-hackers@freebsd.org" Subject: Re: I need a little help in fixing `exclusive sleep mutex urtwn0_com_lock` in CURRENT Message-ID: <20160405164821.0158e0eb@fujitsu> In-Reply-To: <20160331225902.GA32570@wkstn-mjohnston.west.isilon.com> References: <20160330123048.3361a9e4@fujitsu> <56FBBC62.6040905@selasky.org> <20160331204256.5cb1fdaf@portege> <20160331180333.GA25235@wkstn-mjohnston.west.isilon.com> <20160401002337.36700d9b@portege> <20160331225902.GA32570@wkstn-mjohnston.west.isilon.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2016 14:04:02 -0000 > Looking at your original post, the problem isn't related to a missing > unlock. The attempt to lock the ieee80211com is triggering a fault, > presumably because it was freed while the lock was dropped. So DTrace > isn't going to help much here. Yeah... on second though I don't think I'm experienced enough in kernel development to fix this, at least quickly. So if anyone knows how to do it please do. I should probably create a ticket in Bugzilla on this, right? -- Best regards, Aleksander Alekseev http://eax.me/ From owner-freebsd-hackers@freebsd.org Thu Apr 7 03:55:06 2016 Return-Path: Delivered-To: freebsd-hackers@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 A9ABFB061A0; Thu, 7 Apr 2016 03:55:06 +0000 (UTC) (envelope-from seu.aba@gmail.com) Received: from mail-lf0-x241.google.com (mail-lf0-x241.google.com [IPv6:2a00:1450:4010:c07::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4EDF11D8F; Thu, 7 Apr 2016 03:55:06 +0000 (UTC) (envelope-from seu.aba@gmail.com) Received: by mail-lf0-x241.google.com with SMTP id e190so6290408lfe.1; Wed, 06 Apr 2016 20:55:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=o0DSxnfdt3CJksCQTLMlpek1zTv3H1IffmjAWaPQ9MA=; b=Xit8v8tMpa57SfBbRCpWn0hHxT1fuViZSGGPZL0t1eAeTa2fqYMTAR5XFv5IdGBXhF pbuPrPT0lfMVcfKnaehj7DQGQnw5JCdavosUEqgnrkhoan/srtiq5t5iCcA0y+Wnuy3a N26VcLNM3Jdujv3jn97prCRu1wY2ZjnQ8uzMxOSnxPelODQJ2tXOGZOpDPMq4+ojJ/ss /oLWqdqVVoe4m67YRI+3mB0dm9ovnt/wDS3Fe0MeDfX7fmmq7k4x0jxv0uOmxg3+EA3K XxYf0DqXimlQz4wyGGf5kqQOvwmbvEAo3umnAGmxX+zBarcAri6vYH6RRBje0IBydYWn Nd2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=o0DSxnfdt3CJksCQTLMlpek1zTv3H1IffmjAWaPQ9MA=; b=fTe6kIlpMcEa6FmPEalvAPAuRIoJshB8qG2hj2+UUKyZ9VahNqv281IxVcXEQHyuqf GhgYs4Le9bO2VgNhXCGmV6kdjfchEqSWBxfwjysC3zLrV2pVeAyo60h8TaPzyHxO3z6i vgRr/sGpupN4fM4MyUSF1fs77g0X1OR6tLsclwU1pYYr4bGLpLnByp8FP5BHLvKwgnEU LjisIA1xpxay3KOi2uazhZU0uFy7e8bTpfMDUCaaNNs+/h6zN1iAYIw1vhLvFqXalAxi RBnilo6O+hr49ZuNEJfCCcPb4+LmdZNGbaVLeJuCn06Sh4ohPZ01zppIKi5BI0FZyf50 i7VQ== X-Gm-Message-State: AD7BkJJRG5ZBkVG+w9yEf2gQg2GYqNU5iew7Fgl/pBJLeDYmfO0hFZVYDFMKuFE0BdUcvVT+WsKvmKAfNcPNFA== MIME-Version: 1.0 X-Received: by 10.25.160.10 with SMTP id j10mr309019lfe.31.1460001303417; Wed, 06 Apr 2016 20:55:03 -0700 (PDT) Received: by 10.25.136.133 with HTTP; Wed, 6 Apr 2016 20:55:03 -0700 (PDT) Date: Wed, 6 Apr 2016 23:55:03 -0400 Message-ID: Subject: So, what I have read and seen From: Seu Aba To: freebsd-hackers@freebsd.org, freebsd-desktop@freebsd.org, freebsd-current@freebsd.org, freebsd-ppc@freebsd.org, freebsd-questions@freebsd.org, info@freebsd.org, dru@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2016 03:55:06 -0000 Is that the lot of you have treated a homeless man with disrespect simply because he was open and honest about what goes on in his life. I have also read about his ideas and they make perfect sense to me. Aiding and assisting the blind while standing up for others is not a bad thing. The reaction he received from most of you borders on harassment which is illegal in a lot of places. He did not ask any of you for anything and refused both money and help to prove his honesty. Not only that, but, you allow someone known for being rude to convince you that the man did wrong without bothering to gather any other information. If you are not aware of the rudeness and social manipulation of deRaadt, you need to rethink things through. More than one person left OpenBSD because of his lack of respect. It also seems that David Wolfskill - one of the info@freebsd members, had treated this homeless man with disrespect. There is something seriously wrong with all of you to treat such a person with disdain and disrespect. Don't say shit. This man received news that his mother was raped and beat and some of you make jokes about that situation. What in the fuck is wrong with you people? What if that happened to your mother or sister or wife or daughter? How would you handle the situation? Don't say a fucking thing. All of you owe that man an apology. From owner-freebsd-hackers@freebsd.org Thu Apr 7 17:45:47 2016 Return-Path: Delivered-To: freebsd-hackers@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 2E50AB06009 for ; Thu, 7 Apr 2016 17:45:47 +0000 (UTC) (envelope-from vrwmiller@gmail.com) Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EB63F1AEA for ; Thu, 7 Apr 2016 17:45:46 +0000 (UTC) (envelope-from vrwmiller@gmail.com) Received: by mail-oi0-x22b.google.com with SMTP id s79so108202985oie.1 for ; Thu, 07 Apr 2016 10:45:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to; bh=KYGKPGqruvmbZzObj3od5iMtLTWifEd/MJPUAx/zNVU=; b=SYvXTtOxGpaOMFKlkmANpPUBqoZ+FRr/F1rVK0y6D/1UO6IHOnEZ/psZdcJalSB1l3 7TNDb2ePdb3tYtsYt69YPOoco/I6lJ9mErwvhK/+ynCEWtzp2nxCKuf8r/sRdgMVbaVf nH71ZfDZnufUdQGBmuvPmLF1DVIB22ARM+c7uDrZDZGSjUbNV4mSzJJFhRSXwOS29EZm 08nmQUG0dbaAKL+B6MNXiq2sGKbH5tZrN443LIE2SbiaTkeMyxzJTSydLce7eKQgTXIM kTFYpjJPcQOTMX9gIX53fq0hMZPg+Gr9YPhEb6Rbw1R07Yl30piuhWfNXl/Xg08JcE8d mcXQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:date:message-id:subject:from :to; bh=KYGKPGqruvmbZzObj3od5iMtLTWifEd/MJPUAx/zNVU=; b=O7GczQ0BlOKyqlh0FMn8aG6NWYyNALl6avO06DWYmY0DjwX6sYEfFRekGZk1CVC4iy yP1VHxahqwr1CkdyoOnENztjYm6aOfZe1Hht82vwxpwZ6kKtwkjS1did9BEhLdtpveGI 9juClkl4ArIRydAHGnQayEnNaWxa2kNbZnTjtao3CuYI7K7nzgv7Rr5EBPEkJXBxFLhX vR++IFjevAcP3IzUuCSZkItIG1x7VVXB9FzlK2pLKmrJpQe0WN5qf3ssEaBZvIPMhHJx RSxQ3g3/m8PI+TAtjpos0T32IBV7G1jeZv2g/MX1II+dAOu+/2hKL1JzgjbMSzpxUe7K Ratw== X-Gm-Message-State: AD7BkJLc+1s1RvWd2iKECwZMicK0svWoVX3+F5+L5JO7mrAfWviUzX+QVmPGir2CbjxRMAJEnq8Dy00vLIEy5A== MIME-Version: 1.0 X-Received: by 10.157.39.193 with SMTP id c59mr2367919otb.111.1460051146313; Thu, 07 Apr 2016 10:45:46 -0700 (PDT) Sender: vrwmiller@gmail.com Received: by 10.202.198.18 with HTTP; Thu, 7 Apr 2016 10:45:46 -0700 (PDT) Date: Thu, 7 Apr 2016 13:45:46 -0400 X-Google-Sender-Auth: 2O1ZsU8Eo7gKSaHhc44UEK1DFIY Message-ID: Subject: AIO in 10.0-RELEASE From: Rick Miller To: freebsd-hackers@freebsd.org X-Mailman-Approved-At: Thu, 07 Apr 2016 18:00:46 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2016 17:45:47 -0000 Please reply directly as I am not currently subscribed to this particular mailing list... A user has been implementing AIO features in an application on FreeBSD 10.0-RELEASE. They assert that, despite aio(4) stating that it is enabled either statically (with VFS_AIO in the kernel config) or dynamically (kldload), in their development environment there was no requirement for either of these methods of enabling AIO. My google-foo is failing me when it comes to FreeBSD's AIO. This question defies logic, but is it possible that AIO works by default in earlier versions of 10.0 and not in more recent version of 10.0 without any local system changes? It is understood that AIO has recently been enabled by default in FreeBSD 10.3 and -CURRENT. This particular scenario is applicable to 10.0. -- Take care Rick Miller From owner-freebsd-hackers@freebsd.org Fri Apr 8 05:52:15 2016 Return-Path: Delivered-To: freebsd-hackers@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 2CC42B07B3F for ; Fri, 8 Apr 2016 05:52:15 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: from puchar.net (puchar.net [84.10.41.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AEDCF1F13 for ; Fri, 8 Apr 2016 05:52:14 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.15.2/8.14.9) with ESMTPS id u385oScM020754 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 8 Apr 2016 07:50:29 +0200 (CEST) (envelope-from wojtek@puchar.net) Received: from laptop.wojtek.intra (localhost [127.0.0.1]) by laptop.wojtek.intra (8.14.9/8.14.9) with ESMTP id u385oTIF004256 for ; Fri, 8 Apr 2016 07:50:29 +0200 (CEST) (envelope-from wojtek@puchar.net) Received: from localhost (wojtek@localhost) by laptop.wojtek.intra (8.14.9/8.14.9/Submit) with ESMTP id u385oNr9004253 for ; Fri, 8 Apr 2016 07:50:24 +0200 (CEST) (envelope-from wojtek@puchar.net) X-Authentication-Warning: laptop.wojtek.intra: wojtek owned process doing -bs Date: Fri, 8 Apr 2016 07:50:23 +0200 (CEST) From: Wojciech Puchar X-X-Sender: wojtek@laptop.wojtek.intra To: freebsd-hackers@freebsd.org Subject: IPSEC tunnels Message-ID: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Fri, 08 Apr 2016 07:50:29 +0200 (CEST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Apr 2016 05:52:15 -0000 does anyone use this in production? How about performance. OpenVPN performance is poor due to system call/context switch on every packet. I found lots of examples how to configure it, but none where one side is over NAT. Can it be configured that way? Any examples? From owner-freebsd-hackers@freebsd.org Fri Apr 8 07:43:17 2016 Return-Path: Delivered-To: freebsd-hackers@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 2A82FB0807D for ; Fri, 8 Apr 2016 07:43:17 +0000 (UTC) (envelope-from dewaynegeraghty@gmail.com) Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A698F1CAB for ; Fri, 8 Apr 2016 07:43:16 +0000 (UTC) (envelope-from dewaynegeraghty@gmail.com) Received: by mail-lf0-x231.google.com with SMTP id j11so73306965lfb.1 for ; Fri, 08 Apr 2016 00:43:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=uYSv0znjDlnWASGcUIRIFRhkssq01OGcFBluu2RsmM8=; b=0C0bRFqJArSNGUM4E0AAIPZhEYNOMHbfbPCYbPwmsSr9HFip1x89L3BbSgFtt7aRG9 BZkHSMkQ/ZVyPkSxngIsdJUEBmeO40zrtFQdSyb4GwfV7mLujrvJdBUIM9EYs9qetpLg id8sOKj/LRwsQ2nOKd1YovU5aInnFlpRjPCqSPOviA+f2cHjv1HRqVSc9WYytC2HhHzP 2Ag0ZXEiS1cqIFCVcOD3YCraoZslybEcCD8eKYViFRx/kODEhhmxIk1msB66J6OPS2Bq LIQy0CMDlzWeXffQrwJXYRhEXH5nIWGUhAGc1IEDQpxHNHagTKF6agZoRblzgGRio/W0 rvNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=uYSv0znjDlnWASGcUIRIFRhkssq01OGcFBluu2RsmM8=; b=kMEIy1AKuK1Dej5wE3fUPAu3hxQGmpdu3GUhFFLGlvkkgA3y8gHWnbM24rG1itw/yC nxwZb75jYFNwEB5csbHl/cP3zaCQm2fAXZ167hhpefMGPKKv1LnBqf/rw7W5X/1tr9Q8 S46pdHEy7dzz7bkajpfNxytURtAHWnDGbv0gp/hfo7vH2hG6qpEqF6g0vAu3DweFzoIJ 6HZ6utQO8n87quew1x/KUZh6CHWPo/3Pqhlc+k/r8rH6lNYacqFrD0jT1Oy64uzyN+Tn YKJ9UQ3W8ju3CnlWIada4LOeb+itKeYdcbmy6Mxw9PdNHIgJDmQeLjmkidra12o2SYXm x+ew== X-Gm-Message-State: AD7BkJKzieUwUSn4xZKzf3YKhwFmn1DO01wSKCItMkLcyefXpK/gY8PGn+AqyXaXu+iD9ZDu2TKycoqAglCUvQ== MIME-Version: 1.0 X-Received: by 10.25.84.17 with SMTP id i17mr3078264lfb.136.1460101394801; Fri, 08 Apr 2016 00:43:14 -0700 (PDT) Received: by 10.25.146.17 with HTTP; Fri, 8 Apr 2016 00:43:14 -0700 (PDT) In-Reply-To: References: Date: Fri, 8 Apr 2016 17:43:14 +1000 Message-ID: Subject: Re: IPSEC tunnels From: Dewayne Geraghty To: Wojciech Puchar Cc: "freebsd-hackers@freebsd.org" X-Mailman-Approved-At: Fri, 08 Apr 2016 11:10:52 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Apr 2016 07:43:17 -0000 Yes I've used it in production for 10 years. Using fixed passwords between 8 branch sites, a HQ, and a contingency location. I've also used strongswan (ikev2) and certificates but it was non-trivial. All firewalls were NATed, if you need to filter traffic you'll need to do so via enc0 (as I recall). Sorry no examples, generally I found it less trouble to filter the interior side of the few, and/or define the ports that you're allowing-though that starts to get messy. Regards Dewayne PS and for the paranoid, yes the password was changed via time-sync'ed ssh :) On Friday, 8 April 2016, Wojciech Puchar wrote: > does anyone use this in production? How about performance. OpenVPN > performance is poor due to system call/context switch on every packet. > > I found lots of examples how to configure it, but none where one side is > over NAT. Can it be configured that way? Any examples? > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > -- *Disclaimer:* *As implied by email protocols, the information in this message is not confidential. Any intermediary or recipient may inspect, modify (add), copy, forward, reply to, delete, or filter email for any purpose unless said parties are otherwise obligated. Nothing in this message may be legally binding without cryptographic evidence of its integrity and/or confidentiality.* From owner-freebsd-hackers@freebsd.org Fri Apr 8 09:55:09 2016 Return-Path: Delivered-To: freebsd-hackers@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 8C178B08F05 for ; Fri, 8 Apr 2016 09:55:09 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 26E3A1DF8 for ; Fri, 8 Apr 2016 09:55:09 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: by mail-wm0-x22e.google.com with SMTP id n3so15837415wmn.0 for ; Fri, 08 Apr 2016 02:55:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=dxlxpxqkWhvREdglqSCN3oSENEZs4p1IVWsP/HMkj/Y=; b=CyFHpZGm0+3lVatGQEANuctV93Mup6QX6MXUa9t1Y7QUG11LbCUTTaeGkqkADu947T QqkyiwrYZxeXVLD8EE2w5O0YFv3320uP25nXls/lejJkYwGWBsy/OACnE9UnW2W/aYX9 Rq6mJG8NXWZMT3DHiKcSaTO8jAkdDgGjRtNcASN3S0O+vu7LC/k+7Y9ACoEVZ7P2Us6h Tz0/PZ2EcyFL1CjqFAvSliKYVP4Z72cLyAwWA6/tzFat7XQ/KWHmKoU1GMrzistMdQ8b +uyZvIL/p2tl3yke1u/Y2kuzUaBJ7N7q8m4/XqXWwV43LPD1GvwdhsXyO59IDUy5SbAW gy/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=dxlxpxqkWhvREdglqSCN3oSENEZs4p1IVWsP/HMkj/Y=; b=gbxrmMsFh6jcchEloaSyPFVqGaALDSkhuvQY/eqZajwYkI7mVgsj1FAvxKla6HxZA/ reUCZjgklfYSK2kp1mSl0Bt5x9sBHBNKBq2EdUHOIF3ttyEBH6IOaSXAj9ycLG/W1V2I j4l+uFEd2gmLmmrs7B4l1Y5W3C9bPTIt3gWwrhi1oVMMx23c9/jUTILEA4CZgM8CgRSb WX74YO60SQdtf/h2rHf5RRj+pJWmiGEhg/lzjEPlNRM99uoLZsQA5+KHi8XwgC7owDFf x2lFusSQezo7vSHqW4hG6GJgFOiuQtZDr6POGYc3JHm24TIQa9Bzn5ZxGKjVZU2+ena9 T7gQ== X-Gm-Message-State: AD7BkJILXji7sxdbQfkbkz+AsGyN+fLyyJQL08gR22EtbKqVkVmA8Zf2YVqPM5+VESiYVA935qhe4MUTNpbxYQ== MIME-Version: 1.0 X-Received: by 10.195.13.115 with SMTP id ex19mr8538778wjd.56.1460109306886; Fri, 08 Apr 2016 02:55:06 -0700 (PDT) Received: by 10.28.46.67 with HTTP; Fri, 8 Apr 2016 02:55:06 -0700 (PDT) In-Reply-To: References: Date: Fri, 8 Apr 2016 10:55:06 +0100 Message-ID: Subject: Re: IPSEC tunnels From: krad To: Wojciech Puchar Cc: freebsd-hackers@freebsd.org X-Mailman-Approved-At: Fri, 08 Apr 2016 11:11:55 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Apr 2016 09:55:09 -0000 I did do it once a long time ago, and it did work, but remember you are dealing with layer 3 so you cant use normal port forwarding for the tunnel traffic. The key exchange is less problematic. It was a bit of a head ache, and if you can avoid the NAT you will be far better off. On 8 April 2016 at 06:50, Wojciech Puchar wrote: > does anyone use this in production? How about performance. OpenVPN > performance is poor due to system call/context switch on every packet. > > I found lots of examples how to configure it, but none where one side is > over NAT. Can it be configured that way? Any examples? > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@freebsd.org Fri Apr 8 12:58:01 2016 Return-Path: Delivered-To: freebsd-hackers@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 4D05DB085D4 for ; Fri, 8 Apr 2016 12:58:01 +0000 (UTC) (envelope-from afiskon@devzen.ru) Received: from relay11.nicmail.ru (relay11.nicmail.ru [195.208.3.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 000B416F6; Fri, 8 Apr 2016 12:58:00 +0000 (UTC) (envelope-from afiskon@devzen.ru) Received: from [109.70.25.215] (port=60159 helo=fujitsu) by f06.mail.nic.ru with esmtp (Exim 5.55) (envelope-from ) id 1aoVzH-000CAY-0E; Fri, 08 Apr 2016 15:58:11 +0300 Received: from [93.174.131.138] (account afiskon@devzen.ru HELO fujitsu) by proxy02.mail.nic.ru (Exim 5.55) with id 1aoVz1-0006D3-Ru; Fri, 08 Apr 2016 15:57:55 +0300 Date: Fri, 8 Apr 2016 15:57:22 +0300 From: Aleksander Alekseev To: Mark Johnston , freebsd-hackers@freebsd.org Cc: Adrian Chadd , Hans Petter Selasky , Andriy Voskoboinyk Subject: Re: I need a little help in fixing `exclusive sleep mutex urtwn0_com_lock` in CURRENT Message-ID: <20160408155722.04d11ff5@fujitsu> In-Reply-To: References: <20160330123048.3361a9e4@fujitsu> <56FBBC62.6040905@selasky.org> <20160331204256.5cb1fdaf@portege> <20160331180333.GA25235@wkstn-mjohnston.west.isilon.com> <20160401002337.36700d9b@portege> <20160331225902.GA32570@wkstn-mjohnston.west.isilon.com> <20160405164821.0158e0eb@fujitsu> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Apr 2016 12:58:01 -0000 > Yes, please do. You can CC the people who followed up on this thread. > > Thanks for the report! > Done: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208632 Naturally if there is anything I can do to help don't hesitate to ask. -- Best regards, Aleksander Alekseev http://eax.me/ From owner-freebsd-hackers@freebsd.org Fri Apr 8 14:11:44 2016 Return-Path: Delivered-To: freebsd-hackers@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 E505DB08D02 for ; Fri, 8 Apr 2016 14:11:44 +0000 (UTC) (envelope-from ganael.laplanche@corp.ovh.com) Received: from 10.mo175.mail-out.ovh.net (10.mo175.mail-out.ovh.net [46.105.63.108]) (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 A587E1DC5 for ; Fri, 8 Apr 2016 14:11:43 +0000 (UTC) (envelope-from ganael.laplanche@corp.ovh.com) Received: from EX3.OVH.local (corp.ovh.com [5.196.251.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mo175.mail-out.ovh.net (Postfix) with ESMTPS id 5DA31FF80B4 for ; Fri, 8 Apr 2016 11:23:01 +0200 (CEST) Received: from desk533202.ovh.net (109.190.254.5) by EX3.OVH.local (172.16.7.3) with Microsoft SMTP Server (TLS) id 15.1.396.30; Fri, 8 Apr 2016 11:23:01 +0200 From: Ganael Laplanche Organization: OVH To: Subject: Re: EFI ZFS loader success story Date: Fri, 8 Apr 2016 11:23:00 +0200 User-Agent: KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; ) References: <201508121139.40852.ganael.laplanche@corp.ovh.com> In-Reply-To: <201508121139.40852.ganael.laplanche@corp.ovh.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-ID: <201604081123.00463.ganael.laplanche@corp.ovh.com> X-Originating-IP: [109.190.254.5] X-ClientProxiedBy: cas02.OVH.local (172.16.1.2) To EX3.OVH.local (172.16.7.3) X-Ovh-Tracer-Id: 8679843860951644890 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeekkedrgeehgddufecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjnecuuegrihhlohhuthemuceftddtnecu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Apr 2016 14:11:45 -0000 On Wednesday, August 12, 2015 11:39:40 AM Ganael Laplanche wrote: Hi everyone, This is a follow-up to this post : https://lists.freebsd.org/pipermail/freebsd-hackers/2015-August/048141.html > Pushing the limits : > -------------------- >=20 > Using this method, it is even possible to get a system bootable from UEFI > *or* legacy BIOS. > [...] I have just filed a PR that enables that "dual-mode" : https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208629 This patch enables a new "BIOS+UEFI" boot type, allowing the machine to reb= oot=20 either in BIOS mode or in UEFI mode :) Best regards, =2D-=20 Gana=EBl LAPLANCHE