pdfsizeopt – AssertionError: Multivalent failed (status)

This error could mean you’re using a  newer version of Multivalent which no longer has the pdf tools bundled into it. You’ll need this older version with the proper tools.

Download: Multivalent.jar

Just as a note though, pdfsizeopt is a pretty old program that may not be able to handle newer pdfs and may do a poor job optimizing many others.

 

File “./pdfsizeopt”, line 30, in <module>
sys.exit(main.main(sys.argv))
File “./lib/pdfsizeopt/main.py”, line 8081, in main
is_flate_ok=not do_decompress_flate)
File “./lib/pdfsizeopt/main.py”, line 7773, in Save
multivalent_java=multivalent_java)
File “./lib/pdfsizeopt/main.py”, line 7691, in _RunMultivalent
assert False, ‘Multivalent failed (status)’
AssertionError: Multivalent failed (status)

/usr/bin/java -cp /users/lukerehmann/Multivalent.jar -Djava.awt.headless=true tool.pdf.Compress -nopagepiece -noalt -mon ADTTD_Product_Manual-Approved_Labeling_optimized.pdf
Exception in thread “main” java.lang.NoClassDefFoundError: tool/pdf/Compress
Caused by: java.lang.ClassNotFoundException: tool.pdf.Compress
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)

Google Cloud : Service account not enabled on this instance

PHP Fatal error: Uncaught exception ‘Google\\Cloud\\Core\\Exception\\NotFoundException’ with message ‘{“error”:”invalid_request”,”error_description”:”Service account not enabled on this instance”}’ in /var/www/html/vendor/google/cloud/src/Core/RequestWrapper.php:241\nStack trace:\n#0 /var/www/html/vendor/google/cloud/src/Core/RequestWrapper.php(150): Google\\Cloud\\Core\\RequestWrapper->convertToGoogleException(Object(Google\\Cloud\\Core\\Exception\\NotFoundException))\n#1 /var/www/html/vendor/google/cloud/src/Core/RestTrait.php(86): Google\\Cloud\\Core\\RequestWrapper->send(Object(GuzzleHttp\\Psr7\\Request), Array)\n#2 /var/www/html/vendor/google/cloud/src/Storage/Connection/Rest.php(132): Google\\Cloud\\Storage\\Connection\\Rest->send(‘buckets’, ‘insert’, Array)\n#3 /var/www/html/vendor/google/cloud/src/Storage/StorageClient.php(225): Google\\Cloud\\Storage\\Connection\\Rest->insertBucket(Array)\n#4 /var/www/html/gcloudtest.php(20): Google\\Cloud\\Storage\\StorageClient->createBucket(‘my-new-bucket’)\n#5 {main}\n thrown in /var/www/html/vendor/google/cloud/src/Core/RequestWrapper.php on line 241

The FuzeCard Problem – EMV Chip Payments and Bank Negotiations

In the past couple years, we’ve seen the coming and going of several smart card companies promising to merge all your credit, debit, and rewards cards into one smart connected wallet. Despite the excitement surrounding all these products, they seem to run into one common wall when it comes to consumer deployment – EMV “Chip” Payments.

Coin and Plastc Shutdown, leaving millions of backers (and their money) out to dry. While Stratos and Swyp seem to be in a perpetual “sign up to get notified” phase. None of the cards have ever successfully supported Chip and Pin or EMV Payments. Why? Because it requires big connections and a large customer base to convince banks to open up their secure chip and pin technology to your ‘smart card’, and, unfortunately, this requires negotiations with each card issuer.

From FuzeCard’s website:

EMV payments require the approval of the card issuer/banks. Fuze’s chip will be compatible from the launch and this feature will be fully available with a future firmware update

As promising as this may sound, it’s not a software problem that Fuze is up against here and no simple firmware update will give the card the EMV support it needs. BrilliantTS will need to first negotiate with big banks, and that’s a tough sell at least 4 companies have failed to do thus far.

Do their promo cards have working EMV chips? According to their Instagram content, no, not yet.

One post from their instagram shows a box of bpay cards from a startup in South Korea. So, what do bpay and FuzeCard have in common? Both appear to be owned by BrilliantTS.

