UID-Creator testing thread

[CoD]

I open this thread for anyone who is interested in testing bsel's UID-Creator (see this thread for more info)

I start with my feedback: should uid-creator show some message?
Because I didn't get anything: neither good messages nor errror messages.
Additionally I can't find uid.asc, so I think there's something wrong in what I do.

I'm on ubuntu breezy badger, kernel  2.6.12-10

I put uid-creator files in:
/home/cod/uidcreator
and I started the program with:
./uidcreator LD_LIBRARY_PATH=/home/cod/uidcreator
but nothing happens.

What is my mistake?

[bsel]

You have to do it in this order I think:
LD_LIBRARY_PATH=/home/cod/uidcreator ./uidcreator
Because it's no parameter.

It returns error codes back to the console (bash: echo $?).
And against "No messages are good messages" it will give messages on success...

[CoD]

Thanks: it worked.  

[bsel]

With the newest version you don't need to set LD_LIBRARY_PATH.

[bsel]

Dear testers,

do you all get an unique ID? Also after rebooting? And not accidently different IDs.

[CoD]

I'll test. :wink:

[CoD]

Here I am, sorry for all this time without answer.

So: these are my uid.asc:

First trial

Code: [Select]


-----BEGIN SIGNED MESSAGE-----
90ee8483927acb48695092f3188cd69ed716af5b9249383fad8ff25937f34c7d7c5590ca0a6380c8146b138726f1a02ed661d6068c45cc67cdc9dc3aab376297
-----BEGIN SIGNATURE-----
29198acc94cfe3d0fa52418e237d21045f05c601ee9255066b60cc55cac6d0582c4454cf170b672615a1136f4d987ffe5b1b8a4769762b566e426cbc292170a15f20e237ccfa0449410285c0275d6085d740d32e7e20eaa8d1c55df3cbebe02e56dba254fc799d835c7e677697389c484412187db67a1f73aff96efaccabf77b7c315fbf1756c364417779d7842f5e453a39b5ee9b9baf8a5da56a4094a2e767aa091c33adf9c6d7656e712bad6f9f7410feb2081baa32bff0a72b2e9522c80c2eba0aeb091fe9629e69b9c89012b339cca2b718e64eac8396813c0f24ea2b2e9249bd38461e752640592edbc28d81cdc283f8dc344db190790f3dabbece8e6d
-----END SIGNATURE-----


Second trial (same session, just renamed previous uid.asc)

Code: [Select]


-----BEGIN SIGNED MESSAGE-----
90ee8483927acb48695092f3188cd69ed716af5b9249383fad8ff25937f34c7d7c5590ca0a6380c8146b138726f1a02ed661d6068c45cc67cdc9dc3aab376297
-----BEGIN SIGNATURE-----
3dee0ba1dddd23c78e215831202413fe36e6d370293a9a4040ae1d84f6952920969982b5bbbbbf54620328d427e78c13c5954eed632a3f6d3b30aa91a5753e61d1649f4208175def88b2d38968be1f6598dc34110123f27c306a33dbb9cc289e368cec3c1a839e141e2d7a4d740f550adc4b4d64032f78f15a0f90302559cf5588bae22e071a39e744df1d14e146abc416c573af27e09b937b71b8aae25d71df9046a34f9136f3e20756ff566e3db76ae7314e055a58057c439ae18deb1808eec17723975e4a3de7766be2d70c30304c345c2d894e16cd5c4a07d6e6d791c1bf37886d594539272dbcf78df594abc5fd0faa8686d52d112b46a89ce8f9828ea1
-----END SIGNATURE-----


Third trial (after some days and obviously a reboot)

Code: [Select]


-----BEGIN SIGNED MESSAGE-----
90ee8483927acb48695092f3188cd69ed716af5b9249383fad8ff25937f34c7d7c5590ca0a6380c8146b138726f1a02ed661d6068c45cc67cdc9dc3aab376297
-----BEGIN SIGNATURE-----
854ff3acd94f2f3c5c4307111df5f79624f1eba580cf45dd77eac11cbf649350d17b20e5620cf1d6a3381960ccf4a4f3b5f754a04edfa38124f7f17977b5edcaca73abbfa7d074c217da091d2d3e52f9910aa8abb68ff54441cc032bf7ff45d9a1c222dc4a21e56b12e3992e806bc56e8eb6a3786a9f0bd39d4fe3c8d76a6c664fe1ba588097b8d854fb77208ca2ca1c0ad5426f06f45d0e9fc88122c0febe2e06fbb1a875f59e49098545f6d82363f9db960aaea9299a4973d5498dda6df884ddc77bfd708e127f08b2eba84d45b6f4d7b8bd284f119bf60ba70ecede97e88892320bd47bf43785a9642a8562c67da7f994b24bd4328168285a427dac01612d
-----END SIGNATURE-----


As you can see the second part of the signed message (the signature) is changing, while the first part remains the same across days and reboots.

[bsel]

Thanks a lot, CoD.
The second part (signature) changes because it contains the time of signing.
Seems to work