Tag: verify

Magento 2 getting error “Broken reference: The element with the “customer” ID wasn’t found. Verify the ID and try again. [] []” in system.log

I am getting lots of

Broken reference: The element with the "customer" ID wasn't found. Verify the ID and try again. [] []

errors in the error.log. I’ve googled around and tried to trace it with NetBeans but I can’t track down what’s causing it. Everything seems to be working perfectly except this error is getting written repeatedly.

Has anyone any idea what’s causing it or how I might track it down?

As some background, I migrated my site from 1.8.1 to 2.3 (and have since upgraded to 2.3.1 but the error started in 2.3). I wonder if something hasn’t migrated correctly. Note it occurs in both developer and production mode.

Verify from this proof of $\lim x^2$

Preliminary Analysis:

$ $ |x^2-4| = |(x-2)(x+2)| = |x-2|<\frac{\varepsilon}{|x+2|}$ $

Since $ \delta$ can not depend on $ x$ then

choose a small $ \delta_i$ such that $ $ \delta_i<\frac{\varepsilon}{|x+2|}$ $ where $ \delta_i$ does not depend on $ x$

Impose $ |x-2|≤ 1$ then

$ $ -1 ≤x-2 ≥1$ $

$ $ = 1 ≤x ≥3$ $

$ $ = 3 ≤x+2 ≥5$ $

$ $ = -5<3 ≤x+2 ≥5$ $

$ $ = |x+2| ≤5 $ $

put $ \delta_i = \frac{\varepsilon}{5}$

then $ $ \delta_i = \frac{\varepsilon}{5}<\frac{\varepsilon}{|x+2|}$ $

Now we have $ $ |x^2-4| = |(x-2)(x+2)| < 5.|x-2| = |x-2|<\frac{\varepsilon}{5}$ $

Formal proof:

$ \lim_{x\to 2}f(x)=x^2\iff (\forall\varepsilon>0)(\exists\delta>0):0<\lvert x-2\rvert<\delta = \min({1,\frac{\varepsilon}{5}})\implies\bigl\lvert x^2-4\rvert = |(x+2)(x-2)| < 5.|x-2|<5 \frac{\varepsilon}{5} = \varepsilon$

How reliable is rpm –verify when auditing package integrity and what alternatives are there?

