As mentioned in my previous mail, save all the complexities, use a key
system.

You can have your source naked with usual bootloader, but your code look
for, and need an external private key to run.  Sure theft can be done
through unassembled, etc... but it would be easier to redo the system from
scatch.

cheers, ling sm

----- Original Message -----
From: "Ron Anthony" <ronant@OPTONLINE.NET>
To: <PICLIST@mitvma.mit.edu>
Sent: Thursday, July 26, 2001 8:57 PM
Subject: Re: [PIC]: FINAL WORD: A great solution for the PIC16F877 problems
(code protect,bootloader)


> who says I need to distribute a naked hex file?  it'll be a massive,
messy,
> non-sensical, arbitrary, encrypted-out-the-wazoo tornado of CHAOS!!!!!!!!
> if you can crack it, you can have it.  only a moron would spend the time
it
> would take.
>
> -----Original Message-----
> From: pic microcontroller discussion list
> [mailto:PICLIST@MITVMA.MIT.EDU]On Behalf Of Kevin Blain
> Sent: Thursday, July 26, 2001 3:57 AM
> To: PICLIST@MITVMA.MIT.EDU
> Subject: Re: [PIC]: FINAL WORD: A great solution for the PIC16F877
> problems (code protect,bootloader)
>
>
> why does it matter if the part is not protected if you are going to, for
> example email out hex code to update the part with anyway??????
>
> Sure if you code protect the part, the hacker can't read the part using a
> PIC programmer, but they can read the hex file using notepad......
>
>
> Regards, Kevin
>
> --
> http://www.piclist.com hint: PICList Posts must start with ONE topic:
> [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads
>
> --
> http://www.piclist.com hint: PICList Posts must start with ONE topic:
> [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads
>

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads