Cert name genning - incorrect info.

[akruk]

Somewhere in ADCS cert section this was posted:

There is no need of renaming it (cert) - hublist generates unique id for each cert file provided.

This is semi true thus its a nasty bug.
Well yes - our script does generate unique id for zip file but!
once unzipped - its what it was before id genning at hublist.

Simple example.
I had a cert named akrukshub.crt zipped it to akrukshub.zip then uploaded to dchublist.org ok?

Now our script - at "postdata" exactly gets that file - renames it to hub id.zip and stores we know where.

Now client (hublist user) downloads id.zip unzipps it it becomes akrukshub.crt again not id.crt

I'm unsure if this will cause any problems. Lets say everyone will just use mycert.crt as a filename will dc clients like dc++ or any other know which mycert.crt is for which hub??

[Admin]

I'm unsure if this will cause any problems. Lets say everyone will just use mycert.crt as a filename will dc clients like dc++ or any other know which mycert.crt is for which hub??

It will sure overwrite one another. Yes it is a problem.
Wow i will have to check on this. This is seriously wrong.

[Delion]

Let's say everyone will just use mycert.crt as a filename will dc clients like dc++ or any other know which mycert.crt is for which hub??

Yes, it will. DC client doesn't care about crt file names at all.
But! sure, file naming like hubaddress.crt is much more user-friendly.