On Tue, Aug 22, 2023 at 4:52 PM Lavrentiev, Anton (NIH/NLM/NCBI) [C]
via Cygwin wrote:
> > FIFOs which don't make *any* sense
> > ... FWIW, a remote NFS fileystem.
>
> I got an impression that the OP is trying to deploy something (maybe the
> entire Cygwin) onto an
> NFS share. So the named
On 2023-08-22 08:12, Dom Woods - BGS via Cygwin wrote:
I scanned your application through Virus Total as per our company policy and
noticed that the installation process calls out to a suspicious Microsoft IP
13.107.4.50, this ip has been flagged by 8 vendors as malicious, I get varying
On 22/08/2023 17:55, ASSI via Cygwin wrote:
Ken Brown via Cygwin writes:
On 8/21/2023 11:02 AM, ASSI via Cygwin wrote:
(although in this case maybe i got spooked by the change
from 1.2.x to 1.3)
It looks like that's exactly what happened. The version check
compares the first 4 characters of
The following packages have been updated to the latest upstream release
(a patch rollup release):
mpfr-4.2.1-1
mingw64-i686-mpfr-4.2.1-1
mingw64-x86_64-mpfr-4.2.1-1
--
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin-announce mailing list,
The following packages have been updated to the latest upstream release
(a patch rollup release):
mpfr-4.2.1-1
mingw64-i686-mpfr-4.2.1-1
mingw64-x86_64-mpfr-4.2.1-1
--
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin-announce mailing list,
Hello,
I hope I'm using the right list!
I have an X application that uses the cygwin X Server XWin. It works fine on
Windows:
* When I launch the application, XWin launches, then the X app raises it's
window.
When I install this application (and cygwin and XWin) on a virtual machine,
On Tue, Aug 22, 2023 at 9:00 AM Thomas Schweikle wrote:
It is the address of one of the distribution servers. Since this is not
> "one server", but a cluster of servers, your "suspicious" server shows
> only one thing: those "suspicious" flags are suspicious by themselves:
>
> this particular
Ken Brown via Cygwin writes:
> On 8/21/2023 11:02 AM, ASSI via Cygwin wrote:
>> (although in this case maybe i got spooked by the change
>> from 1.2.x to 1.3)
>
> It looks like that's exactly what happened. The version check
> compares the first 4 characters of the version string.
Almost exactly
It is the address of one of the distribution servers. Since this is not
"one server", but a cluster of servers, your "suspicious" server shows
only one thing: those "suspicious" flags are suspicious by themselves:
this particular server ist down since some time and only reports back a
broken
> FIFOs which don't make *any* sense
> ... FWIW, a remote NFS fileystem.
I got an impression that the OP is trying to deploy something (maybe the entire
Cygwin) onto an NFS share. So the named FIFO "file" is also created in there.
It's pointless to assume that the FIFO can be used as a
Everything now works as expected after the texlive update, thanks!
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Hi Cygwin,
I scanned your application through Virus Total as per our company policy and
noticed that the installation process calls out to a suspicious Microsoft IP
13.107.4.50, this ip has been flagged by 8 vendors as malicious, I get varying
responses for what it is used for (an os updater
12 matches
Mail list logo
