Cyberduck Mountain Duck CLI

#9068 closed defect (fixed)

Registration key not valid

Reported by: anguo Owned by: dkocher
Priority: high Milestone: 4.8
Component: core Version: 4.7.3
Severity: normal Keywords: registration, donation, key
Cc: Architecture:
Platform: Windows 10

Description

Hi there, I just donated, and received my key. It still has the correct extension, and opens without a problem. However, no change has appeared on the application. When I mouse over "Help" I can see a message saying "Not a valid registration key". What can I do to fix this?

Thanks in advance

Change History (6)

comment:1 Changed on Oct 26, 2015 at 10:34:38 AM by Gordack

I have the same problem .cyberducklicense doesn't work. Windows 10 x64 Cyberduck 4.7.3

Here is the cyberduck.log

2015-10-26 11:35:26,954 [background-1] ERROR ch.cyberduck.core.ssl.CustomTrustSSLProtocolSocketFactory - Failure NativePRNG SecureRandom not available obtaining secure random NativePRNG
2015-10-26 11:35:48,279 [background-1] ERROR ch.cyberduck.core.ssl.CustomTrustSSLProtocolSocketFactory - Failure NativePRNG SecureRandom not available obtaining secure random NativePRNG
2015-10-26 11:40:57,551 [background-1] ERROR ch.cyberduck.core.ssl.CustomTrustSSLProtocolSocketFactory - Failure NativePRNG SecureRandom not available obtaining secure random NativePRNG
2015-10-26 11:44:44,205 [background-1] ERROR ch.cyberduck.core.ssl.CustomTrustSSLProtocolSocketFactory - Failure NativePRNG SecureRandom not available obtaining secure random NativePRNG
2015-10-26 11:45:43,174 [background-1] ERROR ch.cyberduck.core.ssl.CustomTrustSSLProtocolSocketFactory - Failure NativePRNG SecureRandom not available obtaining secure random NativePRNG
2015-10-26 11:46:32,138 [background-1] ERROR ch.cyberduck.core.ssl.CustomTrustSSLProtocolSocketFactory - Failure NativePRNG SecureRandom not available obtaining secure random NativePRNG
2015-10-26 11:53:48,744 [background-1] ERROR ch.cyberduck.core.ssl.CustomTrustSSLProtocolSocketFactory - Failure NativePRNG SecureRandom not available obtaining secure random NativePRNG
2015-10-26 12:02:48,058 [background-1] ERROR ch.cyberduck.core.ssl.CustomTrustSSLProtocolSocketFactory - Failure NativePRNG SecureRandom not available obtaining secure random NativePRNG
2015-10-26 12:05:29,573 [background-1] ERROR ch.cyberduck.core.ssl.CustomTrustSSLProtocolSocketFactory - Failure NativePRNG SecureRandom not available obtaining secure random NativePRNG
2015-10-26 12:05:42,171 [background-1] ERROR ch.cyberduck.core.ssl.CustomTrustSSLProtocolSocketFactory - Failure NativePRNG SecureRandom not available obtaining secure random NativePRNG
2015-10-26 12:09:30,494 [background-1] ERROR ch.cyberduck.core.ssl.CustomTrustSSLProtocolSocketFactory - Failure NativePRNG SecureRandom not available obtaining secure random NativePRNG
2015-10-26 12:10:39,791 [background-1] ERROR ch.cyberduck.core.ssl.CustomTrustSSLProtocolSocketFactory - Failure NativePRNG SecureRandom not available obtaining secure random NativePRNG
2015-10-26 12:19:15,662 [background-1] ERROR ch.cyberduck.core.ssl.CustomTrustSSLProtocolSocketFactory - Failure NativePRNG SecureRandom not available obtaining secure random NativePRNG
Last edited on Oct 26, 2015 at 10:46:04 AM by Gordack (previous) (diff)

comment:2 Changed on Oct 26, 2015 at 10:52:33 AM by dkocher

  • Owner set to dkocher
  • Priority changed from normal to high
  • Status changed from new to assigned
  • Summary changed from Registration key not valid? to Registration key not valid

comment:3 Changed on Oct 26, 2015 at 10:53:11 AM by dkocher

#9071 closed as duplicate.

comment:4 Changed on Oct 26, 2015 at 10:53:35 AM by dkocher

#9067 closed as duplicate.

comment:5 Changed on Oct 26, 2015 at 11:56:05 AM by Gordack

How did you solve this problem ?

comment:6 Changed on Oct 26, 2015 at 12:37:58 PM by dkocher

  • Milestone set to 4.8
  • Resolution set to fixed
  • Status changed from assigned to closed

In r18407. We will issue a hotfix update.

Note: See TracTickets for help on using tickets.