public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-announce@cygwin.com
Subject: TEST RELEASE: Cygwin 2.5.0-0.5
Date: Fri, 11 Mar 2016 22:03:00 -0000	[thread overview]
Message-ID: <20160311220135.GC3175@calimero.vinschen.de> (raw)

Hi Cygwin friends and users,


I released a new Cygwin TEST version 2.5.0-0.5.

Refresh with mostly bugfixes.

What's new:
-----------

- Full set of POSIX.1e ACL API functions now implemented.
  New APIs: acl_add_perm, acl_calc_mask, acl_clear_perms, acl_copy_entry,
  acl_copy_ext, acl_copy_int, acl_create_entry, acl_delete_def_file,
  acl_delete_entry, acl_delete_perm, acl_dup, acl_free, acl_from_text,
  acl_get_entry, acl_get_fd, acl_get_file, acl_get_permset, acl_get_qualifier,
  acl_get_tag_type, acl_init, acl_set_fd, acl_set_file, acl_set_permset,
  acl_set_qualifier, acl_set_tag_type, acl_size, acl_to_text, acl_valid.

- Most libacl extensions now implemented, too:
  New APIs: acl_check, acl_cmp, acl_entries, acl_equiv_mode, acl_error,
  acl_extended_fd, acl_extended_file, acl_extended_file_nofollow,
  acl_from_mode, acl_get_perm, acl_to_any_text.

- First implementation of pthread_barrier/pthread_barrierattr functions.
  New APIs: pthread_barrierattr_init, pthread_barrierattr_setpshared,
  pthread_barrierattr_getpshared, pthread_barrierattr_destroy,
  pthread_barrier_init, pthread_barrier_destroy, pthread_barrier_wait.

- New APIs: clog10, clog10f.


What changed:
-------------

- Including <sys/acl.h> now *only* includes the POSIX ACL API.  To include
  the old Solaris API, include <cygwin/acl.h>.

- In calls to chmod treat ACLs with extra ACEs *only* for Admins and
  SYSTEM like a trivial ACL.

- Bump POSIX option macros to POSIX.1-2008.

- Profiling data, specifically pc sampling, now covers all threads of a
  program and not just the main thread.  Environment variable GMON_OUT_PREFIX
  enables multiple gmon.out files to preserve profiling data after fork or
  from multiple program runs.


Bug Fixes
---------

- Fix potential hang when using LoadLibraryEx(LOAD_LIBRARY_SEARCH_SYSTEM32).
  Reported and tested via IRC.

- Fix a bug in ACL handling which might result in a spurious extra entry
  for the primary group.  Self-observed.

- printf(3): Handle multibyte decimal point in field size computation.
  Addresses: https://cygwin.com/ml/cygwin/2016-02/msg00014.html

- cygwin_conv_path: Always preserve trailing backslashes in conversion
  to POSIX paths.
  Addresses: https://cygwin.com/ml/cygwin/2016-01/msg00480.html

- Make buffered console characters visible to select().
  Addresses: https://cygwin.com/ml/cygwin/2014-12/msg00118.html

- Always report relocation problems, not only in debug DLL.
  Addresses: https://cygwin.com/ml/cygwin/2016-02/msg00147.html

- Don't spill network credentials of privileged user changing the user
  context via setuid method 1
  (https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd1) into
  user session


Have fun,
Corinna


-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

                 reply	other threads:[~2016-03-11 22:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160311220135.GC3175@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-announce@cygwin.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).