From: se iro <seiro22@mailfence.com>
To: rust-for-linux@vger.kernel.org
Subject: leaky info and kernel modules
Date: Wed, 7 Apr 2021 16:22:43 +0200 (CEST) [thread overview]
Message-ID: <1802230489.25122.1617805363569@ichabod.co-bxl> (raw)
saw post on reddit and github issues where rust compiler adds username and systems paths/info to **release** mode compile bins. also its pkg mgr cargo does the same with registry paths. otherwise its extra strings bloating output that not needed and strip command doesnt work. also not working is compiler opts described
does this impact chat of rust in linux since rust team seems to be ignoring the issue?
ref links (maybe more too):
https://www.reddit.com/r/rust/comments/mfax64/remove_username_from_binary_for_privacy/
https://github.com/rust-lang/rust/issues/40374
https://github.com/rust-lang/rust/issues/40552
https://github.com/rust-lang/rust/issues/75263
https://github.com/rust-lang/cargo/issues/5505
next reply other threads:[~2021-04-07 14:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 14:22 se iro [this message]
2021-04-07 16:50 ` leaky info and kernel modules Geoffrey Thomas
2021-04-07 21:50 ` Miguel Ojeda
2021-04-07 22:12 ` Miguel Ojeda
2021-04-08 2:38 ` se iro
2021-04-08 6:35 ` Miguel Ojeda
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=1802230489.25122.1617805363569@ichabod.co-bxl \
--to=seiro22@mailfence.com \
--cc=rust-for-linux@vger.kernel.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 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.