Currently to verify package integrity, the command rpm --verify is run. In reading the rpm manual (http://ftp.rpm.org/max-rpm/s1-rpm-verify-output.html), there is no indication as to the veracity of the verification process.

It is my understanding solutions such as AIDE and Tripwire expect a known good state and are unable to attest integrity when packages have been updated and/or upgraded.

  • What alternatives are there to assure the integrity of packages post installation as well as subsequent updates and upgrades?
  • How can corruptions by omission or commission be detected and identified?
  • What options are there if a known good state is unknown?

NVRAM Showing Questionable Payload Variables… Can anyone verify if this is normal?

I used the terminal command in macOS ‘nvram -xp’: 

    student:~ admin$   nvram -xp <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict>     <key>ALS_Data</key>     <data>     AKs=     </data>     <key>LocationServicesEnabled</key>     <data>     AQ==     </data>     <key>SmcFlasherResult</key>     <data>     AAAAAAAAAAAAAAAAAAAAAA==     </data>     <key>SystemAudioVolume</key>     <data>     VA==     </data>     <key>SystemAudioVolumeDB</key>     <data>     6w==     </data>     <key>Test_ALS_Data</key>     <data>     AQA=     </data>     <key>backlight-level</key>     <data>     2Qo=     </data>     <key>bluetoothActiveControllerInfo</key>     <data>     j4KsBQAAAAAzFEjXBbzp6g==     </data>     <key>bluetoothInternalControllerInfo</key>     <data>     j4KsBQAAMxRI1wW86eo=     </data>     <key>boot-gamma</key>     <data>     EAYAAN+cAAAAAAAAwgAAAAAAAAAMAAEGTwQDDl8MySdZLFRQ5FpXXFtnXXYff6OMHJYr     rUC5scSGz3TQ99j995Tz//zo+A4AAQesBAMOFwtQQxZGV1/CYuGHoIenneyeqabNp667     scCxxXvKM8+w0vXWmdq66T3q/fRw9f/80voQAAIIJwQEEO8JTz6PMxJK1zxVV5RIIoh4     biaagXqttECR7rp1lbDABZ3zzmaru+zuzf32n9v++YTh/vuH6P/9//I=     </data>     <key>efi-apple-payload0</key>     <data>     PGFycmF5PjxkaWN0PjxrZXk+SU9NYXRjaDwva2V5PjxkaWN0PjxrZXk+SU9Qcm92aWRl     ckNsYXNzPC9rZXk+PHN0cmluZz5JT01lZGlhPC9zdHJpbmc+PGtleT5JT1Byb3BlcnR5     TWF0Y2g8L2tleT48ZGljdD48a2V5PlVVSUQ8L2tleT48c3RyaW5nPjQ3MUE4QUI0LUVB     NjUtNEQzMC1BM0YzLURENjhFMEEwMjRBNTwvc3RyaW5nPjwvZGljdD48L2RpY3Q+PGtl     eT5CTExhc3RCU0ROYW1lPC9rZXk+PHN0cmluZz5kaXNrMHMxPC9zdHJpbmc+PC9kaWN0     PjxkaWN0PjxrZXk+SU9FRklEZXZpY2VQYXRoVHlwZTwva2V5PjxzdHJpbmc+TWVkaWFG     aWxlUGF0aDwvc3RyaW5nPjxrZXk+UGF0aDwva2V5PjxzdHJpbmc+XEVGSVxBUFBMRVxV     UERBVEVSU1xTTUNcTWFjLTdERjIxQ0IzRUQ2OTc3RTUuc21jPC9zdHJpbmc+PC9kaWN0     PjwvYXJyYXk+AA==     </data>     <key>efi-apple-payload0-data</key>     <data>     AgEMANBBAwoAAAAAAQEGAAUcAQEGAAAAAxIKAAAAAAAAAAQBKgABAAAAKAAAAAAAAAAA     QAYAAAAAALSKGkdl6jBNo/PdaOCgJKUCAgQEZgBcAEUARgBJAFwAQQBQAFAATABFAFwA     VQBQAEQAQQBUAEUAUgBTAFwAUwBNAEMAXABNAGEAYwAtADcARABGADIAMQBDAEIAMwBF     AEQANgA5ADcANwBFADUALgBzAG0AYwAAAH//BAA=     </data>     <key>efi-apple-payload1</key>     <data>     PGFycmF5PjxkaWN0PjxrZXk+SU9NYXRjaDwva2V5PjxkaWN0PjxrZXk+SU9Qcm92aWRl     ckNsYXNzPC9rZXk+PHN0cmluZz5JT01lZGlhPC9zdHJpbmc+PGtleT5JT1Byb3BlcnR5     TWF0Y2g8L2tleT48ZGljdD48a2V5PlVVSUQ8L2tleT48c3RyaW5nPjQ3MUE4QUI0LUVB     NjUtNEQzMC1BM0YzLURENjhFMEEwMjRBNTwvc3RyaW5nPjwvZGljdD48L2RpY3Q+PGtl     eT5CTExhc3RCU0ROYW1lPC9rZXk+PHN0cmluZz5kaXNrMHMxPC9zdHJpbmc+PC9kaWN0     PjxkaWN0PjxrZXk+SU9FRklEZXZpY2VQYXRoVHlwZTwva2V5PjxzdHJpbmc+TWVkaWFG     aWxlUGF0aDwvc3RyaW5nPjxrZXk+UGF0aDwva2V5PjxzdHJpbmc+XEVGSVxBUFBMRVxV     UERBVEVSU1xTTUNcZmxhc2hlcl9iYXNlLnNtYzwvc3RyaW5nPjwvZGljdD48L2FycmF5     PgA=     </data>     <key>efi-apple-payload1-data</key>     <data>     AgEMANBBAwoAAAAAAQEGAAUcAQEGAAAAAxIKAAAAAAAAAAQBKgABAAAAKAAAAAAAAAAA     QAYAAAAAALSKGkdl6jBNo/PdaOCgJKUCAgQEVgBcAEUARgBJAFwAQQBQAFAATABFAFwA     VQBQAEQAQQBUAEUAUgBTAFwAUwBNAEMAXABmAGwAYQBzAGgAZQByAF8AYgBhAHMAZQAu     AHMAbQBjAAAAf/8EAA==     </data>     <key>efi-apple-payload2</key>     <data>     PGFycmF5PjxkaWN0PjxrZXk+SU9NYXRjaDwva2V5PjxkaWN0PjxrZXk+SU9Qcm92aWRl     ckNsYXNzPC9rZXk+PHN0cmluZz5JT01lZGlhPC9zdHJpbmc+PGtleT5JT1Byb3BlcnR5     TWF0Y2g8L2tleT48ZGljdD48a2V5PlVVSUQ8L2tleT48c3RyaW5nPjQ3MUE4QUI0LUVB     NjUtNEQzMC1BM0YzLURENjhFMEEwMjRBNTwvc3RyaW5nPjwvZGljdD48L2RpY3Q+PGtl     eT5CTExhc3RCU0ROYW1lPC9rZXk+PHN0cmluZz5kaXNrMHMxPC9zdHJpbmc+PC9kaWN0     PjxkaWN0PjxrZXk+SU9FRklEZXZpY2VQYXRoVHlwZTwva2V5PjxzdHJpbmc+TWVkaWFG     aWxlUGF0aDwvc3RyaW5nPjxrZXk+UGF0aDwva2V5PjxzdHJpbmc+XEVGSVxBUFBMRVxV     UERBVEVSU1xTTUNcZmxhc2hlcl91cGRhdGUuc21jPC9zdHJpbmc+PC9kaWN0PjwvYXJy     YXk+AA==     </data>     <key>efi-apple-payload2-data</key>     <data>     AgEMANBBAwoAAAAAAQEGAAUcAQEGAAAAAxIKAAAAAAAAAAQBKgABAAAAKAAAAAAAAAAA     QAYAAAAAALSKGkdl6jBNo/PdaOCgJKUCAgQEWgBcAEUARgBJAFwAQQBQAFAATABFAFwA     VQBQAEQAQQBUAEUAUgBTAFwAUwBNAEMAXABmAGwAYQBzAGgAZQByAF8AdQBwAGQAYQB0     AGUALgBzAG0AYwAAAH//BAA=     </data>     <key>efi-apple-payload3</key>     <data>     PGFycmF5PjxkaWN0PjxrZXk+SU9NYXRjaDwva2V5PjxkaWN0PjxrZXk+SU9Qcm92aWRl     ckNsYXNzPC9rZXk+PHN0cmluZz5JT01lZGlhPC9zdHJpbmc+PGtleT5JT1Byb3BlcnR5     TWF0Y2g8L2tleT48ZGljdD48a2V5PlVVSUQ8L2tleT48c3RyaW5nPjQ3MUE4QUI0LUVB     NjUtNEQzMC1BM0YzLURENjhFMEEwMjRBNTwvc3RyaW5nPjwvZGljdD48L2RpY3Q+PGtl     eT5CTExhc3RCU0ROYW1lPC9rZXk+PHN0cmluZz5kaXNrMHMxPC9zdHJpbmc+PC9kaWN0     PjxkaWN0PjxrZXk+SU9FRklEZXZpY2VQYXRoVHlwZTwva2V5PjxzdHJpbmc+TWVkaWFG     aWxlUGF0aDwvc3RyaW5nPjxrZXk+UGF0aDwva2V5PjxzdHJpbmc+XEVGSVxBUFBMRVxV     UERBVEVSU1xTTUNcTWFjLTdERjIxQ0IzRUQ2OTc3RTUuZXBtPC9zdHJpbmc+PC9kaWN0     PjwvYXJyYXk+AA==     </data>     <key>efi-apple-payload3-data</key>     <data>     AgEMANBBAwoAAAAAAQEGAAUcAQEGAAAAAxIKAAAAAAAAAAQBKgABAAAAKAAAAAAAAAAA     QAYAAAAAALSKGkdl6jBNo/PdaOCgJKUCAgQEZgBcAEUARgBJAFwAQQBQAFAATABFAFwA     VQBQAEQAQQBUAEUAUgBTAFwAUwBNAEMAXABNAGEAYwAtADcARABGADIAMQBDAEIAMwBF     AEQANgA5ADcANwBFADUALgBlAHAAbQAAAH//BAA=     </data>     <key>efi-apple-recovery</key>     <data>     PGFycmF5PjxkaWN0PjxrZXk+SU9NYXRjaDwva2V5PjxkaWN0PjxrZXk+SU9Qcm92aWRl     ckNsYXNzPC9rZXk+PHN0cmluZz5JT01lZGlhPC9zdHJpbmc+PGtleT5JT1Byb3BlcnR5     TWF0Y2g8L2tleT48ZGljdD48a2V5PlVVSUQ8L2tleT48c3RyaW5nPjQ3MUE4QUI0LUVB     NjUtNEQzMC1BM0YzLURENjhFMEEwMjRBNTwvc3RyaW5nPjwvZGljdD48L2RpY3Q+PGtl     eT5CTExhc3RCU0ROYW1lPC9rZXk+PHN0cmluZz5kaXNrMHMxPC9zdHJpbmc+PC9kaWN0     PjxkaWN0PjxrZXk+SU9FRklEZXZpY2VQYXRoVHlwZTwva2V5PjxzdHJpbmc+TWVkaWFG     aWxlUGF0aDwvc3RyaW5nPjxrZXk+UGF0aDwva2V5PjxzdHJpbmc+XEVGSVxBUFBMRVxG     SVJNV0FSRVxNQkE2MS5zY2FwPC9zdHJpbmc+PC9kaWN0PjwvYXJyYXk+AA==     </data>     <key>efi-backup-boot-device</key>     <data>     PGFycmF5PjxkaWN0PjxrZXk+SU9NYXRjaDwva2V5PjxkaWN0PjxrZXk+SU9Qcm92aWRl     ckNsYXNzPC9rZXk+PHN0cmluZz5JT01lZGlhPC9zdHJpbmc+PGtleT5JT1Byb3BlcnR5     TWF0Y2g8L2tleT48ZGljdD48a2V5PlVVSUQ8L2tleT48c3RyaW5nPkRCOUFFQ0Y2LTg2     QzYtNDcyOS1CRTk5LUM2N0MzREIxMzgwQTwvc3RyaW5nPjwvZGljdD48L2RpY3Q+PGtl     eT5CTExhc3RCU0ROYW1lPC9rZXk+PHN0cmluZz5kaXNrMXMyPC9zdHJpbmc+PC9kaWN0     PjxkaWN0PjxrZXk+SU9FRklEZXZpY2VQYXRoVHlwZTwva2V5PjxzdHJpbmc+TWVkaWFG     aWxlUGF0aDwvc3RyaW5nPjxrZXk+UGF0aDwva2V5PjxzdHJpbmc+XDFBMzk2RjBBLTlD     NjYtMzVGMy05ODA1LTQ2RDBGNEZENjdCNVxTeXN0ZW1cTGlicmFyeVxDb3JlU2Vydmlj     ZXNcYm9vdC5lZmk8L3N0cmluZz48L2RpY3Q+PC9hcnJheT4A     </data>     <key>efi-backup-boot-device-data</key>     <data>     AgEMANBBAwoAAAAAAQEGAAUcAQEGAAAAAxIKAAAAAAAAAAQBKgACAAAAKEAGAAAAAACw     vxkOAAAAACCV+WedIUZClu42JCLFaBoCAgQDJAD3/HS+fAvzSZFHAfQELmhC9uya28aG     KUe+mcZ8PbE4CgQEmgBcADEAQQAzADkANgBGADAAQQAtADkAQwA2ADYALQAzADUARgAz     AC0AOQA4ADAANQAtADQANgBEADAARgA0AEYARAA2ADcAQgA1AFwAUwB5AHMAdABlAG0A     XABMAGkAYgByAGEAcgB5AFwAQwBvAHIAZQBTAGUAcgB2AGkAYwBlAHMAXABiAG8AbwB0     AC4AZQBmAGkAAAB//wQA     </data>     <key>efi-backup-boot-device-data-data</key>     <data>     AgEMANBBAwoAAAAAAQEGAAUcAQEGAAAAAxIKAAAAAAAAAAQBKgACAAAAKEAGAAAAAACw     vxkOAAAAACCV+WedIUZClu42JCLFaBoCAgQDJAD3/HS+fAvzSZFHAfQELmhC9uya28aG     KUe+mcZ8PbE4CgQEmgBcADEAQQAzADkANgBGADAAQQAtADkAQwA2ADYALQAzADUARgAz     AC0AOQA4ADAANQAtADQANgBEADAARgA0AEYARAA2ADcAQgA1AFwAUwB5AHMAdABlAG0A     XABMAGkAYgByAGEAcgB5AFwAQwBvAHIAZQBTAGUAcgB2AGkAYwBlAHMAXABiAG8AbwB0     AC4AZQBmAGkAAAB//wQA     </data>     <key>efi-boot-device</key>     <data>     PGFycmF5PjxkaWN0PjxrZXk+SU9NYXRjaDwva2V5PjxkaWN0PjxrZXk+SU9Qcm92aWRl     ckNsYXNzPC9rZXk+PHN0cmluZz5JT01lZGlhPC9zdHJpbmc+PGtleT5JT1Byb3BlcnR5     TWF0Y2g8L2tleT48ZGljdD48a2V5PlVVSUQ8L2tleT48c3RyaW5nPkRCOUFFQ0Y2LTg2     QzYtNDcyOS1CRTk5LUM2N0MzREIxMzgwQTwvc3RyaW5nPjwvZGljdD48L2RpY3Q+PGtl     eT5CTExhc3RCU0ROYW1lPC9rZXk+PHN0cmluZz5kaXNrMXMyPC9zdHJpbmc+PC9kaWN0     PjxkaWN0PjxrZXk+SU9FRklEZXZpY2VQYXRoVHlwZTwva2V5PjxzdHJpbmc+TWVkaWFG     aWxlUGF0aDwvc3RyaW5nPjxrZXk+UGF0aDwva2V5PjxzdHJpbmc+XDFBMzk2RjBBLTlD     NjYtMzVGMy05ODA1LTQ2RDBGNEZENjdCNVxTeXN0ZW1cTGlicmFyeVxDb3JlU2Vydmlj     ZXNcYm9vdC5lZmk8L3N0cmluZz48L2RpY3Q+PC9hcnJheT4A     </data>     <key>efi-boot-device-data</key>     <data>     AgEMANBBAwoAAAAAAQEGAAUcAQEGAAAAAxIKAAAAAAAAAAQBKgACAAAAKEAGAAAAAACw     vxkOAAAAACCV+WedIUZClu42JCLFaBoCAgQDJAD3/HS+fAvzSZFHAfQELmhC9uya28aG     KUe+mcZ8PbE4CgQEmgBcADEAQQAzADkANgBGADAAQQAtADkAQwA2ADYALQAzADUARgAz     AC0AOQA4ADAANQAtADQANgBEADAARgA0AEYARAA2ADcAQgA1AFwAUwB5AHMAdABlAG0A     XABMAGkAYgByAGEAcgB5AFwAQwBvAHIAZQBTAGUAcgB2AGkAYwBlAHMAXABiAG8AbwB0     AC4AZQBmAGkAAAB//wQA     </data>     <key>fmm-computer-name</key>     <data>     c3R1ZGVudA==     </data>     <key>fmm-mobileme-token-FMM</key>     <data>     YnBsaXN0MDDdAQIDBAUGBwgJCgsMDQ4PFhcOGA4ZGhscHR9fEA91bnJlZ2lzdGVyU3Rh     dGVYdXNlckluZm9ZYXV0aFRva2VuXxARb3NVc2VyRGlzYXBwZWFyZWReZGlzYWJsZUNv     bnRleHRWdXNlcmlkXWVuYWJsZUNvbnRleHRYdXNlcm5hbWVYcGVyc29uSURXYWRkVGlt     ZVRndWlkXxASZW5hYmxlZERhdGFjbGFzc2VzXxATZGF0YWNsYXNzUHJvcGVydGllcxAA     0xAREhMUFV8QFUluVXNlT3duZXJEaXNwbGF5TmFtZV8QE0luVXNlT3duZXJGaXJzdE5h     bWVfEBJJblVzZU93bmVyTGFzdE5hbWVcWXVqaSBPa2FtdXJhVFl1amlXT2thbXVyYV8Q     KEFRQUFBQUJaSE5laWdadGl5VUg4dlZ6Q3JDMnN1MmxadUoxNTZXc34JEQH1XxAbeXVq     aS5va2FtdXJhQG91c2QuazEyLmNhLnVzWjgzNDQxNzE4MDEjQdZHNekcAypfECQzMzYw     MkRERS1EMzI3LTRBRjYtOUY3MS03ODY2MzZERjM3NjOhHl8QIWNvbS5hcHBsZS5EYXRh     Y2xhc3MuRGV2aWNlTG9jYXRvctEeINUhIiMkJSYnKCkqVmFwc0Vudlhob3N0bmFtZV1p     ZHNJZGVudGlmaWVyVnNjaGVtZV1hdXRoTWVjaGFuaXNtWlByb2R1Y3Rpb25fEBNwMjYt     Zm1pcC5pY2xvdWQuY29tXxAkRDQ0MDFGNEUtRkI3QS00M0EyLThCRUEtMDhFMUM2RDAz     NjU4VWh0dHBzVXRva2VuAAgAIwA1AD4ASABcAGsAcgCAAIkAkgCaAJ8AtADKAMwA0wDr     AQEBFgEjASgBMAFbAVwBXwF9AYgBkQG4AboB3gHhAewB8wH8AgoCEQIfAioCQAJnAm0A     AAAAAAACAQAAAAAAAAArAAAAAAAAAAAAAAAAAAACcw==     </data>     <key>fmm-mobileme-token-FMM-BridgeHasAccount</key>     <data>     QnJpZGdlSGFzQWNjb3VudFZhbHVl     </data>     <key>prev-lang:kbd</key>     <data>     ZW4tVVM6MA==     </data> </dict> </plist>

Is it possible to verify the requesting user for a REST transaction secured by JWT at a later date?

I have a React (Javascript) single-page application that authenticates users via username/password/MFA to Keycloak, receives a signed JWT upon successful authentication, and then uses that JWT to call stateless/session-less REST services.

With this setup, or with additional “moving parts” to be added to the overall system, is there a way to at a later date to assert that a certain user identity was responsible for a transaction? Assume that we are able to store any/all data that is in-context (i.e., is part of the REST call for the transaction) at the time the transaction is requested.

Thanks to @alnbhclyn for their thoughts below. I think I need to clarify — the key gap above seems to be the link between a JWT and the specific contents of a transaction. Is there a means of “signing” the transaction with the JWT or some part thereof such that a positive link between the two can be made at any point in the future?

How can google’s ReCaptcha verify identity *and* train AI?

I have heard that the reason the image portion of ReCaptcha contains so many driving questions is that Google is using it to train AI for their self-driving cars. But to make it an effective security measure, wouldn’t Google need to verify that the squares the user clicked on contained stop signs or street lights or whatever they asked for? That would mean they already know what is in each image, so how do they gain new information from it? How can they verify the information is correct without knowing beforehand?

Verify steps in Azure Active Directory for Dynamics 365 Web API use

I’m working with a client who is using Dynamics 365 for their CRM. I need Web API access to retrieve customer data to incorporate it in my external app. Being new to Azure/Dynamics, I’ve been learning and developing using a trial account. The following is what I’ve done in my Azure trial, and what I’m expecting the Azure admin will do for me in the production environment:

  1. Register a new app for my use (e.g., “My App”)
    • AAD › App registrations › New registration
  2. Create client secret (never expires)
    • AAD › App registrations › My App › Certificates & secrets › New client secret
  3. Expose Dynamics CRM API
    • AAD › App registrations › My App › API permissions › Dynamics CRM (Delegated user_impersonation) › [Add permissions]
  4. Grant admin consent
    • AAD › App registrations › My App › API permissions › [Grant admin consent]
  5. Assign ‘My App’ to non-admin user (the user account that I will use to authenticate and make GET requests)
    • AAD › Enterprise Applications › My App › Users and groups › Add user › My User › [Assign]

With the steps that I’ve listed above, everything is working great between my external app and my trial Azure/Dynamics account. I’m successfully authenticating, obtaining oauth2.0 access and refresh tokens, and making GET requests of the dummy customer data – all as a non-admin user.

So, before moving forward, I’m hoping that someone with more experience with Azure/Dynamics can let me know whether or not I have a solid understanding and am doing things in a relatively normal and secure way.