in reply to Re^2: RFC: Algorithm::CouponCode
in thread RFC: Algorithm::CouponCode

That sounds like an attempt at "security through obscurity"

I am not theorising here - you have unwittingly compromised an existing government system - what algorithm I personally would use is neither offered nor relevant - it is more important to understand the impact of leaving it as is.

One world, one people

Replies are listed 'Best First'.
Re^4: RFC: Algorithm::CouponCode
by grantm (Parson) on Apr 28, 2011 at 09:54 UTC

    I'm sorry, I have read and re-read your comment but I don't understand what point you're trying to make. Perhaps you could rephrase it.

    It certainly sounds like I need to update the documentation of my module to discourage further misunderstandings.

      Let me tell it as a story: Once upon a time in the early days of computers a government department chooses a particular mechanism for generating and testing the validity of codes it generates and publishes. It still uses the legacy system in question because noone broke it yet. Lo and behold someone else (you) has accidentally used the same method but is providing it on an online facility that can be brute forced whereas the government system is not available online and cannot be brute forced. How the story continues from here is up to you and the offended government department if they find out.

      One world, one people

        Let me tell it as a story: Once upon a time on Perlmonks there was a software developer who told a story. The story wasn't based on fact but, rather, constructed a straw man for the software developer to argue against. It was all very interesting but, as it bore no relation to reality, not really very applicable.