While using the javax.crypto.* library in a Java application,I got the following error [1] ,[2]saying that "Can not initialize the cryptographic mechanism".

While inspecting the default policies got to know that permissions are already granted for all algorithms.

We also set those to unlimited in java code itself using the [3] and [4].

Still could not resolve the issue.Is there anything that we are missing out on?

kindly give some suggestions on it .

[1]java.lang.SecurityException: Can not initialize cryptographic mechanism

[2]java.lang.SecurityException: Can't read cryptographic policy directory: unlimited

[3] Security.setProperty("crypto.policy", "unlimited");

[4] System.setProperty("java.security.properties","unlimited");

Best ,

DIvya.

On Mon, Apr 10, 2023 at 6:49 PM Divya Sharma <divyasharma26546@gmail.com> wrote:

Thanks, Sebastian issue is resolved.

I want to run simple java code using java binary into bash shell. To achieve it I figured out some modification to the separate run script user_shell_dev.run from bash.run script .But those did not work load java vm in shell.
While booting in Qemu i got the error [1] ,[3] also i am able to spawn a shell into the terminal but while running java in it got [2].
It is not able to initialize the vm to run java.
Kindly suggest a way to achieve this .

[1][init -> java] Error occurred during initialization of VM
init -> java] java.lang.UnsatisfiedLinkError: no zip in java.library.path
[2]Error occurred during the initialization of vm.
Unable to load zip lib "zip.lib.so"

[3][init -> /bin/bash -> 1] Error: ROM-session creation failed (ram_quota=6144, cap_quota=3, label="zip.lib.so")

Thanks,
DIvya.

On Mon, Apr 10, 2023 at 3:52 PM Sebastian Sumpf <Sebastian.Sumpf@genode-labs.com> wrote:
Hello Divya,

On 4/8/23 07:45, Divya Sharma wrote:
> While running the java.run script I got the following error [1]showing out of
> memory allocation.
> Kindly suggest the way to remove it rather than build all the required
> dependencies and packages from scratch.
>
>
> [1]/usr/local/genode/tool/21.05/bin/../lib/gcc/arm-none-eabi/10.3.0/../../../../arm-none-eabi/bin/as: out of memory allocating 9223372036854841471 bytes after a total of 696320 bytes
>

This looks like as if it happens when linking the boot modules of the image
together. Maybe there are too many modules and something got too big? By the
size of the allocation clearly something did overflow, but it's hard to tell
without the actual scenario. What did you change in the "java.run" script?

Regards,

Sebastian

>
>
>
> On Wed, Apr 5, 2023 at 11:02 PM <ttcoder@netcourrier.com
> <mailto:ttcoder@netcourrier.com>> wrote:
>
>
>>
>> Hello Genodians,
>>
>> I am able to run java.run in virt_qemu-arm_v7a. The output is directed to
>> log [ stdout="/dev/log" ], is there a way to redirect the sdtout to
>> terminal [ stdout="/dev/terminal" ] instead of log?
>>
>>
>
> My two cents : the way I do it here is to modify the "config" scenario file
> this way:
> - keep stdout set to "/dev/log"
> - modify the routing to : <route> <service name="LOG"> <child
> name="terminal_log"> ...
> - add a terminal_log component
> - add a terminal component.
>
> It works for me... But if there is a way to specify stdout="/dev/terminal"
> instead, that might be of interest to me as well.
>
> Cedric
>
>
> _______________________________________________
> Genode users mailing list
> users@lists.genode.org <mailto:users@lists.genode.org>
> https://lists.genode.org/listinfo/users
> <https://lists.genode.org/listinfo/users>
>
>
> _______________________________________________
> Genode users mailing list
> users@lists.genode.org
> https://lists.genode.org/listinfo/users

--
Sebastian Sumpf
Genode Labs

http://www.genode-labs.com · http://genode.org

Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden
Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

_______________________________________________
Genode users mailing list
users@lists.genode.org
https://lists.genode.org/listinfo/users