all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Csepp <raingloom@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 61201@debbugs.gnu.org
Subject: bug#61201: Installation hint crashes when user names contain at sign
Date: Fri, 24 Feb 2023 12:18:36 +0100	[thread overview]
Message-ID: <87h6vbjomm.fsf@riseup.net> (raw)
In-Reply-To: <87sfev2w8k.fsf@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> Ludovic Courtès <ludovic.courtes@inria.fr> skribis:
>
>> A funny thing was reported earlier today on the Café Guix channel:
>>
>> $ guix install hello  [17:52]
>> building profile with 5 packages...
>> hint: Backtrace:
>
> [...]
>
>> In guix/ui.scm:
>>     312:5  6 (display-hint _ )
>>   1451:24  5 (texi->plain-text )
>> In texinfo.scm:
>>   1132:22  4 (parse )
>>    980:31  3 (loop #<input: string 2b6e5926be70> (fragment) _ _ )
>>    967:36  2 (loop #<input: string 2b6e5926be70> #f # ?)
>>      92:2  1 (command-spec )
>> In ice-9/boot-9.scm:
>>   1685:16  0 (raise-exception _ #:continuable? )
>>  
>> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
>> Throw to key #E1E1E1">parser-error' with args(#f "Unknown command" univ)'.
>
> Here’s one way to reproduce the bug, showing a crash in ‘display-hint’
> due to an unescaped brace:
>
> $ mkdir /tmp/x{ample
> $ touch /tmp/x{ample/guix.scm
> $ (cd '/tmp/x{ample' ; guix shell)
> guix shell: error: not loading '/tmp/x{ample/guix.scm' because not authorized to do so
> hint: Backtrace:
>           13 (primitive-load "/home/ludo/.config/guix/current/bin/guix")
> In guix/ui.scm:
>    2279:7 12 (run-guix . _)
>   2242:10 11 (run-guix-command _ . _)
> In ice-9/boot-9.scm:
>   1752:10 10 (with-exception-handler _ _ #:unwind? _ #:unwind-for-type _)
> In guix/scripts/shell.scm:
>    308:15  9 (_)
> In guix/ui.scm:
>     312:5  8 (display-hint _ _)
>   1451:24  7 (texi->plain-text _)
> In texinfo.scm:
>   1132:22  6 (parse _)
>    980:31  5 (loop #<input: string 7feb8b300d20> (*fragment*) _ _ _)
>    980:31  4 (loop #<input: string 7feb8b300d20> #f _ _ _)
>    911:31  3 (loop #<input: string 7feb8b300d20> #f #<procedure identity (x)> #f _)
>    746:27  2 (_ #<input: string 7feb8b300d20> #f (example smallexample verbatim lisp smalllisp menu w %) #<procedure 7feb9aea1948 at texin…> …)
> In sxml/ssax/input-parse.scm:
>      88:2  1 (next-token _ _ _ _)
> In ice-9/boot-9.scm:
>   1685:16  0 (raise-exception _ #:continuable? _)
>
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> Throw to key `parser-error' with args `(#<input: string 7feb8b300d20> "EOF while reading a token " "reading char data")'.
>
> Ludo’.

Would it be heresy to recommend that plain strings and strings that
contain texinfo markup be separate types to catch this sort of thing?
In 2023 it's pretty embarrassing to have bugs that are basically SQL
injections.




      parent reply	other threads:[~2023-02-24 11:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 17:05 bug#61201: Installation hint crashes when user names contain at sign Ludovic Courtès
2023-02-24 10:28 ` Ludovic Courtès
2023-02-24 10:40   ` [bug#61749] [PATCH] ui: 'display-hint' quotes extra arguments for Texinfo Ludovic Courtès
2023-02-27 22:55     ` bug#61201: bug#61749: " Ludovic Courtès
2023-02-24 11:18   ` Csepp [this message]

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=87h6vbjomm.fsf@riseup.net \
    --to=raingloom@riseup.net \
    --cc=61201@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.