1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com
Hi there, I just got that error message, asking me to report it here. 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com Not sure if it's interesting? Kind regards, James -- 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
Re: 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com
> https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings I've only been on this list a few months, but I've seen these "find_fast_cwd" questions about twice a month so far. Might I suggest that replacing the "Please report this problem to the public mailing list cygwin@cygwin.com" message in 'bash' with something like: "Please visit https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings for help with this issue" This removes the need for an autoresponder and is more helpful at the same time. Users might be reluctant to join the mailing list just to report this and therefore they may waste their time needlessly trying to track down the problem. -- 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
Re: 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com
On 4/2/2022 3:37 AM, Backwoods BC wrote: https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings I've only been on this list a few months, but I've seen these "find_fast_cwd" questions about twice a month so far. Might I suggest that replacing the "Please report this problem to the public mailing list cygwin@cygwin.com" message in 'bash' with something like: "Please visit https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings for help with this issue" This removes the need for an autoresponder and is more helpful at the same time. Users might be reluctant to join the mailing list just to report this and therefore they may waste their time needlessly trying to track down the problem. The message is baked into ancient versions of Cygwin. I believe the page the auto-responder points them to indicates the fact that their version is old and should be updated. This often happens because someone bundled Cygwin with something else and is not updating the Cygwin version. Modern versions no longer generate the message. In sum, the auto-responder is the best thing we can do about it. At least we don't have to have a human respond. Best wishes - Eliot Moss -- 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
Re: 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com
Never mind I'd say. I got the error when launching C:\Appz\Cygwin\Cygwin.bat Which is just @echo off C: chdir C:\Appz\Cygwin\bin bash --login -i If however I run C:\cygwin64\bin\mintty.exe It works fine. On Sat, Apr 2, 2022 at 8:28 AM James wrote: > Hi there, > > > I just got that error message, asking me to report it here. > > 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute > FAST_CWD pointer. Please report this problem to the public mailing list > cygwin@cygwin.com > > Not sure if it's interesting? > > > Kind regards, > James > -- 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
Re: 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com
>Hi there, >I just got that error message, asking me to report it here. > 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD >pointer. Please report this problem to the public mailing list >cygwin@cygwin.com >Not sure if it's interesting? >Kind regards, >James https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings -- 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
Re: 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com
Voila, thanks! Have a nice weekend ya'all On Sat, Apr 2, 2022 at 8:31 AM wrote: > >Hi there, > > > >I just got that error message, asking me to report it here. > > > 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute > FAST_CWD > >pointer. Please report this problem to the public mailing list > >cygwin@cygwin.com > > >Not sure if it's interesting? > > > >Kind regards, > >James > > > https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings > -- 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
[ANNOUNCEMENT] Updated: libgcrypt20 libgcrypt-devel 1.10.1
The following packages have been upgraded in the Cygwin distribution: * libgcrypt20 1.10.1 * libgcrypt-devel 1.10.1 Libgcrypt is a general purpose cryptography library based on the code used in GnuPG. For more information please see the project home page: https://gnupg.org/software/libgcrypt/ As there are multiple changes each release please see below or read /usr/share/doc/libgcrypt/NEWS after installation; for complete details of changes please see the release info links below, or read /usr/share/doc/libgcrypt/ChangeLog after installation. Noteworthy changes in version 1.10.1 (2022-03-28) * Bug fixes: - Fix minor memory leaks in FIPS mode. - Build fixes for MUSL libc. * Other: - More portable integrity check in FIPS mode. - Add X9.62 OIDs to sha256 and sha512 modules. Release-info: https://dev.gnupg.org/T5810 Noteworthy changes in version 1.10.0 (2022-02-01) * New and extended interfaces: - New control codes to check for FIPS 140-3 approved algorithms. - New control code to switch into non-FIPS mode. - New cipher modes SIV and GCM-SIV as specified by RFC-5297. - Extended cipher mode AESWRAP with padding as specified by RFC-5649. - New set of KDF functions. - New KDF modes Argon2 and Balloon. - New functions for combining hashing and signing/verification. * Performance: - Improved support for PowerPC architectures. - Improved ECC performance on zSeries/s390x by using accelerated scalar multiplication. - Many more assembler performance improvements for several architectures. * Bug fixes: - Fix Elgamal encryption for other implementations. - Fix alignment problem on macOS. - Check the input length of the point in ECDH. - Fix an abort in gcry_pk_get_param for "Curve25519". * Other features: - The control code GCRYCTL_SET_ENFORCED_FIPS_FLAG is ignored because it is useless with the FIPS 140-3 related changes. - Update of the jitter entropy RNG code. - Simplification of the entropy gatherer when using the getentropy system call. * Interface changes relative to the 1.10.0 release: GCRYCTL_SET_DECRYPTION_TAGNEW control code. GCRYCTL_FIPS_SERVICE_INDICATOR_CIPHER NEW control code. GCRYCTL_FIPS_SERVICE_INDICATOR_KDFNEW control code. GCRYCTL_NO_FIPS_MODE = 83 NEW control code. GCRY_CIPHER_MODE_SIV NEW mode. GCRY_CIPHER_MODE_GCM_SIV NEW mode. GCRY_CIPHER_EXTENDED NEW flag. GCRY_SIV_BLOCK_LENNEW macro. gcry_cipher_set_decryption_tagNEW macro. GCRY_KDF_ARGON2 NEW constant. GCRY_KDF_BALLOON NEW constant. GCRY_KDF_ARGON2D NEW constant. GCRY_KDF_ARGON2I NEW constant. GCRY_KDF_ARGON2ID NEW constant. gcry_kdf_hd_t NEW type. gcry_kdf_job_fn_t NEW type. gcry_kdf_dispatch_job_fn_tNEW type. gcry_kdf_wait_all_jobs_fn_t NEW type. struct gcry_kdf_thread_opsNEW struct. gcry_kdf_open NEW function. gcry_kdf_compute NEW function. gcry_kdf_finalNEW function. gcry_kdf_closeNEW function. gcry_pk_hash_sign NEW function. gcry_pk_hash_verify NEW function. gcry_pk_random_override_new NEW function. Release-info: https://dev.gnupg.org/T5691 Noteworthy changes in version 1.9.3 (2021-04-19) * Bug fixes: - Fix build problems on i386 using gcc-4.7. - Fix checksum calculation in OCB decryption for AES on s390. - Fix a regression in gcry_mpi_ec_add related to certain usages of curve 25519. - Fix a symbol not found problem on Apple M1. - Fix for Apple iOS getentropy peculiarity. - Make keygrip computation work for compressed points. * Performance: - Add x86_64 VAES/AVX2 accelerated implementation of Camellia. - Add x86_64 VAES/AVX2 accelerated implementation of AES. - Add VPMSUMD acceleration for GCM mode on PPC. * Internal changes. - Harden MPI conditional code against EM leakage. - Harden Elgamal by introducing exponent blinding. - Fix memory leaks in the error code paths of EdDSA. Release-info: https://dev.gnupg.org/T5305 Noteworthy changes in version 1.9.2 (2021-02-17) * Bug fixes: - Fix build problem for macOS in the random code. - Fix building with --disable-asm on x86. - Check public key for ECDSA verify operation. - Make sure gcry_get_config (NULL) returns a nul-terminated string. - Fix a memory leak in the ECDH code. - Fix a reading beyond end of input buffer in SHA2-avx2. * Other features: - New test driver to allow for standalone regression tests. Release-info: https://dev.gnupg.org/T5276 Noteworthy changes in version 1.9.1 (2021-01-29) * Bug fixes: - Fix exploitable bug in hash functions introduced with 1.9.0.
Re: 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com
On 2022-04-02 01:37, Backwoods BC wrote: https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings I've only been on this list a few months, but I've seen these "find_fast_cwd" questions about twice a month so far. Might I suggest that replacing the "Please report this problem to the public mailing list cygwin@cygwin.com" message in 'bash' with something like: "Please visit https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings for help with this issue" This has been done in recent releases for some years, but ancient legacy releases without changes are still distributed by/with some products or projects, with no effort to upgrade what they distribute, mention of how to upgrade, responsibility for or to their users. Please read the linked FAQ entry for that explanation. Ancient legacy repos such as SourceForge and GoogleCode are fertile sources of such projects as are products from (some not so) defunct embedded systems tool developers. This removes the need for an autoresponder and is more helpful at the same time. Users might be reluctant to join the mailing list just to report this and therefore they may waste their time needlessly trying to track down the problem. That was why the autoresponder was added - reply directly to those folks and point them to a greatly expanded FAQ entry with relevant links explaining the problem and solution, and suggesting other actions. I don't remember anyone clicking the email link at the end to let us know what a product or project was or where it came from, so someone on the list could follow up. And folks wonder why there are software supply chain security issues! -- 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. [Data in binary units and prefixes, physical quantities in SI.] -- 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
Weird results from PyIter_Check
PyIter_Check appears to be the C-level equivalent of isinstance(..., collections.abc.Iterator), testing whether the python next() or the C PyIter_Next will succeed. However, PyIter_Check disagrees with collections.abc.Iterator and next about whether a given object is an iterator. $ cat test_iterator.pyx from cpython.iterator cimport PyIter_Check def is_iterator(obj: object) -> bool: """Check whether obj is an iterator. Should agree with isinstance(obj, collections.abc.Iterator). Parameters -- obj : object Returns --- bool """ return PyIter_Check(obj) $ cythonize --build --inplace test_iterator.pyx running build_ext $ python Python 3.9.10 (main, Jan 20 2022, 21:37:52) [GCC 11.2.0] on cygwin Type "help", "copyright", "credits" or "license" for more information. >>> import test_iterator, os, fractions, collections.abc >>> test_iterator.is_iterator(os.environ) True >>> isinstance(os.environ, collections.abc.Iterator) False >>> next(os.environ) Traceback (most recent call last): File "", line 1, in TypeError: '_Environ' object is not an iterator >>> test_iterator.is_iterator(fractions.Fraction(0, 1)) True >>> isinstance(fractions.Fraction(0, 1), collections.abc.Iterator) False >>> next(fractions.Fraction(0, 1)) Traceback (most recent call last): File "", line 1, in TypeError: 'Fraction' object is not an iterator On Linux, the test function using PyIter_Check agrees with collections.abc.Iterator and next. The test case that led me to this behaviour works the same in Windows as on Linux. Is this expected behavior? -- 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
Re: [ITA] libgcrypt
On 02.04.2022 02:41, Brian Inglis wrote: I'd like to offer to adopt maintenance of libgcrypt. Thanks all yours
Updated: libgcrypt20 libgcrypt-devel 1.10.1
The following packages have been upgraded in the Cygwin distribution: * libgcrypt20 1.10.1 * libgcrypt-devel 1.10.1 Libgcrypt is a general purpose cryptography library based on the code used in GnuPG. For more information please see the project home page: https://gnupg.org/software/libgcrypt/ As there are multiple changes each release please see below or read /usr/share/doc/libgcrypt/NEWS after installation; for complete details of changes please see the release info links below, or read /usr/share/doc/libgcrypt/ChangeLog after installation. Noteworthy changes in version 1.10.1 (2022-03-28) * Bug fixes: - Fix minor memory leaks in FIPS mode. - Build fixes for MUSL libc. * Other: - More portable integrity check in FIPS mode. - Add X9.62 OIDs to sha256 and sha512 modules. Release-info: https://dev.gnupg.org/T5810 Noteworthy changes in version 1.10.0 (2022-02-01) * New and extended interfaces: - New control codes to check for FIPS 140-3 approved algorithms. - New control code to switch into non-FIPS mode. - New cipher modes SIV and GCM-SIV as specified by RFC-5297. - Extended cipher mode AESWRAP with padding as specified by RFC-5649. - New set of KDF functions. - New KDF modes Argon2 and Balloon. - New functions for combining hashing and signing/verification. * Performance: - Improved support for PowerPC architectures. - Improved ECC performance on zSeries/s390x by using accelerated scalar multiplication. - Many more assembler performance improvements for several architectures. * Bug fixes: - Fix Elgamal encryption for other implementations. - Fix alignment problem on macOS. - Check the input length of the point in ECDH. - Fix an abort in gcry_pk_get_param for "Curve25519". * Other features: - The control code GCRYCTL_SET_ENFORCED_FIPS_FLAG is ignored because it is useless with the FIPS 140-3 related changes. - Update of the jitter entropy RNG code. - Simplification of the entropy gatherer when using the getentropy system call. * Interface changes relative to the 1.10.0 release: GCRYCTL_SET_DECRYPTION_TAGNEW control code. GCRYCTL_FIPS_SERVICE_INDICATOR_CIPHER NEW control code. GCRYCTL_FIPS_SERVICE_INDICATOR_KDFNEW control code. GCRYCTL_NO_FIPS_MODE = 83 NEW control code. GCRY_CIPHER_MODE_SIV NEW mode. GCRY_CIPHER_MODE_GCM_SIV NEW mode. GCRY_CIPHER_EXTENDED NEW flag. GCRY_SIV_BLOCK_LENNEW macro. gcry_cipher_set_decryption_tagNEW macro. GCRY_KDF_ARGON2 NEW constant. GCRY_KDF_BALLOON NEW constant. GCRY_KDF_ARGON2D NEW constant. GCRY_KDF_ARGON2I NEW constant. GCRY_KDF_ARGON2ID NEW constant. gcry_kdf_hd_t NEW type. gcry_kdf_job_fn_t NEW type. gcry_kdf_dispatch_job_fn_tNEW type. gcry_kdf_wait_all_jobs_fn_t NEW type. struct gcry_kdf_thread_opsNEW struct. gcry_kdf_open NEW function. gcry_kdf_compute NEW function. gcry_kdf_finalNEW function. gcry_kdf_closeNEW function. gcry_pk_hash_sign NEW function. gcry_pk_hash_verify NEW function. gcry_pk_random_override_new NEW function. Release-info: https://dev.gnupg.org/T5691 Noteworthy changes in version 1.9.3 (2021-04-19) * Bug fixes: - Fix build problems on i386 using gcc-4.7. - Fix checksum calculation in OCB decryption for AES on s390. - Fix a regression in gcry_mpi_ec_add related to certain usages of curve 25519. - Fix a symbol not found problem on Apple M1. - Fix for Apple iOS getentropy peculiarity. - Make keygrip computation work for compressed points. * Performance: - Add x86_64 VAES/AVX2 accelerated implementation of Camellia. - Add x86_64 VAES/AVX2 accelerated implementation of AES. - Add VPMSUMD acceleration for GCM mode on PPC. * Internal changes. - Harden MPI conditional code against EM leakage. - Harden Elgamal by introducing exponent blinding. - Fix memory leaks in the error code paths of EdDSA. Release-info: https://dev.gnupg.org/T5305 Noteworthy changes in version 1.9.2 (2021-02-17) * Bug fixes: - Fix build problem for macOS in the random code. - Fix building with --disable-asm on x86. - Check public key for ECDSA verify operation. - Make sure gcry_get_config (NULL) returns a nul-terminated string. - Fix a memory leak in the ECDH code. - Fix a reading beyond end of input buffer in SHA2-avx2. * Other features: - New test driver to allow for standalone regression tests. Release-info: https://dev.gnupg.org/T5276 Noteworthy changes in version 1.9.1 (2021-01-29) * Bug fixes: - Fix exploitable bug in hash functions introduced with 1.9.0.
