RXOP

Hi,

Our customer has http exception (attached image) when try to install SmartScanEx_106.zip by Remote Operation Client version 1.6.2 (RXOP 3.8.3).

Please help.

Thank you very much.

Hello,

This is a continuation of incident number 3916 I was working on with Alex Reyes for customer Henkel regarding the priority application.

The customer updated the device firmware and are still getting the same issue. The priority application is failing to be set on the device with a 401 error.

I am attaching the latest system tracelog. They reproduced the issue and obtained the tracelog for 1 day only. Looking at it, it looks like they are getting the exact same error on the device they were getting before:

12-11 01:55:28.480 4397 6551 I RCS:FuncConfServ: :decodePassword() start
12-11 01:55:28.490 4397 6551 W System.err: javax.crypto.BadPaddingException: pad block corrupted

Can you confirm their device's firmware is all properly updated? If so, then do we need to go back to Japan and hopefully get some more information?

Regards
Bryan

Hi,

Our customer has http exception (attached image) when try to install SmartScanEx_106.zip by Remote Operation Client version 1.6.2 (RXOP 3.8.3).

Please help.

Thank you very much.

Hi, 

I use this command to get sp value

rxopclient.bat get-sp 172.26.3.43 D:\study\DRS\newDRS\ricohdev\clitools\EQDeviceInitialization\res\acl_sop.dist SYSTEM_SWITCH__09

It reports error:

I tested in  

RXOP-3.8.1-release.zip and RXOP-3.8.3-release.zip

Please help.

Thank you very much.

Hello,

I have updated our RXOP libraries from 3.7.3 to 3.8.3 (including the rxsp servlet zip folders) and I am seeing an error when retrieving SP data on our IM C2000 device. When running it against our MP C2004 device it works fine. So I suspect something to do with the SOP version of rxspservlet and/or something with the IM C2000 not having a Java VM card.

We create an SPManager instance by invoking SPManager.create(ip, usrwim, pwdwim)

The device has a default admin with username "admin" and password blank. At first I thought it may be due to the blank password, so I created a second admin user "admin2" with password = "password", and used those credentials for RXOP, however that also did not work.

The error is:

Hello,

We have a customer that is attempting to set the priority application to our "Secure Print" application during the deployment of our pull print solution to the MFD.

Our deployment is failing to set the priority application with a 401 error. You can see this in the deployment log starting at the 09:11:08 mark. It attempts to use the machine administrator and then tries the fixed default user of pfuncuname. The corresponding log messages in the system trace log occur at 09-16 03:11:02.219. The server and the MFD must be in different timezones.

The question is, why does the machine administrator fail with a 401? According to the device settings, device administrator login should work. If you look at the sop.txt log in the system trace log, you can see this message when trying to set the priority application using the machine administrator:

09-16 03:11:02.219 4790 5221 I priapp_srv: Received POST request
09-16 03:11:02.219 4790 5221 I priapp_srv: set_priority action=jp.co.ricoh.advop.serverservice.SET_PRIORITY_FUNCTION priorityFuncId=#Intent;action=android.intent.action.MAIN;category=android.intent.category.DEFAULT;launchFlags=0x10200000;component=com.lrs.ricohapps.android.securedelivery/.SdActivityLoading;end isLocked=true
09-16 03:11:02.219 4790 5221 I priapp_srv: wait return intent...
09-16 03:11:02.229 4477 4477 I RCS:FPriConfServ: onPreExecute()
09-16 03:11:02.249 4477 6400 I RCS:FPriConfServ: doInBackground()
09-16 03:11:02.249 4477 6400 I RCS:FPriConfServ: :checkLoginSate() start
09-16 03:11:02.279 4477 4477 I RCS:FPriConfServ: checkLoginStateAnsReceiver onReceive mIsOthersLoggingIn=false
09-16 03:11:02.279 4477 6400 I RCS:FPriConfServ: :decodePassword() start
09-16 03:11:02.289 4477 6400 W System.err: javax.crypto.BadPaddingException: pad block corrupted

Not sure why the device is getting an error when attempting to "decodePassword(). Is this something I am doing wrong in the deployment, or does the device have some configuration issue causing this?

This code for the set function priority in our deployment works on all of our devices here and at other customers, so this is the only customer I am aware of experiencing this issue.

Any ideas?

I have attached our deployment log, the system trace log and the rxinst logs.

Regards
Bryan

Hi Ricoh support team,

There are some libraries flagged for outdated jar as below

• bcprov-jdk14-152.jar
• log4j-1.2.17.jar

Could you provide estimates on updating to latest versions for that?

If Ricoh does not have any plan for updating the outdated librabry, is if safe to update them from our site?

Thanks,

During a scan of our software for issues the following 3rd party RXOP libs were flagged, bcprov-jdk14-152.jar and log4j-1.2.17.jar. I see that even if we were to roll out the latest RXOP those two libs have not been updated. While I believe the issues flagged wont be a problem we do need to report the findings to Ricoh per process for your input. Ideally the next release of RXOP will ensure all 3rd party libs are updated to the latest secure versions.

Can you please

• confirm that you agree these two issue are not a problem?
• Let us know if Ricoh plans to update these and other libs to the latest version?
• Comment on thoughtas about Kofax possbily updating libraries where no code change is needed?

Issues flagged are:

bcprov-jdk14-152.jar - CRITICAL https://nvd.nist.gov/vuln/search/results?form_type=Advanced&results_type=overview&search_type=all&cpe_vendor=cpe%3A%2F%3Abouncycastle&cpe_product=cpe%3A%2F%3Abouncycastle%3Alegion-of-the-bouncy-castle-java-crytography-api&cpe_version=cpe%3A%2F%3Abouncycastle%3Alegion-of-the-bouncy-castle-java-crytography-api%3A1.52.0

log4j-1.2.17.jar - CRITICAL https://nvd.nist.gov/vuln/search/results?form_type=Advanced&results_type=overview&search_type=all&cpe_vendor=cpe%3A%2F%3Aapache&cpe_product=cpe%3A%2F%3Aapache%3Alog4j&cpe_version=cpe%3A%2F%3Aapache%3Alog4j%3A1.2.17