Recherche avancée

Sur d’autres sites (5009)

• FFMPEG compiled binaries don't run on XP using MinGW

  10 juin 2015, par Paul Knopf

  I am trying to build windows executables/dlls for Windows XP, and they are not working. They are the correct architecture. They run fine on my Windows 8 device machine.

  I used dependency walker to find missing DLLs, and all were present.

  Here are the compiled executables I am trying to run.

  I ran the windows build script for ffmpeg.

  Here is a dumpbin /headers ffmpeg.exe

  Microsoft (R) COFF/PE Dumper Version 10.00.30319.01
  
  Copyright (C) Microsoft Corporation.  All rights reserved.
  
  
  
  
  
  Dump of file ffmpeg.exe
  
  
  
  PE signature found
  
  
  
  File Type: EXECUTABLE IMAGE
  
  
  
  FILE HEADER VALUES
  
               14C machine (x86)
  
                 7 number of sections
  
             51A40 time date stamp Sun Jan 04 15:53:20 1970
  
                 0 file pointer to symbol table
  
                 0 number of symbols
  
                E0 size of optional header
  
               32F characteristics
  
                     Relocations stripped
  
                     Executable
  
                     Line numbers stripped
  
                     Symbols stripped
  
                     Application can handle large (>2GB) addresses
  
                     32 bit word machine
  
                     Debug information stripped
  
  
  
  OPTIONAL HEADER VALUES
  
               10B magic # (PE32)
  
              2.25 linker version
  
             41400 size of code
  
             4FA00 size of initialized data
  
              1200 size of uninitialized data
  
              14E0 entry point (004014E0)
  
              1000 base of code
  
             43000 base of data
  
            400000 image base (00400000 to 00456FFF)
  
              1000 section alignment
  
               200 file alignment
  
              4.00 operating system version
  
              1.00 image version
  
              4.00 subsystem version
  
                 0 Win32 version
  
             57000 size of image
  
               400 size of headers
  
             597A9 checksum
  
                 3 subsystem (Windows CUI)
  
               140 DLL characteristics
  
                     Dynamic base
  
                     NX compatible
  
            200000 size of stack reserve
  
              1000 size of stack commit
  
            100000 size of heap reserve
  
              1000 size of heap commit
  
                 0 loader flags
  
                10 number of directories
  
                 0 [       0] RVA [size] of Export Directory
  
             51000 [    36F0] RVA [size] of Import Directory
  
                 0 [       0] RVA [size] of Resource Directory
  
                 0 [       0] RVA [size] of Exception Directory
  
                 0 [       0] RVA [size] of Certificates Directory
  
                 0 [       0] RVA [size] of Base Relocation Directory
  
                 0 [       0] RVA [size] of Debug Directory
  
                 0 [       0] RVA [size] of Architecture Directory
  
                 0 [       0] RVA [size] of Global Pointer Directory
  
             56004 [      18] RVA [size] of Thread Storage Directory
  
                 0 [       0] RVA [size] of Load Configuration Directory
  
                 0 [       0] RVA [size] of Bound Import Directory
  
             517F0 [     6C4] RVA [size] of Import Address Table Directory
  
                 0 [       0] RVA [size] of Delay Import Directory
  
                 0 [       0] RVA [size] of COM Descriptor Directory
  
                 0 [       0] RVA [size] of Reserved Directory
  
  
  
  
  
  SECTION HEADER #1
  
     .text name
  
     412BC virtual size
  
      1000 virtual address (00401000 to 004422BB)
  
     41400 size of raw data
  
       400 file pointer to raw data (00000400 to 000417FF)
  
         0 file pointer to relocation table
  
         0 file pointer to line numbers
  
         0 number of relocations
  
         0 number of line numbers
  
  60500060 flags
  
           Code
  
           Initialized Data
  
           RESERVED - UNKNOWN
  
           RESERVED - UNKNOWN
  
           Execute Read
  
  
  
  SECTION HEADER #2
  
     .data name
  
       19C virtual size
  
     43000 virtual address (00443000 to 0044319B)
  
       200 size of raw data
  
     41800 file pointer to raw data (00041800 to 000419FF)
  
         0 file pointer to relocation table
  
         0 file pointer to line numbers
  
         0 number of relocations
  
         0 number of line numbers
  
  C0700040 flags
  
           Initialized Data
  
           RESERVED - UNKNOWN
  
           RESERVED - UNKNOWN
  
           RESERVED - UNKNOWN
  
           Read Write
  
  
  
  SECTION HEADER #3
  
    .rdata name
  
      A7D8 virtual size
  
     44000 virtual address (00444000 to 0044E7D7)
  
      A800 size of raw data
  
     41A00 file pointer to raw data (00041A00 to 0004C1FF)
  
         0 file pointer to relocation table
  
         0 file pointer to line numbers
  
         0 number of relocations
  
         0 number of line numbers
  
  40700040 flags
  
           Initialized Data
  
           RESERVED - UNKNOWN
  
           RESERVED - UNKNOWN
  
           RESERVED - UNKNOWN
  
           Read Only
  
  
  
  SECTION HEADER #4
  
      .bss name
  
      1200 virtual size
  
     4F000 virtual address (0044F000 to 004501FF)
  
         0 size of raw data
  
         0 file pointer to raw data
  
         0 file pointer to relocation table
  
         0 file pointer to line numbers
  
         0 number of relocations
  
         0 number of line numbers
  
  C0700080 flags
  
           Uninitialized Data
  
           RESERVED - UNKNOWN
  
           RESERVED - UNKNOWN
  
           RESERVED - UNKNOWN
  
           Read Write
  
  
  
  SECTION HEADER #5
  
    .idata name
  
      36F0 virtual size
  
     51000 virtual address (00451000 to 004546EF)
  
      3800 size of raw data
  
     4C200 file pointer to raw data (0004C200 to 0004F9FF)
  
         0 file pointer to relocation table
  
         0 file pointer to line numbers
  
         0 number of relocations
  
         0 number of line numbers
  
  C0300040 flags
  
           Initialized Data
  
           RESERVED - UNKNOWN
  
           RESERVED - UNKNOWN
  
           Read Write
  
  
  
  SECTION HEADER #6
  
      .CRT name
  
        3C virtual size
  
     55000 virtual address (00455000 to 0045503B)
  
       200 size of raw data
  
     4FA00 file pointer to raw data (0004FA00 to 0004FBFF)
  
         0 file pointer to relocation table
  
         0 file pointer to line numbers
  
         0 number of relocations
  
         0 number of line numbers
  
  C0300040 flags
  
           Initialized Data
  
           RESERVED - UNKNOWN
  
           RESERVED - UNKNOWN
  
           Read Write
  
  
  
  SECTION HEADER #7
  
      .tls name
  
        20 virtual size
  
     56000 virtual address (00456000 to 0045601F)
  
       200 size of raw data
  
     4FC00 file pointer to raw data (0004FC00 to 0004FDFF)
  
         0 file pointer to relocation table
  
         0 file pointer to line numbers
  
         0 number of relocations
  
         0 number of line numbers
  
  C0300040 flags
  
           Initialized Data
  
           RESERVED - UNKNOWN
  
           RESERVED - UNKNOWN
  
           Read Write
  
  
  
    Summary
  
  
  
          1000 .CRT
  
          2000 .bss
  
          1000 .data
  
          4000 .idata
  
          B000 .rdata
  
         42000 .text
  
          1000 .tls

  When I attempt to run the executable on XP, it just closes. There is no "missing dll" messages, nor anything in the event viewer.

