From owner-freebsd-security@freebsd.org Wed Jan 29 10:58:56 2020 Return-Path: Delivered-To: freebsd-security@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 562161D40B8 for ; Wed, 29 Jan 2020 10:58:56 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com [IPv6:2607:f8b0:4864:20::433]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 4870pl0sGCz4SDD; Wed, 29 Jan 2020 10:58:54 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mail-pf1-x433.google.com with SMTP id n7so8230079pfn.0; Wed, 29 Jan 2020 02:58:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:reply-to:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=3HOHnCWxUOs6nxo/mYrWtsp78zCOKH4TlHzQgxFHZ1k=; b=jd/s4YoB0ONnWLVf+w/VuhHnvmWo8A5SF8pvlC/NKxUpxV+Uz2TS4Sd+tKK7NeGb29 ANO8fpLeeWswW79FRcmAScCqI2gLJIrskutcivAga7i2x/elP4DEMJ+pwuLmaqRgaO7+ TGRQzNjQAZ1ZHHuFnjMaV0usX32Tx0JTl8SgEdKpjbjM7uicSmpSemXgULLIlrb18TQQ ugm2E/BJzvS5rYZLvfkyxiSOetBWVI7UveB7679vcRTVWOKkVHMSYYaf5cZC/N0GJtEU 4llfvCYF3t0iyoq+/O/4gcht+1etyaMnw0c+3ky46WmOy1+EJvB7r1kjqtpCjC1oczwn tlHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:reply-to:subject:to:references:cc:from :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=3HOHnCWxUOs6nxo/mYrWtsp78zCOKH4TlHzQgxFHZ1k=; b=jBV+8ilGltyuUBJbB7wCObgbbABSzxlosMgX0uLul6v8qL2xgJg6gH9T79FWRxE9nO Oh8Iehjx0k8bN1p2tFF8+1OKUrblBe7GvpFmCE8o4h3NtAJlQrTBK88e79l9vsduiCrg E2UfoF5VCex59xk5rDq4fE5otTR5sUdcisEWxcZ3/NlbjRsoFfOEGn9YmyTRqhI3M9/4 YmlFSFG3Jf86A01qw7lzdL+8Sqrv3aTguYziJ5IWop3/okKfxONUqPozwwyC4hxRRNM+ HF8TDDdTwuvmi8/7Fr3qR+4CJLrXyoILKVeiu/LCsFTbLRIiqgSCv3yKRyc1UearXdiU jTVA== X-Gm-Message-State: APjAAAUuzYvtUoHDkpb3N5mZYDTcNGzX/FzcC1vv7CfP/wX5PRnpR3gg nrNsqvwrdFn95LqRrCSLG5JDrPTS X-Google-Smtp-Source: APXvYqw3m2mZvKY6YsK5gww/Bn/zT6RJ+MQcHF6ipXSgwXKPU0b71xBBIorSRVz8b3nqm3ya+dp8pw== X-Received: by 2002:a62:4e05:: with SMTP id c5mr7320064pfb.258.1580295533430; Wed, 29 Jan 2020 02:58:53 -0800 (PST) Received: from [192.168.1.110] (180-150-68-130.b49644.syd.nbn.aussiebb.net. [180.150.68.130]) by smtp.gmail.com with ESMTPSA id y197sm2333033pfc.79.2020.01.29.02.58.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 29 Jan 2020 02:58:52 -0800 (PST) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: @freebsdsecurity Twitter handle? To: Miroslav Lachman <000.fbsd@quip.cz>, Royce Williams , freebsd-security@freebsd.org References: <17390aa6-cf0a-6719-f573-9aca6df8a133@FreeBSD.org> <10370c52-5446-ae64-6d08-572abf76957d@quip.cz> Cc: "secteam@freebsd.org" From: Kubilay Kocak Message-ID: <731c6baa-d3e4-89ee-aa77-5aa6e31cdcec@FreeBSD.org> Date: Wed, 29 Jan 2020 21:58:49 +1100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Thunderbird/73.0 MIME-Version: 1.0 In-Reply-To: <10370c52-5446-ae64-6d08-572abf76957d@quip.cz> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4870pl0sGCz4SDD X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=jd/s4YoB; dmarc=none; spf=pass (mx1.freebsd.org: domain of koobsfreebsd@gmail.com designates 2607:f8b0:4864:20::433 as permitted sender) smtp.mailfrom=koobsfreebsd@gmail.com X-Spamd-Result: default: False [-3.72 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[koobs@FreeBSD.org]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; FORGED_SENDER(0.30)[koobs@FreeBSD.org,koobsfreebsd@gmail.com]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FROM_NEQ_ENVFROM(0.00)[koobs@FreeBSD.org,koobsfreebsd@gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.996,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; TAGGED_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[FreeBSD.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[3.3.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.52)[ip: (-8.74), ipnet: 2607:f8b0::/32(-2.03), asn: 15169(-1.78), country: US(-0.05)]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jan 2020 10:58:56 -0000 On 29/01/2020 8:42 pm, Miroslav Lachman wrote: > Kubilay Kocak wrote on 2020/01/29 03:53: >> On 29/01/2020 7:51 am, Royce Williams wrote: >>> Is the @freebsdsecurity Twitter handle managed by the security team? (If >>> so, looks like it's been fallow since 2016?) >>> >>> If not, is there an equivalent Twitter account that is official? >>> >> >> Hi Royce, >> >> I run @FreeBSDHelp, tweet about FreeBSD security related issues and >> SA's / EN's when announced, and am not aware of an official >> security-oriented presence on Twitter. >> >> I've reached out to @FreeBSDSecurity on twitter to see if I can access >> to the account to facilitate that. >> >> Note: Other official accounts are @freebsd_portmgr and @freebsdcore >> >> I registered @FreeBSDSecteam for potential official tweets by secteam >> & ports-secteams, but haven't put it to use yet. I'll see if I can't >> get something started > > It is always good to have more channels for Security Advisories. > Can somebody convince FreeBSD Security Office to publish Advisories in > vuln.xml at the same as on the website? It is FreeBSD's own tool to > handle vulnerabilities but they are not there. > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243702 This (making sure SA's were added) was brought up in the recent past so I imagine todays SA's are/were either planned, or already in flight to land in the VuXML list. Thank you for creating the issue, its been assigned to secteam cc ports-secteam > Kind regards > Miroslav Lachman