From owner-freebsd-hackers@freebsd.org Fri Oct 2 02:10:39 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6887F3F211A for ; Fri, 2 Oct 2020 02:10:39 +0000 (UTC) (envelope-from jmaharaj2013@gmail.com) Received: from mail-ed1-x542.google.com (mail-ed1-x542.google.com [IPv6:2a00:1450:4864:20::542]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C2YPB52w5z40tr for ; Fri, 2 Oct 2020 02:10:38 +0000 (UTC) (envelope-from jmaharaj2013@gmail.com) Received: by mail-ed1-x542.google.com with SMTP id c8so123869edv.5 for ; Thu, 01 Oct 2020 19:10:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:thread-topic:thread-index:date:message-id :accept-language:content-language:mime-version; bh=7oeyIsVWHH2p2bzEUFmPAdfOFxbmlIzH/6sIXNpgBCQ=; b=cKo6SixyP5sG9PqfWGd66PPu4mNFrMD4Bq2i6OopN/NyW7r5UXWr0ntd0e4lsyY7Xz L2xN47jysnLDY+Lp4NWoXSQEJqFWyuIpiy13b/77+OGS1gfpg9e3OqaIp+RpoktIjBQj mPh0tOR6RPVda1s198PcLjF+PDJdXlEKGL6SZ2WHDwqQtweigIrwamYwAFYc3K/l2/Oj qpsJCHQXWc2vbJeIx2cqT6IjnKqioo/10mgO5oLQI2wyhewyOLxnqS494SqbbCPhw+7P 8vvm6b+CrNVrQpuhf6i8Kb2OTBPqguLOeb18GL1mKjYtFSN9WyIAqLY6v2GeqpDSIG9o 0XtQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:accept-language:content-language:mime-version; bh=7oeyIsVWHH2p2bzEUFmPAdfOFxbmlIzH/6sIXNpgBCQ=; b=mmwR+76uIv6l4xgPkOQfmsinSf8dMuv5ltTLgCD6X2KypUD2m1Yc3ojiNO+sSxnkMB NTonPi439U0rSgISqZgPe02a+z2PuKSfejs4MajsXhEJMhKcuDZR+JOLlv43cabon+Vz hgkprue2THRC0ol2gt8HjEG7SOv67FKxukCh95kSeoTPourVYh5lqhKBHbQNo36FyCCD vOU410oarsn3xHr1se78cAyTUk3kQfPfaw6jW0Wg7qcazb565+BXeac6dM1veOPUUfRj 5bRXMgZUiCxtTVy7+5ZFeMzupeNAW5iFDecncfoKnRzM5MgGz7102gFUgMaGWaL1ORaO oewg== X-Gm-Message-State: AOAM530m7E2ZK6fL14yCiYCtPp/RCeMsCvfWj1qrU7yZlf2Y90QWQDW1 0T9pxAvRk//wU+vZswCViQ2T7j8kK1M= X-Google-Smtp-Source: ABdhPJzN2czSlG2azMlT/lvX2YOE8qqPlxJlOUSa81dIul/2rgeRxAlokjcbxleaaSTK6SejgZ9mYg== X-Received: by 2002:aa7:c70a:: with SMTP id i10mr11448462edq.218.1601604635735; Thu, 01 Oct 2020 19:10:35 -0700 (PDT) Received: from BYAPR05MB6311.namprd05.prod.outlook.com ([2603:1036:307:28c7::5]) by smtp.gmail.com with ESMTPSA id x12sm79308edq.77.2020.10.01.19.10.34 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Oct 2020 19:10:35 -0700 (PDT) From: Raj J Putari To: "freebsd-hackers@freebsd.org" Subject: Idea: Signing software with stuff like ssl certs Thread-Topic: Idea: Signing software with stuff like ssl certs Thread-Index: AQHWmGE1Nuel7zIVI02UZP8EK96NSQ== X-MS-Exchange-MessageSentRepresentingType: 1 Date: Fri, 2 Oct 2020 02:10:32 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-Exchange-Organization-SCL: -1 X-MS-TNEF-Correlator: X-MS-Exchange-Organization-RecordReviewCfmType: 0 MIME-Version: 1.0 X-Rspamd-Queue-Id: 4C2YPB52w5z40tr X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=cKo6Sixy; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of jmaharaj2013@gmail.com designates 2a00:1450:4864:20::542 as permitted sender) smtp.mailfrom=jmaharaj2013@gmail.com X-Spamd-Result: default: False [-3.45 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; NEURAL_HAM_MEDIUM(-0.97)[-0.968]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.003]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::542:from]; NEURAL_HAM_SHORT(-0.48)[-0.481]; TO_DN_EQ_ADDR_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-hackers]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Oct 2020 02:10:39 -0000 No code yet, I don=92t want to use qemu because I heard its fast, but reall= y hacky, but I=92m working on buying parallels on the third with my SSI mon= ey because my dad bought me a mac pro 2013 off amazon (which is amazing by = the way) For ports and packages, a package distributor signs the software with an en= crypted key, and in the kernel we check it and decrypt it on the fly, or st= ore information in the swap (which can be encrypted as well), or in a direc= tory, I suggest in the /var or possible /usr directory, but I don=92t reall= y want to break heirachy for systematic reasons In the kernel, probably in some directory, we have a source file that loads= , checks, and does various checks on the cert and checks it, and if it pass= es the tests, it loads it into memory and executes it, using conventional p= rogramming Failing that, and I can work on this later, but I prefer if someone else di= d, we can just have a userland application that generates a key and signs i= t (not sure how, I haven=92t really googled or checked on it) Also we need some kind of web site and possible a protocol (welcome back 90= s) that deals with issuing certificates for software such as applications, = software, and device drivers, kind of like letsencrypt My logic is that if you cannot access a resource due to encryption, you can= not hack it I honestly suggest. Fork, since if you encrypt the entire kernel, theres go= ing to be problems, so I strongly suggest everyone team up with their assoc= iates and make a fork, or possibly implement it in openbsd What does everyone think? When I get my check, im going to cludge around in= FBSD13-CURRENT