• Your introduction to personally identifiable information : What is PII ?

  15 janvier 2020, par Joselyn Khor — Analytics Tips, Privacy, Security
  When it comes to personally identifiable information (PII), people are becoming more concerned with data privacy. Identifiable information can be used for illegal purposes like identity theft and fraud. 

  So how can you protect yourself as an innocent web browser ?

  If you’re a website owner – how do you protect users and your company from falling prey to privacy breaches ?

  As one of the most trusted analytics companies, we feel our readers would benefit from being as informed as possible about data privacy issues and PII. Learn how you can keep yours or others’ information safe.

  

  Table of Contents

  What does PII stand for ?

  PII acronym

  PII is an acronym for personally identifiable information.

  PII definition

  Personally identifiable information (PII) is a term mainly used in the United States.

  The appendix of OMB M-10-23 (Guidance for Agency Use of Third-Party Website and Applications) gives this definition for PII :

  “The term ‘personally identifiable information’ refers to information which can be used to distinguish or trace an individual’s identity, such as their name, social security number, biometric records, etc. alone, or when combined with other personal or identifying information which is linked or linkable to a specific individual, such as date and place of birth, mother’s maiden name, etc.”

  What can be considered personally identifiable information (PII) ? Some PII examples :

  • Full name/usernames
  • Home address/mailing address
  • Email address
  • Credit card numbers
  • Date of birth
  • Phone numbers
  • Login details

  • Precise locations
  • Account numbers
  • Passwords
  • Security codes (including biometric records)
  • Personal identification numbers
  • Driver license number
  • Get a more comprehensive list here

  What’s non-PII ?

  Anonymous information, or information that can’t be traced back to an individual, can be considered non-PII. 

  Who is affected by the exploitation of PII ?

  Anyone can be affected by the misuse of personal data. Websites can compromise your privacy by mishandling or illegally selling/sharing your data. That may lead identity theft, account fraud and account takeovers. The fear is falling victim to such fraudulent activity. 

  PII can also be an issue when employees have access to the database and the data is not encrypted. For example, anyone working in a bank can access your accounts ; and anyone working at Facebook can read your messages. This shows how privacy breaches can easily happen when employees have access to PII.

  Website owner’s responsibility for data privacy (PII and analytics)

  If you’re using a web analytics tool like Google Analytics or Matomo, best practise is to not collect PII if possible. This is to better respect your website visitor’s privacy. 

  If you work in an industry which needs people to share personal information (e.g. healthcare, security industries, public sector), then you must collect and handle this data securely. 

  

  The US National Institute of Standards and Technology states : “The likelihood of harm caused by a breach involving PII is greatly reduced if an organisation minimises the amount of PII it uses, collects, and stores. For example, an organisation should only request PII in a new form if the PII is absolutely necessary.” 

  How you’re held accountable remains up to the privacy laws of the country you’re doing business in. Make sure you are fully aware of the privacy and data protection laws that relate specifically to you. 

  To reduce the risk of privacy breaches, try collecting as little PII as you can ; purging it as soon as you can ; and making sure your IT security is updated and protected against security threats. 

  With data collection tools like web analytics, data may be tracked through features like User ID, custom variables, and custom dimensions. Sometimes they are also harder to identify when they are present, for example, in page URLs, page titles, or referrers URLs. So make sure you’re optimising your web analytics tools’ settings to ensure you’re asking your users for consent and respecting users’ privacy.

  If you’re using a GDPR compliant tool like Matomo, learn how you can stop processing such personal data

  PII, GDPR and businesses in the US/EU

  You may get confused when considering PII and GDPR (which applies in the EU). The General Data Protection Regulation (GDPR) gives people in the EU more rights over “personal data” – which covers more identifiers than PII (more on PII vs personal data below). GDPR restricts the collection and processing of personal data so businesses need to handle this personal data carefully. 

  According to the GDPR, you can be fined up to 4% of their yearly revenue for data/privacy breaches or non-compliance. 

  

  In the US, there isn’t one overarching data protection law, but there are hundreds of laws on both the federal and state levels to protect PII of US residents. US Congress has enacted industry-specific statutes related to data privacy like HIPAA. Recently state of California also passed the California Consumer Privacy Act (CCPA). 

  To be on the safe side, if you’re using analytics, follow matters relating to “personal data” in the GDPR. It covers more when it comes to protecting user privacy. GDPR rules still apply whenever an EU citizen visits any non EU site (that processes personal data).

  Personally identifiable information (PII) vs personal data

  PII and “personal data” aren’t used interchangeably. All personal data can be PII, but not all PII can be defined as personal data.

  The definition of “personal data” according to the GDPR :

  

  This means “personal data” covers more identifiers, including online identifiers. Examples include : IP addresses and URL names. As well as seemingly “innocent” data like height, job position, company etc. 

  What’s seen as personal data depends on the context. If a piece of information can be combined with others to establish someone’s identity then that can be considered personal data. 

  Under GDPR, when processing personal data, you need explicit consent. So best to be compliant according to GDPR definitions of “personal data” not just what’s considered “PII”.

  How do you keep PII safe ?

  • Try not to give your data away so easily. Read through terms and conditions.
  • Don’t just click ‘agree’ when faced with consent screens, as consent screens are majorly flawed. 
  • Disable third party cookies by default. 
  • Use strong passwords.
  • Be wary of public wifi – hackers can easily access your PII or sensitive data. Use a VPN (virtual private network)
  • Read more on how to keep PII safe. For businesses here’s a checklist on PII compliance.

  How Matomo deals with PII and personal data

  Although Matomo Analytics is a web analytics tool that tracks user activity on your website, we take privacy and PII very seriously – on both our Cloud and On-Premise offerings. 

  If you’re using Matomo and would like to know how you can be fully GDPR compliant and protect user privacy, read more :
  

  • Learn how to not process any personally identifiable information – Anonymise IP addresses, user IDs, and order IDs
  • Matomo protects user privacy by talking the talk and walking the walk
  • Stay ahead of the GDPR with a privacy-respecting analytics platform
  • 11 ways Matomo helps you protect your visitor’s privacy

  Disclaimer

  We are not lawyers and don’t claim to be. The information provided here is to help give an introduction to issues you may encounter when dealing with PII. We encourage every business and website to take data privacy seriously and discuss these issues with your lawyer if you have any concerns. 

  Additional resources :

  • https://www.consumeraffairs.com/finance/identity-theft-statistics.html#identity-theft-trends-in-2019
  • https://ec.europa.eu/info/law/law-topic/data-protection_en
  • https://iclg.com/practice-areas/data-protection-laws-and-regulations/usa
  • https://www.csoonline.com/article/3215864/how-to-protect-personally-identifiable-information-pii-under-gdpr.html
  • https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/key-definitions/what-is-personal-data/

