<Past |
Future> |
3.99.3 (Windows) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.99.5 (Windows) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.100.0 (Windows) |
Divest [8, 9, 10] |
Divest [8, 9, 10] |
Divest [8, 9, 10] |
Divest [9, 10, 11] |
Divest [9, 10, 11] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.98.2 (OS X) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.99.5 (OS X) |
Approved w/Constraints [8, 9, 10] |
Approved w/Constraints [8, 9, 10] |
Approved w/Constraints [8, 9, 10] |
Approved w/Constraints [9, 10, 11] |
Approved w/Constraints [9, 10, 11] |
Approved w/Constraints [9, 10, 11] |
Approved w/Constraints [9, 10, 11] |
Approved w/Constraints [9, 10, 11] |
Approved w/Constraints [9, 10, 11] |
Approved w/Constraints [9, 10, 11] |
Approved w/Constraints [9, 10, 11] |
Approved w/Constraints [9, 10, 11] |
3.100.1 (Windows) |
Approved w/Constraints [8, 9, 10] |
Approved w/Constraints [8, 9, 10] |
Approved w/Constraints [8, 9, 10] |
Approved w/Constraints [9, 10, 11] |
Approved w/Constraints [9, 10, 11] |
Approved w/Constraints [9, 10, 11] |
Approved w/Constraints [9, 10, 11] |
Approved w/Constraints [9, 10, 11] |
Approved w/Constraints [9, 10, 11] |
Approved w/Constraints [9, 10, 11] |
Approved w/Constraints [9, 10, 11] |
Approved w/Constraints [9, 10, 11] |
| | [1] | While the LAME developed software is free, the encoding technology that ready-compiled LAME binaries use is patented. The patents are held by Fraunhofer and administered by Thomson. Patenting raises a theoretical possibility that in some countries a user might need to pay a license fee to legally encode MP3s. It is the responsibility of the user of this technology to ensure it is legally licensed for use in the location of installation. | | [2] | Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations. | | [3] | Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities. | | [4] | While the LAME developed software is free, the encoding technology that ready-compiled LAME binaries use is patented. The patents are held by Fraunhofer and administered by Thomson. Patenting raises a theoretical possibility that in some countries a user might need to pay a license fee to legally encode Moving Pictures Expert Group Three (MP3) files. It is the responsibility of the user of this technology to ensure it is legally licensed for use in the location of installation. | | [5] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [6] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities. | | [7] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [8] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | [9] | Users should check with their supervisor, Information System Security Officer (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations. | | [10] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. | | [11] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. |
|
Note: |
At the time of writing, version 3.100.1 (Windows), 3.99.5 (mac OS X), is the most current versions, released 09/08/20220 and 12/06/2012 respectively. |