dirty
hack -- they depend on internal format used by SharedResources and are doing
a guesswork as to what is FQN and what is not. But at least modifications
there are possible and are minor (not likely to break something else).
--
View this message in context:
http://old.nabble.com
with whatever you like more.
>
--
View this message in context:
http://old.nabble.com/How-to-encrypt-obfuscate-resource-reference--tp27744679p27757852.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsu
dMap.put(encrypted, str);
return encrypted;
}
/**
* Decrypts string.
*/
public static String decrypt(String encrypted)
{
String str = toUnencryptedMap.get(encrypted);
if (str != null)
return str;
str = encryptor.decryp
part of ResourceReference (and possibly something else too).
>> How would I scan for that?
>>
>>
>> Martijn Dashorst wrote:
>>>
>>> Create a unit test case that scans your application for resources and
>>> c
d applying
> your specific logic.
>
--
View this message in context:
http://old.nabble.com/How-to-encrypt-obfuscate-resource-reference--tp27744679p27756016.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
at?
>
>
> Martijn Dashorst wrote:
>>
>> Create a unit test case that scans your application for resources and
>> checks if the class is set. If not, fail. If set, check if it is
>> unique, if not fail.
>>
>> Martijn
>>
>
> --
> View this me
a unit test case that scans your application for resources and
> checks if the class is set. If not, fail. If set, check if it is
> unique, if not fail.
>
> Martijn
>
--
View this message in context:
http://old.nabble.com/How-to-encrypt-obfuscate-resource-reference--tp27744679p277
en introduced that when set will throw an error when an
>> fqn would be used. It will be in 1.4.7, which is currently in the
>> voting phase, so it will be available within a week.
>>
>> But this would mean you'd have to alias all the classes anyway.
>>
>
&g
View this message in context:
http://old.nabble.com/How-to-encrypt-obfuscate-resource-reference--tp27744679p27754862.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicke
he issue, maybe I can just wait it out.
>
>
> bgooren wrote:
>>
>> So I had a quick look at the source code of WebRequestCodingStrategy, and
>> I think it should be possible to create a solution for your problem quite
>> easily:
>>
>
> --
> Vi
had a quick look at the source code of WebRequestCodingStrategy, and
> I think it should be possible to create a solution for your problem quite
> easily:
>
--
View this message in context:
http://old.nabble.com/How-to-encrypt-obfuscate-resource-reference--tp27744679p27754796.html
Sent
cket/SharedResources.html#putClassAlias(java.lang.Class,
>> java.lang.String) class aliases .
>>
>> The upside is that you control the generated URL, the downside is that
>> you have to make sure the alias is u
gt;>
>> The easiest way around this is to specify
>> http://wicket.apache.org/docs/1.4/org/apache/wicket/SharedResources.html#putClassAlias(java.lang.Class,
>> java.lang.String) class aliases .
>>
>> The upside is that you control the generated URL, the downside is tha
/org/apache/wicket/SharedResources.html#putClassAlias(java.lang.Class,
> java.lang.String) class aliases .
>
> The upside is that you control the generated URL, the downside is that you
> have to make sure the alias is unique.
>
--
View this message in context:
http://old.nabble.com
licies we are not allowed to
> expose internal application details -- and fully qualified class name
> certainly fits that category.
--
View this message in context:
http://old.nabble.com/How-to-encrypt-obfuscate-resource-reference--tp27744679p27748507.html
Sent from the Wicke
09560.html
>>
>
> --
> View this message in context:
> http://old.nabble.com/How-to-encrypt-obfuscate-resource-reference--tp27744679p27745911.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -
URLs-are-not-encrypted-(bug-).-td27209560.html
>
--
View this message in context:
http://old.nabble.com/How-to-encrypt-obfuscate-resource-reference--tp27744679p27745911.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---
for a discussion and suggestion see
http://old.nabble.com/CryptedUrlWebRequestCodingStrategy-%2B-WebRequestCodingStrategy-%3D-resource-URLs-are-not-encrypted-(bug-).-td27209560.html
quote "I was able to get around this by subclassing WebRequestCodingStrategy and
overriding methods:
addResourcePar
Hi,
out of the box Wicket generates urls for packaged resources that
contain fully-qualified class names, e.g.:
Now in accordance with our security policies we are not allowed to
expose internal application details -- and fully qualified class name
certainly fits that category.
On the other han
19 matches
Mail list logo
