This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

[5.013] Downloaded Certficates are corrupt

Hi,

i've a big problem. After the up2date to 5.013 the certficates downloaded from the Astaro are corrupt. I just had a call from a customer who called me a few minutes ago, he found this BUG. I tried it and experienced the same problem on our astaro. The customer has to go to Frankfurt tomorrow and wants to set up a new Sentinel connection which is not possible now!

Has anybody the same problem? Please give me feedback.

Thanks and regards,

Mario Techel

This thread was automatically locked due to age.

Parents

0 ido over 21 years ago

Hi,

I experienced the same and using a nice HEX-editor to review the file in comparism with an old one I exported with 5.012 I learned that into the file there is HTML-code included!

Yes, you are right: HTML-Code!!!

Is there any possibility to export certificates within an SSH-session?

ido
Cancel
Vote Up 0 Vote Down

Cancel
0 Stephan_Scholz over 21 years ago in reply to ido

Confirmed. Thank you for reporting this bug. It will be fixed as soon as possible.

Regards,
Stephan
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Stephan_Scholz over 21 years ago in reply to ido

Confirmed. Thank you for reporting this bug. It will be fixed as soon as possible.

Regards,
Stephan
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 JonathanCraft over 21 years ago in reply to Stephan_Scholz

We have had the same problem here, in fact we have had nothing but trouble with ASL5 would love to upgrade our ASL4 box to 5 but at the moment there appears to be too many bugs.

Any ideas when the VPN bugs will be ironed out.

Jonathan
Cancel
Vote Up 0 Vote Down

Cancel
0 KSeemann over 21 years ago in reply to Stephan_Scholz

Now that was FAST!

just installed the V5.014 and downloaded the WebAdmin Certificate and it is even smaller then my "hacked" one...

Mine included 3 Lines more than needed (the "Expires...", "Date..." and "Content-Type..." Lines)... but it worked... [;)]
Cancel
Vote Up 0 Vote Down

Cancel
0 Stephan_Scholz over 21 years ago in reply to Stephan_Scholz

This issue is fixed in 5.014.

Regards,
Stephan
Cancel
Vote Up 0 Vote Down

Cancel