PGP Desktop 9 source code

Discussion in 'privacy technology' started by Hexadecimal Maniac, Aug 5, 2006.

Thread Status:
Not open for further replies.
  1. Hexadecimal Maniac

    Hexadecimal Maniac Registered Member

    Joined:
    Aug 5, 2006
    Posts:
    4
    I've been trying to get some answers about the completeness of the PGP Desktop 9 source code from some clueless people at the PGP forums. If anyone has ever compiled the PGP Desktop 9 code or has some knowledge about it otherwise, could you please clear up this situation. My questions spanned 3 threads with no successful resolution.

    1. http://forums.pgpsupport.com/viewtopic.php?t=6785
    2. http://forums.pgpsupport.com/viewtopic.php?t=6794
    3. http://forums.pgpsupport.com/viewtopic.php?t=6826

    The pertinent questions are in my post on the third thread above (t=6826). I'll reprint them here.

    -------------------------------------------

    I apologize if I'm being passive aggressive, and I probably should have taken this up in my own thread, but I thought your answers were non-committal and could be interpreted in more than one way. I guess I'm just looking for explicit statements about these issues:

    1. You mentioned that you can use your compiled executable in ways that don't violate the license agreement. But obviously there's confusion about what the Internal Review License Agreement is actually saying. I've had 3 people tell me you can't use your own compiled executable on a permanent basis. I don't see anything in the license agreement prohibiting the use of your own compiled executable permanently (as long as you purchase a license and don't share the compiled executable). So, my question is, can I use an executable I compile myself on a permanent basis as long as I purchase a license? I don't want to do anything illegal.

    2. You said an executable compiled from the provided source code would be functional. That doesn't mean it functions exactly the same as the downloadable executable. I realize their may be size differences and other differences between something you compile yourself and a binary you download. But is the source code designed to provide an executable that will function exactly the same as the downloadable version? I realize this may seem like splitting hairs, but I would like an explicit answer.

    3. I also realize that having a source code that provides a perfectly functional executable implies the source code is complete. But I would like a statement explicitly stating the source code is complete. By "complete", I mean all the code that is running in the downloadable executable is freely provided AND nothing that is not running in the downloadable executable is in the freely provided source code.

    4. Is PGP commited to providing the complete source code in the future?

    5. Is the source code for PGP Desktop actually the source code for PGP Desktop Professional (which includes WDE)?

    6. While I've got your attention, I might as well ask a question that I've been wondering about. What mode of operation does PGP use (ECB, CBC, OFB, CFB, LRW, etc.)?

    If you could respond to these questions in the initial thread http://forums.pgpsupport.com/viewtopic.php?t=6794 , I think we can put some of these questions to rest and we would have an easy reference to future questions about the source code. I think their is a lot of general confusion about the PGP source code.

    Thanks

    HexMan
     
Loading...
Thread Status:
Not open for further replies.