• What is PII ? Your introduction to personally identifiable information

  15 janvier 2020, par Joselyn Khor — Analytics Tips, Privacy, Security
  Most websites you visit collect information about you via tools like Google Analytics and Matomo – sometimes collecting personally identifiable information (PII).

  When it comes to PII, people are becoming more concerned about data privacy. Identifiable information can be used for illegal purposes like identity theft and fraud. 

  So how can you protect yourself as an innocent internet browser ? In the case of website owners – how do you protect users and your company from falling prey to privacy breaches ?

  

  As one of the most trusted analytics companies, we feel our readers would benefit from being as informed as possible about data privacy issues and PII. Learn what it means, and what you can do to keep yours or others’ information safe.

  Table of Contents

  What does PII stand for ?

  PII acronym

  PII is an acronym for personally identifiable information.

  PII definition

  Personally identifiable information (PII) is a term used predominantly in the United States.

  The appendix of OMB M-10-23 (Guidance for Agency Use of Third-Party Website and Applications) gives this definition for PII :

  “The term ‘personally identifiable information’ refers to information which can be used to distinguish or trace an individual’s identity, such as their name, social security number, biometric records, etc. alone, or when combined with other personal or identifying information which is linked or linkable to a specific individual, such as date and place of birth, mother’s maiden name, etc.”

  What can be considered personally identifiable information (PII) ? Some PII examples :

  • Full name/usernames
  • Home address/mailing address
  • Email address
  • Credit card numbers
  • Date of birth
  • Phone numbers
  • Login details

  • Precise locations
  • Account numbers
  • Passwords
  • Security codes (including biometric records)
  • Personal identification numbers
  • Driver license number
  • Get a more comprehensive list here

  What’s non-PII ?

  Anonymous information, or information that can’t be traced back to an individual, can be considered non-PII.

  Who is affected by the exploitation of PII ?

  Anyone can be affected by the exploitation of personal data, where you have identity theft, account fraud and account takeovers. When websites resort to illegally selling or sharing your data and compromising your privacy, the fear is falling victim to such fraudulent activity. 

  PII can also be an issue when employees have access to the database and the data is not encrypted. For example, anyone working in a bank can access your accounts ; anyone working at Facebook may be able to read your messages. This shows how privacy breaches can easily happen when employees have access to PII.

  Website owner’s responsibility for data privacy (PII and analytics)

  To respect your website visitor’s privacy, best practice is to avoid collecting PII whenever possible. If you work in an industry which requires people to disclose personal information (e.g. healthcare, security industries, public sector), then you must ensure this data is collected and handled securely. 

  

  The US National Institute of Standards and Technology states : “The likelihood of harm caused by a breach involving PII is greatly reduced if an organisation minimises the amount of PII it uses, collects, and stores. For example, an organisation should only request PII in a new form if the PII is absolutely necessary.” 

  How you’re held accountable remains up to the privacy laws of the country you’re doing business in. Make sure you are fully aware of the privacy and data protection laws that relate specifically to you. 

  To reduce the risk of privacy breaches, try collecting as little PII as you can ; purging it as soon as you can ; and making sure your IT security is updated and protected against security threats. 

  If you’re using data collection tools like web analytics, data may be tracked through features like User ID, custom variables, and custom dimensions. Sometimes they are also harder to identify when they are present, for example, in page URLs, page titles, or referrers URLs. So make sure you’re optimising your web analytics tools’ settings to ensure you’re asking your users for consent and respecting users’ privacy.

  If you’re using a GDPR compliant tool like Matomo, learn how you can stop processing such personal data

  PII, GDPR and businesses in the US/EU

  Because PII is broad, you may run into confusion when considering PII and GDPR (which applies in the EU). The General Data Protection Regulation (GDPR) provides more safeguards for user privacy.

  GDPR grants people in the EU more rights concerning their “personal data” (more on PII vs personal data below). In the EU the GDPR restricts the collection and processing of personal data. The repercussions are severe penalties and fines for privacy infringements. Businesses are required to handle this personal data carefully. You can be fined up to 4% of their yearly revenue for data breaches or non-compliance. 

  

  Although there isn’t an overarching data protection law in the US, there are hundreds of laws on both the federal and state levels to protect the personal data of US residents. US Congress has also enacted industry-specific statutes related to data privacy, and the state of California passed the California Consumer Privacy Act. 

  To be on the safe side, if you are using analytics, follow matters relating to “personal data” in the GDPR. It’s all-encompassing when it comes to protecting user privacy. GDPR rules still apply whenever an EU citizen visits any non EU site (that processes personal data).

  Personally identifiable information (PII) vs personal data

  PII and “personal data” aren’t used interchangeably. All personal data can be PII, but not all PII can be defined as personal data.

  The definition of “personal data” according to the GDPR :

  

  This means “personal data” encompasses a greater number of identifiers which include the online sphere. Examples include : IP addresses and URL names. As well as seemingly “innocent” data like height, job position, company etc. 

  What’s considered personal data depends on the context. If a piece of information can be combined with others to establish someone’s identity then that can be considered personal data. 

  Under GDPR, when processing personal data, you need explicit consent. You need to ensure you’re compliant according to GDPR definitions of “personal data” not just what’s considered “PII”.

  How Matomo deals with PII and personal data

  Although Matomo Analytics is a web analytics software that tracks user activity on your website, we take privacy and PII very seriously – on both our Cloud and On-Premise offerings. 

  If you’re using Matomo and would like to know how you can be fully GDPR compliant and protect user privacy, read more :
  

  • Learn how to not process any personally identifiable information – Anonymise IP addresses, user IDs, and order IDs
  • Matomo protects user privacy by talking the talk and walking the walk
  • Stay ahead of the GDPR with a privacy-respecting analytics platform
  • 11 ways Matomo helps you protect your visitor’s privacy

  Disclaimer

  We are not lawyers and don’t claim to be. The information provided here is to help give an introduction to issues you may encounter when dealing with PII. We encourage every business and website to take data privacy seriously and discuss these issues with your lawyer if you have any concerns. 

  Additional resources :

  • https://www.consumeraffairs.com/finance/identity-theft-statistics.html#identity-theft-trends-in-2019
  • https://ec.europa.eu/info/law/law-topic/data-protection_en
  • https://iclg.com/practice-areas/data-protection-laws-and-regulations/usa
  • https://www.csoonline.com/article/3215864/how-to-protect-personally-identifiable-information-pii-under-gdpr.html
  • https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/key-definitions/what-is-personal-data/