cdsa-maintainers — Mailing list to be used only be the maintainers.

Re: [CDSA-maintainers] A bug or not?

[afchine <Afc...@bu...>]

Hi Dan,
You're right this is a bug. We must have the name of the shared
library after --soname in LDFLAGS. So --soname=libinhrspwbsp.so 
is the good one.
Regards,
Afchine
----- Original Message ----- 
From: "Dan Nuffer" <dn...@ca...>
To: <cds...@so...>
Sent: Friday, January 26, 2001 8:05 PM
Subject: [CDSA-maintainers] A bug or not?


Hi,
I have been experiencing the following problem with cdsa:
Once it is installed, when ldconfig is run, it outputs an error:

[root@boson /sbin]# /sbin/ldconfig
/sbin/ldconfig: /usr/lib/libinhrsdummy.so is not a symbolic link


This is caused because libinhrspwbsp.so is linked with the
"-soname=libinhrsdummy.so" flag

Here is an excerpt from
cdsa_dev/cdsa/src/addins/intel/hrspwbsp/makefile:

LDFLAGS:=       -shared -fPIC \
                -L$(LIB_PATH) \
                -lmds_util \
                -lmds_util_api \
                -leisl \
                -leicl \
                -leber_der \
                -lmds \
                -lport \
                -Wl,-Bstatic -ldl -Wl,-Bdynamic \
                -lpthread \
                -Wl,--soname=libinhrsdummy.so \
                -Wl,--version-script=hrspwbsp.ver



Now, I believe the it should use "--soname=libinhrspwbsp.so" flag
instead.  First, I wanted to check and make sure that this is really a
problem, and that there is not some reason for
"--soname=libinhrsdummy.so"
Does anyone have any ideas about this?

Thanks,
Dan

_______________________________________________
CDSA-maintainers mailing list
CDS...@li...
http://lists.sourceforge.net/lists/listinfo/cdsa-maintainers

[CDSA-maintainers] A bug or not?

[Dan N. <dn...@ca...>]

Hi,
I have been experiencing the following problem with cdsa:
Once it is installed, when ldconfig is run, it outputs an error:

[root@boson /sbin]# /sbin/ldconfig
/sbin/ldconfig: /usr/lib/libinhrsdummy.so is not a symbolic link


This is caused because libinhrspwbsp.so is linked with the
"-soname=libinhrsdummy.so" flag

Here is an excerpt from
cdsa_dev/cdsa/src/addins/intel/hrspwbsp/makefile:

LDFLAGS:=       -shared -fPIC \
                -L$(LIB_PATH) \
                -lmds_util \
                -lmds_util_api \
                -leisl \
                -leicl \
                -leber_der \
                -lmds \
                -lport \
                -Wl,-Bstatic -ldl -Wl,-Bdynamic \
                -lpthread \
                -Wl,--soname=libinhrsdummy.so \
                -Wl,--version-script=hrspwbsp.ver



Now, I believe the it should use "--soname=libinhrspwbsp.so" flag
instead.  First, I wanted to check and make sure that this is really a
problem, and that there is not some reason for
"--soname=libinhrsdummy.so"
Does anyone have any ideas about this?

Thanks,
Dan

RE: [CDSA-maintainers] Adding a file to the cvs repository

[Shafik, M. <moh...@in...>]

Shane,

