From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: chad Newsgroups: gmane.emacs.devel Subject: Re: Bidirectional text and URLs Date: Sun, 30 Nov 2014 15:39:15 -0800 Message-ID: <419C54B5-68C4-4880-B826-33AD30112EAE@gmail.com> References: <87zjbbdt0u.fsf@igel.home> <833892aq3m.fsf@gnu.org> <83egskaf6c.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1417390799 3501 80.91.229.3 (30 Nov 2014 23:39:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 30 Nov 2014 23:39:59 +0000 (UTC) Cc: larsi@gnus.org, schwab@linux-m68k.org, Richard Stallman , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 01 00:39:55 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XvE5q-0006eI-PH for ged-emacs-devel@m.gmane.org; Mon, 01 Dec 2014 00:39:54 +0100 Original-Received: from localhost ([::1]:52187 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XvE5q-0001Jt-Cy for ged-emacs-devel@m.gmane.org; Sun, 30 Nov 2014 18:39:54 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52642) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XvE5Y-0001Jk-E3 for emacs-devel@gnu.org; Sun, 30 Nov 2014 18:39:41 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XvE5S-0000zr-Rl for emacs-devel@gnu.org; Sun, 30 Nov 2014 18:39:36 -0500 Original-Received: from mail-pa0-x232.google.com ([2607:f8b0:400e:c03::232]:39448) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XvE5G-0000wb-Hu; Sun, 30 Nov 2014 18:39:18 -0500 Original-Received: by mail-pa0-f50.google.com with SMTP id bj1so9850951pad.37 for ; Sun, 30 Nov 2014 15:39:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Aj3qtId90UsD5FgAFiCAccmegdwY3DQxHB1ABafx5wk=; b=QN+515TY94Llngyb74KtQ9oJXXTYt4mLkOEx4+IRyy11R4476ng20iHVjgMJxVHivn FCFEjytPfI+QLR5eO0cDC6YL8VD1XaknI2rtporDhmx9d61ne3z6up8HQQ+cy6YN6OEj OrQLxFgiJeURhQ2T+MVdFTJbjjV30njO5BdGtgMq3VDpBcjQkkRMPxMDJ8XQKYqgVvmm YaietIzpT8d2iDMJXUh5zMlSgZIfhxyUzvp0jRmJWR7K3pVA6XqUWfbGYo4yllGOex/M bV7UO9+STDl4MxOoVM0Qk/VcmFStmdLgdIvjJD3XbtefUOO8F9gU83fWGLvA0WEb2Fw+ YKWg== X-Received: by 10.68.131.163 with SMTP id on3mr93948045pbb.169.1417390757262; Sun, 30 Nov 2014 15:39:17 -0800 (PST) Original-Received: from [10.0.1.37] (75-165-99-219.tukw.qwest.net. [75.165.99.219]) by mx.google.com with ESMTPSA id v4sm13814498pdc.61.2014.11.30.15.39.16 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 30 Nov 2014 15:39:16 -0800 (PST) In-Reply-To: <83egskaf6c.fsf@gnu.org> X-Mailer: Apple Mail (2.1993) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::232 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:178551 Archived-At: > On 30 Nov 2014, at 07:20, Eli Zaretskii wrote: > > I'm sorry, but this is not instrumental: it doesn't specify what > "misleading" means. We need a detailed spec for that. Given things we're already identifying the URL in text, is it possible/easy to check for a different directionality of any part of a URL text (including the entire url) compared to the text (not whitespace) before and after the URL? In order to make phishing-style surprises work, the mal-ordered text probably wants to have the left-side string "http[s]://" and the right-side string "//:[s]ptth", right? That should be reasonably easy to check, and would be a good heuristic. I suppose there are non-HTTP schemes that might be troublesome also. Some that come to mind are: ftp, file, imap, jabber, nntp, sip, sips, and xmpp. I can't think of a way offhand to abuse mailto: or about:, but I might just be missing it. Hope that helps, ~Chad