geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevan Miller <kevan.mil...@gmail.com>
Subject Re: ERROR [AbstractEncryption] Unable to decrypt
Date Wed, 25 May 2011 04:38:39 GMT

On May 25, 2011, at 12:18 AM, michael.peterson wrote:

> Cool...here's the results: 
> 
> 
> mipeter2-mac:bin mipeter2$ ./geronimo.sh run 
> Using GERONIMO_HOME:   /Applications/geronimo-tomcat6-javaee5-2.2.1 
> Using GERONIMO_TMPDIR: var/temp 
> Using JRE_HOME: 
> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home 
> Booting Geronimo Kernel (in Java 1.6.0_24)... 
> Starting Geronimo Application Server v2.2.1 
> [*****                                   ]  13%   3s Starting 
> org.apache.ger...2011-05-24 21:18:02,985 ERROR 
> [PluginRepositoryDownloader] userRepositoryList: 
> /Applications/geronimo-tomcat6-javaee5-2.2.1/var/config/plugin-repositories.properties

> 2011-05-24 21:18:02,999 ERROR [PluginRepositoryDownloader] url: 
> http://localhost:8080/plugin/maven-repo/
> 2011-05-24 21:18:02,999 ERROR [PluginRepositoryDownloader] entry: 
> system={Simple}null 

OK. Great. How does that value compare with the actual contents of /Applications/geronimo-tomcat6-javaee5-2.2.1/var/config/plugin-repositories.properties?

The contents of that file should look like:

#List of known plugin repositories. Fomat:  <url>=<username>=<password>
#Thu Apr 28 14:41:55 EDT 2011
http\://localhost\:8080/plugin/maven-repo/=system\={Simple}rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHB1cgACW0Ks8xf4BghU4AIAAHhwAAAAEHnh03EmiNu4VTuWH+xZiRBwdAADQUVT
~/.m2/repository/=

I'm assuming it looks something like:
http\://localhost\:8080/plugin/maven-repo/=system\={Simple}null

If you change to be:
http\://localhost\:8080/plugin/maven-repo/=system\=manager

And start geronimo, what happens? I assume it works with no exception. Well, actually there
may be an exception. Because when we see the plain text password, we'll attempt to obfuscate/encode
the password using a {Simple} encode and rewrite the file with the obfuscated password. I
assume that this encode is failing and instead generating a "null".

--kevan


Mime
View raw message