I hadn't setup the WinCVS as mentioned in SourceForge tutorial
(http://sourceforge.net/docman/display_doc.php?docid=769&group_id=1).
Now everything is working just fine. Thanks.

-Shafik

> -----Original Message-----
> From: Shane Smit [mailto:ss...@ca...]
> Sent: Thursday, December 07, 2000 4:03 PM
> To: Shafik, MohamedX
> Cc: cds...@so...
> Subject: Re: [CDSA-maintainers] Adding a file to the cvs repository
> 
> 
> Shafik,
> 
> 	Did you use your SourceForge user name when you issued 
> the command? (-dshafikm: ... )
> 
> 	-Shane
> 
> On Thu, Dec 07, 2000 at 03:02:57PM -0800, Shafik, MohamedX wrote:
> > Dan,
> > 
> > I wanted to add some stress test scripts to the CVS repository. 
> > When I use the "cvs add" command, it gives me the following error:
> > 
> > cvs [server aborted]: "add" requires write access to the repository
> > 
> > How can I get write access to the repository.
> > 
> > Thanks
> > Shafik
> > 
> > _______________________________________________
> > CDSA-maintainers mailing list
> > CDS...@li...
> > http://lists.sourceforge.net/mailman/listinfo/cdsa-maintainers
> 

Re: [CDSA-maintainers] Adding a file to the cvs repository

[Shane S. <ss...@ca...>]

Shafik,

	Did you use your SourceForge user name when you issued the command? (-dshafikm: ... )

	-Shane

On Thu, Dec 07, 2000 at 03:02:57PM -0800, Shafik, MohamedX wrote:
> Dan,
> 
> I wanted to add some stress test scripts to the CVS repository. 
> When I use the "cvs add" command, it gives me the following error:
> 
> cvs [server aborted]: "add" requires write access to the repository
> 
> How can I get write access to the repository.
> 
> Thanks
> Shafik
> 
> _______________________________________________
> CDSA-maintainers mailing list
> CDS...@li...
> http://lists.sourceforge.net/mailman/listinfo/cdsa-maintainers

[CDSA-maintainers] Adding a file to the cvs repository

[Shafik, M. <moh...@in...>]

Dan,

I wanted to add some stress test scripts to the CVS repository. 
When I use the "cvs add" command, it gives me the following error:

cvs [server aborted]: "add" requires write access to the repository

How can I get write access to the repository.

Thanks
Shafik

Re: [CDSA-maintainers] Changes in CDSA CVS repository at SourceForge

[Dan N. <dn...@ca...>]

"Shafik, MohamedX" wrote:
> 
> Dan,
> 
> I had checked in a file in cdsa_dev/cdsa/src/addins/intel/hrspwbsp/
> directory (hrspwbspi.c) before you removed the 1.1.1.1 branch. When
> I view this via the web page, it shows the revision as 1.1.
> 
> http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi/cdsa_dev/cdsa/src/addins/intel
> /hrspwbsp/?cvsroot=cdsa
> 
> When you browse into the page for that file, it shows the change
> history properly. Do you know why it is showing the version wrongly.
> 
> Thanks
> Shafik
> 

Version 1.1 head the tag: HEAD, and I guess the web page was showing
that 1.1 because of the HEAD tag.
I added a blank line and committed the file- now the web page shows
version 1.3.  Version 1.3 now has the HEAD tag.
So I think, to fix the wrong version showing up for a certain file, just
create a new version and commit it.

--Dan

Re: [CDSA-maintainers] Changes in CDSA CVS repository at SourceForge

[Dan N. <dn...@ca...>]

Dan Nuffer wrote:
> 
> I agree the best solution is to do this.  Let's do it this way:
> Step 1: Each maintainer commits any changes to cvs (or save a patch to
> apply later), deletes their local copy of cdsa checked out code, and
> then e-mails cds...@so... to let me know they've
> done it.
> Step 2: After I have received confirmation from Hugh, Afchine and Shafik
> I will delete all 1.1.1.1 revisions from cvs.
> Step 3: I will e-mail everyone letting them know it is done, and then
> everyone can check out the code again.
> 
> Sound good?
> 
> --Dan
> 

Okay, It's now done.
I ran into some problems (1), but I think it's all been fixed.  Please
re-check out the code and yell if there are any problems!  I have
already checked out the code and started a build, and things seem to be
going smoothly so far.

--Dan

(1) I deleted version 1.1.1.1, and then when I went to check out the
code to make sure everything worked, almost all the files were gone, and
cvs was giving me lots of error messages.  So, looking at the web cvs at
sourceforge, it said that the default branch was 1.1.1.1, so when trying
to check out files it was trying to get non-existent ones.  After lots
of reading man pages and cvs documentation, I discovered how to change
the default branch.  Unfortunately it wouldn't work recursively, so I
had to run the cvs command for each file.  This took most of the day
yesterday to do.  It still hadn't finished when I went home.  It looks
like everything is fine now :)

Re: [CDSA-maintainers] Changes in CDSA CVS repository at SourceForge

[afchine <Afc...@bu...>]

I have commited my changes. For me it's ok now, you can go ahead and remove
the 1.1.1.1 branch. I can wait your signal to do the next check out.
Thanks,
Afchine
----- Original Message ----- 
From: "Dan Nuffer" <dn...@ca...>
To: "Shafik, MohamedX" <moh...@in...>
Cc: <cds...@so...>
Sent: Monday, December 04, 2000 5:34 PM
Subject: Re: [CDSA-maintainers] Changes in CDSA CVS repository at SourceForge


I agree the best solution is to do this.  Let's do it this way:
Step 1: Each maintainer commits any changes to cvs (or save a patch to
apply later), deletes their local copy of cdsa checked out code, and
then e-mails cds...@so... to let me know they've
done it.
Step 2: After I have received confirmation from Hugh, Afchine and Shafik
I will delete all 1.1.1.1 revisions from cvs.
Step 3: I will e-mail everyone letting them know it is done, and then
everyone can check out the code again.

