tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv, Jason McIntyre <jmc@cava.myzen.co.uk>
Subject: [PATCH] \N'nnn' protection.
Date: Sun, 01 May 2011 00:37:27 +0200	[thread overview]
Message-ID: <4DBC8F27.3040600@bsd.lv> (raw)

[-- Attachment #1: Type: text/plain, Size: 479 bytes --]

Hi,

Enclosed is a patch to limit possible \N'nnn' escapes.  \N transforms 
the number 'nnn' into its character representation and is marked as "for 
backwards compatibility" in mandoc_char(7).

I can only find manuals using this for the double-quote \N'34', so this 
seems safe, but maybe one of you knows of crazy \N usage that would 
inspire me to re-think.  However, throwing, e.g., the \b character in 
there will cause at least -Tps and -Tpdf to puke.

Thoughts?

Kristaps

[-- Attachment #2: patch.chars.txt --]
[-- Type: text/plain, Size: 734 bytes --]

Index: chars.c
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/chars.c,v
retrieving revision 1.39
diff -u -r1.39 chars.c
--- chars.c	30 Apr 2011 22:24:31 -0000	1.39
+++ chars.c	30 Apr 2011 22:31:11 -0000
@@ -20,6 +20,7 @@
 #endif
 
 #include <assert.h>
+#include <ctype.h>
 #include <stdio.h>
 #include <stdlib.h>
 #include <string.h>
@@ -148,12 +149,10 @@
 		return('\0');
 
 	i = atoi(p);
-	/* 
-	 * FIXME:
-	 * This is wrong.  Anything could be written here!
-	 * This should be carefully screened for possible characters.
-	 */
-	return(i <= 0 || i > 255 ? '\0' : (char)i);
+	if (isalnum(i) || ispunct(i) || ' ' == (char)i)
+		return(i);
+
+	return('\0');
 }
 
 

             reply	other threads:[~2011-04-30 22:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-30 22:37 Kristaps Dzonsons [this message]
2011-04-30 22:59 ` Ingo Schwarze
2011-04-30 23:18   ` Kristaps Dzonsons

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DBC8F27.3040600@bsd.lv \
    --to=kristaps@bsd.lv \
    --cc=jmc@cava.myzen.co.uk \
    --cc=tech@mdocml.bsd.lv \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).