unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Gregor Giesen <giesen@zaehlwerk.net>
Cc: help-guix@gnu.org
Subject: Re: Extra files in build container
Date: Mon, 19 Jun 2017 23:21:03 +0200	[thread overview]
Message-ID: <87y3sn7jy8.fsf@gnu.org> (raw)
In-Reply-To: <20170619164842.6tu5et5uztpmbxho@zaehlwerk.net> (Gregor Giesen's message of "Mon, 19 Jun 2017 18:48:42 +0200")

Hi Gregor,

Gregor Giesen <giesen@zaehlwerk.net> skribis:

> On Mon, Jun 19, 2017 at 04:49:43PM +0200, Ludovic Courtès wrote:
>> >> I think it would be easier to just use ‘substitute*’ to replace all the
>> >> occurrences of “tcp”, etc., wouldn’t it?
>> > alas many occurences of "tcp", "udp", etc. are hidden in
>> > encrypted/hashed records, so simple plain text substitutions would
>> > break the signatures.
>> 
>> Yes, I can imagine.  But maybe (maybe not!), by selecting the right set
>> of files to modify, and by adjusting the regexp (let’s say “\<tcp\>” or
>> “"tcp"”) to match only what matters, it could work.
> here is a sample record pair:
>
> wks02.types-signed.wb.sidnlabs.nl.      60      IN      WKS     10.0.0.1 udp 0 1 2 domain
> wks02.types-signed.wb.sidnlabs.nl.      60      IN      RRSIG   WKS 8 5 60 20140201000000 20130930114324 62298 types-signed.wb.sidnlabs.nl. P+p1gcQbO4I/sBQUZktrz4Q1osWIFIFGlK8o+SzIXMjxmdNy36vjwW6Sfy97CycbLRFIQ2grPv/cPaXtoMb+usHCoDtl5sSvLTJFmg9hpQ+xm12GvunZvAYAGx9fZic+QvLahSg+cjqX1M0oR9B68gcx+duMdLzawlUcIqX8gmA=
>
> So changing the first line requires to recreating the signature record
> in the second line which I find much more difficult then the LD_PRELOAD.

Indeed, I hadn’t realized that test data included such things.  All
right then!

Ludo’.

      reply	other threads:[~2017-06-19 21:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-15  7:29 Extra files in build container Gregor Giesen
2017-06-16  7:58 ` Ludovic Courtès
2017-06-17  6:58   ` Gregor Giesen
2017-06-19 11:26     ` Ludovic Courtès
2017-06-19 11:44       ` Gregor Giesen
2017-06-19 14:49         ` Ludovic Courtès
2017-06-19 16:48           ` Gregor Giesen
2017-06-19 21:21             ` Ludovic Courtès [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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87y3sn7jy8.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=giesen@zaehlwerk.net \
    --cc=help-guix@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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).