Sound good?

--Dan

"Shafik, MohamedX" wrote:
> 
> Dan,
> 
> I think it will be good to remove the 1.1.1.1 branch, as it will be
> less confusing to other developers. Since not many people have started
> using the cvs, we can probably take the hit now to delete and recheck
> out the files from cvs. Else there is a chance of someone checking into
> the 1.1.1.1 branch instead of the main branch.
> 
> If you think it will be risky to remove this, you can leave it there.
> 
> Thanks
> Shafik
> 
> > I think that the 1.1.1.1 version is a branch version.  It looks like I
> > unknowingly created a branch when I imported everything.  Fortunately,
> > your changes made it into the normal branch.
> > I don't have any experience with cvs branching, so I'm not
> > sure if this
> > will present a problem or not.  I read the cvs documentation on
> > branching, and I think we will be okay as long as changes we make are
> > checked into the 1.x branch and not the 1.1.1.x branch.
> >
> > One option for the admin command I noticed is that we could delete the
> > 1.1.1.1 revisions, and then we would be left with only the 1.1
> > versions.
> >
> > If we do decide to use the -o option to delete the 1.1.1.1 revisions,
> > everyone will have to delete their working copy of cdsa_dev
> > and re-check
> > it out.
> >
> > I think the easiest thing would be to leave it as it is and just make
> > sure that no modifications end up in the 1.1.1.x branch.
> > What do you think?
> >
> > --Dan
> > _______________________________________________
> > CDSA-maintainers mailing list
> > CDS...@li...
> > http://lists.sourceforge.net/mailman/listinfo/cdsa-maintainers
> >
_______________________________________________
CDSA-maintainers mailing list
CDS...@li...
http://lists.sourceforge.net/mailman/listinfo/cdsa-maintainers

RE: [CDSA-maintainers] Changes in CDSA CVS repository at SourceFo rge

[Shafik, M. <moh...@in...>]

Dan,

I have commited some changes to the CVS. You can go ahead and remove
the 1.1.1.1 branch.

Thanks
Shafik

> -----Original Message-----
> From: Dan Nuffer [mailto:dn...@ca...]
> Sent: Monday, December 04, 2000 8:34 AM
> To: Shafik, MohamedX
> Cc: cds...@so...
> Subject: Re: [CDSA-maintainers] Changes in CDSA CVS repository at
> SourceForge
> 
> 
> I agree the best solution is to do this.  Let's do it this way:
> Step 1: Each maintainer commits any changes to cvs (or save a patch to
> apply later), deletes their local copy of cdsa checked out code, and
> then e-mails cds...@so... to let me know they've
> done it.
> Step 2: After I have received confirmation from Hugh, Afchine 
> and Shafik
> I will delete all 1.1.1.1 revisions from cvs.
> Step 3: I will e-mail everyone letting them know it is done, and then
> everyone can check out the code again.
> 
> Sound good?
> 
> --Dan
> 
> "Shafik, MohamedX" wrote:
> > 
> > Dan,
> > 
> > I think it will be good to remove the 1.1.1.1 branch, as it will be
> > less confusing to other developers. Since not many people 
> have started
> > using the cvs, we can probably take the hit now to delete 
> and recheck
> > out the files from cvs. Else there is a chance of someone 
> checking into
> > the 1.1.1.1 branch instead of the main branch.
> > 
> > If you think it will be risky to remove this, you can leave 
> it there.
> > 
> > Thanks
> > Shafik
> > 
> > > I think that the 1.1.1.1 version is a branch version.  It 
> looks like I
> > > unknowingly created a branch when I imported everything.  
> Fortunately,
> > > your changes made it into the normal branch.
> > > I don't have any experience with cvs branching, so I'm not
> > > sure if this
> > > will present a problem or not.  I read the cvs documentation on
> > > branching, and I think we will be okay as long as changes 
> we make are
> > > checked into the 1.x branch and not the 1.1.1.x branch.
> > >
> > > One option for the admin command I noticed is that we 
> could delete the
> > > 1.1.1.1 revisions, and then we would be left with only the 1.1
> > > versions.
> > >
> > > If we do decide to use the -o option to delete the 
> 1.1.1.1 revisions,
> > > everyone will have to delete their working copy of cdsa_dev
> > > and re-check
> > > it out.
> > >
> > > I think the easiest thing would be to leave it as it is 
> and just make
> > > sure that no modifications end up in the 1.1.1.x branch.
> > > What do you think?
> > >
> > > --Dan
> > > _______________________________________________
> > > CDSA-maintainers mailing list
> > > CDS...@li...
> > > http://lists.sourceforge.net/mailman/listinfo/cdsa-maintainers
> > >
> _______________________________________________
> CDSA-maintainers mailing list
> CDS...@li...
> http://lists.sourceforge.net/mailman/listinfo/cdsa-maintainers
> 

