Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 26 Nov 2018 19:00:37 +0100 (CET)
From:      =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no>
To:        FreeBSD questions <freebsd-questions@freebsd.org>
Subject:   Re: Invalid DKIM signatures in this list
Message-ID:  <alpine.BSF.2.21.9999.1811261858180.90197@mail.fig.ol.no>
In-Reply-To: <20181126165916.6c6bf874@gumby.homeunix.com>
References:  <20181126125259.GB86999@admin.sibptus.ru> <alpine.BSF.2.21.9999.1811261704230.90197@mail.fig.ol.no> <20181126165916.6c6bf874@gumby.homeunix.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Mon, 26 Nov 2018 16:59-0000, RW via freebsd-questions wrote:

> On Mon, 26 Nov 2018 17:10:27 +0100 (CET)
> Trond Endrestøl wrote:
> 
> > On Mon, 26 Nov 2018 19:52+0700, Victor Sudakov wrote:
> > 
> > > Dear Colleagues,
> > > 
> > > I have noticed that the Mailman which manages this list keeps the
> > > sender's "DKIM-Signature:" header intact but modifies the body of
> > > the message by adding a footer.  
> > 
> > Are you sure?
> > 
> > When I received your message, the hash was made up using Message-ID, 
> > Subject, To, From, Date, and In-Reply-To. I failed to find the latter 
> > field.
> 
> That's legitimate, it signs the absence of that header if it's not
> present at the time of signing. 

OpenDKIM on my own server, not this one, doesn't take In-Reply-To into 
account unless that header is present in the envelope.

Also, I was unaware of a body hash. My bad.

