Project

General

Profile

Bug #15034

DecoderException: unable to decode base64 string: invalid characters encountered in base64 data

Added by François ARMAND 6 months ago. Updated 15 days ago.

Status:
Released
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

Description

We got an inventory that lead to that error.

We are not sure that the data are actually bad, but in all case, it should not blow up the execution with:

org.bouncycastle.util.encoders.DecoderException: unable to decode base64 string: invalid characters encountered in base64 data
    at org.bouncycastle.util.encoders.Base64.decode(Unknown Source)
    at org.bouncycastle.util.io.pem.PemReader.loadObject(Unknown Source)
    at org.bouncycastle.util.io.pem.PemReader.readPemObject(Unknown Source)
    at org.bouncycastle.openssl.PEMParser.readObject(Unknown Source)
    at com.normation.inventory.domain.PublicKey.$anonfun$publicKey$3(DataTypes.scala:110)
    at scalaz.zio.internal.FiberContext.nextInstr(FiberContext.scala:412)
    at scalaz.zio.internal.FiberContext.evaluateNow(FiberContext.scala:164)
    at scalaz.zio.internal.FiberContext.$anonfun$evaluateLater$1(FiberContext.scala:322)
....
Caused by: 
scalaz.zio.FiberFailure: Fiber failed.|An unchecked error was produced.|org.bouncycastle.util.encoders.DecoderException: unable to decode base64 string: invalid characters encountered in base64 data|?at org.bouncycastle.util.encoders.Base64.decode(Unknown Source)|?at org.bouncycastle.util.io.pem.PemReader.loadObject(Unknown Source)|?at org.bouncycastle.util.io.pem.PemReader.readPemObject(Unknown Source)|?at org.bouncycastle.openssl.PEMParser.readObject(Unknown Source)|?at com.normation.inventory.domain.PublicKey.$anonfun$publicKey$3(DataTypes.scala:110)|?at scalaz.zio.internal.FiberContext.nextInstr(FiberContext.scala:412)|?at scalaz.zio.internal.FiberContext.evaluateNow(FiberContext.scala:164)|?at scalaz.zio.internal.FiberContext.$anonfun$evaluateLater$1(FiberContext.scala:322)|?at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)|?at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)|?at java.lang.Thread.run(Thread.java:748)|Caused by: java.io.IOException: invalid characters encountered in base64 data|?at org.bouncycastle.util.encoders.Base64Encoder.decode(Unknown Source)|?... 11 more
    at scalaz.zio.Runtime.$anonfun$unsafeRun$1(Runtime.scala:45)
    at scalaz.zio.Exit.getOrElse(Exit.scala:31)
    at scalaz.zio.Exit.getOrElse$(Exit.scala:29)
    at scalaz.zio.Exit$Failure.getOrElse(Exit.scala:187)
    at scalaz.zio.Runtime.unsafeRun(Runtime.scala:45)
    at scalaz.zio.Runtime.unsafeRun$(Runtime.scala:44)
    at com.normation.zio$ZioRuntime$.unsafeRun(ZioCommons.scala:242)
    at com.normation.inventory.provisioning.endpoint.FusionReportEndpoint.parseInventory$1(FusionReportEndpoint.scala:133)
    at com.normation.inventory.provisioning.endpoint.FusionReportEndpoint.onSubmit(FusionReportEndpoint.scala:160)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

Associated revisions

Revision 38f490ab (diff)
Added by François ARMAND 6 months ago

Fixes #15034: DecoderException: unable to decode base64 string: invalid characters encountered in base64 data

History

#1

Updated by François ARMAND 6 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/2242
#2

Updated by François ARMAND 6 months ago

  • Status changed from Pending technical review to Pending release
#3

Updated by François ARMAND 5 months ago

  • Description updated (diff)
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
#4

Updated by Vincent MEMBRÉ 15 days ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.0.0~beta1 which was released today.

Also available in: Atom PDF