BrilliantTS’s bpay cards appear to have come to the same brickwall for EMV Payments, indicating only “Reserve Now!” for EMV Chip enabled cards.

bpay Card Options

 

 

 

 

com.OptiBuy.agent and com.MyMacUpdater.agent

Noticed the following suspicious startup items on a  friend’s Mac OS X 10.10.5:

com.MyMacUpdater.agent

com.MyUpdater.agent

com.OptiBuy.agent

The friend had constant McAffe ads in her default browser (Google Chrome).  The computer doesn’t have any recently installed items. The startup items were removed with CCleaner, the computer was updated with the updates available in the app store and restarted. Upon computer restart, Google Chrome indicated “mac search manager” was added. The computer was then updated to the latest version of OSX (macOS Sierra) and restarted.

To update your computer to Sierra, search macOS Sierra in the app store, download, and install. This is a fairly large update so it may take several hours to download and additional time to install.

Recursively Finding (and replacing) All Depreciated

Running the following code from your starting will give you the location of all short open tags in .php extension files. This command recursively searches all directories from the directory you start in.
grep -r --include "*.php" "<?[ ]" .

You may need to modify it if you have .php5 files or other non-php extensions holding php content.

If you’re looking to repalce all of these en-masse, you can do that [very roughly] with the following commands:

replace ALL tags (< ?) with

grep -rl --include "*.php" "<?[^p]" | xargs sed -i 's/<?/<?php/g'

fix any accidently replaced tags that might have happened
grep -rl --include "*.php""<?php" | xargs sed -i 's/<?phpphp/<?php/g'

You should carefully review all replacements done by this code, some php code could break!

Simple Proxmark3 Getting Started Guide on Windows

In the below video, we’ll be scanning a high frequency 13.56 MHZ card (NXP Mifare Classic) and two low frequency 125 kHz cards (HID and EM410x Tag)

Steps:

  1. First, assemble your proxmark
  2. Download the latest compiled Proxmark3 Software from https://rehmann.co/url/proxmark3
  3. Unzip the file contents, and rename the content folder to proxmark3. For the commands following, you should have a folder in your downloads called proxmark3 with the following subfolders: win32, firmware_win, and Windows Driver. If you haven’t already updated your proxmark3 firmware to the latest version, go here.
  4. Open Device Manager to get the COM port of the Proxmark. In this case, it is COM7.
  5. Open Command Prompt (CMD)
  6. Execute the following command to connect to your proxmark3, be sure to replace your COM port with the proper COM port found in Device Manager

    Downloads\proxmark3\win32\proxmark3.exe COM7

  7. You’re now connected to the proxmark3! The following commands will do a low-frequency and high-frequency search for known devices.

    lf search

    hf search

  8. Questions and commends below!

Cards Scanned:

  • T5577 @ 125 kHZ
  • EM410x Tag M1 S50 @ 13.56 MHZ
  • HID ProxCard II @ 125 kHZ

Simple Proxmark3 Firmware Updating Guide [Windows]

Steps for Updating the Firmware on the Proxmark3 on Windows.

  1. Download the latest software and firmware from https://rehmann.co/url/proxmark3 (thanks to gator96100 from proxmark.org)
  2. Extract the downloaded zip file to your downloads folder and change the name to proxmark3
  3. Plug in your proxmark3 and find the COM port it is connected to in Device Manager. Take note of this port.
  4. Unplug your Proxmark3
  5. Run the following single command in Command Prompt (CMD) be sure to changeCOM0 to the proper COM port:

    Downloads\proxmark3\win32\flasher.exe COM0 -b Downloads\proxmark3\firmware_win\bootrom\bootrom.elf Downloads\proxmark3\firmware_win\fullimage.elf

  6. The firmware uploader will then begin to wait for your proxmark3 to be reconnected.
  7. Hold down the button on your proxmark3 and reconnect it. KEEP THE BUTTON HELD DOWN UNTIL THE PROCESS IS COMPLETE!
  8. Once the firmware updater tells you to have a nice day, you can let go of the button and disconnect/reconnect the proxmark.
  9. Get started scanning a card with this guide