69910 - certutil failures under cygwin - absolute paths

Status: RESOLVED FIXED

(NSS :: Tools, defect, P3)

Description

[Sonja Mirtitsch]

certutil works fine as long as there are no absolute paths involved
unlike MKS cygnus uses unix style paths. The same behavior if -d is anything but
the current directory.

I'd like this bug to be a high priority, because I am trying to make the new
tests work on all systems at the same time, and withiout certutil I can do
almost no testing on cygnus. Right now I check the possibility of running
everything in relative paths, they are certainly treated better then absolute
paths. If this works we can make it a lower priority.

I strongly suspect that other tools work the same way


$ certutil -N -d .  -f /tmp/tests.pw.1283
No password file "/tmp/tests.pw.1283" exists.
$ rm cert7.db       key3.db        secmod.db
$ cp /tmp/tests.pw.1283 .
$ certutil -N -d .  -f tests.pw.1283
$ ls
cert7.db       key3.db        secmod.db      tests.pw.1283

Comment 1

[Sonja Mirtitsch]

I rewrote cert.sh to use  relative PATHS, so I reduce the priority, but I'd
still need a fix. If it can't be fixed within the next 2 week plkease assign
back to me.

What I did in the scripts impacts the readability, since each directory and each
filename has a variable for it's absolute and one for the relative value, the
relative one needs to change depending on the cwd and they are used alternately.

Also, other people might want to use the tools under cygnus as well.

Comment 2

[Sonja Mirtitsch]

On second thought - the relative PATHS make the output.log a lot more readable
maybe I will change the QA scripts permanently.
All programms used by tools.sh had the same problem

Comment 3

[Wan-Teh Chang]

Cygnus does not support drive letters well.

"/tmp/tests.pw.1283" probably means "C:/tmp/tests.pw.1283"
under Cygnus.

I guess you were running the test on a drive other than the
C drive?

Comment 4

[Sonja Mirtitsch]

+ Cygnus does not support drive letters well.

Correct. What is now c: is mounted underneath cygnus's virtual root as
/cygdrive/c, d: will be mounted in /cygdrive/d

+ "/tmp/tests.pw.1283" probably means "C:/tmp/tests.pw.1283"
+ under Cygnus.

No. C:/tmp would be refered as /cygdrive/c/tmp which does not exist on my machine.

administrator@SONJANT ~
$ ls /tmp
tests.pw.1005     tests.pw.1049     tests.pw.1105     tests_noise.1105
tests.pw.1023     tests.pw.1080     tests.pw.1283     tests_noise.1283

administrator@SONJANT ~
$ ls /cygdrive/c/tmp
ls: /cygdrive/c/tmp: No such file or directory

+ I guess you were running the test on a drive other than the
+ C drive?

Yes, the tests always run on the nightly builds. The drives don't have any
special meaning under cygnus, as cygnus tries to get as close to Unix as
possible, and I am certain there is a way to mount what is now
/cygdrive/w/nss/nsstip/builds to be /cygdrive/c, but I don't see any benefits?

Comment 5

[Sonja Mirtitsch]

These failures have been removed, a relative PATH Is used everywhere in the script.
I will file a new bug on the cygnus selfserv failures.