From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST: Cygwin 3.0.0-0.2
Date: Thu, 31 Jan 2019 18:15:00 -0000 [thread overview]
Message-ID: <38cd5117-74c8-3f01-453b-e73d54a21835@SystematicSw.ab.ca> (raw)
In-Reply-To: <548239182.20190130215655@yandex.ru>
On 2019-01-30 11:56, Andrey Repin wrote:
>> Re: "(*) It would really be nice not having to ask for these infos every time."
>> may want to append HKLM/SOFTWARE/Microsoft/Windows NT/CurrentVersion/UBR to
>> uname -s sysname to show the patch levels of installed builds, as there appears
>> to be substantial differences between editions and service models.
> Anything from persistent storage is easily falsified.
Should not even be modifiable if there is reg security on the subtree.
Not really a big concern as a target in anything I've seen.
Everything is easily falsified with root privs.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2019-01-31 18:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 14:06 Corinna Vinschen
2019-01-30 16:11 ` Brian Inglis
2019-01-30 17:31 ` Corinna Vinschen
2019-01-30 18:28 ` Richard Campbell
2019-01-30 18:47 ` Brian Inglis
2019-01-30 18:53 ` Corinna Vinschen
2019-01-30 19:01 ` Corinna Vinschen
2019-01-30 20:29 ` Corinna Vinschen
2019-02-17 18:20 ` Brian Inglis
2019-02-18 8:45 ` Corinna Vinschen
2019-01-30 19:05 ` Andrey Repin
2019-01-31 18:15 ` Brian Inglis [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=38cd5117-74c8-3f01-453b-e73d54a21835@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/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).