Still testing needed: New passwd/group AD/SAM integration

Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1.1: Type: text/plain, Size: 3272 bytes --]

Hi folks,


The latest snapshot, 2014-04-10, is a snapshot from CVS HEAD again.
It contains the latest crazy ideas in terms of the user and group
account creation without requiring the /etc/passwd and /etc/group
files.

Not a lot has changed since we made a break to test for 1.7.29,
but there's one important change I'd like to point out:

* cygserver now provides system-wide passwd/group entry caching.

  All processes started *after* cygserver will try to fetch passwd
  and group entries from cygserver.  While this is probably a bit
  slow at the start, the longer cygserver runs, the more information
  is present and later started processes will get the information
  with all due speed.

I attached the latest incarnation of the documentation for this
major change to this mail.

However!

After sweating about some of the details I created in my scrubby mind
back in January/February, I'm not so sure anymore if some if was really
such a bright idea.

Especially two problems cropped up in discussions with local Cygwin
users:


* Support for Cygwin user names different from the Windows username.

  This is a really fat problem.  Assuming you have a Windows user called
  "yoghurt".  Using one of the methods outlined in the chapter "Cygwin
  user names, home dirs, login shells" in the attached document, you
  defined the Cygwin account name for this account as "kefir".

  If so, getpwnam() will be broken for this account.  The problem is
  this:  When your process calls getpwnam ("kefir"), the code has to ask
  Windows for the account name.  This leads to a call LookupAccountName
  ("kefir", ...).  But, obviously there is no Windows account "kefir",
  there's only "yoghurt".

  Fixing this problem leads to terrible performance.  Obviously Cygwin
  doesn't know if "yoghurt" is a local or an AD account.  Or, FWIW, an
  account in some trusted domain.  Finding "kefir" in the SAM of the
  local machine requires to enumerate *all* accounts, until the account
  with
  
    <cygwin name="kefir" .../>

  is found.  Even worse in AD.  An ldap query is required which searches
  for an account with uid="kefir".  The uid attribute is not indexed by
  default.  Same for all trusted domains.

  This would also have to be done for all non-existing user accounts.
  And thus every time you just mistyped a user name.

  Therefore I think it would be better to remove this functionality.
  If you really think you have to use a username different from the
  Windows username, you should probably use a tiny /etc/passwd file
  with just this entry.  The new mkpasswd will create a default entry
  for you with just needs minor tweaking.


* db_separator in /etc/nsswitch.conf

  Is it really such a good idea to have a configurable separator
  char in user and group names?  Is it important that it is
  configurable?  Is '+' a good choice for the default separator?
  Wouldn't the backslash a better and, perhaps, only choice?


Thanks for your testing and thanks for your input in terms of the
above two problems.


Corinna

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

