public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Doug Henderson <djndnbvg@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: Very dangerous hacking ? Surprising relationship between cygwin and Microsoft
Date: Mon, 11 May 2020 11:07:40 -0600	[thread overview]
Message-ID: <CAJ1FpuMqcaL8zWxmzFUC2rQ2_WUerfTrGsERRHEWjgkrOyj2VQ@mail.gmail.com> (raw)
In-Reply-To: <331531811.-1550186875.1589214301322.JavaMail.root@zimbra76-e14.priv.proxad.net>

On Mon, 11 May 2020 at 10:39, akiki <> wrote:
>
> Hi,
>
> On doing an habitual "cygcheck -rs", I was interrogated and ALARMED to see some register keys speaking cygwin :
> <snip>
> I have never see in cygcheck, such reference to cygwin with chrome, firefox , opera ...
> May be something is done to mask them.
>
I use Firefox Nightly and very rarely Chrome, and  I have no internet
related registry keys that refer to cygwin. These browsers may save
similar information, but it is not in the registry.

I suspect that the keys you see are related to using Internet Explorer
and/or Edge. This re-enforces my choice to use Firefox.

HTH
Doug

-- 
Doug Henderson, Calgary, Alberta, Canada - from gmail.com

  reply	other threads:[~2020-05-11 17:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <535856733.-1642430415.1587202868364.JavaMail.root@zimbra76-e14.priv.proxad.net>
2020-04-18 12:42 ` Bug with Windows 10 console akiki
2020-04-18 14:05   ` Thomas Wolff
2020-04-19  3:02     ` Kevin Schnitzius
2020-04-22 19:50   ` Can't use strace on curses application akiki
2020-04-22 19:59     ` Marco Atzeri
2020-05-11 16:25     ` Very dangerous hacking ? Surprising relationship between cygwin and Microsoft akiki
2020-05-11 17:07       ` Doug Henderson [this message]
2020-05-11 18:35       ` David Macek
2020-05-11 19:53         ` Brian Inglis

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=CAJ1FpuMqcaL8zWxmzFUC2rQ2_WUerfTrGsERRHEWjgkrOyj2VQ@mail.gmail.com \
    --to=djndnbvg@gmail.com \
    --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).