RE: [CDSA-maintainers] Changes in CDSA CVS repository at SourceFo rge

[Woodworth, C. <con...@in...>]

Just a reminder that today is the day CDSA code comes off Intel's Corp.
Present Server.

-----Original Message-----
From: Hugh Davies [mailto:hu...@un...]
Sent: Monday, December 04, 2000 8:52 AM
To: Dan Nuffer
Cc: Shafik, MohamedX; cds...@so...
Subject: Re: [CDSA-maintainers] Changes in CDSA CVS repository at
SourceForge


Dan,

Sounds ok to me. I haven't yet set up a local cvs tree so it will
not affect me at present.

Hugh

> I agree the best solution is to do this.  Let's do it this way:
> Step 1: Each maintainer commits any changes to cvs (or save a patch to
> apply later), deletes their local copy of cdsa checked out code, and
> then e-mails cds...@so... to let me know they've
> done it.
> Step 2: After I have received confirmation from Hugh, Afchine and Shafik
> I will delete all 1.1.1.1 revisions from cvs.
> Step 3: I will e-mail everyone letting them know it is done, and then
> everyone can check out the code again.
> 
> Sound good?
> 
> --Dan
> 
> "Shafik, MohamedX" wrote:
> > 
> > Dan,
> > 
> > I think it will be good to remove the 1.1.1.1 branch, as it will be
> > less confusing to other developers. Since not many people have started
> > using the cvs, we can probably take the hit now to delete and recheck
> > out the files from cvs. Else there is a chance of someone checking into
> > the 1.1.1.1 branch instead of the main branch.
> > 
> > If you think it will be risky to remove this, you can leave it there.
> > 
> > Thanks
> > Shafik
> > 
> > > I think that the 1.1.1.1 version is a branch version.  It looks like I
> > > unknowingly created a branch when I imported everything.  Fortunately,
> > > your changes made it into the normal branch.
> > > I don't have any experience with cvs branching, so I'm not
> > > sure if this
> > > will present a problem or not.  I read the cvs documentation on
> > > branching, and I think we will be okay as long as changes we make are
> > > checked into the 1.x branch and not the 1.1.1.x branch.
> > >
> > > One option for the admin command I noticed is that we could delete the
> > > 1.1.1.1 revisions, and then we would be left with only the 1.1
> > > versions.
> > >
> > > If we do decide to use the -o option to delete the 1.1.1.1 revisions,
> > > everyone will have to delete their working copy of cdsa_dev
> > > and re-check
> > > it out.
> > >
> > > I think the easiest thing would be to leave it as it is and just make
> > > sure that no modifications end up in the 1.1.1.x branch.
> > > What do you think?
> > >
> > > --Dan
> > > _______________________________________________
> > > CDSA-maintainers mailing list
> > > CDS...@li...
> > > http://lists.sourceforge.net/mailman/listinfo/cdsa-maintainers
> > >
> _______________________________________________
> CDSA-maintainers mailing list
> CDS...@li...
> http://lists.sourceforge.net/mailman/listinfo/cdsa-maintainers
_______________________________________________
CDSA-maintainers mailing list
CDS...@li...
http://lists.sourceforge.net/mailman/listinfo/cdsa-maintainers

Re: [CDSA-maintainers] Changes in CDSA CVS repository at SourceForge

[Hugh D. <hu...@un...>]

Dan,

Sounds ok to me. I haven't yet set up a local cvs tree so it will
not affect me at present.

Hugh