[-- Attachment #1.2: pwdgrp-doc --]
[-- Type: text/plain, Size: 32247 bytes --]

=======
History
=======

For as long as Cygwin has existed, it has stored user and group
information in /etc/passwd and /etc/group files.  Under the assumption
that these files would never be too large, the first process in a
process tree, as well as every execing process within the tree would
parse them into structures in memory.  Thus every Cygwin process would
contain an expanded copy of the full information from /etc/passwd and
/etc/group.

This approach has a few downsides.  One of them is that the idea to have
always small files is flawed.  Another one is that reading the entire
file is most of the time entirely useless, since most processes only
need information on their own user and the primary group.  Last but not
least, the passwd and group files have to be maintained separately from
the already existing Windows user databases, the local SAM and Active
Directory.

On the other hand, we have to have a mapping between Windows SIDs and
POSIX uid/gid values (see [1]), so we rely on some mechanism to convert
SIDs to uid/gid values and vice versa.

Microsoft "Services for UNIX" (SFU) (which are unfortunately deprecated
since Windows 8/Server 2012) never used passwd/group files.  Rather, SFU
used a fixed, computational mapping between SIDs and POSIX uid/gid.  It
allows to generate uid/gid values from SIDs and vice versa.  The
mechanism is documented, albeit in a confusing way and spread over
multiple MSDN articles.  The Cygwin approach clones the mapping, with
just tiny differences for backward compatibility.


=================
How does it work?
=================

The following description assumes you're comfortable with the concept of
Windows SIDs and RIDs.  For a brief introduction, please read [1].

Cygwin's new mapping between SIDs and uid/gid values works in two ways.

- Read /etc/passwd and /etc/group files, like before, mainly for
  backward compatibility.

- If no files are present, or if an entry is missing in the files, ask
  Windows.

At least, that's the default behaviour now.  It will be configurable
using a file /etc/nsswitch.conf, which is discussed in a later section.
Let's explore the default for now.

If files are present, they will be scanned on demand as soon as a
mapping from SIDs to uid/gid or user names is required.  The new
mechanism will never read the entire file into memory, but only scan for
the requested entry and cache this one in memory[2].

If no entry is found, or no passwd or group file was present, Cygwin
will ask the OS.

Note:  If the first process in a Cygwin process tree determines that no
       /etc/passwd or /etc/group file is present, no other process in
       the entire process tree will try to read the files later on.
       This is done for self-preservation.  It's rather bad if the uid
       or gid of a user changes during the lifetime of a process tree.

       For the same reason, if you delete the /etc/passwd or /etc/group
       file, this will be ignored.  The passwd and group records read
       from the files will persist in memory until either a new
       /etc/passwd or /etc/group files is created, or you exit all
       processes in the current process tree.

       See the note in the section on /etc/nsswitch.conf for some
       comprehensive examples.

So if we've drawn a blank reading the files, we're going to ask the OS.
First thing, we ask the local machine for the SID or the user name.  The
OS functions LookupAccountSid and LookupAccountName[3] are pretty
intelligent.  They have all the stuff built in to ask for any account of
the local machine, the Active Directory domain of the machine, the
Global Catalog of the forest of the domain, as well as any trusted
domain of our forest for the information.  One OS call and we're
practically done...

Except, the calls only return the mapping between SID, account name and
the account's domain.  We don't have a mapping to POSIX uid/gid and
we're missing information on the user's home dir and login shell.

Let's discuss the SID<=>uid/gid mapping first.  Here's how it works.

- Well-known SIDs in the NT_AUTHORITY domain of the S-1-5-RID type, or
  aliases of the S-1-5-32-RID type are mapped to the uid/gid value
  RID[4].  For an overview of well-known SIDs, see [5].

  Examples:

    "SYSTEM" S-1-5-18     <=> uid/gid: 18
    "Users"  S-1-5-32-545 <=> uid/gid: 545

- Other well-known SIDs in the NT_AUTHORITY domain (S-1-5-X-RID):

    S-1-5-X-RID           <=> uid/gid: 0x1000 * X + RID

  Example:

    "NTLM Authentication"
    S-1-5-64-10           <=> uid/gid: 0x4000A == 262154

- Other well-known SIDs:

    S-1-X-Y               <=> uid/gid: 0x10000 + 0x100 * X + Y

  Example:

    "LOCAL" S-1-2-0       <=> uid/gid: 0x10200 == 66048
    "Creator Group"
    S-1-3-1               <=> uid/gid: 0x10301 == 66305

- Logon SIDs:

    The own LogonSid is converted to the fixed uid 0xfff == 4095 and
    named "CurrentSession".  Any other LogonSid is converted to the
    fixed uid 0xffe == 4094 and named "OtherSession".

- Mandatory Labels:

    S-1-16-RID            <=> uid/gid: 0x60000 + RID

  Example:

    "Medium Mandatory Level"
    S-1-16-8192           <=> uid/gid: 0x62000 == 401408

- Accounts from the local machine's user DB (SAM):

    S-1-5-21-X-Y-Z-RID    <=> 0x30000 + RID

  Example:

    "Administrator"
    S-1-5-X-Y-Z-500       <=> uid/gid: 0x301f4 == 197108

- Accounts from the machine's primary domain:
  
    S-1-5-21-X-Y-Z-RID    <=> 0x100000 + RID

  Example:

    "Domain Users"
    S-1-5-X-Y-Z-513       <=> 0x100201 == 1049089

- Accounts from a trusted domain of the machine's primary domain:

    S-1-5-21-X-Y-Z-RID    <=> trustPosixOffset(domain) + RID

  "trustPosixOffset"?  This needs a bit of explanation.  This value
  exists in Windows domains already since before Active Directory days.
  What happens is this.  If you create a domain trust between two
  domains, a trustedDomain entry will be added to both databases.  It
  describes how *this* domain trusts the *other* domain.  One attribute
  of a trust is a 32 bit value called "trustPosixOffset"  For each new
  trust, trustPosixOffset will get some automatic value.  In recent AD
  domain implementations, the first trusted domain will get
  trustPosixOffset set to 0x80000000.  Following domains will get lower
  values.  Unfortunately the domain admins are allowed to set the
  trustPosixOffset value for each trusted domain to some arbitrary 32
  bit value, no matter what the other trustPosixOffsets are seet to,
  thus allowing any kind of collisions between the trustPosixOffsets of
  domains.  That's not exactly helpful, but as the user of this value,
  we have to *trust* the domain admins to set trustPosixOffset to
  sensible values, or to keep it at the system chosen values.

  So, for the first (or only) trusted domain of your domain, the
  automatic offset is 0x80000000.  An example for a user of that trusted
  domain is:

    S-1-5-X-Y-Z-1234         <=> uid/gid 0x800004d2 == 2147484882

  There's only one problem with this approach.  Assuming you're running
  in the context of a local SAM user on a domain member machine.  Local
  users don't have the right to fetch this kind of domain information
  from the DC, they'll get permission denied.  In this case Cygwin will
  fake a, mostly, sensible trustPosixOffset value for this session.

- Local accounts from another machine in the network:

  There's no SID<=>uid/gid mapping implemented for this case.  The
  problem is, there's no way to generate a bijective mapping.  There's
  no central place which keeps an analogue value of the
  trustPosixOffset, and there's the additional problem that the
  LookupAccountSid and LookupAccountName functions cannnot resolve the
  SIDs, unless they know the name of the machine this SID comes from.
  And even then it will probably suffer a "Permission denied" when
  trying to ask the machine for its local account.

  SFU just prints the account RID in this case, Cygwin maps the account
  to the fake accounts "Unknown+User"/"Unknown+Group" with uid/gid -1.

Now we have a semi-bijective mapping between SIDs and POSIX uid/gid
values, but, given that we have potentially users and groups in
different domains having the same name, how do we uniquely differ
between them by name?  Well, we can do that by making their names unique
in a per-machine way.  Dependent on the domain membership of the
account, and dependent of the machine being a domain member or not, the
user and group names will be generated using a domain prefix and a
separator character between domain and account name.  The default
separator character is the plus sign, '+', as in SFU.

- Well-known SIDs will have the separator character prepended:

    "+SYSTEM", "+LOCAL", "+Medium Mandatory Level", ...

- If the machine is no domain member machine, only local accounts can be
  resolved into names, so for ease of use, just the account names are
  used as Cygwin user/group names:

    "corinna", "bigfoot", "None", ...

- If the machine is a domain member machine, all accounts from the
  primary domain of the machine are mapped to Cygwin names without
  domain prefix:

    "corinna", "bigfoot", "Domain Users", ...

  while accounts from other domains are prepended by their domain:

    "DOMAIN1+corinna", "DOMAIN2+bigfoot", "DOMAIN3+Domain Users", ...

- Local machine accounts of a domain member machine get a Cygwin user
  name the same way as accounts from another domain:  The local machine
  name gets prepended:

    "MYMACHINE+corinna", "MYMACHINE+bigfoot", "MYMACHINE+None", ...

- If LookupAccountSid fails, Cygwin checks the accounts against the
  known trusted domains.  If the account is from one of the trusted
  domains, an artificial account name is created.  It consists of the
  domain name, and a special name created from the account RID:

    "MY_DOM+User(1234)", "MY_DOM+Group(5678)"

  Otherwise we know nothing about this SID, so it will be mapped to the
  fake accounts "Unknown+User"/"Unknown+Group" with uid/gid -1.


=======
Caching
=======

The information fetched from file or the Windows account database is cached
by the process.  The cached information is inherited by child processes.

WHile usually working fine, this has some drawbacks.  Consider a shell
calling `id'.  `id' fetches all group information from the current token
and caches them.  Unfortunately `id' doesn't start any child processes,
so the information is lost as soon as `id' exits.

But there's another caching mechanism available.  If cygserver is
running it will provide passwd and group entry caching for all processes
in a Cygwin process tree, which first process has been started after
cygserver.  So, if you start a Cygwin Terminal and cygserver is
running at the time, mintty, the shell, and all child processes will
use cygserver caching.  If you start a Cygwin Terminal and cygserver is
not running a the time, none of the processes started inside this
terminal window will use cygserver caching.

The advantage of cygserver caching is that it's system-wide and, as long
as cygserver is running, unforgetful.  Every Cygwin process on the system
will have the cygserver cache at its service.  Additionally, all information
requested from cygserver once, will be cached inside the process itself
and, again, propagated to child processes.


==========================================
Cygwin user names, home dirs, login shells
==========================================

Obviously, if you don't maintain passwd and group files, you need to
have a way to maintain the other fields of a passwd entry as well.
Three things come to mind:

- You want to use a Cygwin user name different from your Windows
  user name.

- You want a home dir different from the default /home/$USER.

- You want to specify a different login shell than /bin/bash.

How this is done depends on your account being a domain account or a
local account.  Let's start with the default.  Assuming your Windows
account name is "bigfoot" and your domain is "MY_DOM".  Your default
passwd entry in absence of anything I'll describe below looks like this:

  bigfoot:*:<uid>:<gid>:U-MY_DOM\bigfoot,S-1-5-....:/home/bigfoot:/bin/bash

or, if your account is from a different domain than the primary domain of
the machine:

  MY_DOM+bigfoot:*:<uid>:<gid>:U-MY_DOM\bigfoot,S-1-5-....:/home/bigfoot:/bin/bash

Yes, the default homedir is still /home/bigfoot.

If your account is a domain account:

  Either create an /etc/passwd and/or /etc/group file with entries for
  your account and use that, just as before.

  Or, Cygwin will utilize the posixAccount/posixGroup attributes per RFC
  2307[6].  These attributes are by default available in Active Directory
  since Windows Server 2003 R2.  They are "not set", unless utilized by
  the (deprecated since Server 2012 R2) Active Directory "Server for
  NIS" feature.  The user attributes utilized by Cygwin are:

    uid                If set, will be used as Cygwin user name.
    uidNumber          See next section.
    gecos              Content will be added to the pw_gecos field.
    unixHomeDirectory  If set, will be used as Cygwin home directory.
    loginShell         If set, will be used as Cygwin login shell.

  The group attributes utilized by Cygwin are:

    gidNumber          See next section.

  Apart from power shell scripting or inventing new CLI tools, these
  attributes can be changed using the "Attribute Editor" tab in the user
  properties dialog of the "Active Directory Users and Computers"
  MMC snap-in.  Alternatively, if the "Server for NIS" administration
  feature has been installed, there will be a "UNIX Attributes" tab which
  contains the required fields, except for the gecos field, which isn't
  really important anyway.  Last resort is "ADSI Edit".

  The primary group of a user is always the Windows primary group set in
  Active Directory and can't be changed.

If your machine is not a domain member machine or your account is a
local account for some reason:

  Either create an /etc/passwd and/or /etc/group file with entries for
  your account and use that, just as before.

  Or enter the information into the "Comment" field of your local user
  entry.  In the "Local Users and Groups" MMC snap-in it's called
  "Description".

  You can utilze this field even if you're running a "home edition" of
  Windows, using the command line.  The "net user" command allows to set
  all values in the SAM, even if the GUI is crippled.

  A Cygwin SAM comment entry looks like this:

    <cygwin key="value" key="value" [...] />

  The supported keys are

    name="value"      Sets the Cygwin user name to value.

    home="value"      Sets the Cygwin home dir to value.

    shell="value"     Sets the Cygwin login shell to value.

    group="value"     Sets the Cygwin primary group of the account
                      to value, provided that the user *is* already
                      a member of that group.  This allows to
                      override the default "None" primary group for
                      local accounts.
		      One nice idea here is, for instance group="Users".
		      This is the *Windows* name of the group, not the
		      Cygwin name, assuming they differ.

    unix="value"      Sets the NFS/Samba uid of the user to the decimal
                      value.  See the next chapter.

  The <cygwin .../> string can start at any point in the comment, but
  you have to follow the rules:

  - It starts with "<cygwin " and ends with "/>".
  - The "cygwin" string and the key names have to be lowercase.
  - No spaces between key and "value", just the equal sign.
  - The value must be placed within double quotes and it must not
    contain a double quote itself.  The double quotes are required
    for the decimal values as well!

  CMD example:

    net user corinna /comment:"<cygwin home=\"/home/foo\"/>"

  Bash example (use single quotes):

    net user corinna /comment:'<cygwin home="/home/foo"/>'

  For changing group comments, use the `net localgroup' command.  The
  supported key/value pair for groups are

    name="value"      Sets the Cygwin group name to value.

    unix="value"      Sets the NFS/Samba gid of the group to the
                      decimal value.  See the next chapter.


===================
NFS account mapping
===================

Microsoft's NFS client does not map the uid/gid values on the NFS shares
to SIDs.  There's no such thing as a (fake) security descriptor returned
to the application.  Rather, via an undocumented API an applications can
fetch RFC 1813 compatible NFSv3 stat information from the share[7].
This is what Cygwin is using to show stat information for files on NFS
shares.

The problem is, while all other information in this stat record, like
timestamps, file size etc., can be used by Cygwin, Cygwin had no way to
map the values of the st_uid and st_gid members to a Windows SID for a
long time.  So it just faked the file owner info and claimed that it's
you.

However, SFU has, over time, developed multiple methods to map UNIX
uid/gid values on NFS shares to Windows SIDs.  You'll find the full
documentation of the mapping methods in [8].

Cygwin now utilizes the RFC 2307 mapping for this purpose.  This is most
of the time provided by an AD domain, but it could also be a standalone
LDAP mapping server.  Per RFC 2307, the uid is in the attribute
uidNumber.  For groups, the gid is in the gidNumber attribute.

When Cygwin stat's files on an NFS share, it asks the mapping server via
LDAP in two different ways, depending on the role of the mapping server.

- If the server is an AD domain controller, it asks for an account with
  uidNumber attribute == st_uid field of the stat record returned by
  NFS.  If an account matches, AD returns the Windows SID, so we have an
  immediate mapping from UNIX uid to a Windows SID, if the user account
  has a valid uidNumber attribute.  For groups, the method is the same,
  just that Cygwin asks for a group with gidNumber attribute == st_gid
  field of the stat record.

- If the server is a standalone LDAP mapping server Cygwin asks for the
  same uidNumber/gidNumber attributes, but it can't expect that the LDAP
  server knows anything about Windows SIDs.  Rather, the mapping server
  returns the account name.  Cygwin then asks the DC for an account with
  this name, and if that succeeds, we have a mapping between UNIX
  uid/gid and Windows SIDs.

The mapping will be cached for the lifetime of the process, and inherited
by child processes.


=====================
Samba account mapping
=====================

A fully set up Samba with domain integration is running winbindd to
map Window SIDs to artificially created UNIX uids and gids, and this
mapping is transparent within the domain, so Cygwin doesn't have to do
anything special.

However, setting up winbindd isn't for everybody, and it fails to map
Windows accounts to already existing UNIX users or groups.  In contrast
to NFS, Samba returns security descriptors, but unmapped UNIX accounts
get special SIDs:

- A UNIX user account with uid X is mapped to the Windows SID S-1-22-1-X.

- A UNIX group account with gid X is mapped to SID S-1-22-2-X.

As you can see, even though we have SIDs, they just reflect the actual
uid/gid values on the UNIX box in the RID value.  It's only marginally
different from the NFS method, so why not just use the same method as
for NFS?

That's what Cygwin will do.  If it encounters a S-1-22-x-y SID, it
will perform the same RFC 2307 mapping as for NFS shares.

For home users without any Windows domain or LDAP server per RFC 2307,
but with a Linux machine running Samba, just add this information to
your SAM account.  Assuming the uid of your Linux user account is 505
and the gid of your primary group is, say, 100, just add the values to
your SAM user and group accounts.  The following example assumes you
didn't already add something else to the comment field.

To your user's SAM comment (remember: called "Description" in the GUI),
add:

  <cygwin group="Users" unix="505"/>

To the user's group SAM comment add:

  <cygwin unix="100"/>

This should be sufficient to work on your Samba share and to see
all files owned by your Linux user account as your files.


===========================
The /etc/nsswitch.conf file
===========================

Last, but not least, let's talk about the way to configure how the
mapping works on your machine.  On Linux and some other UNIXy OSes, we
have a file called /etc/nsswitch.conf[9].  One part of it is to specify
how the passwd and group entries are generated.  That's what Cygwin now
provides as well.

The /etc/nsswitch.conf file is optional.  If you don't have one, Cygwin
uses sensible defaults.

Note:  The /etc/nsswitch.conf file is read exactly once by the first
       process of a Cygwin process tree.  If there was no /etc/nsswitch.conf
       file when this first process started, then no other process in
       the running Cygwin process trees will try to read the file.

       If you create or change /etc/nsswitch.conf, you need to restart
       all Cygwin processes that need to see the change.  If the process
       you want to see the change is a child of another process, you
       need to restart all of that process's parents, too.

       For example, if you run Vim inside the default Cygwin Terminal,
       Vim is a child of your shell, which is a child of mintty.exe.  If
       you edit /etc/nsswitch.conf in that Vim instance, your shell
       won't immediately see the change, nor will Vim if you restart it
       from that same shell instance.  This is because both are getting
       their nsswitch information from their ancestor, mintty.exe.  You
       need to start a fresh terminal window for the change to take
       effect.

       By contrast, if you leave that Cygwin Terminal window open after
       making the change to /etc/nsswitch.conf, then restart a Cygwin
       service like cron, cron will see the change, because it is not a
       child of mintty.exe or any other Cygwin process. (Technically, it
       is a child of cygrunsrv, but that instance also restarts when you
       restart the service.)

       The reason we point all this out is that the requirements for
       restarting things are not quite as stringent as when you replace
       cygwin1.dll. If you have three process trees, you have three
       independent copies of the nsswitch information.  If you start a
       fresh process tree, it will see the changes.  As long as any
       process in an existing process tree remains running, all
       processes in that tree will continue to use the old information.

So, what mischief can we perform with /etc/nsswitch.conf?  To explain,
lets have a look into an /etc/nsswitch.conf file set up to all default
values:

  # /etc/nsswitch.conf
  passwd: files db
  group:  files db

  db_prefix:    auto
  db_separator: +
  db_enum:      cache builtin

The first line, starting with a hash '#' is a comment.  The hash
character starts a comment, just as in shell scripts.  Everything up to
the end of the line is ignored.  So this:

  foo:  bar # baz

means, for the entry "foo", do "bar", ignore everything after the hash
sign.  "baz" is only a comment.

The other lines define the available settings.  The first word up to a
colon is a keyword.  Note that the colon *must* follow immediately after
the keyword.  This is a valid line:

  foo: bar

This is not valid:

  foo  :  bar

Apart from this restriction, the reminder of the line can have as
may spaces and TABs as you like.  This is a valid line:

        foo:                       bar                baz

Now let's have a look at the available keywords and settings.

The two lines starting with the keywords "passwd" and "group" define
where Cygwin gets its passwd and group information from.  "files" means,
fetch the information from the corresponding file in the /etc directory.
"db" means, fetch the information from the Windows account databases,
the SAM for local accounts, Active Directory for domain account.
Examples:

  passwd: files

Read passwd entries only from /etc/passwd.

  group: db

Read group entries only from SAM/AD.

  group: files # db

Read group entries only from /etc/group ("db" is ignored due to the
preceding hash sign).

  passwd: files db

Read passwd entries from /etc/passwd.  If a user account isn't found,
try to find it in SAM or AD.  This is the default for both, passwd
and group information.

  group: db files

This is a valid entry, but the order will be ignored by Cygwin.  If
both, files and db are specified, Cygwin will always try the files
first, then the db.

The remaining entries define certain aspects of the Windows account
database search.  "db_prefix" determines how the Cygwin user or group
name is created:

  db_prefix: auto

    This is the default.  If your account is from the primary domain of
    your machine, or if your machine is a standalone machine (not a domain
    member), your Cygwin account name is just the Windows account
    name.
    If your account is from another domain, or if you're logged in as
    local user on a domain machine, the Cygwin username will be the
    combination of Windows domainname and username, with the separator
    char in between:

      MY_DOM+username      (foreign domain)
      MACHINE+username     (local account)
    
    Builtin accounts have just the separator char prepended:

      +LOCAL
      +Users

    Unknown accounts on NFS or Samba shares (that is, accounts which
    cannot be mapped to Windows user accounts via RFC 2307) get a
    Cygwin account name consisting of the artificial domains "Unix_User"
    or "Unix_Group" and the uid/gid value, for instance:

      Unix_User+0          (root)
      Unix_Group+10        (wheel)

  db_prefx: primary

    Like "auto", but primary domain accounts will be prepended by
    the domainname as well.

  db_prefix: always

    All accounts, even the builtin accounts, will have the domain
    name prepended:

      BUILTIN+Users

    As a special case, if the Cygwin account name differs from the
    Windows account name, it will be prepended by the artificial domain
    name "Posix_User" or "Posix_Group" if db_prefix is set to "always":

      Posix_User+cygwin_user_name
      Posix_Group+cygwin_group_name

"db_separator" defines the spearator char used to prepend the domain
name to the user or group name.  The default is '+':

    MY_DOM+username

With "db_separator", you can define any ASCII char except space,
tab, carriage return, line feed, and the colon, as separator char.
Example:

  db_separator: \

    MY_DOM\username

"db_enum" defines the depth of a database search, if an application
calls one of the enumeration functions getpwent[10] or getgrent[11].
The problem with these functions is, they neither allow to define how many
entries will be enumerated when calling them in a loop, nor do they
allow to add some filter criteria.  They were designed back in the days,
when only /etc/passwd and /etc/group files existed and the number of
user accounts on a typical UNIX system was seldomly a three-digit
number.

These days, with user and group databases sometimes going in the
six-digit range, they are a potential burden.  For that reason, Cygwin
does not enumerate all user or group accounts by default, but rather
just a very small list, consisting only of the accounts cached in memory
by the current process, as well as a handful of predefined builtin
accounts.

"db_enum" allows to specify the accounts to enumerate in a fine-grained
way.  It takes a list of sources as argument:

  db_enum:  source1 source2 ...

The recognized sources are the following:

  none             No output from getpwent/getgrent at all.

  all              The opposite.  Enumerates accounts from all known
                   sources, including all trusted domains.

  cache            Enumerate all accounts currently cached in memory.

  builtin          Enumerate the predefined builtin accounts for backward
                   compatibility.  These are five passwd accounts
                   (SYSTEM, LocalService, NetworkService, Administrators,
                   TrustedInstaller) and two group accounts (SYSTEM and
                   TrustedInstaller).

  files            Enumerate the accounts from /etc/passwd or /etc/group.

  local            Enumerate all accounts from the local SAM.

  primary          Enumerate all accounts from the primary domain.

  alltrusted	   Enumerate all accounts from all trusted domains.

  some.domain	   Enumerate all accounts from the trusted domain some.domain.
                   The trusted domain can be given as Netbios flat name
                   (MY_DOMAIN) or as dns domain name (my_domain.corp).
                   In contrast to the aforementioned fixed source keywords,
                   distinct domain names are caseinsensitive.  Only domains
                   which are actually trusted domains are enumerated.
                   Unknown domains are simply ignored.

Please note that getpwent/getgrent do *not* test if an account was
already listed from another source, so an account can easily show up
twice or three times.  Such a test would be rather tricky, nor does the
Linux implementation perform such test.  Here are a few examples for
/etc/nsswitch.conf:

  db_enum: none

    No output from getpwent/getgrent at all.  The first call to the
    function immediately returns a NULL pointer.

  db_enum: cache files

    Enumerate all accounts cached by the current process, plus all entries
    from either the /etc/passwd or /etc/group file.

  db_enum: cache local primary

    Enumerate all accounts cached by the current process, all accounts
    from the SAM of the local machine, and all accounts from the
    primary domain of the machine.

  db_enum: local primary alltrusted

    Enumerate the accounts from the machine's SAM, from the primary domain
    of the machine, and from all trusted domains.

  db_enum: primary domain1.corp sub.domain.corp domain2.net

    Enumerate the accounts from the primary domain and from the domains
    domain1.corp, sub.domain.corp and domain2.net.

  db_enum: all

    Enumerate everything and the kitchen sink.


==========
Footnotes:
==========

[1] http://cygwin.com/cygwin-ug-net/ntsec.html

[2] This may change.  Right now the file is read in 32K chunks, but
    we could easily read the file in 64K chunks and, if we find the
    file is < 64K anyway, just cache the entire bunch, like before.
    Not implemented yet, but something to keep in mind.

[3] http://msdn.microsoft.com/en-us/library/windows/desktop/aa379166%28v=vs.85%29.aspx
    http://msdn.microsoft.com/en-us/library/windows/desktop/aa379159%28v=vs.85%29.aspx

[4] This is where Cygwin differs from SFU.  The reason is that we need
    the old uid/gid values for backward compatibility.  There are Cygwin
    packages (cron, for instance) who rely on the fact that the uid of
    SYSTEM is 18.  In SFU, these accounts get mapped like the other
    built in SIDs.

[5] http://support.microsoft.com/kb/243330

[6] https://tools.ietf.org/html/rfc2307

[7] https://tools.ietf.org/html/rfc1813

[8] http://msdn.microsoft.com/en-us/library/cc980032.aspx

[9] http://linux.die.net/man/5/nsswitch.conf

[10] http://linux.die.net/man/3/getpwent

[11] http://linux.die.net/man/3/getgrent

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Chris J. Breisch]

Corinna Vinschen wrote:
> * cygserver now provides system-wide passwd/group entry caching.
>
>    All processes started *after* cygserver will try to fetch passwd
>    and group entries from cygserver.  While this is probably a bit
>    slow at the start, the longer cygserver runs, the more information
>    is present and later started processes will get the information
>    with all due speed.
>

This sounds awesome.

> * Support for Cygwin user names different from the Windows username.
>
[snip]
>    Therefore I think it would be better to remove this functionality.
>    If you really think you have to use a username different from the
>    Windows username, you should probably use a tiny /etc/passwd file
>    with just this entry.  The new mkpasswd will create a default entry
>    for you with just needs minor tweaking.

I haven't contributed much to this testing, but I'm on board with that idea.

>
>
> * db_separator in /etc/nsswitch.conf
>
>    Is it really such a good idea to have a configurable separator
>    char in user and group names?  Is it important that it is
>    configurable?  Is '+' a good choice for the default separator?
>    Wouldn't the backslash a better and, perhaps, only choice?
>
>
I'd vote against '+' and in favor of '\' as long as there is no 
potential for confusion with Windows Domains and accounts/machine names, 
i.e. <domain name>\{<user name>,<machine name>}.

It doesn't sound to me like that would be an issue with how you want to 
use things, but that's my only concern at the moment.


-- 
Chris J. Breisch

--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 2293 bytes --]

On Apr 10 11:19, Chris J. Breisch wrote:
> Corinna Vinschen wrote:
> >* cygserver now provides system-wide passwd/group entry caching.
> >
> >   All processes started *after* cygserver will try to fetch passwd
> >   and group entries from cygserver.  While this is probably a bit
> >   slow at the start, the longer cygserver runs, the more information
> >   is present and later started processes will get the information
> >   with all due speed.
> >
> 
> This sounds awesome.
> 
> >* Support for Cygwin user names different from the Windows username.
> >
> [snip]
> >   Therefore I think it would be better to remove this functionality.
> >   If you really think you have to use a username different from the
> >   Windows username, you should probably use a tiny /etc/passwd file
> >   with just this entry.  The new mkpasswd will create a default entry
> >   for you with just needs minor tweaking.
> 
> I haven't contributed much to this testing, but I'm on board with that idea.
> 
> >
> >
> >* db_separator in /etc/nsswitch.conf
> >
> >   Is it really such a good idea to have a configurable separator
> >   char in user and group names?  Is it important that it is
> >   configurable?  Is '+' a good choice for the default separator?
> >   Wouldn't the backslash a better and, perhaps, only choice?
> >
> >
> I'd vote against '+' and in favor of '\' as long as there is no
> potential for confusion with Windows Domains and accounts/machine
> names, i.e. <domain name>\{<user name>,<machine name>}.
> 
> It doesn't sound to me like that would be an issue with how you want
> to use things, but that's my only concern at the moment.

I don't think there could be such a confusion (might depend on my code,
knock on wood), but if so, it would occur with '+' as well.  This
kind of confusion would not depend on the actual separator used.

The only reason I dislike backslash a bit is, that the backslash is
the escape char in the shell, so you would have remember every time
you type in such an account name to escape the account name,
DOMAIN\\username or "DOMAIN\username"


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Ken Brown]

On 4/10/2014 10:53 AM, Corinna Vinschen wrote:
> Hi folks,
>
>
> The latest snapshot, 2014-04-10, is a snapshot from CVS HEAD again.
> It contains the latest crazy ideas in terms of the user and group
> account creation without requiring the /etc/passwd and /etc/group
> files.
>
> Not a lot has changed since we made a break to test for 1.7.29,
> but there's one important change I'd like to point out:
>
> * cygserver now provides system-wide passwd/group entry caching.
>
>    All processes started *after* cygserver will try to fetch passwd
>    and group entries from cygserver.  While this is probably a bit
>    slow at the start, the longer cygserver runs, the more information
>    is present and later started processes will get the information
>    with all due speed.

Do we need to install cygserver.exe from the snapshot in order to get 
this functionality, or is cygwin1.dll enough?

Ken


--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]

On Apr 10 13:21, Ken Brown wrote:
> On 4/10/2014 10:53 AM, Corinna Vinschen wrote:
> >Hi folks,
> >
> >
> >The latest snapshot, 2014-04-10, is a snapshot from CVS HEAD again.
> >It contains the latest crazy ideas in terms of the user and group
> >account creation without requiring the /etc/passwd and /etc/group
> >files.
> >
> >Not a lot has changed since we made a break to test for 1.7.29,
> >but there's one important change I'd like to point out:
> >
> >* cygserver now provides system-wide passwd/group entry caching.
> >
> >   All processes started *after* cygserver will try to fetch passwd
> >   and group entries from cygserver.  While this is probably a bit
> >   slow at the start, the longer cygserver runs, the more information
> >   is present and later started processes will get the information
> >   with all due speed.
> 
> Do we need to install cygserver.exe from the snapshot in order to
> get this functionality, or is cygwin1.dll enough?

This required new code in cygserver to handle the application requests,
so you need the snapshot cygserver.


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Warren Young]

On 4/10/2014 09:28, Corinna Vinschen wrote:
>
> The only reason I dislike backslash a bit is, that the backslash is
> the escape char in the shell, so you would have remember every time
> you type in such an account name to escape the account name,
> DOMAIN\\username or "DOMAIN\username"

Is this DOMAIN\username syntax merely mimicking a Windowsism, or does it 
directly translate into a semantically meaningful construct to Windows? 
  I mean, do you have to parse it and reassemble the data for Windows' 
benefit, or do you pass this string straight to some Windows API?

If cygwin1.dll must premasticate the string for Windows' benefit, you 
can use any separator character you like.  In that case, I'd think 
forward slash makes more sense, since it says, "This works like POSIX 
paths: cygwin1.dll is translating this to something else for you behind 
the scenes."  Backslash signals that what you're doing is something 
Windows understands natively.

As for your original question, I can't see why you'd need it to be 
configurable as long as it's escapable.  If you can escape the 
delimiter, then you can hardcode it to anything you like, since there's 
a path out of any conflict.

--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Warren Young]

On 4/10/2014 08:53, Corinna Vinschen wrote:
> * Support for Cygwin user names different from the Windows username.
>
>    This is a really fat problem.

Who needs this functionality?

Is it some legacy of passwd(5) compatibility, such as the wish to have 
colons in Windows login names?

Does the move to AD/SAM eliminate the original need, so that you 
actually have *two* reasons to stop paying the runtime expense?

--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 2136 bytes --]

On Apr 10 12:39, Warren Young wrote:
> On 4/10/2014 09:28, Corinna Vinschen wrote:
> >
> >The only reason I dislike backslash a bit is, that the backslash is
> >the escape char in the shell, so you would have remember every time
> >you type in such an account name to escape the account name,
> >DOMAIN\\username or "DOMAIN\username"
> 
> Is this DOMAIN\username syntax merely mimicking a Windowsism, or
> does it directly translate into a semantically meaningful construct
> to Windows?  I mean, do you have to parse it and reassemble the data
> for Windows' benefit, or do you pass this string straight to some
> Windows API?

Right now, since the separator char is configurable, it's of course
mimicking and converting to the windows style where required.

> If cygwin1.dll must premasticate the string for Windows' benefit,
> you can use any separator character you like.  In that case, I'd
> think forward slash makes more sense, since it says, "This works
> like POSIX paths: cygwin1.dll is translating this to something else
> for you behind the scenes."  Backslash signals that what you're
> doing is something Windows understands natively.
> 
> As for your original question, I can't see why you'd need it to be
> configurable as long as it's escapable.  If you can escape the
> delimiter, then you can hardcode it to anything you like, since
> there's a path out of any conflict.

A local cygwin user told me that the users in their company would
probably be confused by the '+ or, FWIW, any other non-backslash char,
because they were drilled to see and use usernames always in domain\name
form, or even in domain\\user form when logging in to Linux.

I like slashes a lot more for obvious reasons.  But maybe, and that
wouldn't be too hard to implement, we could accept account names with
slash and with backslash, just as we do with pathnames.  Output of
usernames would be with slashes, of course.

Well, just an idea.


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]

On Apr 10 12:42, Warren Young wrote:
> On 4/10/2014 08:53, Corinna Vinschen wrote:
> >* Support for Cygwin user names different from the Windows username.
> >
> >   This is a really fat problem.
> 
> Who needs this functionality?

I don't remember, but some user on this list wrote in February about how
he uses this for... something.  Something to do with logging in to other
machines or so.

> Is it some legacy of passwd(5) compatibility, such as the wish to
> have colons in Windows login names?

No, it's just some legacy of how we allow this for /etc/passwd and
/etc/group.  See, for instance entries like

  root:S-1-5-21-544:0:

to fake a root group backed by the administrators group.  It 
seemed like a good idea at the time (2000 or so) and this would
not be possible anymore.  But, in fact, I was trying to make sure
all the time that our applications don't rely on this.  And if we
actually have an application which relies on this, it's a bug.

> Does the move to AD/SAM eliminate the original need, so that you
> actually have *two* reasons to stop paying the runtime expense?

I never had this need.  To me it was just a funny extension.  But maybe
other users are using this, so I'm a bit unlucky now that I invented it
in the first place.


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1580 bytes --]

On Apr 10 21:11, Corinna Vinschen wrote:
> On Apr 10 12:42, Warren Young wrote:
> > On 4/10/2014 08:53, Corinna Vinschen wrote:
> > >* Support for Cygwin user names different from the Windows username.
> > >
> > >   This is a really fat problem.
> > 
> > Who needs this functionality?
> 
> I don't remember, but some user on this list wrote in February about how
> he uses this for... something.  Something to do with logging in to other
> machines or so.
> 
> > Is it some legacy of passwd(5) compatibility, such as the wish to
> > have colons in Windows login names?
> 
> No, it's just some legacy of how we allow this for /etc/passwd and
> /etc/group.  See, for instance entries like
> 
>   root:S-1-5-21-544:0:
> 
> to fake a root group backed by the administrators group.  It 
> seemed like a good idea at the time (2000 or so) and this would
> not be possible anymore.  But, in fact, I was trying to make sure
> all the time that our applications don't rely on this.  And if we
> actually have an application which relies on this, it's a bug.
> 
> > Does the move to AD/SAM eliminate the original need, so that you
> > actually have *two* reasons to stop paying the runtime expense?
> 
> I never had this need.  To me it was just a funny extension.  But maybe
> other users are using this, so I'm a bit unlucky now that I invented it
> in the first place.

s/unlucky/unhappy/


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Achim Gratz]

Corinna Vinschen writes:
> * cygserver now provides system-wide passwd/group entry caching.
>
>   All processes started *after* cygserver will try to fetch passwd
>   and group entries from cygserver.  While this is probably a bit
>   slow at the start, the longer cygserver runs, the more information
>   is present and later started processes will get the information
>   with all due speed.

Does this mean there is no caching without cygserver running?

> * Support for Cygwin user names different from the Windows username.

This one always seemed a bit odd to me.  The only use I could think up
is if your Windows username contains non-ASCII or spaces and you'd want
to avoid dealing with that within Cygwin.

> * db_separator in /etc/nsswitch.conf

I can't see a pressing need for configurable separators here.  Domain
users are probably already accustomed to seeing Domain\User, so that'd
be a natural default unless somebody had a pretty good reason for
something different.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Larry Hall (Cygwin)]

On 4/10/2014 3:04 PM, Corinna Vinschen wrote:
> I like slashes a lot more for obvious reasons.  But maybe, and that
> wouldn't be too hard to implement, we could accept account names with
> slash and with backslash, just as we do with pathnames.  Output of
> usernames would be with slashes, of course.
>
> Well, just an idea.


Yeah but I'd say it's a good one if it it can be done without too much
trouble.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Eric Blake]

[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]

On 04/10/2014 01:46 PM, Achim Gratz wrote:
> Corinna Vinschen writes:
>> * cygserver now provides system-wide passwd/group entry caching.
>>
>>   All processes started *after* cygserver will try to fetch passwd
>>   and group entries from cygserver.  While this is probably a bit
>>   slow at the start, the longer cygserver runs, the more information
>>   is present and later started processes will get the information
>>   with all due speed.
> 
> Does this mean there is no caching without cygserver running?
> 
>> * Support for Cygwin user names different from the Windows username.
> 
> This one always seemed a bit odd to me.  The only use I could think up
> is if your Windows username contains non-ASCII or spaces and you'd want
> to avoid dealing with that within Cygwin.

Windows allows usernames with spaces.  POSIX says such names are
non-portable (although it doesn't go so far as to completely exclude
them).  Furthermore, tilde expansion does NOT work for user names with
spaces.

I've had machines in the past where my windows username had a space; the
ability to remap my passwd file to a non-space name was a lifesaver.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Eric Blake]

[-- Attachment #1: Type: text/plain, Size: 2667 bytes --]

On 04/10/2014 01:04 PM, Corinna Vinschen wrote:

> 
> A local cygwin user told me that the users in their company would
> probably be confused by the '+ or, FWIW, any other non-backslash char,
> because they were drilled to see and use usernames always in domain\name
> form, or even in domain\\user form when logging in to Linux.
> 
> I like slashes a lot more for obvious reasons.  But maybe, and that
> wouldn't be too hard to implement, we could accept account names with
> slash and with backslash, just as we do with pathnames.  Output of
> usernames would be with slashes, of course.

POSIX says:

http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html
> User Name
> A string that is used to identify a user; see also User Database. To be portable across systems conforming to POSIX.1-2008, the value is composed of characters from the portable filename character set. The <hyphen> character should not be used as the first character of a portable user name.

It also says this for shell tilde expansion:

http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_01
>  If none of the characters in the tilde-prefix are quoted, the characters in the tilde-prefix following the <tilde> are treated as a possible login name from the user database. A portable login name cannot contain characters outside the set given in the description of the LOGNAME environment variable in XBD Other Environment Variables.

and following that link:
> For a value of LOGNAME to be portable across implementations of POSIX.1-2008, the value should be composed of characters from the portable filename character set.

In short, in POSIX systems, user names are solely from the set
[-_.a-zA-Z0-9]; which excludes +, \, or any other separator we come up
with.  I'm fine with using a non-portable character (this is, after all,
a cygwin extension of how to map Windows user names to a Linux emulation
environment).  But keeping in mind the rules on tilde expansion,

~a+b/file

can undergo tilde expansion for username 'a+b', but

~a\\b/file

cannot do so, because the \ is necessarily always quoted.  There is no
way to get tilde expansion to work for a username containing a shell
metacharacter, which frowns on quite a few otherwise useful characters,
including \.

Worse, the thought of using / as the separator gives me the willies - it
is BOUND to go wrong.  The expression

~a/b/file

is NOT requesting 'file' within user 'a/b's home, but 'b/file' within
user 'a's home.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Warren Young]

On 4/10/2014 14:20, Eric Blake wrote:
> is BOUND to go wrong.  The expression
>
> ~a/b/file
>
> is NOT requesting 'file' within user 'a/b's home, but 'b/file' within
> user 'a's home.

Excellent point.

Doesn't that also argue against backslash, due to the DLL's attempts to 
automatically cope with DOS paths?

Once you exclude all characters that neither the shell nor the DLL nor 
Windows will interpret specially, what's left?  According to TLDP[*], 
nothing.

Soooo....emoji?  :)


[*] http://tldp.org/LDP/abs/html/special-chars.html

--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Duncan Roe]

On Thu, Apr 10, 2014 at 09:11:20PM +0200, Corinna Vinschen wrote:
> On Apr 10 12:42, Warren Young wrote:
> > On 4/10/2014 08:53, Corinna Vinschen wrote:
> > >* Support for Cygwin user names different from the Windows username.
> > >
> > >   This is a really fat problem.
> >
> > Who needs this functionality?
>
> I don't remember, but some user on this list wrote in February about how
> he uses this for... something.  Something to do with logging in to other
> machines or so.
>
> > Is it some legacy of passwd(5) compatibility, such as the wish to
> > have colons in Windows login names?
>
> No, it's just some legacy of how we allow this for /etc/passwd and
> /etc/group.  See, for instance entries like
>
>   root:S-1-5-21-544:0:
>
> to fake a root group backed by the administrators group.  It
> seemed like a good idea at the time (2000 or so) and this would
> not be possible anymore.  But, in fact, I was trying to make sure
> all the time that our applications don't rely on this.  And if we
> actually have an application which relies on this, it's a bug.
>
> > Does the move to AD/SAM eliminate the original need, so that you
> > actually have *two* reasons to stop paying the runtime expense?
>
> I never had this need.  To me it was just a funny extension.  But maybe
> other users are using this, so I'm a bit unlucky now that I invented it
> in the first place.
>
>
> Corinna
>
Yes, I'm one of those users. I need my login name to match the Linux systems so
I can use rsh and not be challenged for a password when the cygwin host name is
in ~/.rhosts

Cheers ... Duncan.

--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Warren Young]

On 4/10/2014 20:16, Duncan Roe wrote:
> Yes, I'm one of those users. I need my login name to match the Linux systems so
> I can use rsh and not be challenged for a password when the cygwin host name is
> in ~/.rhosts

If you switch to SSH, you can solve this by putting this into your 
~/.ssh/config file:

      Host myremotehost
          User duncan_roe

That is, you can override defaults (like login name) on a per-connection 
basis.  Anything you can pass as an option to ssh(1) can be changed 
here, so you don't have to keep providing the option.

With pre-shared keys, I don't think you'll see a difference in behavior 
relative to rsh.

--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Duncan Roe]

On Thu, Apr 10, 2014 at 09:47:26PM -0600, Warren Young wrote:
> On 4/10/2014 20:16, Duncan Roe wrote:
> >Yes, I'm one of those users. I need my login name to match the Linux systems so
> >I can use rsh and not be challenged for a password when the cygwin host name is
> >in ~/.rhosts
>
> If you switch to SSH, you can solve this by putting this into your
> ~/.ssh/config file:
>
>      Host myremotehost
>          User duncan_roe
>
> That is, you can override defaults (like login name) on a per-connection
> basis.  Anything you can pass as an option to ssh(1) can be changed here, so
> you don't have to keep providing the option.
>
> With pre-shared keys, I don't think you'll see a difference in behavior
> relative to rsh.
>
I don't want to switch to ssh. rsh is in an expect script, so providing ssh
options every time would not be a problem. But I want to use rsh.

--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 2566 bytes --]

On Apr 10 14:20, Eric Blake wrote:
> On 04/10/2014 01:04 PM, Corinna Vinschen wrote:
> > A local cygwin user told me that the users in their company would
> > probably be confused by the '+ or, FWIW, any other non-backslash char,
> > because they were drilled to see and use usernames always in domain\name
> > form, or even in domain\\user form when logging in to Linux.
> > 
> > I like slashes a lot more for obvious reasons.  But maybe, and that
> > wouldn't be too hard to implement, we could accept account names with
> > slash and with backslash, just as we do with pathnames.  Output of
> > usernames would be with slashes, of course.
> 
> POSIX says:
> [...]
> In short, in POSIX systems, user names are solely from the set
> [-_.a-zA-Z0-9]; which excludes +, \, or any other separator we come up
> with.  I'm fine with using a non-portable character (this is, after all,
> a cygwin extension of how to map Windows user names to a Linux emulation
> environment).  But keeping in mind the rules on tilde expansion,
> 
> ~a+b/file
> 
> can undergo tilde expansion for username 'a+b', but
> 
> ~a\\b/file
> 
> cannot do so, because the \ is necessarily always quoted.  There is no
> way to get tilde expansion to work for a username containing a shell
> metacharacter, which frowns on quite a few otherwise useful characters,
> including \.
> 
> Worse, the thought of using / as the separator gives me the willies - it
> is BOUND to go wrong.  The expression
> 
> ~a/b/file
> 
> is NOT requesting 'file' within user 'a/b's home, but 'b/file' within
> user 'a's home.

This is a really good point.  This effectively eliminates slash from
the picture and the backslash reduces usability a lot, it seems.

So we might actually be better off by sticking to a configurable
separator char and default '+'?

What bugs me a bit is what this means for applications which expect
fixed usernames.  Sshd, for instance, expects the fixed username
"sshd" right now when using privilege separation.  I discussed this
with the OpenSSH devs, and they understand the problem, but they think
this should be handled by a Cygwin-specific function.  So there's some
extra work in it for me to get OpenSSH up to speed with this change,
but I fear I'm not the only one.  The more configurable stuff like this
is, the more complicated it gets maintaining some packages.


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 761 bytes --]

On Apr 10 16:21, Warren Young wrote:
> On 4/10/2014 14:20, Eric Blake wrote:
> >is BOUND to go wrong.  The expression
> >
> >~a/b/file
> >
> >is NOT requesting 'file' within user 'a/b's home, but 'b/file' within
> >user 'a's home.
> 
> Excellent point.
> 
> Doesn't that also argue against backslash, due to the DLL's attempts
> to automatically cope with DOS paths?
> 
> Once you exclude all characters that neither the shell nor the DLL
> nor Windows will interpret specially, what's left?  According to
> TLDP[*], nothing.
> 
> Soooo....emoji?  :)

Or Non-breaking-space...


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 2274 bytes --]

On Apr 11 16:20, Duncan Roe wrote:
> On Thu, Apr 10, 2014 at 09:47:26PM -0600, Warren Young wrote:
> > On 4/10/2014 20:16, Duncan Roe wrote:
> > >Yes, I'm one of those users. I need my login name to match the Linux systems so
> > >I can use rsh and not be challenged for a password when the cygwin host name is
> > >in ~/.rhosts
> >
> > If you switch to SSH, you can solve this by putting this into your
> > ~/.ssh/config file:
> >
> >      Host myremotehost
> >          User duncan_roe
> >
> > That is, you can override defaults (like login name) on a per-connection
> > basis.  Anything you can pass as an option to ssh(1) can be changed here, so
> > you don't have to keep providing the option.
> >
> > With pre-shared keys, I don't think you'll see a difference in behavior
> > relative to rsh.
> >
> I don't want to switch to ssh. rsh is in an expect script, so providing ssh
> options every time would not be a problem. But I want to use rsh.

OTOH, if there *is* an official workaround which is, "use the /etc/passwd
file to chnage your username", wouldn't that be sufficient?

I understand your point, but the search problem in the Windows user DBs
as I outlined persists.

What I did a couple of weeks ago ws to change the mkpasswd tool so that
it creates the exact same passwd entries as you get when fetching them
directly from Windows.  For instance, the passwd entry generated for
my AD account inside of Cygwin will look like this:

corinna:*:1049577:1049701:Corinna Vinschen,U-VINSCHEN\corinna,S-1-5-21-2913048732-1697188782-3448811101-1001:/home/corinna:/bin/tcsh

Using the "new" mkpasswd, calling `mkpasswd -d -u corinna', I get the
exact same entry!  If I write this into /etc/passwd, I'm getting the
exact same correct uid and gid values, but I can change my username:

  $ mkpasswd -d -u corinna > /etc/passwd
  $ sed -i -e 's/^corinna:/cathy:/' /etc/passwd
  [logout/login]
  $ id
  uid=1049577(cathy) gid=1049701(vinschen) groups=1049701(vinschen),
  559(+Performance Log Users),545(+Users),[...]

That should be sufficient, shouldn't it?


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 2597 bytes --]

On Apr 10 21:46, Achim Gratz wrote:
> Corinna Vinschen writes:
> > * cygserver now provides system-wide passwd/group entry caching.
> >
> >   All processes started *after* cygserver will try to fetch passwd
> >   and group entries from cygserver.  While this is probably a bit
> >   slow at the start, the longer cygserver runs, the more information
> >   is present and later started processes will get the information
> >   with all due speed.
> 
> Does this mean there is no caching without cygserver running?

Huh?  I really didn't expect this question.  Of course the in-process
caching is still present.  Read the new chapter called "Caching" in the
document I attached to my OP.  Or, even better, I just quote it here,
for your convenience:

=======
Caching
=======

The information fetched from file or the Windows account database is cached
by the process.  The cached information is inherited by child processes.

While usually working fine, this has some drawbacks.  Consider a shell
calling `id'.  `id' fetches all group information from the current token
and caches them.  Unfortunately `id' doesn't start any child processes,
so the information is lost as soon as `id' exits.

But there's another caching mechanism available.  If cygserver is
running it will provide passwd and group entry caching for all processes
in a Cygwin process tree, which first process has been started after
cygserver.  So, if you start a Cygwin Terminal and cygserver is
running at the time, mintty, the shell, and all child processes will
use cygserver caching.  If you start a Cygwin Terminal and cygserver is
not running a the time, none of the processes started inside this
terminal window will use cygserver caching.

The advantage of cygserver caching is that it's system-wide and, as long
as cygserver is running, unforgetful.  Every Cygwin process on the system
will have the cygserver cache at its service.  Additionally, all information
requested from cygserver once, will be cached inside the process itself
and, again, propagated to child processes.


> > * db_separator in /etc/nsswitch.conf
> 
> I can't see a pressing need for configurable separators here.  Domain
> users are probably already accustomed to seeing Domain\User, so that'd
> be a natural default unless somebody had a pretty good reason for
> something different.

Eric's mail on this is pretty enlightening.


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1687 bytes --]

On Apr 10 14:24, Eric Blake wrote:
> On 04/10/2014 01:46 PM, Achim Gratz wrote:
> > Corinna Vinschen writes:
> >> * cygserver now provides system-wide passwd/group entry caching.
> >>
> >>   All processes started *after* cygserver will try to fetch passwd
> >>   and group entries from cygserver.  While this is probably a bit
> >>   slow at the start, the longer cygserver runs, the more information
> >>   is present and later started processes will get the information
> >>   with all due speed.
> > 
> > Does this mean there is no caching without cygserver running?
> > 
> >> * Support for Cygwin user names different from the Windows username.
> > 
> > This one always seemed a bit odd to me.  The only use I could think up
> > is if your Windows username contains non-ASCII or spaces and you'd want
> > to avoid dealing with that within Cygwin.
> 
> Windows allows usernames with spaces.  POSIX says such names are
> non-portable (although it doesn't go so far as to completely exclude
> them).  Furthermore, tilde expansion does NOT work for user names with
> spaces.
> 
> I've had machines in the past where my windows username had a space; the
> ability to remap my passwd file to a non-space name was a lifesaver.

... and this remapping username via /etc/passwd will not go away.  It's
the DB search which is a problem in terms of a special Cygwin username.
Doing this with /etc/passwd is a no-brainer.  See my mail I just wrote:

http://cygwin.com/ml/cygwin/2014-04/msg00298.html


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Ken Brown]

[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]

On 4/10/2014 10:53 AM, Corinna Vinschen wrote:
> Hi folks,
>
>
> The latest snapshot, 2014-04-10, is a snapshot from CVS HEAD again.
> It contains the latest crazy ideas in terms of the user and group
> account creation without requiring the /etc/passwd and /etc/group
> files.

I installed the complete snapshot and moved /etc/passwd and /etc/group 
out of the way.  Now all users have gid == uid:

$ mkpasswd.exe
+SYSTEM:*:18:18:U-NT AUTHORITY\SYSTEM,S-1-5-18:/home/SYSTEM:/bin/bash
[...]
kbrown:*:197610:197610:...
[...]
sshd:*:197613:197613:...

$ mkgroup.exe
+SYSTEM:S-1-5-18:18:
[...]
HomeUsers:S-1-5-21-2633657340-2046398995-3442950202-1003:197611:
None:S-1-5-21-2633657340-2046398995-3442950202-513:197121:

Shouldn't ordinary users (like kbrown) have gid == 197121?  All files I 
created as kbrown prior to the test show group "None", and all files I 
created after the test show group "kbrown".

Is this a bug, or is there something weird about my system that's making 
this happen?  cygcheck output is attached.

Ken

