Thanks, Larry! I didn't think that this would be a policy that made a lot of sense. There used to be a piece of software manufactured by a German company. The software was a Braille screen reader for Windows. It would only work with a Braille display that was also manufactured by this company. At the time, their least expensive Braille display went for about $8000. The software went for another $1000. Yet, the software was copy protected. Always found that one strange, in that if you didn't own this expensive piece of hardware, their software wouldn't do you any good anyway. Talk about overkill! -----Original Message----- From: bookport-bounce@xxxxxxxxxxxxx [mailto:bookport-bounce@xxxxxxxxxxxxx] On Behalf Of LARRY SKUTCHAN Sent: Tuesday, October 25, 2005 11:04 AM To: bookport@xxxxxxxxxxxxx Subject: [bookport] Re: Fun facts APH will never do this. The developers feel the same way. >>> kevin@xxxxxxxxxxx Tuesday, October 25, 2005 11:43:34 AM >>> I hate unit specific encryption in all cases, that's just not the way to go, it's the path of the paranoid. -----Original Message----- From: bookport-bounce@xxxxxxxxxxxxx [mailto:bookport-bounce@xxxxxxxxxxxxx] On Behalf Of Richard Ring Sent: Tuesday, October 25, 2005 10:07 AM To: bookport@xxxxxxxxxxxxx Subject: [bookport] Re: Fun facts I must add my concern here. This idea would gravely reduce the flexibility and functionality of the unit by limiting the options that users currently have. Having said that, let's wait until APH weighs in on this one before we jump to conclusions. -----Original Message----- From: bookport-bounce@xxxxxxxxxxxxx [mailto:bookport-bounce@xxxxxxxxxxxxx] On Behalf Of Brian Buhrow Sent: Tuesday, October 25, 2005 10:00 AM To: bookport@xxxxxxxxxxxxx Subject: [bookport] Re: Fun facts Hello. I sure hope you're wrong and Springer and/or APH does not follow this course of action for transfers of non-proprietary data, including Daisy books from Bookshare. The implication of what you say also means that if you have two bookports, you couldn't share CF cards between them. As a Bookport user, and as a guy who talks to a number of folks about technology for the blind, I would have serious reservations about recommending the Bookport or the Bookcourier if unit-specific encryption becomes standard for all book transfers. Not only would it represent a new level of inconvenience for users on a number of levels, especially those who own or use multiple devices, but would add a significant support burden to APH and/or Springer, helping users diagnose problems with files they couldn't examine on the Bookport, or copy elsewhere for testing. Once again, I can't express how bad of an idea I think this is, and for reasons that I don't think will become obvious until it's already done, and the Bookport becomes yet another technology footnote in history. Please, no!!! Remember, the laser disk! -Brian On Oct 25, 12:57am, <chris.BP.FL@xxxxxxxxxxxxxxx> wrote: } Subject: [bookport] Re: Fun facts } This is a multi-part message in MIME format. } } ------=_NextPart_000_0058_01C5D8FF.143AB8E0 } Content-Type: text/plain; charset="us-ascii" } Content-Transfer-Encoding: 7bit } } >From some discussion directly with Springer about some problems and } questuions about BC and (Dutch) Daisy 2.02 books and writing directly to CF } I understood some (or all?) data types will in future be (or are already?) } encrypted, using the BC serial no. to derive some encrypting key. If done } so, CF from BC and BP will not be interchangabe for encrypted data without } special provisions in BC and/or BP, which probably can only be made by } Springer and/or APH. } } } } Chris Sauer } } The Netherlands } } } } } -- } No virus found in this outgoing message. } Checked by AVG Anti-Virus. } Version: 7.0.344 / Virus Database: 267.12.4/146 - Release Date: 10/21/2005 } } } } ------=_NextPart_000_0058_01C5D8FF.143AB8E0 } Content-Type: text/html; charset="us-ascii" } Content-Transfer-Encoding: quoted-printable } } <html> } } <head> } <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = } charset=3Dus-ascii"> } } } <meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)"> } } <style> } <!-- } /* Style Definitions */ } p.MsoNormal, li.MsoNormal, div.MsoNormal } {margin:0mm; } margin-bottom:.0001pt; } font-size:12.0pt; } font-family:"Times New Roman";} } a:link, span.MsoHyperlink } {color:blue; } text-decoration:underline;} } a:visited, span.MsoHyperlinkFollowed } {color:purple; } text-decoration:underline;} } p.MsoPlainText, li.MsoPlainText, div.MsoPlainText } {margin:0mm; } margin-bottom:.0001pt; } font-size:10.0pt; } font-family:"Courier New";} } p } {margin-right:0mm; } margin-left:0mm; } font-size:12.0pt; } font-family:"Times New Roman";} } span.emailstyle17 } {font-family:Arial; } color:windowtext;} } span.emailstyle20 } {font-family:Arial;} } span.EmailStyle21 } {font-family:Arial;} } @page Section1 } {size:612.0pt 792.0pt; } margin:72.0pt 90.0pt 72.0pt 90.0pt;} } div.Section1 } {page:Section1;} } --> } </style> } } </head> } } <body lang=3DEN-US link=3Dblue vlink=3Dpurple> } } <div class=3DSection1> } } <p class=3DMsoNormal><font size=3D2 face=3DArial><span = } style=3D'font-size:10.0pt; } font-family:Arial'>From some discussion directly with Springer about = } some } problems and questuions about BC and (Dutch) Daisy 2.02 books and = } writing } directly to CF I understood some (or all?) data types will in future be = } (or are } already?) encrypted, using the BC serial no. to derive some encrypting = } key. If } done so, CF from BC and BP will not be interchangabe for encrypted data = } without } special provisions in BC and/or BP, which probably can only be = } made by } Springer and/or APH.</span></font></p> } } <p class=3DMsoNormal><font size=3D2 face=3DArial><span = } style=3D'font-size:10.0pt; } font-family:Arial'> </span></font></p> } } <p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span = } lang=3DNL } style=3D'font-size:10.0pt'>Chris Sauer</span></font></p> } } <p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span = } style=3D'font-size: } 10.0pt'>The <u1:country-region><u1:place>Netherlands</span></font></p> } } </u1:place></u1:country-region> } } <p><font size=3D3 face=3D"Times New Roman"><span = } style=3D'font-size:12.0pt'> </span></font></p> } } </div> } } </body> } } </html> } <BR> } } <P><FONT SIZE=3D2>--<BR> } No virus found in this outgoing message.<BR> } Checked by AVG Anti-Virus.<BR> } Version: 7.0.344 / Virus Database: 267.12.4/146 - Release Date: = } 10/21/2005<BR> } </FONT> </P> } ------=_NextPart_000_0058_01C5D8FF.143AB8E0-- } } >-- End of excerpt from <chris.BP.FL@xxxxxxxxxxxxxxx>