-- 
Trond.
From owner-freebsd-questions@freebsd.org  Mon Nov 26 18:53:22 2018
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 608DE114085B
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Mon, 26 Nov 2018 18:53:22 +0000 (UTC)
 (envelope-from carmel_ny@outlook.com)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com
 (mail-oln040092005061.outbound.protection.outlook.com [40.92.5.61])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits))
 (Client CN "mail.protection.outlook.com",
 Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 4FDBF82DFF
 for <freebsd-questions@freebsd.org>; Mon, 26 Nov 2018 18:53:21 +0000 (UTC)
 (envelope-from carmel_ny@outlook.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com;
 s=selector1;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
 bh=OqM3Wf40XfjqkhcIGc/zQgPLpmOe/Uu3JT5e+aBnKSc=;
 b=L8e6z9wWnpprd8x3FUjopKADgWN6RGtDn2D0ZZoasjM1aGupx3Gc2pAFydEF1pFvCwbVJEr/PZ0YzQRlizcP3w2BYTtCAaUx+vlGFwAQexreT+FG7iLPmGfSQxaqzBZEx18DZCI54Ww2q2Z+8TIeiBnXWGnQCHXiWHl1CY1Kb9c/XWk3nBfTY2Ts0ojzXhhQ7QIXY+JSLcMVWBiEpM/8z5d0YI60XmVBhQZO7/dFjIOeNPNhW34NUoOU3TOTEgjwp+8cEITgj1IB4ky+OS4L3O33wHovKIZdww9H4ldaIWql7tjzu/ceCiL7kUtod15gtAD1eNOazIFMTEtEyXN3Gg==
Received: from SN1NAM02FT011.eop-nam02.prod.protection.outlook.com
 (10.152.72.58) by SN1NAM02HT127.eop-nam02.prod.protection.outlook.com
 (10.152.73.102) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1339.15; Mon, 26 Nov
 2018 18:53:19 +0000
Received: from BL0PR20MB2098.namprd20.prod.outlook.com (10.152.72.57) by
 SN1NAM02FT011.mail.protection.outlook.com (10.152.72.82) with Microsoft SMTP
 Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 15.20.1339.15 via Frontend Transport; Mon, 26 Nov 2018 18:53:19 +0000
Received: from BL0PR20MB2098.namprd20.prod.outlook.com
 ([fe80::6088:db58:c3b4:31f2]) by BL0PR20MB2098.namprd20.prod.outlook.com
 ([fe80::6088:db58:c3b4:31f2%4]) with mapi id 15.20.1361.019; Mon, 26 Nov 2018
 18:53:19 +0000
From: Carmel NY <carmel_ny@outlook.com>
To: FreeBSD <freebsd-questions@freebsd.org>
Subject: Re: Possible updating of "mount_smbfs"
Thread-Topic: Possible updating of "mount_smbfs"
Thread-Index: AQHUhLlvO1VyZUr7CUq4lnsb/TAwZA==
Date: Mon, 26 Nov 2018 18:53:19 +0000
Message-ID: <BL0PR20MB20985F774C1DDB8573FEF4F380D70@BL0PR20MB2098.namprd20.prod.outlook.com>
References: <DM5PR20MB21024CFFA05B729FD51C876080D60@DM5PR20MB2102.namprd20.prod.outlook.com>
 <20181126012820.2f862cc2.freebsd@edvax.de>
In-Reply-To: <20181126012820.2f862cc2.freebsd@edvax.de>
Reply-To: FreeBSD <freebsd-questions@freebsd.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-clientproxiedby: BN7PR10CA0012.namprd10.prod.outlook.com
 (2603:10b6:406:bc::25) To BL0PR20MB2098.namprd20.prod.outlook.com
 (2603:10b6:207:45::10)
x-mailer: Claws Mail 3.17.1 (GTK+ 2.24.32; x86_64-w64-mingw32)
x-incomingtopheadermarker: OriginalChecksum:6295CFA6C46867F779B35ED039F93CECFDBB83CC51A383F8DDC1F3346144A60A;
 UpperCasedChecksum:9A1B45830D1A6412D52DE35BA99F12965703A96AB5B1B4649D0484BD9769F124;
 SizeAsReceived:7554; Count:51
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [Q2qph/TPw2sJ8ZvLh/e/nIiqSnhpXz56QXQVJiMkLzg=]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN1NAM02HT127;
 6:lX8+Ui8+MCC074IGMwx7cUl9STxlv7bnUP4i/dZeUtFEXnq5SsLEBce4Y512aymOrWxOw45FUyw6h4HHIcgdfyksPDFm+/K9ZKg2cSAFWUa+nRHG16l0nk2mWHef1gFthXXwKMVvEN6Oj4M9y/EVOtTpxdI5LLe3RXZpwj2qHcSTkz4Ypbo22ha4KZkfPU3DwDA/ixjjU8SILXRtJNodZqlBC07RabZX8sfgbQBomR6yAFGJ02UQB42M1obe6Uj8FNw67FmtgW9VpJ7rIAbcJ+gwBwEc5Uq3QwrbtgQq52kVhApWYT089S5XIM6NYgZWfd1wP7+JIc+3gZSX6npBKoi9jCPxXtiMsesafIzO0X8bAWj90y5AjA/yPoj84avEiFxU0ASErcgREeZfWL5e6pBhOYYQ/KATEYIKP/4WzYOwJrOUgheeS43JkrHLf7/L1x+QiB0QdExpew4psGM5cA==;
 5:6gmbB98tuDC1+c1Tc6cdhaVr2tBDrj9cCn6frRubXghifUJYe2QFDeo6eJ1JVUz8WzfPxbKV2JQy0K9WVknQwOBeZwAzVGhTQPlHU7ue2AkMVW3bMvExJkubnUVxYUFUv+0E4V0pmkzmzGNx4ijl1hAYTqPQfUH4oRNneZQbYN8=;
 7:/apVtr3pAf04uNL1tSp7a0A3YzUVHZXEhosCU5G0kqon7v1Z92lQzqwsqkBg2c70GXKEzHfC7T0IINCl4ViAAat3uQCNAt8dm0B0J+3TuivnbFs1kMkOsqVEKSxRI2XL44b4fbZwLoeVi40CAdymVQ==
x-incomingheadercount: 51
x-eopattributedmessage: 0
x-microsoft-antispam: BCL:0; PCL:0;
 RULEID:(2390098)(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1603101475)(1601125500)(1701031045);
 SRVR:SN1NAM02HT127; 
x-ms-traffictypediagnostic: SN1NAM02HT127:
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(4566010)(82015058);
 SRVR:SN1NAM02HT127; BCL:0; PCL:0; RULEID:; SRVR:SN1NAM02HT127; 
x-microsoft-antispam-message-info: YCT0biHsJ5+WAgHkYWLr270JM+wMmKgEvwWCfyFDD8kSODOQAfgb69pgCuxCsb+T
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E4B1D61022C9ED498A2CDDEC221B2351@namprd20.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 9a4e3081-9524-43cf-bfc3-dcaef82d5da1
X-MS-Exchange-CrossTenant-Network-Message-Id: fa3331b6-a6e1-4ae6-7fe7-08d653d06eb2
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 9a4e3081-9524-43cf-bfc3-dcaef82d5da1
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Nov 2018 18:53:19.7967 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1NAM02HT127
X-Rspamd-Queue-Id: 4FDBF82DFF
X-Spamd-Result: default: False [2.08 / 15.00]; ARC_NA(0.00)[];
 HAS_REPLYTO(0.00)[freebsd-questions@freebsd.org];
 R_DKIM_ALLOW(-0.20)[outlook.com];
 NEURAL_HAM_MEDIUM(-0.97)[-0.967,0]; FROM_HAS_DN(0.00)[];
 R_SPF_ALLOW(-0.20)[+ip4:40.92.0.0/14];
 FREEMAIL_FROM(0.00)[outlook.com]; MIME_GOOD(-0.10)[text/plain];
 TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.91)[-0.914,0];
 RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[4];
 TO_DN_ALL(0.00)[];
 MX_GOOD(-0.01)[cached: outlook-com.olc.protection.outlook.com];
 DKIM_TRACE(0.00)[outlook.com:+];
 RCVD_IN_DNSWL_NONE(0.00)[61.5.92.40.list.dnswl.org : 127.0.3.0];
 NEURAL_HAM_SHORT(-0.03)[-0.030,0];
 DMARC_POLICY_ALLOW(-0.50)[outlook.com,none];
 FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[];
 FREEMAIL_ENVFROM(0.00)[outlook.com]; REPLYTO_EQ_TO_ADDR(5.00)[]
X-Rspamd-Server: mx1.freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>;
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Nov 2018 18:53:22 -0000

On Mon, 26 Nov 2018 01:28:20 +0100, Polytropon stated:

>On Sun, 25 Nov 2018 12:21:46 +0000, Carmel NY wrote:
>> Microsoft publicly deprecated the SMBv1 protocol in 2014. Unfortunately,
>> this nullifies the use of "mount_smbfs", I was wondering if there are an=
y
>> plans to update the "mount_smbfs" utility? =20
>
>Well, I don't think so. The FreBSD provided tools for mounting
>non-native filesystems don't seem to be the adivsed choice. Just
>as mount_ntfs has been removed from the OS and its functionality
>transitioned to FUSE, access to CIFS shares should probably be
>done with FUSE, too.
>
>Luckily, there's SMBNetFS (sysutils/fusefs-smbnetfs), which looks
>like the natural replacement.
>
>See:
>
>https://www.freshports.org/sysutils/fusefs-smbnetfs/
>
>https://sourceforge.net/projects/smbnetfs/
>
>Unlike mount_smbfs, it supports the recent versions of Samba.
>I wouldn't be surprised if one day /usr/sbin/mount_smbfs would
>no longer be present after a regular FreeBSD install... ;-)

Unfortunately, I cannot get it to work. There is virtually no documentation
for it. Plus,I just read that it only supports SMBv1, which makes it useles=
s
for my needs. In addition, I was just reading an article I found with Googl=
e
that states that I have to have a GUI loaded, There is no GUI installed on =
my
FreeBSD box, and I don't intend to install one.

--=20
Carmel



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.21.9999.1811261858180.90197>