> I agree the best solution is to do this.  Let's do it this way:
> Step 1: Each maintainer commits any changes to cvs (or save a patch to
> apply later), deletes their local copy of cdsa checked out code, and
> then e-mails cds...@so... to let me know they've
> done it.
> Step 2: After I have received confirmation from Hugh, Afchine and Shafik
> I will delete all 1.1.1.1 revisions from cvs.
> Step 3: I will e-mail everyone letting them know it is done, and then
> everyone can check out the code again.
> 
> Sound good?
> 
> --Dan
> 
> "Shafik, MohamedX" wrote:
> > 
> > Dan,
> > 
> > I think it will be good to remove the 1.1.1.1 branch, as it will be
> > less confusing to other developers. Since not many people have started
> > using the cvs, we can probably take the hit now to delete and recheck
> > out the files from cvs. Else there is a chance of someone checking into
> > the 1.1.1.1 branch instead of the main branch.
> > 
> > If you think it will be risky to remove this, you can leave it there.
> > 
> > Thanks
> > Shafik
> > 
> > > I think that the 1.1.1.1 version is a branch version.  It looks like I
> > > unknowingly created a branch when I imported everything.  Fortunately,
> > > your changes made it into the normal branch.
> > > I don't have any experience with cvs branching, so I'm not
> > > sure if this
> > > will present a problem or not.  I read the cvs documentation on
> > > branching, and I think we will be okay as long as changes we make are
> > > checked into the 1.x branch and not the 1.1.1.x branch.
> > >
> > > One option for the admin command I noticed is that we could delete the
> > > 1.1.1.1 revisions, and then we would be left with only the 1.1
> > > versions.
> > >
> > > If we do decide to use the -o option to delete the 1.1.1.1 revisions,
> > > everyone will have to delete their working copy of cdsa_dev
> > > and re-check
> > > it out.
> > >
> > > I think the easiest thing would be to leave it as it is and just make
> > > sure that no modifications end up in the 1.1.1.x branch.
> > > What do you think?
> > >
> > > --Dan
> > > _______________________________________________
> > > CDSA-maintainers mailing list
> > > CDS...@li...
> > > http://lists.sourceforge.net/mailman/listinfo/cdsa-maintainers
> > >
> _______________________________________________
> CDSA-maintainers mailing list
> CDS...@li...
> http://lists.sourceforge.net/mailman/listinfo/cdsa-maintainers

Re: [CDSA-maintainers] Changes in CDSA CVS repository at SourceForge

[Dan N. <dn...@ca...>]

I agree the best solution is to do this.  Let's do it this way:
Step 1: Each maintainer commits any changes to cvs (or save a patch to
apply later), deletes their local copy of cdsa checked out code, and
then e-mails cds...@so... to let me know they've
done it.
Step 2: After I have received confirmation from Hugh, Afchine and Shafik
I will delete all 1.1.1.1 revisions from cvs.
Step 3: I will e-mail everyone letting them know it is done, and then
everyone can check out the code again.

Sound good?

--Dan

"Shafik, MohamedX" wrote:
> 
> Dan,
> 
> I think it will be good to remove the 1.1.1.1 branch, as it will be
> less confusing to other developers. Since not many people have started
> using the cvs, we can probably take the hit now to delete and recheck
> out the files from cvs. Else there is a chance of someone checking into
> the 1.1.1.1 branch instead of the main branch.
> 
> If you think it will be risky to remove this, you can leave it there.
> 
> Thanks
> Shafik
> 
> > I think that the 1.1.1.1 version is a branch version.  It looks like I
> > unknowingly created a branch when I imported everything.  Fortunately,
> > your changes made it into the normal branch.
> > I don't have any experience with cvs branching, so I'm not
> > sure if this
> > will present a problem or not.  I read the cvs documentation on
> > branching, and I think we will be okay as long as changes we make are
> > checked into the 1.x branch and not the 1.1.1.x branch.
> >
> > One option for the admin command I noticed is that we could delete the
> > 1.1.1.1 revisions, and then we would be left with only the 1.1
> > versions.
> >
> > If we do decide to use the -o option to delete the 1.1.1.1 revisions,
> > everyone will have to delete their working copy of cdsa_dev
> > and re-check
> > it out.
> >
> > I think the easiest thing would be to leave it as it is and just make
> > sure that no modifications end up in the 1.1.1.x branch.
> > What do you think?
> >
> > --Dan
> > _______________________________________________
> > CDSA-maintainers mailing list
> > CDS...@li...
> > http://lists.sourceforge.net/mailman/listinfo/cdsa-maintainers
> >

RE: [CDSA-maintainers] Changes in CDSA CVS repository at SourceFo rge

[Shafik, M. <moh...@in...>]

Dan,

I think it will be good to remove the 1.1.1.1 branch, as it will be
less confusing to other developers. Since not many people have started 
using the cvs, we can probably take the hit now to delete and recheck 
out the files from cvs. Else there is a chance of someone checking into 
the 1.1.1.1 branch instead of the main branch.

If you think it will be risky to remove this, you can leave it there.

Thanks
Shafik

