Aaron Stone wrote:
<snip>
I truly don't understand why the filesystem state and whatnot matters
here, because unless I'm truly missing something, what we're looking at is
the need to assume that the two messages inserted into two different
databases on two different dbmail hosts cannot ever have the same message
id. Our proposed approach is the prefix each key with some value that is
unique to the host / instance of dbmail which is doing the inserting and
therefore cannot be shared by any of the other machines in the cluster.
Aaron
I have understood from reading the RFC that the UUID consists of
three parts, MAC+random_number+time. Where the random number is
reevaluated each time the delivery process starts.
What is the probability of two colliding UUIDs?
What happens when two UUIDs collide?
Is it worth all trouble doing avoiding duplicate UUIDs?
<snip>
Then
Vladimir Rüntü wrote:
> Just some thouhts from me.
>
> Is it possible to change the MAC address either in the hardware
> or in the packets? If yes then this makes the system
> vulnearable to the hackers.
>
> But this idea to pregenerate the unique keys works to my mind.
> There is only one instance of dbmail-maintenance that should be
> executed now and then. This instance should pregenereate the
> keys.
>
>
> best wishes,
>
> Vlads
>
You can change the MAC on some ethernet boards, i beleive the
command is "ifconfig".
To do this you have to be root. If a hacker has aquired root my
opinion is that you are cooked anyway.
/Magnus
