Source: http://www.google.com/patents/US20040006701?ie=ISO-8859-1&dq=7069184
Timestamp: 2015-05-27 07:08:39
Document Index: 552159514

Matched Legal Cases: ['arty 38', 'arty 38', 'arty 38', 'arty 38', 'arty 38', 'arty 38']

Patent US20040006701 - Method and apparatus for authentication of recorded audio - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsA set of procedures is described which permit signing digital audio recordings by means of private keys, and which permit later authentication of such recordings, for example in a courtroom, in a way that is well suited to comprehension by non-technical personnel. Importantly, the explanation leading...http://www.google.com/patents/US20040006701?utm_source=gb-gplus-sharePatent US20040006701 - Method and apparatus for authentication of recorded audioAdvanced Patent SearchPublication numberUS20040006701 A1Publication typeApplicationApplication numberUS 10/249,408Publication dateJan 8, 2004Filing dateApr 7, 2003Priority dateApr 13, 2002Publication number10249408, 249408, US 2004/0006701 A1, US 2004/006701 A1, US 20040006701 A1, US 20040006701A1, US 2004006701 A1, US 2004006701A1, US-A1-20040006701, US-A1-2004006701, US2004/0006701A1, US2004/006701A1, US20040006701 A1, US20040006701A1, US2004006701 A1, US2004006701A1InventorsRoman Kresina, Michael LandinoOriginal AssigneeAdvanced Decisions Inc.Export CitationBiBTeX, EndNote, RefManReferenced by (9), Classifications (12), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetMethod and apparatus for authentication of recorded audio
BRIEF DESCRIPTION OF DRAWINGS [0011] The invention will be described with respect to a drawing in several figures, of which [0012]FIG. 1 shows information flow through a trusted third party and through an audio signer. [0013]FIG. 2 shows information flow for an authentication process. [0014]FIG. 3 shows hardware and information and physical flow from a manufacturing station through a certification authority to a customer. [0015]FIGS. 4 and 5 show hardware and information flow from an archive location to an authenticating player location, assisted by a third party. [0016]FIG. 6 shows process flow for a new system according to the invention. [0017]FIG. 7 shows process flow for handling the expiration of a hardware security module. [0018]FIG. 8 shows process flow for handling a faulty hardware security module. [0019]FIG. 9 shows process flow for audio authentication according to the invention. [0020]FIG. 10 shows a flowchart of steps followed with non-technical personnel to arrive at a finding as to authenticity.
[0021] Where possible, like reference designations have been used for like elements in the figures of the drawing. DETAILED DESCRIPTION [0022]FIG. 1 shows information flow through a trusted third party and through an audio signer. In this embodiment of the invention, the audio signing system 6 may be part of an audio recording device or be a separate device whose sole purpose is to sign audio data. Preferably the signing takes place at the same time as the recording or integrally as part of the recording process. Alternatively the signing may take place nearly contemporaneously with the audio event of interest. [0023] Audio data 9 is first processed into a digest 11 by an algorithm 10 such as SHA-1, MD5 or others. (The choice of a particular digest is not material to this discussion and those skilled in the art may readily select from among many well-known digests.) The audio digest 11 (sometimes called a hash) is then signed by a private key 5 using a signature algorithm such as RSA, DSA or others in order to produce an audio signature 12. (The choice of a particular signature algorithm is not material to this discussion and those skilled in the art may readily select from among many well-known signature algorithms.) [0024] The system 6 uses a key pair comprising a private key 5 and an associated public key 7 which is used at a later time. Because the public key 7 is used at a later time to verify the signature of the audio, it must be available outside of the audio signing system 6. It may be “published” in any format, for example on a web site or a public key server. In the embodiment given here, the public key is specified as being in the standard X509 certificate format. This format is convenient because it provides for the ability to have the certificate 8 signed by a higher authority. Although there may be several levels of signatures (each level signing the one below it), in this example there is a “disinterested third party” or agency 1 that also has a key pair comprising private key 2 and public key 3. The agency's public key 3 is also published or distributed in some manner, in this case also an X509 certificate 4. [0025]FIG. 2 shows information flow for an authentication process. In an exemplary implementation for the process of verifying the signature of the audio, if the signed audio had been modified in any way, the following authentication process will fail. [0026] The audio 16 is first reduced to a digest 18 by the same algorithm 17 (10 in FIG. 1) that was used in the signing process of FIG. 1. This digest 18 as well as the signature 19 are verified to be valid or not valid based upon the public key (7 in FIG. 1) that is located in the public certificate 15 of the audio signer (6 in FIG. 1). At this point even if the verification result is “valid” there can still be doubt as to the validity of the audio signer's public certificate 15, thus, the public certificate 14 of the agency (1 in FIG. 1) is used to validate the authenticity of the audio signer's public certificate 15. This validation process leads to a verification 20 which yields an overall validation result 21. [0027] As will be appreciated by those skilled in the art, for well-constructed key pairs, revelation of the public key does not reveal the private key. Generating a tampered file that appears to be authentic would require possession of the private key. Explaining the system to a judge or jury or other non-technical persons only requires disclosure of the algorithms generally and disclosure of the public keys, but does not require disclosure of the private keys. As a consequence, such explanation does not put the judge or jury or other non-technical persons (or the press or members of the general public attending the courtroom proceedings) into possession of information that compromises the system or enables persons to generate tampered files that appear to be authentic. The explanation, if carried out successfully, will nonetheless permit the judge or jury, and indeed members of the general public, to arrive at reliable and trustworthy conclusions as to the authenticity of the recorded audio. These highly desirable results are discussed in more detail below. [0028] Such issues do not arise in the same way in most prior-art applications of public-key cryptography. For example when such cryptography or authentication is used to secure communications between an automated teller machine and a bank, the only persons who need to be convinced that the system is operating in a way that achieves its goals are technically trained persons such as bank employees and the manufacturers of the associated systems. Indeed the daily circumstance will be that no humans need to be convinced of anything, and it is simply that machines at two ends of a communications link need each to be convinced as to the authenticity and correctness of the communications. [0029]FIG. 3 shows hardware and information and physical flow from a manufacturing station through a certification authority to a customer. A manufacturing station 30 is used to create a hardware security module 31. A hardware security module 31 will contain storage for public and private keys. It will preferably contain dedicated hardware providing cryptographic engine functions, or in some cases may use a suitably programmed general-purpose processor to provide such functions. It is preferably designed in physical packaging that makes it exceedingly difficult, if not impossible, to open the packaging and to gain access to the stored data such as the private key or keys therein. Such modules may be custom-designed to provide optimal support for the aims of the invention, or may be selected from myriad standard commercial off-the-shelf hardware security modules intended to serve a variety of public-key cryptographic purposes. One suitable HSM is the Luna 2 HSM from Chrysalis-ITS of Ottawa, Canada. Those skilled in the art will have no difficulty selecting an appropriate module for the present invention. [0030] The hardware security module (HSM) is shipped to an initialization station 32 in tamper-evident packaging. The initialization station 32 initializes the HSM 33 and validates that the HSM 33 did come from the expected manufacturing station 30, by inspection of the tamper-evident packaging and optionally by checking for stored data within the HSM 33 providing such validation. A key pair comprising a public key and a private key are created in the HSM 33 and stored there, and the public key is extracted. The public key is expressed in a certificate 36 which is signed by the certification authority 35. The signed certificate is stored in the HSM 33. [0031] The HSM 33 has a unique internal serial number. The initialization station 32 creates a user password associated with the HSM serial number. The password is programmed into the HSM 33 so that persons not possessing the password are unable to gain access to functions of the HSM 33. The password is provided to a customer, preferably in a tamper-evident package. [0032] The HSM 33 is shipped to the customer in a tamper-evident package. Most preferably the shipment of the HSM 33 is by means of a different delivery method than the provision of the password. At a minimum the two shipments are preferably done on different days and it is desirable that they be done by different carriers, in packages carrying no external markings that would prompt an observer to draw a connection between the packages. [0033] The customer inserts the HSM 34 into a reader at an archiving station 37. The customer then enters the password, gains access to the HSM 34, and changes the password to one selected by the customer. The archiving station 37, sometimes called an “archiver,” is now available for archiving audio recordings. [0034] It will be appreciated that nothing about the invention requires that the manufacturing station 30 be physically distant from the initialization station 32, thus requiring the tamper-evident shipping described above. For example the two stations could be physically adjacent in a single secure building, in which case there may be no need for tamper-evident shipping. Efficiency and economy of manufacture, however, will likely prompt establishment of a manufacturing station 30 that serves a variety of geographically diverse initialization stations for various purposes, in which case the tamper-evident shipping is desirable. [0035]FIGS. 4 and 5 show hardware and information flow from an archive location to an authenticating player location, assisted by a third party. [0036] Turning first to FIG. 4, what is shown is an archiving process in somewhat more detail than was previously discussed in connection with FIG. 1. The previously mentioned archiver 37 (previously mentioned in connection with FIG. 3) may be seen, equipped with an HSM 35 containing a public key and a private key comprising a key pair. In this example, an audio file 41 needs to be archived (corresponding to the audio file 9 in FIG. 1). A hash 40 is generated based upon the contents of the audio file (corresponding to algorithm 10 in FIG. 1). The hash 40 is signed by the private key of the HSM 35 (corresponding to private key 5 in FIG. 1). The result is a signature 42 (corresponding to audio signature 12 in FIG. 1). [0037]FIG. 4 also shows a certificate 39 which contains the public key from the HSM 35. (This corresponds to the certificate 8 in FIG. 1 containing public key 7, signed by private key 2 of agency 1 in FIG. 1.) Nothing about the system requires that the signing of certificate 39 take place at the same time as the hashing 40 and signing 42, and indeed in the general case it is expected that the signing of certificate 39 need take place only once (when the key pair of HSM 35 is set up) while the hashing 40 and signing 42 will take place myriad times, once for each audio file 41 requiring archiving. [0038] Also shown in FIG. 4 is the composite file 46 which contains the audio 47 (previously audio 41), the audio signature 48 (previously signature 42), and certificate 49 (previously certificate 39). [0039] The composite file 46 contains these several elements as a matter of convenience since it contains nearly everything needed for the authentication that will follow. Those skilled in the art will appreciate that, although it is less desirable to do so, it would be possible to omit the certificate 49 and instead to provide merely a pointer to some external location where the certificate 49 is stored, in which case the party performing authentication would need to use the pointer to retrieve the certificate 49. Indeed, though there would be little reason to do so, the composite file 46 could also omit the audio signature 48 which could be stored elsewhere until needed. Those skilled in the art will appreciate, however, that for the authentication to succeed, the various “building blocks” that permit arriving at a conclusion as to authenticity must somehow be collected to perform the steps that are about to be described. The particular packaging of the building blocks may be varied to suit particular needs. [0040] Returning to FIG. 4, what will now be described is an authentication process corresponding to that described in FIG. 2. The audio file 47 (corresponding to audio 16 in FIG. 2) is passed through a hash function to generate a hash output 51 (digest 18 in FIG. 2 being the output of 17 in FIG. 2). Importantly the hash function at 51 needs to be the same one used at 40, but this is not a problem since hash functions are conventional, easy to describe, and well understood, and if the would-be authenticator were to employ a hash function at 51 that did not match the hash function at 40 it would be immediately apparent since no files would ever authenticate. Even a single successful authentication permits confidence that the correct hash function is being used and this confidence applies to all later efforts to authenticate packages 46 from the particular archiver 37. [0041] The signature 48 is decrypted by the public key in certificate 49 (15 in FIG. 2) and the result should match the hash output 51. If it does, then the data have been authenticated (subject to the question whether the certificate 49 is itself authentic). The third party 38, however, previously signed the certificate 49 (previously 39) with its private key. This permits the authenticating player 43 to use the public key of the third party 38, which is contained in the certificate 44. This public key is applied to the signature in the certificate 49. The result should match the public key in the certificate 49, and if it does, then the certificate 49 has been authenticated by the third party 38. Unless there is some reason to doubt the trustworthiness of the third party 38, the sequence of authentications will have authenticated the audio 47 (previously 41) and it may be played, for example to a judge or jury. In one embodiment of the invention, the player is unable to play the audio unless the authentication has succeeded, and in another embodiment, the player can play regardless of the outcome of the authentication, and an indication is given to the user as to whether the authentication succeeded or failed. [0042]FIG. 5 shows the data flows of FIG. 4 but in a simplified fashion. The archiver 37 archives audio files, for example telephone calls to or from a prison. Each audio file 47 (typically encoded as a WAV file following well-known standards for digital storage of audio) is incorporated into a package 46 containing, as mentioned above in connection with FIG. 4, an audio signature 48 and a certificate 49. This is later transmitted to a courtroom where it is loaded into an authenticating player 43. A certificate 44 is received from third party 38. The certificate 44 and the package 46 permit reaching a conclusion as to authenticity of the audio file 47 and it is played on the player. [0043] Those skilled in the art will immediately appreciate that while the sequence of events is described with respect to a single trusted third party 38, it may be convenient to have a chain of third parties, with the trusted party being at the “root” and intervening signers providing an unbroken chain of signatures down to the archiver 37 and to the authenticator 43. The selection of a single signer or a chain of signers is not material to the invention described here. [0044]FIG. 6 shows process flow for setup of a new authentication system according to the invention. In FIG. 6 (and in FIGS. 7-9 below), customer 60 may for example be a governmental entity operating both a prison and a courthouse, and retailer 61 and initialization provider 62 may be seen, as well as HSM manufacturer 63. The retailer 61 places an order 64 for some minimum number of tokens (HSMs). The HSM manufacturer 63 manufactures and ships tokens 65 which are kept by the initialization provider 62 until needed. The customer 60 places an order 66 for an authentication system with the retailer 61. Orders are accumulated 67. The retailer 61 delivers a subscriber agreement 68 to the customer 60 who agrees with the terms and conditions 69. The retailer 61 then places an order 70 with the initialization provider 62 for HSMs. The initialization provider 62 initializes the tokens (HSMs) 71, associates particular HSM IDs with particular customers, and provides details 72 of same to the retailer 61. The initialization provider 62 ships 73 the HSMs to the customer 60 and, as discussed above in connection with FIG. 3, ships 74 corresponding passwords to the customer 60. The customer 60 installs 75 the HSMs, activates them 76 with the passwords, and changes 77 the passwords, all as previously described in connection with FIG. 3. [0045] Those skilled in the art will appreciate that while the customer 60, initialization provider 62, HSM manufacturer 63, and retailer 61 are shown in FIGS. 6-9 as distinct entities, and while this arrangement is probably to be preferred, nothing about the invention requires that they be distinct. As one example the retailer 61 and initialization provider 62 could be one and the same without deviating from the invention. As another example the initialization provider 62 and HSM manufacturer 63 could be one and the same. Finally, a customer 60 such as a government entity might choose to perform some or all of the other three functions itself. It will be appreciated, of course, that the overall level of trust of the system may well be enhanced by having the initialization performed by a party who is distinct from the customer 60, that party preferably being a disinterested and trusted third party. [0046]FIG. 7 shows process flow for handling the expiration of a hardware security module. Those skilled in the art are aware that any particular public/private key pair is preferably treated as having a particular life, and that the pair is preferably taken out of service on a time scale that is thought to be short when compared with an estimated time to obtain the private key based upon knowledge of the public key. Where an RSA public key is involved, for example, this time is estimated based on a guess as to the likely time required for factoring a large integer. To this end, each HSM is preferably put into service with a predetermined expiration date. Thus in FIG. 7 the initialization provider 62 may notify 80 the retailer 61 that an HSM has an imminent expiration date (e.g. six months away). The retailer 61 may then notify 81 the customer 60 of the imminent expiration. The customer 60 then places an order 82 for a replacement HSM. The retailer 61 accumulates 83 such orders and passes the order 84 to the initialization provider 62. The initialization provider 62 then initializes the tokens (HSMs) 85 (corresponding to 71 in FIG. 6), associates particular HSM IDs with particular customers, and provides details 86 (corresponding to 72 in FIG. 6) of same to the retailer 61. The initialization provider 62 ships 87 (corresponding to 73 in FIG. 6) the HSMs to the customer 60 and, as discussed above in connection with FIG. 3, ships 88 (corresponding to 74 in FIG. 6) corresponding passwords to the customer 60. The customer 60 removes the expiring HSMs 89 and installs new HSMs (corresponding to 75 in FIG. 6), activates them 90 (corresponding to 76 in FIG. 6) with the passwords, and changes 91 (corresponding to 77 in FIG. 1) the passwords, all as previously described in connection with FIG. 3. The customer 60 then returns 92 the old HSMs to the retailer 61 and requests revocation of the associated certificates. The retailer 61 returns 93 the expired HSMs to the initialization provider 62 and requests revocation of the associated certificates. The initialization provider 62 revokes 95 the certificates and recycles the HSMs for reuse. The retailer 61 sends revocation notices 94 to the customer 60. [0047]FIG. 8 shows process flow for handling a faulty hardware security module. No matter how reliable the HSMs are, it is important to provide for the possibility, however unlikely, that any particular HSM might fail prior to its expiration date. Thus in FIG. 8, the customer 60 may notify 101 the retailer 61 that an HSM has failed. The retailer 61 places an order 102 for a replacement HSM to the initialization provider 62. The initialization provider 62 then initializes the tokens (HSMs) 103, associates a particular HSM ID with the particular customer, and provides details 104 of same to the retailer 61. The initialization provider 62 ships 105 the HSM to the customer 60 and, as discussed above in connection with FIG. 3, ships 106 a corresponding password to the customer 60. The customer 60 removes the faulty HSM 107 and installs the replacement HSM, activates it 108 with the password, and changes 109 the password, all as previously described in connection with FIG. 3. The customer 60 then returns 110 the faulty HSM to the retailer 61 and requests revocation of the associated certificate. The retailer 61 returns 111 the faulty HSM to the initialization provider 62 and requests revocation of the associated certificate. The initialization provider 62 revokes 13 the certificate. The retailer 61 sends a revocation notice 112 to the customer 60. [0048]FIG. 9 shows process flow for audio authentication according to the invention. The customer 60 sends an audio file on a CD-ROM in step 121. The audio file is, for example, package 46 in FIGS. 4 and 5. The audio file is sent, for example, to a courthouse 120. The courthouse 120 obtains the signed certificate from the package 46 and determines who is the supposed signer. The courthouse, having identified the supposed signer, contacts that entity (initialization provider 62) to request that entity's public key and a certificate revocation list in step 122. At step 123 a response provides the certificate and the list. The courthouse then performs authentication in step 124, as described above in connection with FIG. 2. [0049]FIG. 10 shows a flowchart of steps followed with non-technical personnel to arrive at a finding as to authenticity. At step 141, the system of public and private keys is explained to the nonpersonnel, for example a judge and/or jury. This explanation may include a discussion of the mathematics of public and private keys as well as a discussion of the data flow and process steps described above. Hash algorithms may be discussed. [0050] At 142, the judge and/or jury may follow the retrieval of the root public key from the signing authority and its use in authenticating the HSM certificate contained in the package 46, as well as the use of the public key in the HSM certificate to authenticate the hash signature of the audio file. [0051] Finally at 143 the audio file may be played so that the judge and/or jury may hear what was originally recorded, for example a telephone call or other voice communications. This occurs under circumstances in which the judge and/or jury have reached their own conclusion as to the authenticity of the audio. [0052] Stated differently, an embodiment of the invention may comprise an authentication method comprising the steps of making a digital audio recording of an event, yielding a first file, extracting a hash from the first file, cryptographically signing the hash using a first private key corresponding to a first public key, yielding a signature, cryptographically signing the first public key using a second private key corresponding to a second public key, yielding a certificate further comprising the first public key, communicating the first file, the signature, and the certificate to the at least one person, and communicating the second public key from a trusted source to the at least one person. [0053] Next an explanation is provided to the at least one person of the extracting step, the first signing step, and the second signing step, and of the correspondence between the first private and public keys, and of the correspondence between the second private and public keys, the certificate is authenticated by means of the second public key, the authenticating performed in the presence of the at least one person, the signature is authenticated by means of the first public key from the certificate, the authenticating performed in the presence of the at least one person; and the audio recording is played in the presence of the at least one person. [0054] In a typical situation the at least one person will be a person who has not previously been knowledgeable about the items being explained. For example this may be a juror who has not previously been exposed to public key cryptography and to hash functions. [0055] It is instructive to discuss the internal structure of the package 46 in FIGS. 4 and 5. In a simple case the designer of the package 46 might devise a structure in which the only way to “play” the package 46 is through specialized software which would separate the audio information from the other items of data, and which would then play the audio data using a conventional player that can play WAV files. But in one embodiment of the invention, the structure of the package 46 may be devised so that the package may not only be played by the specialized authentication system but may also be played on a conventional player that can play WAV files. This is particularly helpful, for example, to persons who may wish to listen to the audio files prior to their use in court. Such persons (e.g. lawyers preparing for court) are typically interested simply in hearing the audio and are not, at such a moment, concerned about proving the authenticity of the audio. This permits copies of the package 46 (distributed, say, on CD-ROMs) to be listened to by persons who have ordinary personal computers, without the need to have an authenticating system. [0056] Those skilled in the art are well aware of the internal format of conventional WAV files. A WAV file is made up of “chunks” such as RIFF chunks, Format chunks, Data chunks and other chunks. [0057] The WAV file always starts with four bytes spelling the word “RIFF” in ASCII (American standard code for information interchange). [0058] Next comes four bytes which give the total file-size (less eight bytes). Depending on the operating system and the particular player, if these four bytes express a size that is inconsistent with the file size reported by the operating system this may be an indication that the file has been corrupted. For this discussion the four bytes spelling the word “RIFF” and the four bytes giving the total file-size are collectively called the “RIFF chunk.” Next comes a portion of four bytes spelling “WAVE” in ASCII. [0059] Next comes a format portion (or “chunk”) that begins with four bytes spelling “fmt” (note the trailing space) in ASCII, followed by four bytes setting forth the number of bytes in the “format” portion. This chunk continues with bytes that convey format information including a number of channels, a sampling frequency, a number of bytes per second, and a number of bits per sample. [0060] Next comes a “data” chunk defined by four bytes spelling “data” in ASCII, and four bytes specifying the number of data bytes. These data bytes convey the audio information of the file. [0061] The standard for WAV players requires that software can successfully read WAV files containing unknown chunks. Should an unknown chunk name be encountered, then the accompanying size field should be read, and the data bytes (the number of which is specified by the size field) should be skipped. This means that new chunks can be defined without breaking compatibility with legacy software. This aspect of the standard is relied upon to permit placing the signature and certificate information into the WAV file while preserving compatibility with conventional WAV players. [0062] A conventional WAV player will read and interpret bytes from the start of the WAV file to the “data” bytes, and will then read and interpret the data bytes, the number of which is specified as described. If there are any more bytes in the WAV file after the specified number of data bytes have been interpreted, those additional bytes are ignored by the conventional WAV player and are significant only in the limited sense that they play a part in the total file size and thus should contribute to an actual file size that is consistent with the previously mentioned bytes that give the total file-size. Some WAV players will simply ignore the bytes after the audio data chunk, while others will attempt to read the signature and certificate chunks but will ignore them as soon as it is determined that the chunk name is not known to the player. [0063] In one embodiment of the system according to the invention, the signing process involves the following steps: [0064] 1. A custom chunk containing Call Record information is added to the end of the file, that is, at a location that is after the audio data bytes. [0065] 2. Another custom chunk containing information about the algorithm used to create the signature as well as the time and date of the signing is added to the end of the file. [0066] 3. The archiving system then goes to the beginning of the file and indexes past the RIFF chunk. [0067] 4. The system then calculates the hash from the point just past the RIFF chunk to the end of the file. In doing so, it is calculating a hash based on the format chunk, the data chunk, and the two custom chunks just mentioned. [0068] 5. The system then signs the hash to create a signature. [0069] 6. The system then adds another custom chunk to the end of the file which contains the signature. [0070] 7. The system then adds another custom chunk (termed a certificate chunk) to the end of the file (now just after the signature chunk). This certificate chunk will contain the X509 certificate for the signing device, in this case the HSM of the archiving system. [0071] 8. The system then indexes to the beginning of the file and reads the RIFF chunk which contains the file size. [0072] 9. The system then updates the file size by adding the size of all the custom chunks that were added. [0073] 10. The system then writes an updated RIFF chunk back to the beginning of the WAV file. [0074] What results from this procedure can be a digital audio file comprising first, second, and third portions, the first portion comprising format information, the second portion comprising audio data and means indicating the location of the end of the audio data, the third portion comprising a cryptographic signature of at least the second portion. In particular the cryptographic signature is preferably the result of a private key, the file further comprising a cryptographic certificate containing a public key corresponding to the private key. There may be an additional portion indicative of the length of the file. To save computational burden on the WAV player and on the authentication system it is desirable that the third portion follow the second portion rather than precede it. [0075] In one embodiment, what is described is a method for use with a digital audio file comprising first and second portions, the first portion comprising format information, the second portion comprising audio data and means indicating the location of the end of the audio data, the method comprising the steps of calculating a hash based at least on the audio data, cryptographically signing the hash, yielding a signature; and adding a third portion to the file comprising the signature. The cryptographic signing may be performed with respect to a private key, the method further comprising the step of adding a fourth portion to the file comprising a cryptographic certificate comprising a public key corresponding to the private key. If the file further comprises information indicative of the length of the file, the method further will comprise the step of determining the new length of the file after addition of the additional portion or portions; and within the file, updating the information indicative of the length of the file based on the determined new length. [0076] In the particular case of a WAV file, what results is a digital audio file having a length and a format, the file comprising four bytes spelling the word “RIFF” in ASCII, four bytes defining a first number indicative of the file length less 8, a number of bytes indicative of the format of the file, four bytes spelling the word “data” in ASCII, four bytes indicative of the length of the portion containing audio data bytes, the data bytes themselves, and a cryptographic signature calculated with respect to at least the first number of data bytes. The file may also contain, before or after the signature, a cryptographic certificate containing a public key corresponding to the private key that was used to calculate the signature. [0077] The WAV file thus modified and signed (the package 46) will contain all the information that is needed by the authentication system to verify the authenticity of the file. [0078] Advantageously, any “standard” WAV file player will still be able to play the WAV file in a normal fashion because the additional custom chunks will not be recognized by the player and will be ignored. In particular, the standard WAV player will reach the “data” chunk, will determine how many bytes of data exist, and will ignore any file contents after that number of bytes of data have been read. [0079] Those skilled in the art will readily devise myriad obvious variations and improvements without departing from the invention, all of which are intended to fall within the claims that follow. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7080199 *Jul 15, 2003Jul 18, 2006Lsi Logic CorporationMethod to maintain data integrity during flash file transfer to raid controller flash using a terminal emulation programUS7519274Dec 8, 2003Apr 14, 2009Divx, Inc.File format for multiple track digital dataUS8014527 *Sep 1, 2004Sep 6, 2011Samsung Electronics Co., Ltd.Apparatus and method for reusing pair of public and private keysUS8121264 *Nov 22, 2006Feb 21, 2012Securus Technologies, Inc.Protected data container for storing data relating to recorded calls in a manner that enables the data to be authenticatedUS8472792Oct 24, 2005Jun 25, 2013Divx, LlcMultimedia distribution systemUS8731369Dec 17, 2004May 20, 2014Sonic Ip, Inc.Multimedia distribution system for multimedia files having subtitle informationUS8989390 *Dec 11, 2006Mar 24, 2015Qualcomm IncorporatedCertify and split system and method for replacing cryptographic keysUSRE45052Apr 14, 2011Jul 29, 2014Sonic Ip, Inc.File format for multiple track digital dataWO2006112843A1 *Apr 19, 2005Oct 26, 2006Sean WardDistributed acoustic fingerprint based recognition* Cited by examinerClassifications U.S. Classification713/189, 713/181, 713/176, 713/175International ClassificationH04L9/32Cooperative ClassificationH04L2209/38, H04L9/321, H04L9/3263, H04L2209/56, H04L9/3247European ClassificationH04L9/32T, H04L9/32SLegal EventsDateCodeEventDescriptionApr 7, 2003ASAssignmentOwner name: ADVANCED DECISIONS INC., CONNECTICUTFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KRESINA, ROMAN;LANDINO, MICHAEL;REEL/FRAME:013582/0273Effective date: 20030407RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services