> I think that the 1.1.1.1 version is a branch version.  It looks like I
> unknowingly created a branch when I imported everything.  Fortunately,
> your changes made it into the normal branch.
> I don't have any experience with cvs branching, so I'm not 
> sure if this
> will present a problem or not.  I read the cvs documentation on
> branching, and I think we will be okay as long as changes we make are
> checked into the 1.x branch and not the 1.1.1.x branch.
> 
> One option for the admin command I noticed is that we could delete the
> 1.1.1.1 revisions, and then we would be left with only the 1.1
> versions.  
> 
> If we do decide to use the -o option to delete the 1.1.1.1 revisions,
> everyone will have to delete their working copy of cdsa_dev 
> and re-check
> it out.
> 
> I think the easiest thing would be to leave it as it is and just make
> sure that no modifications end up in the 1.1.1.x branch.
> What do you think?
> 
> --Dan
> _______________________________________________
> CDSA-maintainers mailing list
> CDS...@li...
> http://lists.sourceforge.net/mailman/listinfo/cdsa-maintainers
> 

Re: [CDSA-maintainers] Changes in CDSA CVS repository at SourceForge

[Dan N. <dn...@ca...>]

afchine wrote:
> 
> I put source and makefile changes for AIX and some other issues to CDSA CVS repository.
> 
> Thu Nov 30 15:51:55 CET 2000 Afc...@bu...
>         * add "configure" to set environment before make CDSA
>         * change in rules.mk, replace CCM_PROJECT_PATH by CVS_PATH,
>         add specific rules for AIX
>         * add install, uninstall product and develoment kit to the main makefile
>         * add Linux and AIX directories under build directory
>         * update linux_readme.txt and add aix_readme.txt
>         * change makefiles for AIX
>         * port Cryptoki Adatation Layer on Linux
>         * add GPKCS11* Based CSP plugged to Cryptoki Adatation Layer
>         * remove xmlparse import directory, replaced by use of
>         w3c-libwww-devel package on Linux
> 
> But I think that I made a bad manipulation because the release of modified files is upgraded from
> 1.1.1.1 to 1.2. and not to 1.1.1.2. Is it normal?
> 

I think that the 1.1.1.1 version is a branch version.  It looks like I
unknowingly created a branch when I imported everything.  Fortunately,
your changes made it into the normal branch.
I don't have any experience with cvs branching, so I'm not sure if this
will present a problem or not.  I read the cvs documentation on
branching, and I think we will be okay as long as changes we make are
checked into the 1.x branch and not the 1.1.1.x branch.

One option for the admin command I noticed is that we could delete the
1.1.1.1 revisions, and then we would be left with only the 1.1
versions.  
Here's the text from the documentation:

`-oRANGE'
     Deletes ("outdates") the revisions given by RANGE.

     Note that this command can be quite dangerous unless you know
     _exactly_ what you are doing (for example see the warnings below
     about how the REV1:REV2 syntax is confusing).

     If you are short on disc this option might help you.  But think
     twice before using it--there is no way short of restoring the
     latest backup to undo this command!  If you delete different
     revisions than you planned, either due to carelessness or (heaven
     forbid) a CVS bug, there is no opportunity to correct the error
     before the revisions are deleted.  It probably would be a good
     idea to experiment on a copy of the repository first.
...
     Make sure that no-one has checked out a copy of the revision you
     outdate.  Strange things will happen if he starts to edit it and
     tries to check it back in.  For this reason, this option is not a
     good way to take back a bogus commit; commit a new revision
     undoing the bogus change instead (*note Merging two revisions::.).



If we do decide to use the -o option to delete the 1.1.1.1 revisions,
everyone will have to delete their working copy of cdsa_dev and re-check
it out.

I think the easiest thing would be to leave it as it is and just make
sure that no modifications end up in the 1.1.1.x branch.
What do you think?

--Dan

[CDSA-maintainers] Changes in CDSA CVS repository at SourceForge

[afchine <Afc...@bu...>]

I put source and makefile changes for AIX and some other issues to CDSA CVS repository.

Thu Nov 30 15:51:55 CET 2000 Afc...@bu...
        * add "configure" to set environment before make CDSA
        * change in rules.mk, replace CCM_PROJECT_PATH by CVS_PATH,
        add specific rules for AIX
        * add install, uninstall product and develoment kit to the main makefile
        * add Linux and AIX directories under build directory
        * update linux_readme.txt and add aix_readme.txt
        * change makefiles for AIX
        * port Cryptoki Adatation Layer on Linux
        * add GPKCS11* Based CSP plugged to Cryptoki Adatation Layer
        * remove xmlparse import directory, replaced by use of
        w3c-libwww-devel package on Linux

But I think that I made a bad manipulation because the release of modified files is upgraded from 
1.1.1.1 to 1.2. and not to 1.1.1.2. Is it normal?

Regards
afchine

Afc...@bu...
Bull, R&D, Networking & Security
France

[CDSA-maintainers] RE: Directory structure of cdsa is now fixed.

[Woodworth, C. <con...@in...>]

Dan and Shafik,

Where are we on these two issues:

	1)testing/verify on windows 
	2)deleting old directory structure in cvs and getting current one 

-----Original Message-----
From: Dan Nuffer [mailto:dn...@ca...]
Sent: Wednesday, November 22, 2000 9:37 AM
To: cds...@so...
Cc: con...@in...
Subject: Directory structure of cdsa is now fixed.


Hi all,

This morning, Sourceforge got to our help request and erased the bad CVS
directory structure for cdsa_dev.  I have reimported the code with the
correct structure, and applied the changes Shafik sent me for the
windows build files.  However, I am unable to test the windows build
process, since I don't have any windows machines around here...  It
would be good if Shafik could just verify that the windows build
proecess still works.

Since the directory structure changed, if any of you have a working cvs
repository of cdsa_dev, you should delete it and re-checkout to avoid
conflicts and confusion.
Now that this is done, we can go ahead and start making changes to the
code base in cvs.


--Dan

[Fwd: Re: [CDSA-maintainers] Directory structure of cdsa is now fixed.]

[Dan N. <dn...@ca...>]

Whoops, I hit reply when I should've hit reply-all to send it to the
list.

-------- Original Message --------
Subject: Re: [CDSA-maintainers] Directory structure of cdsa is now
fixed.
Date: Mon, 27 Nov 2000 10:07:28 -0700
From: Dan Nuffer <dn...@ca...>
To: "Shafik, MohamedX" <moh...@in...>
References:
<414...@or...>

"Shafik, MohamedX" wrote:
> 
> Dan,
> 
> Thanks for getting the directory structure fixed. I was
> successful in building it on Windows. I had to fix couple
> of things in the CVS:
> 
> - I had sent intelac.dsp file copied under
>   cdsa_dev/cdsa/src/addins/cssmac/intelac directory instead of
>   cdsa_dev/cdsa/src/addins/cssmac/intel_ac. I rectified this
>   at SourceForge CVS. But the directory .../cssmac/intelac is
>   still there. Can you help in removing this directory.

Well, we will need to submit a help request to sourceforge.  Shane, how
do we do that?

> 
> - I missed sending you the updated Pkcstokn.dsp file in
>   cdsa_dev/cdsa/src/addins/cssmcsp/pkcs_2_0 directory. I have
>   updated CVS with the correct one.
> 
> I noticed some missing directories under cdsa/src/imports.
> These directories are place holders for optional CSP adaptation
> layers like BSafe, Chryslis, Luna etc. There are references in
> the Quick Start Guide to these directories. It will be nice to
> have them there.
> 
> BTW, how do I add a directory in the CVS?

Hmm, it looks like cvs ignores empty directories when importing.  I
didn't realize they didn't get imported.  cvs also doesn't create empty
directories when someone checks out the source code.  If we want those
directories to be always present for someone who checks out the source,
we will have to place some sort of file in them.  Maybe a README
explaining what they are for.  I will do this.

Adding a directory to cvs is easy, you just make the directory and then
do a cvs add on it.
Example:

mkdir BSafe
cvs add BSafe

--Dan

RE: [CDSA-maintainers] Directory structure of cdsa is now fixed.

[Shafik, M. <moh...@in...>]

Dan,

Thanks for getting the directory structure fixed. I was
successful in building it on Windows. I had to fix couple
of things in the CVS:

- I had sent intelac.dsp file copied under 
  cdsa_dev/cdsa/src/addins/cssmac/intelac directory instead of 
  cdsa_dev/cdsa/src/addins/cssmac/intel_ac. I rectified this
  at SourceForge CVS. But the directory .../cssmac/intelac is
  still there. Can you help in removing this directory.

- I missed sending you the updated Pkcstokn.dsp file in 
  cdsa_dev/cdsa/src/addins/cssmcsp/pkcs_2_0 directory. I have
  updated CVS with the correct one.

I noticed some missing directories under cdsa/src/imports. 
These directories are place holders for optional CSP adaptation
layers like BSafe, Chryslis, Luna etc. There are references in
the Quick Start Guide to these directories. It will be nice to
have them there. 

BTW, how do I add a directory in the CVS?

I am having a minor problem with the CTS build. I will update the
CVS early next week with the changes. Also I will update the
documentation with instructions on installing Tetware and CTS tests.

Happy Holidays! 

Best Regards
Shafik


> -----Original Message-----
> From: Dan Nuffer [mailto:dn...@ca...]
> Sent: Wednesday, November 22, 2000 9:37 AM
> To: cds...@so...
> Cc: con...@in...
> Subject: [CDSA-maintainers] Directory structure of cdsa is now fixed.
> 
> 
> Hi all,
> 
> This morning, Sourceforge got to our help request and erased 
> the bad CVS
> directory structure for cdsa_dev.  I have reimported the code with the
> correct structure, and applied the changes Shafik sent me for the
> windows build files.  However, I am unable to test the windows build
> process, since I don't have any windows machines around here...  It
> would be good if Shafik could just verify that the windows build
> proecess still works.
> 
> Since the directory structure changed, if any of you have a 
> working cvs
> repository of cdsa_dev, you should delete it and re-checkout to avoid
> conflicts and confusion.
> Now that this is done, we can go ahead and start making changes to the
> code base in cvs.
> 
> 
> --Dan
> _______________________________________________
> CDSA-maintainers mailing list
> CDS...@li...
> http://lists.sourceforge.net/mailman/listinfo/cdsa-maintainers
> 

[CDSA-maintainers] Directory structure of cdsa is now fixed.

[Dan N. <dn...@ca...>]

Hi all,

This morning, Sourceforge got to our help request and erased the bad CVS
directory structure for cdsa_dev.  I have reimported the code with the
correct structure, and applied the changes Shafik sent me for the
windows build files.  However, I am unable to test the windows build
process, since I don't have any windows machines around here...  It
would be good if Shafik could just verify that the windows build
proecess still works.

Since the directory structure changed, if any of you have a working cvs
repository of cdsa_dev, you should delete it and re-checkout to avoid
conflicts and confusion.
Now that this is done, we can go ahead and start making changes to the
code base in cvs.


--Dan

Re: [CDSA-maintainers] ssh command line version on Windows

[Hugh D. <hu...@un...>]

Shafik,

Try doing a search via www.google.com using search key
	win32 ssh

There is quite a lot, there may be something you can use.
I have not used any of them so cannot recommend anything.

Regards,
	Hugh

On Tue, Nov 21, 2000 at 06:20:51PM -0800, Shafik, MohamedX wrote:
> Dan,
> 
> Do you know where I can find a command line version of ssh running on
> Windows platform.
> 
> Thanks
> Shafik
> 
> _______________________________________________
> CDSA-maintainers mailing list
> CDS...@li...
> http://lists.sourceforge.net/mailman/listinfo/cdsa-maintainers

Re: [CDSA-maintainers] ssh command line version on Windows

[afchine <Afc...@bu...>]

Shafik,
Look at http://sfdocs.sourceforge.net/sfdocs/display_topic.php?topicid=19
then download SSH at
ftp://ftp.cs.hut.fi/pub/ssh/SSHWin-2.3.0.exe

Afchine

----- Original Message ----- 
From: "Shafik, MohamedX" <moh...@in...>
To: <cds...@so...>
Sent: Wednesday, November 22, 2000 3:20 AM
Subject: [CDSA-maintainers] ssh command line version on Windows


> Dan,
> 
> Do you know where I can find a command line version of ssh running on
> Windows platform.
> 
> Thanks
> Shafik
> 

[CDSA-maintainers] ssh command line version on Windows

[Shafik, M. <moh...@in...>]

Dan,

Do you know where I can find a command line version of ssh running on
Windows platform.

Thanks
Shafik

[CDSA-maintainers] CDSA distribution files uploaded to sourceforge.

[Dan N. <dn...@ca...>]

I uploaded the CDSA files that are available on Intel's CPS to
Sourceforge.
The 4 files (cdsacode.zip, cdsa_man.zip, cdsadocs.zip, cdsa_cts.zip) are
now availble for people to download from the main CDSA Sourceforge
project page.

--Dan

[CDSA-maintainers] Test

[Shane S. <ss...@ca...>]

	This is just a test of our cdsa-maintainers mailing list.  Also, if anybody still has any problems with CVS, SSH, or anything to do with SourceForge in general, please respond to this message publicly (Perhaps more than one person has the same question). There are still some people that haven't joined the mailing list, please encourage anyone who should be involved in this to do so.

	-Shane Smit
	Caldera, Inc.