[-- Attachment #2: cygcheck.out --]
[-- Type: text/plain, Size: 90106 bytes --]


Cygwin Configuration Diagnostics
Current System Time: Sat Apr 12 00:27:15 2014

Windows 7 Home Premium Ver 6.1 Build 7601 Service Pack 1

Path:	C:\cygwin64\home\kbrown-admin\bin
	C:\cygwin64\usr\local\bin
	C:\cygwin64\bin
	C:\Program Files\Common Files\Microsoft Shared\Windows Live
	C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live
	C:\Windows\system32
	C:\Windows
	C:\Windows\System32\Wbem
	C:\Windows\System32\WindowsPowerShell\v1.0
	C:\Program Files (x86)\Windows Live\Shared
	C:\Program Files (x86)\Common Files\Intuit\QBPOSSDKRuntime
	C:\cygwin64\lib\lapack

Output from C:\cygwin64\bin\id.exe
UID: 197609(kbrown-admin)     GID: 197609(kbrown-admin)
197609(kbrown-admin)          197121(None)
197611(HomeUsers)             544(+Administrators)
545(+Users)                   4(+INTERACTIVE)
66049(+CONSOLE LOGON)         11(+Authenticated Users)
15(+This Organization)        4095(CurrentSession)
66048(+LOCAL)                 262154(+NTLM Authentication)
405504(+High Mandatory Level)

SysDir: C:\Windows\system32
WinDir: C:\Windows

USER = 'kbrown-admin'
PWD = '/home/kbrown-admin'
HOME = '/home/kbrown-admin'

MANPATH = '/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man'
APPDATA = 'C:\Users\kbrown-admin\AppData\Roaming'
ProgramW6432 = 'C:\Program Files'
HOSTNAME = 'sbrown-PC'
TERM = 'xterm'
PROCESSOR_IDENTIFIER = 'Intel64 Family 6 Model 42 Stepping 7, GenuineIntel'
WINDIR = 'C:\Windows'
PUBLIC = 'C:\Users\Public'
OLDPWD = '/c/Users/kbrown/Desktop'
TIME_STYLE = 'long-iso'
USERDOMAIN = 'sbrown-PC'
CommonProgramFiles(x86) = 'C:\Program Files (x86)\Common Files'
OS = 'Windows_NT'
ALLUSERSPROFILE = 'C:\ProgramData'
TEMP = '/tmp'
COMMONPROGRAMFILES = 'C:\Program Files\Common Files'
configsetroot = 'C:\Windows\ConfigSetRoot'
USERNAME = 'kbrown-admin'
PROCESSOR_LEVEL = '6'
ProgramFiles(x86) = 'C:\Program Files (x86)'
PSModulePath = 'C:\Windows\system32\WindowsPowerShell\v1.0\Modules\'
FP_NO_HOST_CHECK = 'NO'
SYSTEMDRIVE = 'C:'
LANG = 'en_US.UTF-8'
USERPROFILE = 'C:\Users\kbrown-admin'
TZ = 'America/New_York'
PS1 = '\[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n# '
CommonProgramW6432 = 'C:\Program Files\Common Files'
PROCESSOR_ARCHITECTURE = 'AMD64'
LOCALAPPDATA = 'C:\Users\kbrown-admin\AppData\Local'
HISTCONTROL = 'ignoredups'
ProgramData = 'C:\ProgramData'
SHLVL = '1'
PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC'
COMSPEC = 'C:\Windows\system32\cmd.exe'
TMP = '/tmp'
SYSTEMROOT = 'C:\Windows'
PRINTER = 'Quicken PDF Printer'
PROCESSOR_REVISION = '2a07'
INFOPATH = '/usr/local/info:/usr/share/info:/usr/info:'
PROGRAMFILES = 'C:\Program Files'
NUMBER_OF_PROCESSORS = '4'
COMPUTERNAME = 'SBROWN-PC'
_ = '/usr/bin/cygcheck'

HKEY_CURRENT_USER\Software\Cygwin
HKEY_CURRENT_USER\Software\Cygwin\Installations
  (default) = '\??\C:\cygwin'
  e022582115c10879 = '\??\C:\cygwin64'
  03ece2098ddffe1e = '\??\C:\cygwin64a'
HKEY_CURRENT_USER\Software\Cygwin\Program Options
HKEY_CURRENT_USER\Software\Cygwin\setup
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations
  (default) = '\??\C:\cygwin64'
  03ece2098ddffe1e = '\??\C:\cygwin64a'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Program Options
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup
  (default) = 'C:\cygwin64'
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygwin\Installations
  (default) = '\??\C:\cygwin'
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygwin\Program Options
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygwin\setup
  (default) = 'C:\cygwin'

obcaseinsensitive set to 1

Cygwin installations found in the registry:
  System: Key: e022582115c10879 Path: C:\cygwin64
  System: Key: 03ece2098ddffe1e Path: C:\cygwin64a (ORPHANED)
  User:   Key: c5e39b7a9d22bafb Path: C:\cygwin
  User:   Key: e022582115c10879 Path: C:\cygwin64
  User:   Key: 03ece2098ddffe1e Path: C:\cygwin64a (ORPHANED)

c:  hd  NTFS    113910Mb  80% CP CS UN PA FC     OS

C:\cygwin64      /          system  binary,auto
C:               /c         system  binary,posix=0
C:\cygwin64\bin  /usr/bin   system  binary,auto
C:\cygwin64\lib  /usr/lib   system  binary,auto
cygdrive prefix  /cygdrive  user    binary,auto

Found: C:\cygwin64\bin\awk
 -> C:\cygwin64\bin\gawk.exe
Found: C:\cygwin64\bin\bash.exe
Found: C:\cygwin64\bin\cat.exe
Found: C:\cygwin64\bin\cp.exe
Found: C:\cygwin64\bin\cpp.exe
Not Found: crontab
Found: C:\cygwin64\bin\find.exe
Found: C:\Windows\system32\find.exe
Warning: C:\cygwin64\bin\find.exe hides C:\Windows\system32\find.exe
Found: C:\cygwin64\bin\gcc.exe
Found: C:\cygwin64\bin\gdb.exe
Found: C:\cygwin64\bin\grep.exe
Found: C:\cygwin64\bin\kill.exe
Found: C:\cygwin64\bin\ld.exe
Found: C:\cygwin64\bin\ls.exe
Found: C:\cygwin64\bin\make.exe
Found: C:\cygwin64\bin\mv.exe
Found: C:\cygwin64\bin\patch.exe
Found: C:\cygwin64\bin\perl.exe
Found: C:\cygwin64\bin\rm.exe
Found: C:\cygwin64\bin\sed.exe
Found: C:\cygwin64\bin\ssh.exe
Found: C:\cygwin64\bin\sh.exe
Found: C:\cygwin64\bin\tar.exe
Found: C:\cygwin64\bin\test.exe
Found: C:\cygwin64\bin\vi.exe
Found: C:\cygwin64\bin\vim.exe

  127k 2013/06/23 C:\cygwin64\bin\cygapr-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygapr-1-0.dll" v0.0 ts=2013-06-23 18:53
  115k 2013/08/11 C:\cygwin64\bin\cygaprutil-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygaprutil-1-0.dll" v0.0 ts=2013-08-11 19:13
  575k 2013/05/30 C:\cygwin64\bin\cygarchive-13.dll - os=4.0 img=0.0 sys=5.2
                  "cygarchive-13.dll" v0.0 ts=2013-05-30 03:06
   38k 2013/07/19 C:\cygwin64\bin\cygargp-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygargp-0.dll" v0.0 ts=2013-07-19 15:07
  510k 2014/03/20 C:\cygwin64\bin\cygasn1-8.dll - os=4.0 img=0.0 sys=5.2
                  "cygasn1-8.dll" v0.0 ts=2014-03-20 04:54
  643k 2013/04/30 C:\cygwin64\bin\cygaspell-15.dll - os=4.0 img=0.0 sys=5.2
                  "cygaspell-15.dll" v0.0 ts=2013-04-30 08:11
    9k 2013/06/24 C:\cygwin64\bin\cygasprintf-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygasprintf-0.dll" v0.0 ts=2013-06-24 04:36
  107k 2014/03/12 C:\cygwin64\bin\cygatk-1.0-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygatk-1.0-0.dll" v0.0 ts=2014-03-12 07:45
  145k 2014/03/12 C:\cygwin64\bin\cygatk-bridge-2.0-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygatk-bridge-2.0-0.dll" v0.0 ts=2014-03-12 08:36
   87k 2014/01/29 C:\cygwin64\bin\cygatomic-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygatomic-1.dll" v0.0 ts=2014-01-29 01:15
  137k 2014/03/12 C:\cygwin64\bin\cygatspi-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygatspi-0.dll" v0.0 ts=2014-03-12 08:18
   16k 2013/03/26 C:\cygwin64\bin\cygattr-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygattr-1.dll" v0.0 ts=2013-03-26 18:26
  174k 2013/04/29 C:\cygwin64\bin\cygautotrace-3.dll - os=4.0 img=0.0 sys=5.2
                  "cygautotrace-3.dll" v0.0 ts=2013-04-29 09:23
   59k 2013/06/04 C:\cygwin64\bin\cygavahi-client-3.dll - os=4.0 img=0.0 sys=5.2
                  "cygavahi-client-3.dll" v0.0 ts=2013-06-04 05:29
   42k 2013/06/04 C:\cygwin64\bin\cygavahi-common-3.dll - os=4.0 img=0.0 sys=5.2
                  "cygavahi-common-3.dll" v0.0 ts=2013-06-04 05:28
   13k 2013/06/04 C:\cygwin64\bin\cygavahi-glib-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygavahi-glib-1.dll" v0.0 ts=2013-06-04 05:29
  125k 2013/03/11 C:\cygwin64\bin\cygblkid-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygblkid-1.dll" v0.0 ts=2013-03-11 03:08
    7k 2013/05/29 C:\cygwin64\bin\cygboost_atomic-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_atomic-mt-1_53.dll" v0.0 ts=2013-05-29 23:31
   24k 2013/05/29 C:\cygwin64\bin\cygboost_chrono-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_chrono-mt-1_53.dll" v0.0 ts=2013-05-29 23:31
   49k 2013/05/29 C:\cygwin64\bin\cygboost_date_time-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_date_time-mt-1_53.dll" v0.0 ts=2013-05-29 23:31
   83k 2013/05/29 C:\cygwin64\bin\cygboost_filesystem-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_filesystem-mt-1_53.dll" v0.0 ts=2013-05-29 23:31
  255k 2013/05/29 C:\cygwin64\bin\cygboost_graph-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_graph-mt-1_53.dll" v0.0 ts=2013-05-29 23:32
   92k 2013/05/29 C:\cygwin64\bin\cygboost_iostreams-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_iostreams-mt-1_53.dll" v0.0 ts=2013-05-29 23:32
  670k 2013/05/29 C:\cygwin64\bin\cygboost_locale-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_locale-mt-1_53.dll" v0.0 ts=2013-05-29 23:33
   63k 2013/05/29 C:\cygwin64\bin\cygboost_math_c99-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_math_c99-mt-1_53.dll" v0.0 ts=2013-05-29 23:34
   68k 2013/05/29 C:\cygwin64\bin\cygboost_math_c99f-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_math_c99f-mt-1_53.dll" v0.0 ts=2013-05-29 23:34
  320k 2013/05/29 C:\cygwin64\bin\cygboost_math_tr1-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_math_tr1-mt-1_53.dll" v0.0 ts=2013-05-29 23:33
  321k 2013/05/29 C:\cygwin64\bin\cygboost_math_tr1f-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_math_tr1f-mt-1_53.dll" v0.0 ts=2013-05-29 23:34
   42k 2013/05/29 C:\cygwin64\bin\cygboost_prg_exec_monitor-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_prg_exec_monitor-mt-1_53.dll" v0.0 ts=2013-05-29 23:37
  361k 2013/05/29 C:\cygwin64\bin\cygboost_program_options-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_program_options-mt-1_53.dll" v0.0 ts=2013-05-29 23:36
   11k 2013/05/29 C:\cygwin64\bin\cygboost_random-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_random-mt-1_53.dll" v0.0 ts=2013-05-29 23:36
  913k 2013/05/29 C:\cygwin64\bin\cygboost_regex-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_regex-mt-1_53.dll" v0.0 ts=2013-05-29 23:32
  363k 2013/05/29 C:\cygwin64\bin\cygboost_serialization-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_serialization-mt-1_53.dll" v0.0 ts=2013-05-29 23:37
   74k 2013/05/29 C:\cygwin64\bin\cygboost_signals-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_signals-mt-1_53.dll" v0.0 ts=2013-05-29 23:37
   19k 2013/05/29 C:\cygwin64\bin\cygboost_system-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_system-mt-1_53.dll" v0.0 ts=2013-05-29 23:31
   70k 2013/05/29 C:\cygwin64\bin\cygboost_thread-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_thread-mt-1_53.dll" v0.0 ts=2013-05-29 23:32
   17k 2013/05/29 C:\cygwin64\bin\cygboost_timer-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_timer-mt-1_53.dll" v0.0 ts=2013-05-29 23:37
  520k 2013/05/29 C:\cygwin64\bin\cygboost_unit_test_framework-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_unit_test_framework-mt-1_53.dll" v0.0 ts=2013-05-29 23:38
  991k 2013/05/29 C:\cygwin64\bin\cygboost_wave-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_wave-mt-1_53.dll" v0.0 ts=2013-05-29 23:38
  257k 2013/05/29 C:\cygwin64\bin\cygboost_wserialization-mt-1_53.dll - os=4.0 img=0.0 sys=5.2
                  "cygboost_wserialization-mt-1_53.dll" v0.0 ts=2013-05-29 23:37
   64k 2013/03/07 C:\cygwin64\bin\cygbz2-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygbz2-1.dll" v0.0 ts=2013-03-07 02:54
 1061k 2014/03/13 C:\cygwin64\bin\cygcairo-2.dll - os=4.0 img=0.0 sys=5.2
                  "cygcairo-2.dll" v0.0 ts=2014-03-13 21:39
   26k 2014/03/13 C:\cygwin64\bin\cygcairo-gobject-2.dll - os=4.0 img=0.0 sys=5.2
                  "cygcairo-gobject-2.dll" v0.0 ts=2014-03-13 21:39
  122k 2014/03/13 C:\cygwin64\bin\cygcairo-script-interpreter-2.dll - os=4.0 img=0.0 sys=5.2
                  "cygcairo-script-interpreter-2.dll" v0.0 ts=2014-03-13 21:40
   13k 2013/03/06 C:\cygwin64\bin\cygcatgets1.dll - os=4.0 img=0.0 sys=5.2
                  "cygcatgets1.dll" v0.0 ts=2013-03-06 14:34
   10k 2013/03/07 C:\cygwin64\bin\cygcharset-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygcharset-1.dll" v0.0 ts=2013-03-07 03:03
  117k 2013/05/05 C:\cygwin64\bin\cygcloog-isl-4.dll - os=4.0 img=0.0 sys=5.2
                  "cygcloog-isl-4.dll" v0.0 ts=2013-05-05 16:41
   12k 2013/03/11 C:\cygwin64\bin\cygcom_err-2.dll - os=4.0 img=0.0 sys=5.2
                  "cygcom_err-2.dll" v0.0 ts=2013-03-11 03:59
   31k 2013/04/24 C:\cygwin64\bin\cygcord-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygcord-1.dll" v0.0 ts=2013-04-24 23:14
  203k 2013/04/21 C:\cygwin64\bin\cygcroco-0.6-3.dll - os=4.0 img=0.0 sys=5.2
                  "cygcroco-0.6-3.dll" v0.0 ts=2013-04-21 06:25
    9k 2013/03/07 C:\cygwin64\bin\cygcrypt-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygcrypt-0.dll" v0.0 ts=2013-03-07 09:29
 1747k 2014/02/05 C:\cygwin64\bin\cygcrypto-1.0.0.dll - os=4.0 img=0.0 sys=5.2
                  "cygcrypto-1.0.0.dll" v0.0 ts=2014-02-05 10:49
  404k 2013/12/18 C:\cygwin64\bin\cygcurl-4.dll - os=4.0 img=0.0 sys=5.2
                  "cygcurl-4.dll" v0.0 ts=2013-12-18 05:17
   23k 2013/04/12 C:\cygwin64\bin\cygdatrie-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygdatrie-1.dll" v0.0 ts=2013-04-12 07:10
 1526k 2013/03/08 C:\cygwin64\bin\cygdb-5.3.dll - os=4.0 img=0.0 sys=5.2
                  "cygdb-5.3.dll" v0.0 ts=2013-03-08 07:55
  242k 2014/03/31 C:\cygwin64\bin\cygdbus-1-3.dll - os=4.0 img=0.0 sys=5.2
                  "cygdbus-1-3.dll" v0.0 ts=1970-01-01 00:00
  124k 2013/04/21 C:\cygwin64\bin\cygdbus-glib-1-2.dll - os=4.0 img=0.0 sys=5.2
                  "cygdbus-glib-1-2.dll" v0.0 ts=2013-04-21 07:12
  111k 2013/03/08 C:\cygwin64\bin\cygdb_cxx-5.3.dll - os=4.0 img=0.0 sys=5.2
                  "cygdb_cxx-5.3.dll" v0.0 ts=2013-03-08 07:56
  472k 2013/03/08 C:\cygwin64\bin\cygdb_sql-5.3.dll - os=4.0 img=0.0 sys=5.2
                  "cygdb_sql-5.3.dll" v0.0 ts=2013-03-08 07:58
  169k 2014/02/10 C:\cygwin64\bin\cygdialog-11.dll - os=4.0 img=0.0 sys=5.2
                  "cygdialog-11.dll" v0.0 ts=2014-02-10 01:24
  154k 2013/10/20 C:\cygwin64\bin\cygedit-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygedit-0.dll" v0.0 ts=2013-10-20 21:56
  158k 2013/04/23 C:\cygwin64\bin\cygEMF-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygEMF-1.dll" v0.0 ts=2013-04-23 06:39
  147k 2013/07/31 C:\cygwin64\bin\cygexpat-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygexpat-1.dll" v0.0 ts=2013-07-31 22:53
   72k 2013/09/02 C:\cygwin64\bin\cygexslt-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygexslt-0.dll" v0.0 ts=2013-09-02 17:55
   31k 2013/08/06 C:\cygwin64\bin\cygfam-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygfam-0.dll" v0.0 ts=2013-08-06 20:09
   22k 2013/05/12 C:\cygwin64\bin\cygffi-6.dll - os=4.0 img=0.0 sys=5.2
                  "cygffi-6.dll" v0.0 ts=2013-05-12 22:53
 1054k 2013/03/23 C:\cygwin64\bin\cygfftw3-3.dll - os=4.0 img=0.0 sys=5.2
                  "cygfftw3-3.dll" v0.0 ts=2013-03-23 09:03
 1014k 2013/03/23 C:\cygwin64\bin\cygfftw3f-3.dll - os=4.0 img=0.0 sys=5.2
                  "cygfftw3f-3.dll" v0.0 ts=2013-03-23 08:57
   24k 2013/03/23 C:\cygwin64\bin\cygfftw3f_threads-3.dll - os=4.0 img=0.0 sys=5.2
                  "cygfftw3f_threads-3.dll" v0.0 ts=2013-03-23 08:57
   23k 2013/03/23 C:\cygwin64\bin\cygfftw3_threads-3.dll - os=4.0 img=0.0 sys=5.2
                  "cygfftw3_threads-3.dll" v0.0 ts=2013-03-23 09:03
  210k 2013/08/05 C:\cygwin64\bin\cygfontconfig-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygfontconfig-1.dll" v0.0 ts=2013-08-05 07:59
   25k 2013/06/06 C:\cygwin64\bin\cygfontenc-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygfontenc-1.dll" v0.0 ts=2013-06-06 22:13
   53k 2013/05/06 C:\cygwin64\bin\cygformw-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygformw-10.dll" v0.0 ts=2013-05-06 08:10
  545k 2013/04/21 C:\cygwin64\bin\cygfpx-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygfpx-1.dll" v0.0 ts=2013-04-21 12:24
  585k 2014/03/31 C:\cygwin64\bin\cygfreetype-6.dll - os=4.0 img=0.0 sys=5.2
                  "cygfreetype-6.dll" v0.0 ts=1970-01-01 00:00
   41k 2014/04/04 C:\cygwin64\bin\cygFS-6.dll - os=4.0 img=0.0 sys=5.2
                  "cygFS-6.dll" v0.0 ts=1970-01-01 00:00
  103k 2013/04/24 C:\cygwin64\bin\cyggc-1.dll - os=4.0 img=0.0 sys=5.2
                  "cyggc-1.dll" v0.0 ts=2013-04-24 23:14
    8k 2013/04/24 C:\cygwin64\bin\cyggccpp-1.dll - os=4.0 img=0.0 sys=5.2
                  "cyggccpp-1.dll" v0.0 ts=2013-04-24 23:14
   67k 2014/01/29 C:\cygwin64\bin\cyggcc_s-seh-1.dll - os=4.0 img=0.0 sys=5.2
                  "cyggcc_s-seh-1.dll" v0.0 ts=2014-01-29 00:47
  176k 2014/03/20 C:\cygwin64\bin\cyggck-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cyggck-1-0.dll" v0.0 ts=2014-03-20 03:06
  156k 2013/08/06 C:\cygwin64\bin\cyggconf-2-4.dll - os=4.0 img=0.0 sys=5.2
                  "cyggconf-2-4.dll" v0.0 ts=2013-08-06 20:22
  470k 2014/03/20 C:\cygwin64\bin\cyggcr-base-3-1.dll - os=4.0 img=0.0 sys=5.2
                  "cyggcr-base-3-1.dll" v0.0 ts=2014-03-20 03:07
  357k 2014/03/20 C:\cygwin64\bin\cyggcr-ui-3-1.dll - os=4.0 img=0.0 sys=5.2
                  "cyggcr-ui-3-1.dll" v0.0 ts=2014-03-20 03:09
  472k 2013/03/13 C:\cygwin64\bin\cyggcrypt-11.dll - os=4.0 img=0.0 sys=5.2
                  "cyggcrypt-11.dll" v0.0 ts=2013-03-13 02:27
  239k 2013/04/21 C:\cygwin64\bin\cyggd-2.dll - os=4.0 img=0.0 sys=5.2
                  "cyggd-2.dll" v0.0 ts=2013-04-21 15:06
   29k 2013/03/11 C:\cygwin64\bin\cyggdbm-4.dll - os=4.0 img=0.0 sys=5.2
                  "cyggdbm-4.dll" v0.0 ts=2013-03-11 05:00
   12k 2013/03/11 C:\cygwin64\bin\cyggdbm_compat-4.dll - os=4.0 img=0.0 sys=5.2
                  "cyggdbm_compat-4.dll" v0.0 ts=2013-03-11 05:01
  547k 2014/03/30 C:\cygwin64\bin\cyggdk-3-0.dll - os=4.0 img=0.0 sys=5.2
                  "cyggdk-3-0.dll" v0.0 ts=2014-03-30 07:56
  602k 2014/03/28 C:\cygwin64\bin\cyggdk-x11-2.0-0.dll - os=4.0 img=0.0 sys=5.2
                  "cyggdk-x11-2.0-0.dll" v0.0 ts=2014-03-28 17:57
  215k 2014/03/12 C:\cygwin64\bin\cyggdk_pixbuf-2.0-0.dll - os=4.0 img=0.0 sys=5.2
                  "cyggdk_pixbuf-2.0-0.dll" v0.0 ts=2014-03-12 08:07
  183k 2013/06/24 C:\cygwin64\bin\cyggettextlib-0-18-1.dll - os=4.0 img=0.0 sys=5.2
                  "cyggettextlib-0-18-1.dll" v0.0 ts=2013-06-24 04:38
  252k 2013/06/24 C:\cygwin64\bin\cyggettextpo-0.dll - os=4.0 img=0.0 sys=5.2
                  "cyggettextpo-0.dll" v0.0 ts=2013-06-24 04:43
  227k 2013/06/24 C:\cygwin64\bin\cyggettextsrc-0-18-1.dll - os=4.0 img=0.0 sys=5.2
                  "cyggettextsrc-0-18-1.dll" v0.0 ts=2013-06-24 04:40
 1108k 2014/01/29 C:\cygwin64\bin\cyggfortran-3.dll - os=4.0 img=0.0 sys=5.2
                  "cyggfortran-3.dll" v0.0 ts=2014-01-29 01:27
   32k 2013/07/22 C:\cygwin64\bin\cyggif-4.dll - os=4.0 img=0.0 sys=5.2
                  "cyggif-4.dll" v0.0 ts=2013-07-22 05:17
 1189k 2014/04/02 C:\cygwin64\bin\cyggio-2.0-0.dll - os=4.0 img=0.0 sys=5.2
                  "cyggio-2.0-0.dll" v0.0 ts=1970-01-01 00:00
  396k 2013/10/09 C:\cygwin64\bin\cygGL-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygGL-1.dll" v0.0 ts=2013-10-09 03:31
  213k 2013/10/09 C:\cygwin64\bin\cygglapi-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygglapi-0.dll" v0.0 ts=2013-10-09 01:25
  904k 2014/04/02 C:\cygwin64\bin\cygglib-2.0-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygglib-2.0-0.dll" v0.0 ts=1970-01-01 00:00
  477k 2013/04/09 C:\cygwin64\bin\cygGLU-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygGLU-1.dll" v0.0 ts=2013-04-09 07:56
  220k 2013/04/09 C:\cygwin64\bin\cygglut-3.dll - os=4.0 img=0.0 sys=5.2
                  "cygglut-3.dll" v0.0 ts=2013-04-09 08:57
   15k 2014/04/02 C:\cygwin64\bin\cyggmodule-2.0-0.dll - os=4.0 img=0.0 sys=5.2
                  "cyggmodule-2.0-0.dll" v0.0 ts=1970-01-01 00:00
  516k 2014/04/05 C:\cygwin64\bin\cyggmp-10.dll - os=4.0 img=0.0 sys=5.2
                  "cyggmp-10.dll" v0.0 ts=1970-01-01 00:00
   23k 2014/04/05 C:\cygwin64\bin\cyggmpxx-4.dll - os=4.0 img=0.0 sys=5.2
                  "cyggmpxx-4.dll" v0.0 ts=1970-01-01 00:00
  126k 2014/03/12 C:\cygwin64\bin\cyggnome-keyring-0.dll - os=4.0 img=0.0 sys=5.2
                  "cyggnome-keyring-0.dll" v0.0 ts=2014-03-12 21:20
  904k 2013/05/29 C:\cygwin64\bin\cyggnutls-28.dll - os=4.0 img=0.0 sys=5.2
                  "cyggnutls-28.dll" v0.0 ts=2013-05-29 16:52
   84k 2013/05/29 C:\cygwin64\bin\cyggnutls-openssl-27.dll - os=4.0 img=0.0 sys=5.2
                  "cyggnutls-openssl-27.dll" v0.0 ts=2013-05-29 16:52
   83k 2013/05/29 C:\cygwin64\bin\cyggnutls-xssl-0.dll - os=4.0 img=0.0 sys=5.2
                  "cyggnutls-xssl-0.dll" v0.0 ts=2013-05-29 16:52
   41k 2013/05/29 C:\cygwin64\bin\cyggnutlsxx-28.dll - os=4.0 img=0.0 sys=5.2
                  "cyggnutlsxx-28.dll" v0.0 ts=2013-05-29 16:52
  277k 2014/04/02 C:\cygwin64\bin\cyggobject-2.0-0.dll - os=4.0 img=0.0 sys=5.2
                  "cyggobject-2.0-0.dll" v0.0 ts=1970-01-01 00:00
   46k 2014/01/29 C:\cygwin64\bin\cyggomp-1.dll - os=4.0 img=0.0 sys=5.2
                  "cyggomp-1.dll" v0.0 ts=2014-01-29 00:49
   17k 2013/03/13 C:\cygwin64\bin\cyggpg-error-0.dll - os=4.0 img=0.0 sys=5.2
                  "cyggpg-error-0.dll" v0.0 ts=2013-03-13 01:03
  116k 2013/08/05 C:\cygwin64\bin\cyggraphite2-3.dll - os=4.0 img=3.0 sys=5.2
                  "cyggraphite2-3.dll" v0.0 ts=2013-08-05 07:33
 7684k 2013/04/30 C:\cygwin64\bin\cyggs-9.dll - os=4.0 img=0.0 sys=5.2
                  "cyggs-9.dll" v0.0 ts=2013-04-30 12:31
 1998k 2013/08/14 C:\cygwin64\bin\cyggsl-0.dll - os=4.0 img=0.0 sys=5.2
                  "cyggsl-0.dll" v0.0 ts=2013-08-14 20:33
  247k 2013/08/14 C:\cygwin64\bin\cyggslcblas-0.dll - os=4.0 img=0.0 sys=5.2
                  "cyggslcblas-0.dll" v0.0 ts=2013-08-14 20:30
  198k 2014/03/20 C:\cygwin64\bin\cyggssapi-3.dll - os=4.0 img=0.0 sys=5.2
                  "cyggssapi-3.dll" v0.0 ts=2014-03-20 06:15
   10k 2014/04/02 C:\cygwin64\bin\cyggthread-2.0-0.dll - os=4.0 img=0.0 sys=5.2
                  "cyggthread-2.0-0.dll" v0.0 ts=1970-01-01 00:00
 4720k 2014/03/30 C:\cygwin64\bin\cyggtk-3-0.dll - os=4.0 img=0.0 sys=5.2
                  "cyggtk-3-0.dll" v0.0 ts=2014-03-30 08:08
 3929k 2014/03/28 C:\cygwin64\bin\cyggtk-x11-2.0-0.dll - os=4.0 img=0.0 sys=5.2
                  "cyggtk-x11-2.0-0.dll" v0.0 ts=2014-03-28 18:03
  178k 2014/03/23 C:\cygwin64\bin\cyggvfscommon-0.dll - os=4.0 img=0.0 sys=5.2
                  "cyggvfscommon-0.dll" v0.0 ts=2014-03-23 20:48
  316k 2014/01/09 C:\cygwin64\bin\cygharfbuzz-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygharfbuzz-0.dll" v0.0 ts=2014-01-09 07:16
   10k 2014/01/09 C:\cygwin64\bin\cygharfbuzz-icu-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygharfbuzz-icu-0.dll" v0.0 ts=2014-01-09 07:16
   14k 2014/03/20 C:\cygwin64\bin\cygheimbase-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygheimbase-1.dll" v0.0 ts=2014-03-20 04:52
   24k 2014/03/20 C:\cygwin64\bin\cygheimntlm-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygheimntlm-0.dll" v0.0 ts=2014-03-20 06:13
   29k 2013/03/14 C:\cygwin64\bin\cyghistory7.dll - os=4.0 img=0.0 sys=5.2
                  "cyghistory7.dll" v0.0 ts=2013-03-14 11:14
  166k 2013/05/14 C:\cygwin64\bin\cyghogweed-2.dll - os=4.0 img=0.0 sys=5.2
                  "cyghogweed-2.dll" v0.0 ts=2013-05-14 07:42
  236k 2014/03/20 C:\cygwin64\bin\cyghx509-5.dll - os=4.0 img=0.0 sys=5.2
                  "cyghx509-5.dll" v0.0 ts=2014-03-20 04:55
   78k 2013/03/15 C:\cygwin64\bin\cygICE-6.dll - os=4.0 img=0.0 sys=5.2
                  "cygICE-6.dll" v0.0 ts=2013-03-15 09:46
  360k 2013/07/29 C:\cygwin64\bin\cygicons-0.dll - os=4.0 img=1.4 sys=5.2
                  "cygicons-0.dll" v0.0 ts=2013-07-29 02:27
  998k 2013/03/07 C:\cygwin64\bin\cygiconv-2.dll - os=4.0 img=0.0 sys=5.2
                  "cygiconv-2.dll" v0.0 ts=2013-03-07 03:03
21806k 2013/06/25 C:\cygwin64\bin\cygicudata51.dll - os=4.0 img=0.0 sys=5.2
                  "cygicudata51.dll" v0.0 ts=2013-06-25 06:30
 1717k 2013/06/25 C:\cygwin64\bin\cygicui18n51.dll - os=4.0 img=0.0 sys=5.2
                  "cygicui18n51.dll" v0.0 ts=2013-06-25 06:28
   43k 2013/06/25 C:\cygwin64\bin\cygicuio51.dll - os=4.0 img=0.0 sys=5.2
                  "cygicuio51.dll" v0.0 ts=2013-06-25 06:30
  305k 2013/06/25 C:\cygwin64\bin\cygicule51.dll - os=4.0 img=0.0 sys=5.2
                  "cygicule51.dll" v0.0 ts=2013-06-25 06:28
   38k 2013/06/25 C:\cygwin64\bin\cygiculx51.dll - os=4.0 img=0.0 sys=5.2
                  "cygiculx51.dll" v0.0 ts=2013-06-25 06:28
   49k 2013/06/25 C:\cygwin64\bin\cygicutest51.dll - os=4.0 img=0.0 sys=5.2
                  "cygicutest51.dll" v0.0 ts=2013-06-25 06:29
  140k 2013/06/25 C:\cygwin64\bin\cygicutu51.dll - os=4.0 img=0.0 sys=5.2
                  "cygicutu51.dll" v0.0 ts=2013-06-25 06:29
 1231k 2013/06/25 C:\cygwin64\bin\cygicuuc51.dll - os=4.0 img=0.0 sys=5.2
                  "cygicuuc51.dll" v0.0 ts=2013-06-25 06:27
  195k 2013/04/05 C:\cygwin64\bin\cygidn-11.dll - os=4.0 img=0.0 sys=5.2
                  "cygidn-11.dll" v0.0 ts=2013-04-05 09:58
   38k 2013/06/24 C:\cygwin64\bin\cygintl-8.dll - os=4.0 img=0.0 sys=5.2
                  "cygintl-8.dll" v0.0 ts=2013-06-24 04:36
  294k 2013/09/09 C:\cygwin64\bin\cygiodbc-2.dll - os=4.0 img=0.0 sys=5.2
                  "cygiodbc-2.dll" v0.0 ts=2013-09-09 16:36
   66k 2013/09/09 C:\cygwin64\bin\cygiodbcinst-2.dll - os=4.0 img=0.0 sys=5.2
                  "cygiodbcinst-2.dll" v0.0 ts=2013-09-09 16:35
  888k 2013/05/05 C:\cygwin64\bin\cygisl-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygisl-10.dll" v0.0 ts=2013-05-05 16:36
  271k 2013/04/11 C:\cygwin64\bin\cygjasper-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygjasper-1.dll" v0.0 ts=2013-04-11 08:18
   48k 2013/04/26 C:\cygwin64\bin\cygjbig-2.dll - os=4.0 img=0.0 sys=5.2
                  "cygjbig-2.dll" v0.0 ts=2013-04-26 06:24
  236k 2013/04/12 C:\cygwin64\bin\cygjpeg-8.dll - os=4.0 img=0.0 sys=5.2
                  "cygjpeg-8.dll" v0.0 ts=2013-04-12 05:00
   23k 2014/03/20 C:\cygwin64\bin\cygkafs-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygkafs-0.dll" v0.0 ts=2014-03-20 06:13
   83k 2013/05/30 C:\cygwin64\bin\cygkpathsea-6.dll - os=4.0 img=0.0 sys=5.2
                  "cygkpathsea-6.dll" v0.0 ts=2013-05-30 15:10
  403k 2014/03/20 C:\cygwin64\bin\cygkrb5-26.dll - os=4.0 img=0.0 sys=5.2
                  "cygkrb5-26.dll" v0.0 ts=2014-03-20 06:12
   44k 2013/06/18 C:\cygwin64\bin\cyglber-2-4-2.dll - os=4.0 img=0.0 sys=5.2
                  "cyglber-2-4-2.dll" v0.0 ts=2013-06-17 21:00
  188k 2013/04/10 C:\cygwin64\bin\cyglcms-1.dll - os=4.0 img=0.0 sys=5.2
                  "cyglcms-1.dll" v0.0 ts=2013-04-10 12:13
  283k 2013/09/03 C:\cygwin64\bin\cyglcms2-2.dll - os=4.0 img=0.0 sys=5.2
                  "cyglcms2-2.dll" v0.0 ts=2013-09-03 13:56
  243k 2013/06/18 C:\cygwin64\bin\cygldap-2-4-2.dll - os=4.0 img=0.0 sys=5.2
                  "cygldap-2-4-2.dll" v0.0 ts=2013-06-17 21:00
  260k 2013/06/18 C:\cygwin64\bin\cygldap_r-2-4-2.dll - os=4.0 img=0.0 sys=5.2
                  "cygldap_r-2-4-2.dll" v0.0 ts=2013-06-17 21:01
    6k 2014/04/10 C:\cygwin64\bin\cyglsa64.dll - os=4.0 img=0.0 sys=5.2
                  "cyglsa64.dll" v0.0 ts=2014-04-10 09:23
   34k 2013/05/27 C:\cygwin64\bin\cygltdl-7.dll - os=4.0 img=0.0 sys=5.2
                  "cygltdl-7.dll" v0.0 ts=2013-05-27 07:22
  129k 2013/03/07 C:\cygwin64\bin\cyglzma-5.dll - os=4.0 img=0.0 sys=5.2
                  "cyglzma-5.dll" v0.0 ts=2013-03-07 10:20
  124k 2013/03/19 C:\cygwin64\bin\cyglzo2-2.dll - os=4.0 img=0.0 sys=5.2
                  "cyglzo2-2.dll" v0.0 ts=2013-03-19 05:35
  107k 2014/03/27 C:\cygwin64\bin\cygmagic-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygmagic-1.dll" v0.0 ts=1970-01-01 00:00
  291k 2013/10/12 C:\cygwin64\bin\cygMagick++-5.dll - os=4.0 img=0.0 sys=5.2
                  "cygMagick++-5.dll" v0.0 ts=2013-10-12 18:21
 4157k 2013/10/12 C:\cygwin64\bin\cygMagickCore-5.dll - os=4.0 img=0.0 sys=5.2
                  "cygMagickCore-5.dll" v0.0 ts=2013-10-12 18:17
 1088k 2013/10/12 C:\cygwin64\bin\cygMagickWand-5.dll - os=4.0 img=0.0 sys=5.2
                  "cygMagickWand-5.dll" v0.0 ts=2013-10-12 18:19
  132k 2014/01/21 C:\cygwin64\bin\cygmcpp-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygmcpp-0.dll" v0.0 ts=2014-01-21 18:41
   28k 2013/05/06 C:\cygwin64\bin\cygmenuw-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygmenuw-10.dll" v0.0 ts=2013-05-06 08:10
   42k 2013/08/12 C:\cygwin64\bin\cygmetalink-3.dll - os=4.0 img=0.0 sys=5.2
                  "cygmetalink-3.dll" v0.0 ts=2013-08-13 00:02
  331k 2013/09/03 C:\cygwin64\bin\cygming-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygming-1.dll" v0.0 ts=2013-09-03 12:51
   87k 2014/04/05 C:\cygwin64\bin\cygmpc-3.dll - os=4.0 img=0.0 sys=5.2
                  "cygmpc-3.dll" v0.0 ts=1970-01-01 00:00
  319k 2013/05/05 C:\cygwin64\bin\cygmpfr-4.dll - os=4.0 img=0.0 sys=5.2
                  "cygmpfr-4.dll" v0.0 ts=2013-05-05 13:40
  119k 2013/05/02 C:\cygwin64\bin\cygMrm-4.dll - os=4.0 img=0.0 sys=5.2
                  "cygMrm-4.dll" v0.0 ts=2013-05-02 09:20
 2833k 2013/12/06 C:\cygwin64\bin\cygmysqlclient-18.dll - os=4.0 img=18.0 sys=5.2
                  "cygmysqlclient-18.dll" v0.0 ts=2013-12-06 01:49
  447k 2014/03/27 C:\cygwin64\bin\cygnativeGLthunk.dll - os=4.0 img=0.0 sys=5.2
                  "cygnativeGLthunk.dll" v0.0 ts=2014-03-27 20:33
   52k 2013/05/06 C:\cygwin64\bin\cygncurses++w-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygncurses++w-10.dll" v0.0 ts=2013-05-06 08:14
  295k 2013/05/06 C:\cygwin64\bin\cygncursesw-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygncursesw-10.dll" v0.0 ts=2013-05-06 08:08
  126k 2013/04/24 C:\cygwin64\bin\cygneon-27.dll - os=4.0 img=0.0 sys=5.2
                  "cygneon-27.dll" v0.0 ts=2013-04-24 08:25
  188k 2013/06/05 C:\cygwin64\bin\cygnetpbm-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygnetpbm-10.dll" v0.0 ts=2013-06-05 16:55
  177k 2013/05/14 C:\cygwin64\bin\cygnettle-4.dll - os=4.0 img=0.0 sys=5.2
                  "cygnettle-4.dll" v0.0 ts=2013-05-14 07:42
   58k 2013/06/04 C:\cygwin64\bin\cygogrove-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygogrove-1.dll" v0.0 ts=2013-06-04 21:36
  123k 2014/01/31 C:\cygwin64\bin\cygopenjpeg-1.dll - os=4.0 img=1.5 sys=5.2
                  "cygopenjpeg-1.dll" v0.0 ts=2014-01-31 05:12
 3166k 2013/10/09 C:\cygwin64\bin\cygOSMesa-8.dll - os=4.0 img=0.0 sys=5.2
                  "cygOSMesa-8.dll" v0.0 ts=2013-10-09 03:31
 1486k 2013/06/04 C:\cygwin64\bin\cygosp-5.dll - os=4.0 img=0.0 sys=5.2
                  "cygosp-5.dll" v0.0 ts=2013-06-04 21:16
  344k 2013/06/04 C:\cygwin64\bin\cygospgrove-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygospgrove-1.dll" v0.0 ts=2013-06-04 21:36
 1810k 2013/06/04 C:\cygwin64\bin\cygostyle-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygostyle-1.dll" v0.0 ts=2013-06-04 21:37
  207k 2014/03/13 C:\cygwin64\bin\cygp11-kit-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygp11-kit-0.dll" v0.0 ts=2014-03-13 03:35
   13k 2013/05/06 C:\cygwin64\bin\cygpanelw-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygpanelw-10.dll" v0.0 ts=2013-05-06 08:09
  261k 2014/03/20 C:\cygwin64\bin\cygpango-1.0-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygpango-1.0-0.dll" v0.0 ts=2014-03-20 10:59
   41k 2014/03/20 C:\cygwin64\bin\cygpangocairo-1.0-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygpangocairo-1.0-0.dll" v0.0 ts=2014-03-20 10:59
   69k 2014/03/20 C:\cygwin64\bin\cygpangoft2-1.0-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygpangoft2-1.0-0.dll" v0.0 ts=2014-03-20 10:59
   27k 2014/03/20 C:\cygwin64\bin\cygpangoxft-1.0-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygpangoxft-1.0-0.dll" v0.0 ts=2014-03-20 10:59
   11k 2013/07/23 C:\cygwin64\bin\cygpaper-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygpaper-1.dll" v0.0 ts=2013-07-23 05:40
  271k 2014/03/12 C:\cygwin64\bin\cygpcre-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygpcre-1.dll" v0.0 ts=2014-03-12 02:35
  247k 2014/03/12 C:\cygwin64\bin\cygpcre16-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygpcre16-0.dll" v0.0 ts=2014-03-12 02:35
  243k 2014/03/12 C:\cygwin64\bin\cygpcre32-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygpcre32-0.dll" v0.0 ts=2014-03-12 02:35
   30k 2014/03/12 C:\cygwin64\bin\cygpcrecpp-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygpcrecpp-0.dll" v0.0 ts=2014-03-12 02:35
   10k 2014/03/12 C:\cygwin64\bin\cygpcreposix-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygpcreposix-0.dll" v0.0 ts=2014-03-12 02:35
 1580k 2013/03/11 C:\cygwin64\bin\cygperl5_14.dll - os=4.0 img=0.0 sys=5.2
                  "cygperl5_14.dll" v0.0 ts=2013-03-12 00:25
  656k 2014/01/10 C:\cygwin64\bin\cygpixman-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygpixman-1-0.dll" v0.0 ts=2014-01-10 01:32
  147k 2013/03/19 C:\cygwin64\bin\cygpng15-15.dll - os=4.0 img=0.0 sys=5.2
                  "cygpng15-15.dll" v0.0 ts=2013-03-19 02:58
 1847k 2013/06/05 C:\cygwin64\bin\cygpoppler-28.dll - os=4.0 img=0.0 sys=5.2
                  "cygpoppler-28.dll" v0.0 ts=2013-06-05 06:22
 1866k 2014/01/13 C:\cygwin64\bin\cygpoppler-37.dll - os=4.0 img=0.0 sys=5.2
                  "cygpoppler-37.dll" v0.0 ts=2014-01-13 04:09
 1897k 2014/02/23 C:\cygwin64\bin\cygpoppler-44.dll - os=4.0 img=0.0 sys=5.2
                  "cygpoppler-44.dll" v0.0 ts=2014-02-23 20:36
   41k 2013/10/21 C:\cygwin64\bin\cygpopt-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygpopt-0.dll" v0.0 ts=2013-10-21 21:52
  145k 2014/02/02 C:\cygwin64\bin\cygpq-5.dll - os=4.0 img=0.0 sys=5.2
                  "cygpq-5.dll" v0.0 ts=2014-02-02 21:42
  122k 2013/04/21 C:\cygwin64\bin\cygproxy-1.dll - os=4.0 img=1.0 sys=5.2
                  "cygproxy-1.dll" v0.0 ts=2013-04-21 10:24
    8k 2013/04/30 C:\cygwin64\bin\cygpspell-15.dll - os=4.0 img=0.0 sys=5.2
                  "cygpspell-15.dll" v0.0 ts=2013-04-30 08:12
  349k 2013/04/28 C:\cygwin64\bin\cygpstoedit-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygpstoedit-0.dll" v0.0 ts=2013-04-28 09:25
   38k 2013/05/30 C:\cygwin64\bin\cygptexenc-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygptexenc-1.dll" v0.0 ts=2013-05-30 15:10
   15k 2013/10/24 C:\cygwin64\bin\cygpyglib-2.0-python2.7-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygpyglib-2.0-python2.7-0.dll" v0.0 ts=2013-10-24 20:39
  302k 2014/01/29 C:\cygwin64\bin\cygquadmath-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygquadmath-0.dll" v0.0 ts=2014-01-29 01:16
   83k 2013/06/05 C:\cygwin64\bin\cygrarian-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygrarian-0.dll" v0.0 ts=2013-06-05 01:24
  193k 2013/03/14 C:\cygwin64\bin\cygreadline7.dll - os=4.0 img=0.0 sys=5.2
                  "cygreadline7.dll" v0.0 ts=2013-03-14 11:14
   57k 2014/03/20 C:\cygwin64\bin\cygroken-18.dll - os=4.0 img=0.0 sys=5.2
                  "cygroken-18.dll" v0.0 ts=2014-03-20 04:53
  200k 2014/03/12 C:\cygwin64\bin\cygrsvg-2-2.dll - os=4.0 img=0.0 sys=5.2
                  "cygrsvg-2-2.dll" v0.0 ts=2014-03-13 00:52
 1816k 2014/02/06 C:\cygwin64\bin\cygruby191.dll - os=4.0 img=0.0 sys=5.2
                  "cygruby191.dll" v1.9 ts=2014-02-06 21:07
   96k 2014/01/16 C:\cygwin64\bin\cygsasl2-3.dll - os=4.0 img=0.0 sys=5.2
                  "cygsasl2-3.dll" v0.0 ts=2014-01-16 17:34
  248k 2014/03/12 C:\cygwin64\bin\cygsecret-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygsecret-1-0.dll" v0.0 ts=2014-03-12 21:29
   82k 2013/12/13 C:\cygwin64\bin\cygserf-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygserf-1-0.dll" v0.0 ts=2013-12-13 00:46
   28k 2014/01/14 C:\cygwin64\bin\cygSM-6.dll - os=4.0 img=0.0 sys=5.2
                  "cygSM-6.dll" v0.0 ts=2014-01-14 23:23
  564k 2014/04/02 C:\cygwin64\bin\cygsoup-2.4-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygsoup-2.4-1.dll" v0.0 ts=1970-01-01 00:00
   12k 2014/04/02 C:\cygwin64\bin\cygsoup-gnome-2.4-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygsoup-gnome-2.4-1.dll" v0.0 ts=1970-01-01 00:00
  677k 2013/05/29 C:\cygwin64\bin\cygsource-highlight-4.dll - os=4.0 img=0.0 sys=5.2
                  "cygsource-highlight-4.dll" v0.0 ts=2013-05-30 00:22
  721k 2014/03/11 C:\cygwin64\bin\cygsqlite3-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygsqlite3-0.dll" v0.0 ts=2014-03-11 21:05
  141k 2013/03/11 C:\cygwin64\bin\cygssh2-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygssh2-1.dll" v0.0 ts=2013-03-11 11:42
  376k 2014/02/05 C:\cygwin64\bin\cygssl-1.0.0.dll - os=4.0 img=0.0 sys=5.2
                  "cygssl-1.0.0.dll" v0.0 ts=2014-02-05 10:49
   11k 2014/01/29 C:\cygwin64\bin\cygssp-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygssp-0.dll" v0.0 ts=2014-01-29 01:14
  892k 2014/01/29 C:\cygwin64\bin\cygstdc++-6.dll - os=4.0 img=0.0 sys=5.2
                  "cygstdc++-6.dll" v0.0 ts=2014-01-29 00:57
  356k 2014/02/22 C:\cygwin64\bin\cygsvn_client-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygsvn_client-1-0.dll" v0.0 ts=2014-02-22 18:35
   63k 2014/02/22 C:\cygwin64\bin\cygsvn_delta-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygsvn_delta-1-0.dll" v0.0 ts=2014-02-22 18:34
   70k 2014/02/22 C:\cygwin64\bin\cygsvn_diff-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygsvn_diff-1-0.dll" v0.0 ts=2014-02-22 18:34
   30k 2014/02/22 C:\cygwin64\bin\cygsvn_fs-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygsvn_fs-1-0.dll" v0.0 ts=2014-02-22 18:34
  150k 2014/02/22 C:\cygwin64\bin\cygsvn_fs_base-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygsvn_fs_base-1-0.dll" v0.0 ts=2014-02-22 18:34
  180k 2014/02/22 C:\cygwin64\bin\cygsvn_fs_fs-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygsvn_fs_fs-1-0.dll" v0.0 ts=2014-02-22 18:34
   10k 2014/02/22 C:\cygwin64\bin\cygsvn_fs_util-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygsvn_fs_util-1-0.dll" v0.0 ts=2014-02-22 18:34
   45k 2014/02/22 C:\cygwin64\bin\cygsvn_ra-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygsvn_ra-1-0.dll" v0.0 ts=2014-02-22 18:35
   30k 2014/02/22 C:\cygwin64\bin\cygsvn_ra_local-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygsvn_ra_local-1-0.dll" v0.0 ts=2014-02-22 18:34
  162k 2014/02/22 C:\cygwin64\bin\cygsvn_ra_serf-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygsvn_ra_serf-1-0.dll" v0.0 ts=2014-02-22 18:34
   94k 2014/02/22 C:\cygwin64\bin\cygsvn_ra_svn-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygsvn_ra_svn-1-0.dll" v0.0 ts=2014-02-22 18:34
  182k 2014/02/22 C:\cygwin64\bin\cygsvn_repos-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygsvn_repos-1-0.dll" v0.0 ts=2014-02-22 18:34
  380k 2014/02/22 C:\cygwin64\bin\cygsvn_subr-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygsvn_subr-1-0.dll" v0.0 ts=2014-02-22 18:34
  618k 2014/02/22 C:\cygwin64\bin\cygsvn_wc-1-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygsvn_wc-1-0.dll" v0.0 ts=2014-02-22 18:34
  242k 2013/04/26 C:\cygwin64\bin\cygt1-5.dll - os=4.0 img=0.0 sys=5.2
                  "cygt1-5.dll" v0.0 ts=2013-04-25 17:35
   69k 2013/04/22 C:\cygwin64\bin\cygtasn1-6.dll - os=4.0 img=0.0 sys=5.2
                  "cygtasn1-6.dll" v0.0 ts=2013-04-22 01:25
   31k 2013/04/12 C:\cygwin64\bin\cygthai-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygthai-0.dll" v0.0 ts=2013-04-12 12:02
   51k 2013/05/06 C:\cygwin64\bin\cygticw-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygticw-10.dll" v0.0 ts=2013-05-06 08:08
  359k 2013/04/24 C:\cygwin64\bin\cygtiff-5.dll - os=4.0 img=0.0 sys=5.2
                  "cygtiff-5.dll" v0.0 ts=2013-04-24 06:30
   10k 2013/04/24 C:\cygwin64\bin\cygtiffxx-5.dll - os=4.0 img=0.0 sys=5.2
                  "cygtiffxx-5.dll" v0.0 ts=2013-04-24 06:30
  362k 2013/05/02 C:\cygwin64\bin\cygUil-4.dll - os=4.0 img=0.0 sys=5.2
                  "cygUil-4.dll" v0.0 ts=2013-05-02 09:21
 1154k 2013/04/20 C:\cygwin64\bin\cygunistring-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygunistring-0.dll" v0.0 ts=2013-04-20 19:38
  166k 2013/06/12 C:\cygwin64\bin\cygustr-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygustr-1.dll" v0.0 ts=2013-06-12 09:42
   15k 2013/03/11 C:\cygwin64\bin\cyguuid-1.dll - os=4.0 img=0.0 sys=5.2
                  "cyguuid-1.dll" v0.0 ts=2013-03-11 03:07
 3069k 2013/07/19 C:\cygwin64\bin\cygwin1-20130719.dll - os=4.0 img=0.0 sys=5.2
                  "cygwin1.dll" v0.0 ts=2013-07-19 13:36
 3072k 2014/04/02 C:\cygwin64\bin\cygwin1-20140329.dll - os=4.0 img=0.0 sys=5.2
                  "cygwin1.dll" v0.0 ts=1970-01-01 00:00
 3110k 2014/04/10 C:\cygwin64\bin\cygwin1-20140410.dll - os=4.0 img=0.0 sys=5.2
                  "cygwin1.dll" v0.0 ts=1970-01-01 00:00
 3073k 2014/04/07 C:\cygwin64\bin\cygwin1-prev.dll - os=4.0 img=0.0 sys=5.2
                  "cygwin1.dll" v0.0 ts=1970-01-01 00:00
  161k 2014/03/20 C:\cygwin64\bin\cygwind-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygwind-0.dll" v0.0 ts=2014-03-20 04:53
   30k 2013/11/15 C:\cygwin64\bin\cygwrap-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygwrap-0.dll" v0.0 ts=2013-11-15 19:58
 1120k 2014/01/10 C:\cygwin64\bin\cygX11-6.dll - os=4.0 img=0.0 sys=5.2
                  "cygX11-6.dll" v0.0 ts=2014-01-10 01:15
    8k 2014/01/10 C:\cygwin64\bin\cygX11-xcb-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygX11-xcb-1.dll" v0.0 ts=2014-01-10 01:15
   12k 2013/06/06 C:\cygwin64\bin\cygXau-6.dll - os=4.0 img=0.0 sys=5.2
                  "cygXau-6.dll" v0.0 ts=2013-06-06 06:23
  368k 2014/01/15 C:\cygwin64\bin\cygXaw-7.dll - os=4.0 img=0.0 sys=5.2
                  "cygXaw-7.dll" v0.0 ts=2014-01-15 02:53
  296k 2013/04/08 C:\cygwin64\bin\cygXaw3d-8.dll - os=4.0 img=0.0 sys=5.2
                  "cygXaw3d-8.dll" v0.0 ts=2013-04-08 22:20
   97k 2013/08/14 C:\cygwin64\bin\cygxcb-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygxcb-1.dll" v0.0 ts=2013-08-14 19:30
   70k 2013/08/14 C:\cygwin64\bin\cygxcb-glx-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygxcb-glx-0.dll" v0.0 ts=2013-08-14 19:31
   17k 2013/03/17 C:\cygwin64\bin\cygxcb-icccm-4.dll - os=4.0 img=0.0 sys=5.2
                  "cygxcb-icccm-4.dll" v0.0 ts=2013-03-17 22:48
   16k 2013/03/17 C:\cygwin64\bin\cygxcb-image-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygxcb-image-0.dll" v0.0 ts=2013-03-17 22:42
   31k 2013/08/14 C:\cygwin64\bin\cygxcb-render-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygxcb-render-0.dll" v0.0 ts=2013-08-14 19:31
   11k 2013/08/14 C:\cygwin64\bin\cygxcb-shm-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygxcb-shm-0.dll" v0.0 ts=2013-08-14 19:31
   17k 2013/03/17 C:\cygwin64\bin\cygxcb-util-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygxcb-util-1.dll" v0.0 ts=2013-03-17 22:33
   11k 2013/03/18 C:\cygwin64\bin\cygXcomposite-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygXcomposite-1.dll" v0.0 ts=2013-03-18 23:05
   34k 2013/06/06 C:\cygwin64\bin\cygXcursor-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygXcursor-1.dll" v0.0 ts=2013-06-06 21:15
   10k 2013/04/08 C:\cygwin64\bin\cygXdamage-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygXdamage-1.dll" v0.0 ts=2013-04-08 22:24
   21k 2013/03/13 C:\cygwin64\bin\cygXdmcp-6.dll - os=4.0 img=0.0 sys=5.2
                  "cygXdmcp-6.dll" v0.0 ts=2013-03-13 04:58
   56k 2013/06/06 C:\cygwin64\bin\cygXext-6.dll - os=4.0 img=0.0 sys=5.2
                  "cygXext-6.dll" v0.0 ts=2013-06-06 10:04
   19k 2013/06/06 C:\cygwin64\bin\cygXfixes-3.dll - os=4.0 img=0.0 sys=5.2
                  "cygXfixes-3.dll" v0.0 ts=2013-06-06 20:27
  210k 2014/04/04 C:\cygwin64\bin\cygXfont-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygXfont-1.dll" v0.0 ts=1970-01-01 00:00
   73k 2013/03/14 C:\cygwin64\bin\cygXft-2.dll - os=4.0 img=0.0 sys=5.2
                  "cygXft-2.dll" v0.0 ts=2013-03-14 05:18
   56k 2013/07/29 C:\cygwin64\bin\cygXi-6.dll - os=4.0 img=0.0 sys=5.2
                  "cygXi-6.dll" v0.0 ts=2013-07-29 07:30
   10k 2013/06/06 C:\cygwin64\bin\cygXinerama-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygXinerama-1.dll" v0.0 ts=2013-06-06 21:33
  125k 2013/04/08 C:\cygwin64\bin\cygxkbfile-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygxkbfile-1.dll" v0.0 ts=2013-04-08 21:24
 2275k 2013/05/02 C:\cygwin64\bin\cygXm-4.dll - os=4.0 img=0.0 sys=5.2
                  "cygXm-4.dll" v0.0 ts=2013-05-02 09:19
 1212k 2013/04/21 C:\cygwin64\bin\cygxml2-2.dll - os=4.0 img=0.0 sys=5.2
                  "cygxml2-2.dll" v0.0 ts=2013-04-21 05:57
   85k 2014/01/15 C:\cygwin64\bin\cygXmu-6.dll - os=4.0 img=0.0 sys=5.2
                  "cygXmu-6.dll" v0.0 ts=2014-01-15 02:27
   14k 2014/01/15 C:\cygwin64\bin\cygXmuu-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygXmuu-1.dll" v0.0 ts=2014-01-15 02:27
   59k 2014/01/15 C:\cygwin64\bin\cygXpm-4.dll - os=4.0 img=0.0 sys=5.2
                  "cygXpm-4.dll" v0.0 ts=2014-01-15 00:59
   54k 2013/07/01 C:\cygwin64\bin\cygXpm-noX-4.dll - os=4.0 img=0.0 sys=5.2
                  "cygXpm-noX-4.dll" v0.0 ts=2013-07-01 12:24
   34k 2014/01/14 C:\cygwin64\bin\cygXrandr-2.dll - os=4.0 img=0.0 sys=5.2
                  "cygXrandr-2.dll" v0.0 ts=2014-01-14 23:56
   35k 2013/06/14 C:\cygwin64\bin\cygXrender-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygXrender-1.dll" v0.0 ts=2013-06-14 09:29
  207k 2013/09/02 C:\cygwin64\bin\cygxslt-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygxslt-1.dll" v0.0 ts=2013-09-02 17:55
   12k 2013/03/14 C:\cygwin64\bin\cygXss-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygXss-1.dll" v0.0 ts=2013-03-14 04:07
  320k 2013/06/06 C:\cygwin64\bin\cygXt-6.dll - os=4.0 img=0.0 sys=5.2
                  "cygXt-6.dll" v0.0 ts=2013-06-06 20:43
   21k 2013/06/06 C:\cygwin64\bin\cygXtst-6.dll - os=4.0 img=0.0 sys=5.2
                  "cygXtst-6.dll" v0.0 ts=2013-06-06 20:36
  120k 2014/03/30 C:\cygwin64\bin\cygyaml-0-2.dll - os=4.0 img=0.0 sys=5.2
                  "cygyaml-0-2.dll" v0.0 ts=2014-03-30 06:16
   79k 2013/05/09 C:\cygwin64\bin\cygz.dll - os=4.0 img=0.0 sys=5.2
                  "cygz.dll" v0.0 ts=2013-05-09 22:20
   24k 2013/05/30 C:\cygwin64\bin\cygzzip-0-13.dll - os=4.0 img=0.0 sys=5.2
                  "cygzzip-0-13.dll" v0.0 ts=2013-05-30 03:34
   12k 2013/05/30 C:\cygwin64\bin\cygzzipfseeko-0-13.dll - os=4.0 img=0.0 sys=5.2
                  "cygzzipfseeko-0-13.dll" v0.0 ts=2013-05-30 03:34
   15k 2013/05/30 C:\cygwin64\bin\cygzzipmmapped-0-13.dll - os=4.0 img=0.0 sys=5.2
                  "cygzzipmmapped-0-13.dll" v0.0 ts=2013-05-30 03:34
    9k 2013/05/30 C:\cygwin64\bin\cygzzipwrap-0-13.dll - os=4.0 img=0.0 sys=5.2
                  "cygzzipwrap-0-13.dll" v0.0 ts=2013-05-30 03:34
 3110k 2014/04/10 C:\cygwin64\bin\cygwin1.dll - os=4.0 img=0.0 sys=5.2
                  "cygwin1.dll" v0.0 ts=1970-01-01 00:00
    Cygwin DLL version info:
        DLL version: 1.7.29
        DLL epoch: 19
        DLL old termios: 5
        DLL malloc env: 28
        Cygwin conv: 181
        API major: 0
        API minor: 272
        Shared data: 5
        DLL identifier: cygwin1
        Mount registry: 3
        Cygwin registry name: Cygwin
        Program options name: Program Options
        Installations name: Installations
        Cygdrive default prefix: 
        Build date: 
        Snapshot date: 20140410-08:22:10
        Shared id: cygwin1S5

  443k 2013/11/17 C:\cygwin64\lib\lapack\cygblas-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygblas-0.dll" v0.0 ts=2013-11-17 14:09
 5626k 2013/11/17 C:\cygwin64\lib\lapack\cyglapack-0.dll - os=4.0 img=0.0 sys=5.2
                  "cyglapack-0.dll" v0.0 ts=2013-11-17 14:09

Service             : cygserver           
Display name        : CYGWIN cygserver
Current State       : Running
Controls Accepted   : Stop
Command             : /usr/sbin/cygserver
stdin path          : /dev/null
stdout path         : /var/log/cygserver.log
stderr path         : /var/log/cygserver.log
Process Type        : Own Process
Startup             : Automatic
Account             : LocalSystem

Service             : sshd                
Display name        : CYGWIN sshd
Current State       : Running
Controls Accepted   : Stop
Command             : /usr/sbin/sshd -D
stdin path          : /dev/null
stdout path         : /var/log/sshd.log
stderr path         : /var/log/sshd.log
Process Type        : Own Process
Startup             : Automatic
Dependencies        : tcpip
Account             : .\cyg_server


Cygwin Package Information
Last downloaded files to: C:\downloads\cygwin
Last downloaded files from: http://sanibeltranquility.com/cygwin/

Package                               Version                Status
_autorebase                           000129-1               OK
_update-info-dir                      00268-1                OK
alternatives                          1.3.30c-10             OK
appdata-tools                         0.1.7-1                OK
aspell                                0.60.6.1-1             OK
aspell-en                             7.1.0-1                OK
asymptote                             2.23-1                 OK
at-spi2-core                          2.10.2-1               OK
autoconf                              13-1                   OK
autoconf2.1                           2.13-12                OK
autoconf2.5                           2.69-2                 OK
automake                              9-1                    OK
automake1.10                          1.10.3-2               OK
automake1.11                          1.11.6-2               OK
automake1.12                          1.12.6-2               OK
automake1.13                          1.13.4-1               OK
automake1.14                          1.14-1                 OK
automake1.4                           1.4p6-11               OK
automake1.5                           1.5-11                 OK
automake1.6                           1.6.3-12               OK
automake1.7                           1.7.9-11               OK
automake1.8                           1.8.5-11               OK
automake1.9                           1.9.6-11               OK
base-cygwin                           3.3-1                  OK
base-files                            4.1-1                  OK
bash                                  4.1.11-2               OK
bc                                    1.06.95-1              OK
bdftopcf                              1.0.4-3                OK
biber                                 1.5-1                  OK
binutils                              2.24.51-2              OK
bison                                 2.7.1-1                OK
build-docbook-catalog                 1.5-2                  OK
bzip2                                 1.0.6-2                OK
bzr                                   2.6b2-1                OK
bzr-fastimport                        0.13.0-1               OK
ca-certificates                       1.97-1                 OK
cocom                                 0.996-1                OK
compositeproto                        0.4.2-1                OK
coreutils                             8.15-3                 OK
crypt                                 1.1-1                  OK
csih                                  0.9.7-1                OK
curl                                  7.34.0-1               OK
cvs                                   1.11.23-1              OK
cygcheck-dep                          2.0-1                  OK
cygport                               0.15.0-1               OK
cygrunsrv                             1.50-1                 OK
cygutils                              1.4.14-1               OK
cygutils-extra                        1.4.14-1               OK
cygutils-x11                          1.4.14-1               OK
cygwin                                1.7.29-2               OK
cygwin-debuginfo                      1.7.29-2               OK
damageproto                           1.2.1-1                OK
dash                                  0.5.7-4                OK
dblatex                               0.3.4-1                OK
dbus                                  1.6.18-1               OK
dconf-service                         0.18.0-1               OK
desktop-file-utils                    0.21-1                 OK
dialog                                1.2-20140112-1         OK
diffstat                              1.58-1                 OK
diffutils                             3.3-1                  OK
docbook-dsssl                         1.79-2                 OK
docbook-xml412                        4.1.2-2                OK
docbook-xml42                         4.2-4                  OK
docbook-xml43                         4.3-2                  OK
docbook-xml44                         4.4-2                  OK
docbook-xsl                           1.77.1-1               OK
dos2unix                              6.0.4-1                OK
dri-drivers                           8.0.5-5                OK
ed                                    1.9-1                  OK
editrights                            1.02-1                 OK
emacs                                 24.3.50-3              OK
emacs-auctex                          11.87-2                OK
emacs-debuginfo                       24.3.50-3              OK
emacs-el                              24.3.50-3              OK
emacs-w32                             24.3.50-3              OK
emacs-X11                             24.3.50-3              OK
file                                  5.18-1                 OK
findutils                             4.5.11-1               OK
fixesproto                            5.0-1                  OK
flex                                  2.5.37-3               OK
font-adobe-dpi100                     1.0.2-1                OK
font-adobe-dpi75                      1.0.2-1                OK
font-adobe-utopia-dpi75               1.0.3-1                OK
font-alias                            1.0.3-1                OK
font-bh-dpi75                         1.0.2-1                OK
font-bh-lucidatypewriter-dpi75        1.0.2-1                OK
font-bitstream-dpi75                  1.0.2-1                OK
font-cantarell-otf                    0.0.15-1               OK
font-daewoo-misc                      1.0.2-1                OK
font-encodings                        1.0.4-1                OK
font-isas-misc                        1.0.2-1                OK
font-jis-misc                         1.0.2-1                OK
font-misc-misc                        1.1.1-1                OK
font-sony-misc                        1.0.2-1                OK
fontconfig                            2.10.93-1              OK
fontsproto                            2.1.2-1                OK
fslsfonts                             1.0.4-1                OK
fstobdf                               1.0.5-1                OK
gamin                                 0.1.10-14              OK
gap                                   4.7.2-1                OK
gap-ace                               4.7.2-1                OK
gap-anupq                             4.7.2-1                OK
gap-itc                               4.7.2-1                OK
gap-kbmag                             4.7.2-1                OK
gap-nq                                4.7.2-1                OK
gap-suggested                         4.7.2-1                OK
gawk                                  4.1.0-1                OK
gcc-core                              4.8.2-3                OK
gcc-g++                               4.8.2-3                OK
gconf-desktop-schemas                 2.32.1-3               OK
GConf2                                3.2.6-2                OK
gcr                                   3.10.1-1               OK
gdb                                   7.6.50-4               OK
getent                                2.18.90-1              OK
gettext                               0.18.1.1-3             OK
gettext-devel                         0.18.1.1-3             OK
ghostscript                           9.06-2                 OK
ghostscript-fonts-other               6.0-1                  OK
ghostscript-fonts-std                 8.11-1                 OK
git                                   1.7.9-1                OK
glib2.0-networking                    2.38.2-1               OK
glproto                               1.4.17-1               OK
gmp                                   6.0.0a-1               OK
gnome-common                          3.10.0-1               OK
gnome-doc-utils                       0.20.10-2              OK
gnome-icon-theme                      3.10.0-1               OK
gnome-keyring                         3.10.1-1               OK
gnupg                                 1.4.16-1               OK
gnutls                                3.2.0-4                OK
gnutls-devel                          3.2.0-4                OK
grep                                  2.16-1                 OK
groff                                 1.22.2-2               OK
gsettings-desktop-schemas             3.10.1-1               OK
gsl                                   1.16-1                 OK
gtk-doc                               1.19-2                 OK
gtk-update-icon-cache                 3.10.7-2               OK
gv                                    3.7.4-1                OK
gvfs                                  1.18.3-1               OK
gvim                                  7.4.182-1              OK
gzip                                  1.4-1                  OK
hicolor-icon-theme                    0.12-1                 OK
hostname                              3.13-1                 OK
idle3                                 3.2.5-3                OK
ImageMagick                           6.7.6.3-4              OK
inputproto                            2.3-1                  OK
intltool                              0.50.2-2               OK
ipc-utils                             1.0-2                  OK
itstool                               1.2.0-1                OK
kbproto                               1.0.6-1                OK
less                                  458-1                  OK
lftp                                  4.4.14-1               OK
libapr1                               1.4.8-1                OK
libaprutil1                           1.5.2-4                OK
libarchive13                          3.1.2-2                OK
libargp                               20110921-2             OK
libasn1_8                             1.5.3-1                OK
libaspell15                           0.60.6.1-1             OK
libasprintf0                          0.18.1.1-3             OK
libatk-bridge2.0-devel                2.10.2-1               OK
libatk-bridge2.0_0                    2.10.2-1               OK
libatk1.0-devel                       2.10.0-1               OK
libatk1.0_0                           2.10.0-1               OK
libatomic1                            4.8.2-3                OK
libatspi-devel                        2.10.2-1               OK
libatspi0                             2.10.2-1               OK
libattr1                              2.4.46-1               OK
libautotrace3                         0.31.1-1               OK
libavahi-client3                      0.6.31-2               OK
libavahi-common3                      0.6.31-2               OK
libavahi-glib1                        0.6.31-2               OK
libblkid1                             2.21.2-1               OK
libboost1.53                          1.53.0-2               OK
libbz2-devel                          1.0.6-2                OK
libbz2_1                              1.0.6-2                OK
libcairo-devel                        1.12.16-1              OK
libcairo2                             1.12.16-1              OK
libcatgets1                           1.1-2                  OK
libcharset1                           1.14-1                 OK
libcloog-isl4                         0.18.0-2               OK
libcom_err2                           1.42.7-1               OK
libcroco0.6_3                         0.6.8-1                OK
libcrypt0                             1.1-1                  OK
libcurl4                              7.34.0-1               OK
libdatrie1                            0.2.6-1                OK
libdb5.3                              5.3.21-1               OK
libdbus-glib_1_2                      0.100.2-1              OK
libdbus1-devel                        1.6.18-1               OK
libdbus1_3                            1.6.18-1               OK
libdialog11                           1.2-20140112-1         OK
libedit0                              20130712-1             OK
libEMF1                               1.0.7-1                OK
libexpat-devel                        2.1.0-3                OK
libexpat1                             2.1.0-3                OK
Empty package libexpat1-devel
libexpat1-devel                       2.1.0-3                OK
libfam0                               0.1.10-14              OK
libffi-devel                          3.0.13-1               OK
libffi6                               3.0.13-1               OK
libfftw3_3                            3.3.3-1                OK
libfontconfig-devel                   2.10.93-1              OK
libfontconfig1                        2.10.93-1              OK
libfontenc-devel                      1.1.2-1                OK
libfontenc1                           1.1.2-1                OK
libfpx1                               1.3.1.2-1              OK
libfreetype-devel                     2.5.3-1                OK
libfreetype6                          2.5.3-1                OK
libFS-devel                           1.0.6-1                OK
libFS6                                1.0.6-1                OK
libgc1                                7.2d-2                 OK
libgcc1                               4.8.2-3                OK
libgck1_0                             3.10.1-1               OK
libgconf2_4                           3.2.6-2                OK
libgcr3-common                        3.10.1-1               OK
libgcr3_1                             3.10.1-1               OK
libgcrypt11                           1.5.0-1                OK
libgd-devel                           2.0.36RC1-1            OK
libgd2                                2.0.36RC1-1            OK
libgdbm4                              1.10-2                 OK
libgdk_pixbuf2.0-devel                2.30.4-1               OK
libgdk_pixbuf2.0_0                    2.30.4-1               OK
libgettextpo0                         0.18.1.1-3             OK
libgfortran3                          4.8.2-3                OK
libgif-devel                          4.1.6-12               OK
libgif4                               4.1.6-12               OK
libGL-devel                           8.0.5-5                OK
libGL1                                8.0.5-5                OK
libglapi0                             8.0.5-5                OK
libglib2.0-devel                      2.38.2-2               OK
libglib2.0_0                          2.38.2-2               OK
libGLU1                               9.0.0-1                OK
libglut3                              2.8.1-1                OK
libgmp-devel                          6.0.0a-1               OK
libgmp10                              6.0.0a-1               OK
libgmpxx4                             6.0.0a-1               OK
libgnome-keyring0                     3.10.1-1               OK
libgnutls28                           3.2.0-4                OK
libgomp1                              4.8.2-3                OK
libgpg-error0                         1.10-1                 OK
libgraphite2-devel                    1.2.3-1                OK
libgraphite2_3                        1.2.3-1                OK
libgs-devel                           9.06-2                 OK
libgs9                                9.06-2                 OK
libgssapi3                            1.5.3-1                OK
libgtk2.0_0                           2.24.23-1              OK
libgtk3-devel                         3.10.7-2               OK
libgtk3_0                             3.10.7-2               OK
libharfbuzz-devel                     0.9.25-1               OK
libharfbuzz0                          0.9.25-1               OK
libheimbase1                          1.5.3-1                OK
libheimntlm0                          1.5.3-1                OK
libhogweed2                           2.7-1                  OK
libhx509_5                            1.5.3-1                OK
libICE-devel                          1.0.8-1                OK
libICE6                               1.0.8-1                OK
libiconv                              1.14-1                 OK
libiconv-devel                        1.14-1                 OK
libiconv2                             1.14-1                 OK
libicu-devel                          51.2-1                 OK
libicu51                              51.2-1                 OK
libidn-devel                          1.26-1                 OK
libidn11                              1.26-1                 OK
libintl8                              0.18.1.1-3             OK
libiodbc2                             3.52.8-2               OK
libisl10                              0.11.1-2               OK
libjasper1                            1.900.1-13             OK
libjbig2                              2.0-12                 OK
libjpeg-devel                         1.2.1-2                OK
libjpeg8                              1.2.1-2                OK
libkafs0                              1.5.3-1                OK
libkpathsea-devel                     20130529-1             OK
libkpathsea6                          20130529-1             OK
libkrb5_26                            1.5.3-1                OK
liblapack0                            3.5.0-2                OK
liblcms1                              1.19-1                 OK
liblcms2-devel                        2.5-1                  OK
liblcms2_2                            2.5-1                  OK
libltdl7                              2.4.2-3                OK
liblzma5                              5.0.4-1                OK
liblzo2_2                             2.06-1                 OK
libMagick-devel                       6.7.6.3-4              OK
libMagickCore5                        6.7.6.3-4              OK
libmcpp0                              2.7.2-2                OK
libmetalink3                          0.1.2-1                OK
libming1                              0.4.5-1                OK
libmpc3                               1.0.2-1                OK
libmpfr4                              3.1.2-1                OK
libmysqlclient18                      5.5.35-1               OK
libncursesw-devel                     5.9-4                  OK
libncursesw10                         5.9-4                  OK
libneon27                             0.29.6-1               OK
libnetpbm10                           10.61.02-1             OK
libnettle-devel                       2.7-1                  OK
libnettle4                            2.7-1                  OK
libopenjpeg1                          1.5.1-3                OK
libopenldap2_4_2                      2.4.35-1               OK
libopenssl100                         1.0.1f-3               OK
libOSMesa8                            8.0.5-5                OK
libosp5                               1.5.2-2                OK
libostyle1                            1.4devel1-3            OK
libp11-kit-devel                      0.20.2-1               OK
libp11-kit0                           0.20.2-1               OK
libpango1.0-devel                     1.36.3-1               OK
libpango1.0_0                         1.36.3-1               OK
libpaper-common                       1.1.24-2               OK
libpaper-devel                        1.1.24-2               OK
libpaper1                             1.1.24-2               OK
libpcre-devel                         8.34-1                 OK
libpcre1                              8.34-1                 OK
libpcre16_0                           8.34-1                 OK
libpcre32_0                           8.34-1                 OK
libpcrecpp0                           8.34-1                 OK
libpcreposix0                         8.34-1                 OK
libpixman1-devel                      0.32.4-1               OK
libpixman1_0                          0.32.4-1               OK
libpng-devel                          1.5.14-1               OK
libpng15                              1.5.14-1               OK
libpoppler-devel                      0.24.5-1               OK
libpoppler28                          0.20.5-3               OK
libpoppler37                          0.22.5-2               OK
libpoppler44                          0.24.5-1               OK
libpopt0                              1.16-1                 OK
libpq5                                9.3.2-2                OK
libproxy1                             0.4.11-2               OK
libpstoedit0                          3.61-1                 OK
libptexenc1                           20130529-1             OK
libquadmath0                          4.8.2-3                OK
librarian0                            0.8.1-12               OK
libreadline-devel                     6.2-1                  OK
libreadline7                          6.2-1                  OK
libroken18                            1.5.3-1                OK
librsvg2-devel                        2.40.1-1               OK
librsvg2_2                            2.40.1-1               OK
libsasl2_3                            2.1.26-6               OK
libsecret1_0                          0.16-1                 OK
libserf1_0                            1.3.3-1                OK
libSM-devel                           1.2.2-1                OK
libSM6                                1.2.2-1                OK
libsoup-gnome2.4_1                    2.44.2-2               OK
libsoup2.4_1                          2.44.2-2               OK
libsource-highlight-common            3.1.7-3                OK
libsource-highlight4                  3.1.7-3                OK
libsqlite3_0                          3.8.4.1-1              OK
libssh2_1                             1.4.2-1                OK
libssp0                               4.8.2-3                OK
libstdc++6                            4.8.2-3                OK
libtasn1-devel                        3.3-1                  OK
libtasn1_6                            3.3-1                  OK
libthai0                              0.1.19-1               OK
libtiff-devel                         3.9.7-3                OK
libtiff5                              3.9.7-3                OK
libtool                               2.4.2-3                OK
libunistring0                         0.9.3-2                OK
libustr1                              1.0.4-12               OK
libuuid1                              2.21.2-1               OK
libwind0                              1.5.3-1                OK
libwrap0                              7.6-22                 OK
libX11-devel                          1.6.2-1                OK
libX11-xcb-devel                      1.6.2-1                OK
libX11-xcb1                           1.6.2-1                OK
libX11_6                              1.6.2-1                OK
libXau-devel                          1.0.8-1                OK
libXau6                               1.0.8-1                OK
libXaw-devel                          1.0.12-1               OK
libXaw3d-devel                        1.6.2-1                OK
libXaw3d8                             1.6.2-1                OK
libXaw7                               1.0.12-1               OK
libxcb-devel                          1.9.1-2                OK
libxcb-glx-devel                      1.9.1-2                OK
libxcb-glx0                           1.9.1-2                OK
libxcb-icccm4                         0.3.9-1                OK
libxcb-image0                         0.3.9-1                OK
libxcb-render-devel                   1.9.1-2                OK
libxcb-render0                        1.9.1-2                OK
libxcb-shm-devel                      1.9.1-2                OK
libxcb-shm0                           1.9.1-2                OK
libxcb-util1                          0.3.9-1                OK
libxcb1                               1.9.1-2                OK
libXcomposite-devel                   0.4.3-1                OK
libXcomposite1                        0.4.3-1                OK
libXcursor-devel                      1.1.14-1               OK
libXcursor1                           1.1.14-1               OK
libXdamage-devel                      1.1.4-1                OK
libXdamage1                           1.1.4-1                OK
libXdmcp-devel                        1.1.1-1                OK
libXdmcp6                             1.1.1-1                OK
libXext-devel                         1.3.2-1                OK
libXext6                              1.3.2-1                OK
libXfixes-devel                       5.0.1-1                OK
libXfixes3                            5.0.1-1                OK
libXfont-devel                        1.4.7-2                OK
libXfont1                             1.4.7-2                OK
libXft-devel                          2.3.1-1                OK
libXft2                               2.3.1-1                OK
libXi-devel                           1.7.2-1                OK
libXi6                                1.7.2-1                OK
libXinerama-devel                     1.1.3-1                OK
libXinerama1                          1.1.3-1                OK
libxkbfile1                           1.0.8-1                OK
libXm4                                2.3.4-1                OK
libxml2                               2.9.1-1                OK
libxml2-devel                         2.9.1-1                OK
libXmu-devel                          1.1.2-1                OK
libXmu6                               1.1.2-1                OK
libXmuu1                              1.1.2-1                OK
libXpm-devel                          3.5.11-1               OK
libXpm-noX                            3.5.10-1               OK
libXpm-noX-devel                      3.5.10-1               OK
libXpm-noX_4                          3.5.10-1               OK
libXpm4                               3.5.11-1               OK
libXrandr-devel                       1.4.2-1                OK
libXrandr2                            1.4.2-1                OK
libXrender-devel                      0.9.8-1                OK
libXrender1                           0.9.8-1                OK
libxslt                               1.1.28-1               OK
libXss1                               1.2.2-1                OK
libXt-devel                           1.1.4-1                OK
libXt6                                1.1.4-1                OK
libXtst6                              1.2.2-1                OK
libyaml0_2                            0.1.6-1                OK
libzzip-devel                         0.13.62-1              OK
libzzip0.13                           0.13.62-1              OK
lndir                                 1.0.3-1                OK
login                                 1.10-10                OK
luit                                  20130217-1             OK
m4                                    1.4.17-1               OK
magnus                                20060324-1             OK
make                                  4.0.90-1               OK
man                                   1.6g-2                 OK
mcpp                                  2.7.2-2                OK
mingw64-i686-binutils                 2.24.0.1.acd6540-1     OK
mingw64-i686-bzip2                    1.0.6-4                OK
mingw64-i686-gcc-core                 4.8.2-1                OK
mingw64-i686-gcc-g++                  4.8.2-1                OK
mingw64-i686-headers                  3.1.0-1                OK
mingw64-i686-libgcrypt                1.5.3-1                OK
mingw64-i686-libgpg-error             1.12-1                 OK
mingw64-i686-minizip                  1.2.8-3                OK
mingw64-i686-pkg-config               0.28-1                 OK
mingw64-i686-pthreads                 20100619-5             OK
mingw64-i686-runtime                  3.1.0-1                OK
mingw64-i686-winpthreads              3.1.0-1                OK
mingw64-i686-zlib                     1.2.8-3                OK
mingw64-x86_64-binutils               2.24.0.1.acd6540-1     OK
mingw64-x86_64-bzip2                  1.0.6-4                OK
mingw64-x86_64-gcc-core               4.8.2-1                OK
mingw64-x86_64-gcc-g++                4.8.2-1                OK
mingw64-x86_64-headers                3.1.0-1                OK
mingw64-x86_64-libgcrypt              1.5.3-1                OK
mingw64-x86_64-libgpg-error           1.12-1                 OK
mingw64-x86_64-minizip                1.2.8-3                OK
mingw64-x86_64-pkg-config             0.28-1                 OK
mingw64-x86_64-pthreads               20100619-5             OK
mingw64-x86_64-runtime                3.1.0-1                OK
mingw64-x86_64-winpthreads            3.1.0-1                OK
mingw64-x86_64-xz                     5.0.5-1                OK
mingw64-x86_64-zlib                   1.2.8-3                OK
mintty                                1.2-beta1-1            OK
mkfontdir                             1.0.7-1                OK
mkfontscale                           1.1.1-1                OK
netpbm                                10.61.02-1             OK
openjade                              1.4devel1-3            OK
OpenSP                                1.5.2-2                OK
openssh                               6.6p1-1                OK
openssl                               1.0.1f-3               OK
p11-kit                               0.20.2-1               OK
p11-kit-trust                         0.20.2-1               OK
patch                                 2.7.1-1                OK
perl                                  5.14.4-1               OK
perl-Business-ISBN                    2.06-1                 OK
perl-Business-ISBN-Data               20120719.001-1         OK
perl-Business-ISMN                    1.11-1                 OK
perl-Business-ISSN                    0.91-1                 OK
perl-Data-Compare                     1.22-1                 OK
perl-Data-Diver                       1.0101-1               OK
perl-Data-Dump                        1.22-1                 OK
perl-Date-Simple                      3.03-1                 OK
perl-DBI                              1.623-2                OK
perl-Encode-Locale                    1.03-1                 OK
perl-Error                            0.17019-1              OK
perl-File-Find-Rule                   0.33-1                 OK
perl-File-Listing                     6.04-1                 OK
perl-File-Slurp                       9999.19-1              OK
perl-File-Slurp-Unicode               0.7.1-1                OK
perl-HTML-Parser                      3.70-1                 OK
perl-HTML-Tagset                      3.20-1                 OK
perl-HTTP-Cookies                     6.01-1                 OK
perl-HTTP-Date                        6.02-1                 OK
perl-HTTP-Message                     6.06-1                 OK
perl-HTTP-Negotiate                   6.01-1                 OK
perl-IO-Socket-SSL                    1.88-1                 OK
perl-IPC-Run3                         0.045-1                OK
perl-List-AllUtils                    0.03-1                 OK
perl-List-MoreUtils                   0.33-1                 OK
perl-Log-Log4perl                     1.41-1                 OK
perl-LWP                              6.05-1                 OK
perl-LWP-MediaTypes                   6.02-1                 OK
perl-LWP-Protocol-https               6.04-1                 OK
perl-Mozilla-CA                       20130114-2             OK
perl-Net-HTTP                         6.06-1                 OK
perl-Net-SSLeay                       1.54-1                 OK
perl-Number-Compare                   0.03-1                 OK
perl-Params-Util                      1.07-1                 OK
perl-Readonly                         1.03-1                 OK
perl-Regexp-Common                    2013031301-1           OK
perl-Text-BibTeX                      0.66-1                 OK
perl-Text-Glob                        0.09-1                 OK
perl-Tie-Cycle                        1.17-1                 OK
perl-Tk                               804.030-3              OK
perl-Unicode-Collate                  0.97-1                 OK
perl-URI                              1.60-1                 OK
perl-WWW-RobotRules                   6.02-1                 OK
perl-XML-LibXML                       2.0018-1               OK
perl-XML-LibXML-Simple                0.93-1                 OK
perl-XML-LibXSLT                      1.80-1                 OK
perl-XML-NamespaceSupport             1.11-1                 OK
perl-XML-Parser                       2.41-1                 OK
perl-XML-SAX                          0.99-2                 OK
perl-XML-SAX-Base                     1.08-1                 OK
pkg-config                            0.27.1-1               OK
poppler-data                          0.4.6-1                OK
popt                                  1.16-1                 OK
python                                2.7.5-3                OK
python-crypto                         2.6-1                  OK
python-fastimport                     0.9.2-1                OK
python-gobject                        2.28.6-5               OK
python-imaging                        1.1.7-5                OK
python-libxml2                        2.9.1-1                OK
python-paramiko                       1.10.1-1               OK
python-pyrex                          0.9.9-2                OK
python-test                           2.7.5-3                OK
python-tkinter                        2.7.5-3                OK
python3                               3.2.5-3                OK
python3-tkinter                       3.2.5-3                OK
randrproto                            1.4.0-1                OK
rarian                                0.8.1-12               OK
rebase                                4.4.1-1                OK
renderproto                           0.11.1-1               OK
rsync                                 3.0.9-1                OK
ruby                                  1.9.3-p484-1           OK
ruby-json                             1.8.0-1                OK
ruby-rake                             10.0.4-1               OK
ruby-rdoc                             3.12.2-1               OK
run                                   1.3.0-1                OK
run2                                  0.4.2-2                OK
sed                                   4.2.2-3                OK
sgml-common                           0.6.3-3                OK
shared-mime-info                      1.2-1                  OK
showfont                              1.0.4-1                OK
source-highlight                      3.1.7-3                OK
subversion                            1.8.8-1                OK
t1lib-devel                           5.1.2-1                OK
t1lib5                                5.1.2-1                OK
tar                                   1.26-1                 OK
tcl                                   8.5.11-1               OK
tcl-tix                               8.4.3-2                OK
tcl-tk                                8.5.11-1               OK
tcsh                                  6.18.01-3              OK
terminfo                              5.9-4                  OK
texinfo                               5.2-1                  OK
texlive                               20130529-1             OK
texlive-collection-basic              20130529-1             OK
texlive-collection-bibtexextra        20130529-2             OK
texlive-collection-binextra           20130529-1             OK
texlive-collection-fontsextra         20130529-1             OK
texlive-collection-fontsrecommended   20130529-1             OK
texlive-collection-fontutils          20130529-1             OK
texlive-collection-genericrecommended 20130529-1             OK
texlive-collection-htmlxml            20130529-1             OK
texlive-collection-langenglish        20130529-1             OK
texlive-collection-langeuropean       20130529-1             OK
texlive-collection-langfrench         20130529-1             OK
Missing file: /usr/share/texmf-dist/doc/latex/hausarbeit-jura/README. from package texlive-collection-langgerman
texlive-collection-langgerman         20130529-1             Incomplete
texlive-collection-latex              20130529-1             OK
texlive-collection-latexextra         20130529-1             OK
texlive-collection-latexrecommended   20130529-1             OK
texlive-collection-luatex             20130529-1             OK
texlive-collection-mathextra          20130529-1             OK
texlive-collection-pictures           20130529-1             OK
texlive-collection-xetex              20130529-1             OK
transfig                              3.2.5d-1               OK
tzcode                                2013c-1                OK
unison2.40                            2.40.102-1             OK
unzip                                 6.0-1                  OK
upx                                   3.91-1                 OK
util-linux                            2.21.2-1               OK
vim                                   7.4.182-1              OK
vim-common                            7.4.182-1              OK
vim-minimal                           7.4.182-1              OK
w32api-headers                        3.1.0-1                OK
w32api-runtime                        3.1.0-1                OK
w3m                                   0.5.3-1                OK
wget                                  1.13.4-1               OK
which                                 2.20-2                 OK
xauth                                 1.0.8-1                OK
xcursor-themes                        1.0.4-1                OK
xextproto                             7.3.0-1                OK
xf86-video-dummy                      0.3.7-1                OK
xf86-video-nested                     0.1.0-4                OK
xfig                                  3.2.5b-1               OK
xfs                                   1.1.3-1                OK
xfsinfo                               1.0.4-1                OK
xgap                                  4.7.2-1                OK
xineramaproto                         1.2.1-1                OK
xinit                                 1.3.2-1                OK
xkbcomp                               1.2.4-1                OK
xkeyboard-config                      2.11-1                 OK
xml2po                                0.20.10-2              OK
xmlto                                 0.0.25-1               OK
xmodmap                               1.0.8-1                OK
xorg-server                           1.15.0-4               OK
xorg-server-common                    1.15.0-4               OK
xpdf                                  3.03-1                 OK
xproto                                7.0.25-1               OK
xrdb                                  1.1.0-1                OK
xterm                                 302-1                  OK
xwinclip                              1.15.0-4               OK
xxd                                   7.4.182-1              OK
xz                                    5.0.4-1                OK
yelp-tools                            3.10.0-1               OK
yelp-xsl                              3.10.1-1               OK
zip                                   3.0-1                  OK
zlib-devel                            1.2.8-1                OK
zlib0                                 1.2.8-1                OK
zziplib                               0.13.62-1              OK
Use -h to see help about each section

[-- Attachment #3: Type: text/plain, Size: 218 bytes --]

--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Duncan Roe]

On Fri, Apr 11, 2014 at 02:39:34PM +0200, Corinna Vinschen wrote:
> On Apr 11 16:20, Duncan Roe wrote:
> > On Thu, Apr 10, 2014 at 09:47:26PM -0600, Warren Young wrote:
> > > On 4/10/2014 20:16, Duncan Roe wrote:
> > > >Yes, I'm one of those users. I need my login name to match the Linux systems so
> > > >I can use rsh and not be challenged for a password when the cygwin host name is
> > > >in ~/.rhosts
> > >
> > > If you switch to SSH, you can solve this by putting this into your
> > > ~/.ssh/config file:
> > >
> > >      Host myremotehost
> > >          User duncan_roe
> > >
> > > That is, you can override defaults (like login name) on a per-connection
> > > basis.  Anything you can pass as an option to ssh(1) can be changed here, so
> > > you don't have to keep providing the option.
> > >
> > > With pre-shared keys, I don't think you'll see a difference in behavior
> > > relative to rsh.
> > >
> > I don't want to switch to ssh. rsh is in an expect script, so providing ssh
> > options every time would not be a problem. But I want to use rsh.
>
> OTOH, if there *is* an official workaround which is, "use the /etc/passwd
> file to chnage your username", wouldn't that be sufficient?

Yes it's perfect. That's what I use.
>
> I understand your point, but the search problem in the Windows user DBs
> as I outlined persists.
>
> What I did a couple of weeks ago ws to change the mkpasswd tool so that
> it creates the exact same passwd entries as you get when fetching them
> directly from Windows.  For instance, the passwd entry generated for
> my AD account inside of Cygwin will look like this:
>
> corinna:*:1049577:1049701:Corinna Vinschen,U-VINSCHEN\corinna,S-1-5-21-2913048732-1697188782-3448811101-1001:/home/corinna:/bin/tcsh
>
> Using the "new" mkpasswd, calling `mkpasswd -d -u corinna', I get the
> exact same entry!  If I write this into /etc/passwd, I'm getting the
> exact same correct uid and gid values, but I can change my username:
>
>   $ mkpasswd -d -u corinna > /etc/passwd
>   $ sed -i -e 's/^corinna:/cathy:/' /etc/passwd
>   [logout/login]
>   $ id
>   uid=1049577(cathy) gid=1049701(vinschen) groups=1049701(vinschen),
>   559(+Performance Log Users),545(+Users),[...]
>
> That should be sufficient, shouldn't it?
>
I do that already. Good to hear it as sound practice from you though,

Cheers ... Duncan.

--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]

On Apr 11 19:36, Ken Brown wrote:
> On 4/10/2014 10:53 AM, Corinna Vinschen wrote:
> >Hi folks,
> >
> >
> >The latest snapshot, 2014-04-10, is a snapshot from CVS HEAD again.
> >It contains the latest crazy ideas in terms of the user and group
> >account creation without requiring the /etc/passwd and /etc/group
> >files.
> 
> I installed the complete snapshot and moved /etc/passwd and
> /etc/group out of the way.  Now all users have gid == uid:
> 
> $ mkpasswd.exe
> +SYSTEM:*:18:18:U-NT AUTHORITY\SYSTEM,S-1-5-18:/home/SYSTEM:/bin/bash
> [...]
> kbrown:*:197610:197610:...
> [...]
> sshd:*:197613:197613:...
> 
> $ mkgroup.exe
> +SYSTEM:S-1-5-18:18:
> [...]
> HomeUsers:S-1-5-21-2633657340-2046398995-3442950202-1003:197611:
> None:S-1-5-21-2633657340-2046398995-3442950202-513:197121:
> 
> Shouldn't ordinary users (like kbrown) have gid == 197121?  All
> files I created as kbrown prior to the test show group "None", and
> all files I created after the test show group "kbrown".
> 
> Is this a bug, or is there something weird about my system that's
> making this happen?  cygcheck output is attached.

Definitely a bug.  I "optimized" the code a couple of weeks ago and
while I was at it I "optimized" away the code evaluating local user's
primary gid.  Duh.  I'm just building a new snapshot.


Thanks for the report,
Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Ken Brown]

On 4/12/2014 7:13 AM, Corinna Vinschen wrote:
> On Apr 11 19:36, Ken Brown wrote:
>> On 4/10/2014 10:53 AM, Corinna Vinschen wrote:
>>> Hi folks,
>>>
>>>
>>> The latest snapshot, 2014-04-10, is a snapshot from CVS HEAD again.
>>> It contains the latest crazy ideas in terms of the user and group
>>> account creation without requiring the /etc/passwd and /etc/group
>>> files.
>>
>> I installed the complete snapshot and moved /etc/passwd and
>> /etc/group out of the way.  Now all users have gid == uid:
>>
>> $ mkpasswd.exe
>> +SYSTEM:*:18:18:U-NT AUTHORITY\SYSTEM,S-1-5-18:/home/SYSTEM:/bin/bash
>> [...]
>> kbrown:*:197610:197610:...
>> [...]
>> sshd:*:197613:197613:...
>>
>> $ mkgroup.exe
>> +SYSTEM:S-1-5-18:18:
>> [...]
>> HomeUsers:S-1-5-21-2633657340-2046398995-3442950202-1003:197611:
>> None:S-1-5-21-2633657340-2046398995-3442950202-513:197121:
>>
>> Shouldn't ordinary users (like kbrown) have gid == 197121?  All
>> files I created as kbrown prior to the test show group "None", and
>> all files I created after the test show group "kbrown".
>>
>> Is this a bug, or is there something weird about my system that's
>> making this happen?  cygcheck output is attached.
>
> Definitely a bug.  I "optimized" the code a couple of weeks ago and
> while I was at it I "optimized" away the code evaluating local user's
> primary gid.  Duh.  I'm just building a new snapshot.

Works fine now.  Thanks.

Ken

--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]

On Apr 12 10:20, Ken Brown wrote:
> On 4/12/2014 7:13 AM, Corinna Vinschen wrote:
> >On Apr 11 19:36, Ken Brown wrote:
> >>On 4/10/2014 10:53 AM, Corinna Vinschen wrote:
> >>>Hi folks,
> >>>
> >>>
> >>>The latest snapshot, 2014-04-10, is a snapshot from CVS HEAD again.
> >>>It contains the latest crazy ideas in terms of the user and group
> >>>account creation without requiring the /etc/passwd and /etc/group
> >>>files.
> >>
> >>I installed the complete snapshot and moved /etc/passwd and
> >>/etc/group out of the way.  Now all users have gid == uid:
> >>
> >>$ mkpasswd.exe
> >>+SYSTEM:*:18:18:U-NT AUTHORITY\SYSTEM,S-1-5-18:/home/SYSTEM:/bin/bash
> >>[...]
> >>kbrown:*:197610:197610:...
> >>[...]
> >>sshd:*:197613:197613:...
> >>
> >>$ mkgroup.exe
> >>+SYSTEM:S-1-5-18:18:
> >>[...]
> >>HomeUsers:S-1-5-21-2633657340-2046398995-3442950202-1003:197611:
> >>None:S-1-5-21-2633657340-2046398995-3442950202-513:197121:
> >>
> >>Shouldn't ordinary users (like kbrown) have gid == 197121?  All
> >>files I created as kbrown prior to the test show group "None", and
> >>all files I created after the test show group "kbrown".
> >>
> >>Is this a bug, or is there something weird about my system that's
> >>making this happen?  cygcheck output is attached.
> >
> >Definitely a bug.  I "optimized" the code a couple of weeks ago and
> >while I was at it I "optimized" away the code evaluating local user's
> >primary gid.  Duh.  I'm just building a new snapshot.
> 
> Works fine now.  Thanks.

Good to hear.


Thanks,
Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Andrey Repin]

Greetings, Corinna Vinschen!

> The latest snapshot, 2014-04-10, is a snapshot from CVS HEAD again.
> It contains the latest crazy ideas in terms of the user and group
> account creation without requiring the /etc/passwd and /etc/group
> files.

> Not a lot has changed since we made a break to test for 1.7.29,
> but there's one important change I'd like to point out:

> * cygserver now provides system-wide passwd/group entry caching.

>   All processes started *after* cygserver will try to fetch passwd
>   and group entries from cygserver.  While this is probably a bit
>   slow at the start, the longer cygserver runs, the more information
>   is present and later started processes will get the information
>   with all due speed.

Does this mean that I could benefit from running cygserver in local
environment?
Specifically, if I'm using Cygwin tools outside Cygwin shell?

> I attached the latest incarnation of the documentation for this
> major change to this mail.

> However!

> After sweating about some of the details I created in my scrubby mind
> back in January/February, I'm not so sure anymore if some if was really
> such a bright idea.

> Especially two problems cropped up in discussions with local Cygwin
> users:


> * Support for Cygwin user names different from the Windows username.

I think I said it before, but I'll just repeat that I don't see this as a
feature.
Confusion option, at best. The worst case you've just outlined below.

>   Fixing this problem leads to terrible performance.  Obviously Cygwin
>   doesn't know if "yoghurt" is a local or an AD account.  Or, FWIW, an
>   account in some trusted domain.  Finding "kefir" in the SAM of the
>   local machine requires to enumerate *all* accounts, until the account
>   with
>   
>     <cygwin name="kefir" .../>
> 
>   is found.  Even worse in AD.  An ldap query is required which searches
>   for an account with uid="kefir".  The uid attribute is not indexed by
>   default.  Same for all trusted domains.


> * db_separator in /etc/nsswitch.conf

>   Is it really such a good idea to have a configurable separator
>   char in user and group names?  Is it important that it is
>   configurable?  Is '+' a good choice for the default separator?
>   Wouldn't the backslash a better and, perhaps, only choice?

The "+" as a separator was conceived in *NIX because backslash has a long
history of being a way-too-meaningful escape character.
(Though, you know it, I'll just say it for other interested parties.)
I don't have an opinion on it, but I tend to favor native semantics, means,
the backslash.
If anyone are familiar with modern state of preferred domain separator
in Samba 4, would that effect the decision?


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 13.04.2014, <14:11>

Sorry for my terrible english...


--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Andrey Repin]

Greetings, Eric Blake!

>> A local cygwin user told me that the users in their company would
>> probably be confused by the '+ or, FWIW, any other non-backslash char,
>> because they were drilled to see and use usernames always in domain\name
>> form, or even in domain\\user form when logging in to Linux.
>> 
>> I like slashes a lot more for obvious reasons.  But maybe, and that
>> wouldn't be too hard to implement, we could accept account names with
>> slash and with backslash, just as we do with pathnames.  Output of
>> usernames would be with slashes, of course.

> POSIX says:

> http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html
>> User Name
>> A string that is used to identify a user; see also User Database. To be
>> portable across systems conforming to POSIX.1-2008, the value is composed
>> of characters from the portable filename character set. The <hyphen>
>> character should not be used as the first character of a portable user name. 

> It also says this for shell tilde expansion:

> http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_01
>>  If none of the characters in the tilde-prefix are quoted, the characters
>> in the tilde-prefix following the <tilde> are treated as a possible login
>> name from the user database. A portable login name cannot contain
>> characters outside the set given in the description of the LOGNAME
>> environment variable in XBD Other Environment Variables.

> and following that link:
>> For a value of LOGNAME to be portable across implementations of
>> POSIX.1-2008, the value should be composed of characters from the portable
>> filename character set.

> In short, in POSIX systems, user names are solely from the set
> [-_.a-zA-Z0-9]; which excludes +, \, or any other separator we come up
> with.

This is all nice and dandy, but user _name_ (logon name) in Windows is as
strict, as POSIX mandates (down to character set limitations), the domain
prefix is only used, when you absolutely need to specify it, and it is not
an integral part of the name.

> I'm fine with using a non-portable character (this is, after all,
> a cygwin extension of how to map Windows user names to a Linux emulation
> environment).  But keeping in mind the rules on tilde expansion,

> ~a+b/file

> can undergo tilde expansion for username 'a+b', but

> ~a\\b/file

> cannot do so, because the \ is necessarily always quoted.  There is no
> way to get tilde expansion to work for a username containing a shell
> metacharacter, which frowns on quite a few otherwise useful characters,
> including \.

> Worse, the thought of using / as the separator gives me the willies - it
> is BOUND to go wrong.  The expression

> ~a/b/file

> is NOT requesting 'file' within user 'a/b's home, but 'b/file' within
> user 'a's home.

This is a grey area. Shell macros is only available is the shell prompt
itself and scripts executed by this shell.
And is not portable at all.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 13.04.2014, <14:22>

Sorry for my terrible english...


--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Andrey Repin]

Greetings, Corinna Vinschen!

> What bugs me a bit is what this means for applications which expect
> fixed usernames.  Sshd, for instance, expects the fixed username
> "sshd" right now when using privilege separation.  I discussed this
> with the OpenSSH devs, and they understand the problem, but they think
> this should be handled by a Cygwin-specific function.  So there's some
> extra work in it for me to get OpenSSH up to speed with this change,
> but I fear I'm not the only one.  The more configurable stuff like this
> is, the more complicated it gets maintaining some packages.

I really don't see a problem. Is this implementation-dependent issue?
99% you are operating within "current domain" and do not need to specify
domain prefix at all.
I know I only ever had to specify domain prefix, when logging to the RPC pipe
of a domain server from a standalone station. And that was only because
Windows break login sequence while there's no account with same login/password
in local SAM.
When I'm already on a domain system, I just specify a username without a
prefix and go forth.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 13.04.2014, <14:28>

Sorry for my terrible english...


--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Andrey Repin]

Greetings, Corinna Vinschen!

>> >The latest snapshot, 2014-04-10, is a snapshot from CVS HEAD again.
>> >It contains the latest crazy ideas in terms of the user and group
>> >account creation without requiring the /etc/passwd and /etc/group
>> >files.
>> >
>> >Not a lot has changed since we made a break to test for 1.7.29,
>> >but there's one important change I'd like to point out:
>> >
>> >* cygserver now provides system-wide passwd/group entry caching.
>> >
>> >   All processes started *after* cygserver will try to fetch passwd
>> >   and group entries from cygserver.  While this is probably a bit
>> >   slow at the start, the longer cygserver runs, the more information
>> >   is present and later started processes will get the information
>> >   with all due speed.
>> 
>> Do we need to install cygserver.exe from the snapshot in order to
>> get this functionality, or is cygwin1.dll enough?

> This required new code in cygserver to handle the application requests,
> so you need the snapshot cygserver.

I think he was asking, if we are _required_ to install cygserver, or the dll
is enough?


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 13.04.2014, <14:37>

Sorry for my terrible english...


--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]

On Apr 13 14:34, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
> 
> > What bugs me a bit is what this means for applications which expect
> > fixed usernames.  Sshd, for instance, expects the fixed username
> > "sshd" right now when using privilege separation.  I discussed this
> > with the OpenSSH devs, and they understand the problem, but they think
> > this should be handled by a Cygwin-specific function.  So there's some
> > extra work in it for me to get OpenSSH up to speed with this change,
> > but I fear I'm not the only one.  The more configurable stuff like this
> > is, the more complicated it gets maintaining some packages.
> 
> I really don't see a problem. Is this implementation-dependent issue?
> 99% you are operating within "current domain" and do not need to specify
> domain prefix at all.

Uh, but you're missing the situation where the machine is a domain
machine but the privilege separation account "sshd" is created in
the local SAM.  That's what the ssh-host-config script might do.
Sshd will have to use MACHINE<separator>sshd as username for privsep
in this case.


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]

On Apr 13 14:27, Andrey Repin wrote:
>   But keeping in mind the rules on tilde expansion,
> 
> > ~a+b/file
> 
> > can undergo tilde expansion for username 'a+b', but
> 
> > ~a\\b/file
> 
> > cannot do so, because the \ is necessarily always quoted.  There is no
> > way to get tilde expansion to work for a username containing a shell
> > metacharacter, which frowns on quite a few otherwise useful characters,
> > including \.
> 
> > Worse, the thought of using / as the separator gives me the willies - it
> > is BOUND to go wrong.  The expression
> 
> > ~a/b/file
> 
> > is NOT requesting 'file' within user 'a/b's home, but 'b/file' within
> > user 'a's home.
> 
> This is a grey area. Shell macros is only available is the shell prompt
> itself and scripts executed by this shell.
> And is not portable at all.

But is it such a bright idea to break it for everybody?  It's obviously
not a problem for non-domain, single-user systems.  And I guess
companies which set db_separator to "\" and db_prefix to "always" don't
care for this detail.  But in other companies with lots of login
domains, you have a potentially huge number of users working on machines
in another domain and the separator char would be present quite often.


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1553 bytes --]

On Apr 13 14:38, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
> 
> >> >The latest snapshot, 2014-04-10, is a snapshot from CVS HEAD again.
> >> >It contains the latest crazy ideas in terms of the user and group
> >> >account creation without requiring the /etc/passwd and /etc/group
> >> >files.
> >> >
> >> >Not a lot has changed since we made a break to test for 1.7.29,
> >> >but there's one important change I'd like to point out:
> >> >
> >> >* cygserver now provides system-wide passwd/group entry caching.
> >> >
> >> >   All processes started *after* cygserver will try to fetch passwd
> >> >   and group entries from cygserver.  While this is probably a bit
> >> >   slow at the start, the longer cygserver runs, the more information
> >> >   is present and later started processes will get the information
> >> >   with all due speed.
> >> 
> >> Do we need to install cygserver.exe from the snapshot in order to
> >> get this functionality, or is cygwin1.dll enough?
> 
> > This required new code in cygserver to handle the application requests,
> > so you need the snapshot cygserver.
> 
> I think he was asking, if we are _required_ to install cygserver, or the dll
> is enough?

I didn't understand it that way, but of course cygserver is just an
option, to get another, system-wide way of caching, not a requirement to
get caching at all.


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 3191 bytes --]

On Apr 13 14:18, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
> > * cygserver now provides system-wide passwd/group entry caching.
> 
> >   All processes started *after* cygserver will try to fetch passwd
> >   and group entries from cygserver.  While this is probably a bit
> >   slow at the start, the longer cygserver runs, the more information
> >   is present and later started processes will get the information
> >   with all due speed.
> 
> Does this mean that I could benefit from running cygserver in local
> environment?
> Specifically, if I'm using Cygwin tools outside Cygwin shell?

Yes.  As long as cygserver is running, it caches and is available to
all processes.  The overhead is a single bidirectional communication 
via a named pipe per passwd/group entry.

> > Especially two problems cropped up in discussions with local Cygwin
> > users:
> 
> > * Support for Cygwin user names different from the Windows username.
> 
> I think I said it before, but I'll just repeat that I don't see this as a
> feature.
> Confusion option, at best. The worst case you've just outlined below.

Yeah, the discussion so far didn't really sway me from removing this
option.

> > * db_separator in /etc/nsswitch.conf
> 
> >   Is it really such a good idea to have a configurable separator
> >   char in user and group names?  Is it important that it is
> >   configurable?  Is '+' a good choice for the default separator?
> >   Wouldn't the backslash a better and, perhaps, only choice?
> 
> The "+" as a separator was conceived in *NIX because backslash has a long

in *NIX?  Do you mean SFU or is there other precedent of the '+
character I'm not aware of?

> history of being a way-too-meaningful escape character.
> (Though, you know it, I'll just say it for other interested parties.)
> I don't have an opinion on it, but I tend to favor native semantics, means,
> the backslash.
> If anyone are familiar with modern state of preferred domain separator
> in Samba 4, would that effect the decision?

Quoting from the smb.conf man page:

   winbind separator (G)

       This parameter allows an admin to define the character used when
       listing a username of the form of DOMAIN \user. This parameter is
       only applicable when using the pam_winbind.so and nss_winbind.so
       modules for UNIX services.

       Please note that setting this parameter to + causes problems with
       group membership at least on glibc systems, as the character + is
       used as a special character for NIS in /etc/group.

       Default: winbind separator = '\'

       Example: winbind separator = +

We don't have the glibc/NIS problem, of course.  I'm not going to
comment on this, I'd really like to see what you guys think.  Obvious
choices are:

- Keep "db_separator", + as default
- Keep "db_separator", \ as default
- Remove "db_separator", fixed character +
- Remove "db_separator", fixed character \
- Something entirely different.


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Andrey Repin]

Greetings, Corinna Vinschen!

>> > What bugs me a bit is what this means for applications which expect
>> > fixed usernames.  Sshd, for instance, expects the fixed username
>> > "sshd" right now when using privilege separation.  I discussed this
>> > with the OpenSSH devs, and they understand the problem, but they think
>> > this should be handled by a Cygwin-specific function.  So there's some
>> > extra work in it for me to get OpenSSH up to speed with this change,
>> > but I fear I'm not the only one.  The more configurable stuff like this
>> > is, the more complicated it gets maintaining some packages.
>> 
>> I really don't see a problem. Is this implementation-dependent issue?
>> 99% you are operating within "current domain" and do not need to specify
>> domain prefix at all.

> Uh, but you're missing the situation where the machine is a domain
> machine but the privilege separation account "sshd" is created in
> the local SAM.  That's what the ssh-host-config script might do.
> Sshd will have to use MACHINE<separator>sshd as username for privsep
> in this case.

Never been in such situation, thanks for clarification.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 14.04.2014, <12:57>

Sorry for my terrible english...


--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Andrey Repin]

Greetings, Corinna Vinschen!

>> > * db_separator in /etc/nsswitch.conf
>> 
>> >   Is it really such a good idea to have a configurable separator
>> >   char in user and group names?  Is it important that it is
>> >   configurable?  Is '+' a good choice for the default separator?
>> >   Wouldn't the backslash a better and, perhaps, only choice?
>> 
>> The "+" as a separator was conceived in *NIX because backslash has a long

> in *NIX?  Do you mean SFU or is there other precedent of the '+
> character I'm not aware of?

Ok, Samba specifically. Sorry I was unclear.

>> history of being a way-too-meaningful escape character.
>> (Though, you know it, I'll just say it for other interested parties.)
>> I don't have an opinion on it, but I tend to favor native semantics, means,
>> the backslash.
>> If anyone are familiar with modern state of preferred domain separator
>> in Samba 4, would that effect the decision?

> Quoting from the smb.conf man page:

>    winbind separator (G)

>        This parameter allows an admin to define the character used when
>        listing a username of the form of DOMAIN \user. This parameter is
>        only applicable when using the pam_winbind.so and nss_winbind.so
>        modules for UNIX services.

>        Please note that setting this parameter to + causes problems with
>        group membership at least on glibc systems, as the character + is
>        used as a special character for NIS in /etc/group.

>        Default: winbind separator = '\'

>        Example: winbind separator = +

> We don't have the glibc/NIS problem, of course.  I'm not going to
> comment on this, I'd really like to see what you guys think.  Obvious
> choices are:

> - Keep "db_separator", + as default
> - Keep "db_separator", \ as default
> - Remove "db_separator", fixed character +
> - Remove "db_separator", fixed character \
> - Something entirely different.

mmm... For something entirely different...
Fixed db_separator = \
Default domain setting somewhere to tell Cygwin to look for users there first.
Environment variable to specify/override default domain on the fly.
Or even simpler, just an environment variable establishing the list of
domains to lookup. And the order of lookup.

Perhaps, convoluted, but could cover many cases, where simple user name would
be ambiguous, but useful. And doesn't break standalone installations, if not set.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 14.04.2014, <13:00>

Sorry for my terrible english...


--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1407 bytes --]

On Apr 14 13:08, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
> > We don't have the glibc/NIS problem, of course.  I'm not going to
> > comment on this, I'd really like to see what you guys think.  Obvious
> > choices are:
> 
> > - Keep "db_separator", + as default
> > - Keep "db_separator", \ as default
> > - Remove "db_separator", fixed character +
> > - Remove "db_separator", fixed character \
> > - Something entirely different.
> 
> mmm... For something entirely different...
> Fixed db_separator = \
> Default domain setting somewhere to tell Cygwin to look for users there first.

For clarity: There is no "looking for users first at"...  capability at
all.  The user is searched via the functions LookupAccountSid and
LookupAccountName and they decide by themselves in what order to look.

> Environment variable to specify/override default domain on the fly.

You mean, for deciding which domain goes unprepended?  That would be in
the nsswitch.conf file, but it would be possible to implement that.
But does it make sense?  Yet another configuration variable?

> Or even simpler, just an environment variable establishing the list of
> domains to lookup. And the order of lookup.

Not possible.


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Andrey Repin]

Greetings, Corinna Vinschen!

> For clarity: There is no "looking for users first at"...  capability at
> all.  The user is searched via the functions LookupAccountSid and
> LookupAccountName and they decide by themselves in what order to look.

Got it.

>> Environment variable to specify/override default domain on the fly.

> You mean, for deciding which domain goes unprepended?  That would be in
> the nsswitch.conf file, but it would be possible to implement that.
> But does it make sense?  Yet another configuration variable?

Look at it from the usability standpoint. The problem is not the separator
character, the problem is the ambiguity of the account names in certain
situations.
Yes, one of the solutions is to implement a separator character that doesn't
conflict with current functionality, but satisfy the requirement to be a
distinguished separation character.
But this is not the only possible solution.

>> Or even simpler, just an environment variable establishing the list of
>> domains to lookup. And the order of lookup.

> Not possible.

Yeah, dreams rarely come true. And often coming out weird, when they do.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 15.04.2014, <02:56>

Sorry for my terrible english...


--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1517 bytes --]

On Apr 15 03:00, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
> 
> > For clarity: There is no "looking for users first at"...  capability at
> > all.  The user is searched via the functions LookupAccountSid and
> > LookupAccountName and they decide by themselves in what order to look.
> 
> Got it.
> 
> >> Environment variable to specify/override default domain on the fly.
> 
> > You mean, for deciding which domain goes unprepended?  That would be in
> > the nsswitch.conf file, but it would be possible to implement that.
> > But does it make sense?  Yet another configuration variable?
> 
> Look at it from the usability standpoint. The problem is not the separator
> character, the problem is the ambiguity of the account names in certain
> situations.

What amiguity exactly?  Care to make up a dirt simple example?

> Yes, one of the solutions is to implement a separator character that doesn't
> conflict with current functionality, but satisfy the requirement to be a
> distinguished separation character.

That would be '+'.  And, in a way, the backslash could do as well.
If it works for Samba as default...

I'm pretty torn, right now.  This is one of the "features" of such
a solution where you simply can't do it right for all users.  So
I guess I should better stick to a configurable default.  Sigh.


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Ken Brown]

I've come across a glitch involving sshd and cygserver.  I normally have 
both running, but I've discovered that I have to start sshd before I 
start cygserver, or else I have problems (can't ssh from a 
non-administrator account to an administrator account).  Here are the 
details on 64 bit Cygwin; I haven't tested 32 bit:

I've installed the full 2014-04-12 snapshot and removed /etc/passwd and 
/etc/group.  I have an ordinary user kbrown and an administrator user 
kbrown-admin.  I now do the following:

1. Start sshd.
2. Start cygserver.
3. Start a Cygwin Terminal as user kbrown.
4. ssh into the kbrown-admin account (with publickey authentication used 
by default).

$ ssh kbrown-admin@localhost
Enter passphrase for key '/home/kbrown/.ssh/id_rsa':
setsockopt IPV6_TCLASS 16: Protocol not available:
Last login: Tue Apr 15 13:57:12 2014 from fe80::9956:cbba:6928:151c%11

Everything is fine.

Now I close the Cygwin Terminal, stop both services, and restart them in 
the other order (cygserver first, then sshd).  Repeating steps 3 and 4, 
I can't login:

$ ssh kbrown-admin@localhost
kbrown-admin@localhost's password:
Permission denied, please try again.
kbrown-admin@localhost's password:

Notice that (a) I didn't get a prompt for the passphrase for my ssh key, 
and (b) my password wasn't accepted.

Ken

--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1654 bytes --]

On Apr 15 14:14, Ken Brown wrote:
> I've come across a glitch involving sshd and cygserver.  I normally
> have both running, but I've discovered that I have to start sshd
> before I start cygserver, or else I have problems (can't ssh from a
> non-administrator account to an administrator account).  Here are
> the details on 64 bit Cygwin; I haven't tested 32 bit:
> 
> I've installed the full 2014-04-12 snapshot and removed /etc/passwd
> and /etc/group.  I have an ordinary user kbrown and an administrator
> user kbrown-admin.  I now do the following:
> 
> 1. Start sshd.
> 2. Start cygserver.
> 3. Start a Cygwin Terminal as user kbrown.
> 4. ssh into the kbrown-admin account (with publickey authentication
> used by default).
> 
> $ ssh kbrown-admin@localhost
> Enter passphrase for key '/home/kbrown/.ssh/id_rsa':
> setsockopt IPV6_TCLASS 16: Protocol not available:
> Last login: Tue Apr 15 13:57:12 2014 from fe80::9956:cbba:6928:151c%11
> 
> Everything is fine.
> 
> Now I close the Cygwin Terminal, stop both services, and restart
> them in the other order (cygserver first, then sshd).  Repeating
> steps 3 and 4, I can't login:
> 
> $ ssh kbrown-admin@localhost
> kbrown-admin@localhost's password:
> Permission denied, please try again.
> kbrown-admin@localhost's password:
> 
> Notice that (a) I didn't get a prompt for the passphrase for my ssh
> key, and (b) my password wasn't accepted.

Thanks for the report, Ken.  I'll have a look.


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 2797 bytes --]

Hi Ken,

On Apr 16 10:04, Corinna Vinschen wrote:
> On Apr 15 14:14, Ken Brown wrote:
> > I've come across a glitch involving sshd and cygserver.  I normally
> > have both running, but I've discovered that I have to start sshd
> > before I start cygserver, or else I have problems (can't ssh from a
> > non-administrator account to an administrator account).  Here are
> > the details on 64 bit Cygwin; I haven't tested 32 bit:
> > 
> > I've installed the full 2014-04-12 snapshot and removed /etc/passwd
> > and /etc/group.  I have an ordinary user kbrown and an administrator
> > user kbrown-admin.  I now do the following:
> > 
> > 1. Start sshd.
> > 2. Start cygserver.
> > 3. Start a Cygwin Terminal as user kbrown.
> > 4. ssh into the kbrown-admin account (with publickey authentication
> > used by default).
> > 
> > $ ssh kbrown-admin@localhost
> > Enter passphrase for key '/home/kbrown/.ssh/id_rsa':
> > setsockopt IPV6_TCLASS 16: Protocol not available:
> > Last login: Tue Apr 15 13:57:12 2014 from fe80::9956:cbba:6928:151c%11
> > 
> > Everything is fine.
> > 
> > Now I close the Cygwin Terminal, stop both services, and restart
> > them in the other order (cygserver first, then sshd).  Repeating
> > steps 3 and 4, I can't login:
> > 
> > $ ssh kbrown-admin@localhost
> > kbrown-admin@localhost's password:
> > Permission denied, please try again.
> > kbrown-admin@localhost's password:
> > 
> > Notice that (a) I didn't get a prompt for the passphrase for my ssh
> > key, and (b) my password wasn't accepted.
> 
> Thanks for the report, Ken.  I'll have a look.

To clarify:  This is a non-domain machine, right?  And sshd is running
under the cyg_server account while cygserver is running under the
LocalSystem account?

I'm just testing this, only with a domain machine and domain accounts,
and I can't reproduce this.  I have a bit of a problem to test this on a
non-domain machine because my network is set up for domain machines...

However, I found that I made a blatant mistake in cygserver.  The
message length was computed one byte too short, so the trailing \0 in
the passwd/group string wasn't transmitted.  This *might* be the cause
for your problem.

I just built a new snapshot.  Can you please try if this fixes it for
you?  Make sure to use the new cygserver!

While I was at it, I also added a patch to get rid of the "setsockopt
IPV6_TCLASS 16: Protocol not available" message.  I just *love* it if
Microsoft defines socket options in their headers, but then simply
returns WSAENOPROTOOPT when the appliction dares to use them...


Thanks,
Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Still testing needed: New passwd/group AD/SAM integration

[Ken Brown]

On 4/16/2014 2:35 AM, Corinna Vinschen wrote:
> Hi Ken,
>
> On Apr 16 10:04, Corinna Vinschen wrote:
>> On Apr 15 14:14, Ken Brown wrote:
>>> I've come across a glitch involving sshd and cygserver.  I normally
>>> have both running, but I've discovered that I have to start sshd
>>> before I start cygserver, or else I have problems (can't ssh from a
>>> non-administrator account to an administrator account).  Here are
>>> the details on 64 bit Cygwin; I haven't tested 32 bit:
>>>
>>> I've installed the full 2014-04-12 snapshot and removed /etc/passwd
>>> and /etc/group.  I have an ordinary user kbrown and an administrator
>>> user kbrown-admin.  I now do the following:
>>>
>>> 1. Start sshd.
>>> 2. Start cygserver.
>>> 3. Start a Cygwin Terminal as user kbrown.
>>> 4. ssh into the kbrown-admin account (with publickey authentication
>>> used by default).
>>>
>>> $ ssh kbrown-admin@localhost
>>> Enter passphrase for key '/home/kbrown/.ssh/id_rsa':
>>> setsockopt IPV6_TCLASS 16: Protocol not available:
>>> Last login: Tue Apr 15 13:57:12 2014 from fe80::9956:cbba:6928:151c%11
>>>
>>> Everything is fine.
>>>
>>> Now I close the Cygwin Terminal, stop both services, and restart
>>> them in the other order (cygserver first, then sshd).  Repeating
>>> steps 3 and 4, I can't login:
>>>
>>> $ ssh kbrown-admin@localhost
>>> kbrown-admin@localhost's password:
>>> Permission denied, please try again.
>>> kbrown-admin@localhost's password:
>>>
>>> Notice that (a) I didn't get a prompt for the passphrase for my ssh
>>> key, and (b) my password wasn't accepted.
>>
>> Thanks for the report, Ken.  I'll have a look.
>
> To clarify:  This is a non-domain machine, right?  And sshd is running
> under the cyg_server account while cygserver is running under the
> LocalSystem account?

Yes to all.

> I'm just testing this, only with a domain machine and domain accounts,
> and I can't reproduce this.  I have a bit of a problem to test this on a
> non-domain machine because my network is set up for domain machines...
>
> However, I found that I made a blatant mistake in cygserver.  The
> message length was computed one byte too short, so the trailing \0 in
> the passwd/group string wasn't transmitted.  This *might* be the cause
> for your problem.
>
> I just built a new snapshot.  Can you please try if this fixes it for
> you?  Make sure to use the new cygserver!

Yes, that fixed it.  Thanks.

> While I was at it, I also added a patch to get rid of the "setsockopt
> IPV6_TCLASS 16: Protocol not available" message.

Good.  It's nice to see that anymore.

Ken

--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Ken Brown]

On 4/16/2014 8:28 AM, Ken Brown wrote:
> On 4/16/2014 2:35 AM, Corinna Vinschen wrote:
>> Hi Ken,
>>
>> On Apr 16 10:04, Corinna Vinschen wrote:
>>> On Apr 15 14:14, Ken Brown wrote:
>>>> I've come across a glitch involving sshd and cygserver.  I normally
>>>> have both running, but I've discovered that I have to start sshd
>>>> before I start cygserver, or else I have problems (can't ssh from a
>>>> non-administrator account to an administrator account).  Here are
>>>> the details on 64 bit Cygwin; I haven't tested 32 bit:
>>>>
>>>> I've installed the full 2014-04-12 snapshot and removed /etc/passwd
>>>> and /etc/group.  I have an ordinary user kbrown and an administrator
>>>> user kbrown-admin.  I now do the following:
>>>>
>>>> 1. Start sshd.
>>>> 2. Start cygserver.
>>>> 3. Start a Cygwin Terminal as user kbrown.
>>>> 4. ssh into the kbrown-admin account (with publickey authentication
>>>> used by default).
>>>>
>>>> $ ssh kbrown-admin@localhost
>>>> Enter passphrase for key '/home/kbrown/.ssh/id_rsa':
>>>> setsockopt IPV6_TCLASS 16: Protocol not available:
>>>> Last login: Tue Apr 15 13:57:12 2014 from fe80::9956:cbba:6928:151c%11
>>>>
>>>> Everything is fine.
>>>>
>>>> Now I close the Cygwin Terminal, stop both services, and restart
>>>> them in the other order (cygserver first, then sshd).  Repeating
>>>> steps 3 and 4, I can't login:
>>>>
>>>> $ ssh kbrown-admin@localhost
>>>> kbrown-admin@localhost's password:
>>>> Permission denied, please try again.
>>>> kbrown-admin@localhost's password:
>>>>
>>>> Notice that (a) I didn't get a prompt for the passphrase for my ssh
>>>> key, and (b) my password wasn't accepted.
>>>
>>> Thanks for the report, Ken.  I'll have a look.
>>
>> To clarify:  This is a non-domain machine, right?  And sshd is running
>> under the cyg_server account while cygserver is running under the
>> LocalSystem account?
>
> Yes to all.
>
>> I'm just testing this, only with a domain machine and domain accounts,
>> and I can't reproduce this.  I have a bit of a problem to test this on a
>> non-domain machine because my network is set up for domain machines...
>>
>> However, I found that I made a blatant mistake in cygserver.  The
>> message length was computed one byte too short, so the trailing \0 in
>> the passwd/group string wasn't transmitted.  This *might* be the cause
>> for your problem.
>>
>> I just built a new snapshot.  Can you please try if this fixes it for
>> you?  Make sure to use the new cygserver!
>
> Yes, that fixed it.  Thanks.
>
>> While I was at it, I also added a patch to get rid of the "setsockopt
>> IPV6_TCLASS 16: Protocol not available" message.
>
> Good.  It's nice to see that anymore.
                   ^
                  not

--
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

Re: Still testing needed: New passwd/group AD/SAM integration

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 2219 bytes --]

On Apr 16 08:32, Ken Brown wrote:
> On 4/16/2014 8:28 AM, Ken Brown wrote:
> >On 4/16/2014 2:35 AM, Corinna Vinschen wrote:
> >>On Apr 16 10:04, Corinna Vinschen wrote:
> >>>On Apr 15 14:14, Ken Brown wrote:
> >>>>I've come across a glitch involving sshd and cygserver.  [...]
> >>>>Now I close the Cygwin Terminal, stop both services, and restart
> >>>>them in the other order (cygserver first, then sshd).  Repeating
> >>>>steps 3 and 4, I can't login:
> >>>>
> >>>>$ ssh kbrown-admin@localhost
> >>>>kbrown-admin@localhost's password:
> >>>>Permission denied, please try again.
> >>>>kbrown-admin@localhost's password:
> >>>>
> >>>>Notice that (a) I didn't get a prompt for the passphrase for my ssh
> >>>>key, and (b) my password wasn't accepted.
> >>>
> >>>Thanks for the report, Ken.  I'll have a look.
> >>
> >>To clarify:  This is a non-domain machine, right?  And sshd is running
> >>under the cyg_server account while cygserver is running under the
> >>LocalSystem account?
> >
> >Yes to all.
> >
> >>I'm just testing this, only with a domain machine and domain accounts,
> >>and I can't reproduce this.  I have a bit of a problem to test this on a
> >>non-domain machine because my network is set up for domain machines...
> >>
> >>However, I found that I made a blatant mistake in cygserver.  The
> >>message length was computed one byte too short, so the trailing \0 in
> >>the passwd/group string wasn't transmitted.  This *might* be the cause
> >>for your problem.
> >>
> >>I just built a new snapshot.  Can you please try if this fixes it for
> >>you?  Make sure to use the new cygserver!
> >
> >Yes, that fixed it.  Thanks.
> >
> >>While I was at it, I also added a patch to get rid of the "setsockopt
> >>IPV6_TCLASS 16: Protocol not available" message.
> >
> >Good.  It's nice to see that anymore.
>                   ^
>                  not

Thanks for testing!  I had hoped that this is the culprit.   The
difference was obviously something realted to using or not using
cygserver...


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]