You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Mikhail Loenko (JIRA)" <ji...@apache.org> on 2007/03/12 11:55:09 UTC
[jira] Created: (HARMONY-3363) [DRLVM] contribution of alternative
bytecode verifier
[DRLVM] contribution of alternative bytecode verifier
-----------------------------------------------------
Key: HARMONY-3363
URL: https://issues.apache.org/jira/browse/HARMONY-3363
Project: Harmony
Issue Type: New Feature
Components: Contributions
Reporter: Mikhail Loenko
This is contribution of experimental bytecode verifier on behalf of Intel.
"Experimental" means that there is no formal proof currently available of its equivalence to the step-by-step verification algorithm described in the spec.
The only known difference to the conventional verifier is dead code verification: RI makes stricter checks against dead code.
Since it's about dead code, this difference does not affect vulnerability
Comparing to the current Harmony verifier, this one is supposed to be complete (Harmony currently does not support jsr/ret verification) and much faster
So, I'm attaching 3 files:
The first one: Verifier_bulk.zip is a bulk contribution on behalf of Intel for archiving purposes. It contains the legal files as well
The second one: Verifier_patch is my fix to the bugs that I found while the first archive was coming thru legal
The third archive Verifier_patched.zip is a merge for previous two. It's an up-to-date version for all the engineering purposes
To try it out one should replace the current 'verifier' directory in vm with the new one and rebuild
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HARMONY-3363) [DRLVM] contribution of alternative
bytecode verifier
Posted by "Mikhail Loenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Loenko resolved HARMONY-3363.
-------------------------------------
Resolution: Fixed
verifier was integrated at r556523
switched as default at r556809
documentation was integrated at r557193
testing is OK so far
> [DRLVM] contribution of alternative bytecode verifier
> -----------------------------------------------------
>
> Key: HARMONY-3363
> URL: https://issues.apache.org/jira/browse/HARMONY-3363
> Project: Harmony
> Issue Type: New Feature
> Components: Contributions
> Reporter: Mikhail Loenko
> Assignee: Mikhail Loenko
> Attachments: cp-verifier.htm, Verifier_bulk.zip, Verifier_patch, Verifier_patched.zip, Verifier_patched2.zip
>
>
> This is contribution of experimental bytecode verifier on behalf of Intel.
> "Experimental" means that there is no formal proof currently available of its equivalence to the step-by-step verification algorithm described in the spec.
> The only known difference to the conventional verifier is dead code verification: RI makes stricter checks against dead code.
> Since it's about dead code, this difference does not affect vulnerability
> Comparing to the current Harmony verifier, this one is supposed to be complete (Harmony currently does not support jsr/ret verification) and much faster
> So, I'm attaching 3 files:
> The first one: Verifier_bulk.zip is a bulk contribution on behalf of Intel for archiving purposes. It contains the legal files as well
> The second one: Verifier_patch is my fix to the bugs that I found while the first archive was coming thru legal
> The third archive Verifier_patched.zip is a merge for previous two. It's an up-to-date version for all the engineering purposes
> To try it out one should replace the current 'verifier' directory in vm with the new one and rebuild
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-3363) [DRLVM] contribution of alternative
bytecode verifier
Posted by "Mikhail Loenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Loenko updated HARMONY-3363:
------------------------------------
Attachment: Verifier_patch
> [DRLVM] contribution of alternative bytecode verifier
> -----------------------------------------------------
>
> Key: HARMONY-3363
> URL: https://issues.apache.org/jira/browse/HARMONY-3363
> Project: Harmony
> Issue Type: New Feature
> Components: Contributions
> Reporter: Mikhail Loenko
> Attachments: Verifier_bulk.zip, Verifier_patch, Verifier_patched.zip
>
>
> This is contribution of experimental bytecode verifier on behalf of Intel.
> "Experimental" means that there is no formal proof currently available of its equivalence to the step-by-step verification algorithm described in the spec.
> The only known difference to the conventional verifier is dead code verification: RI makes stricter checks against dead code.
> Since it's about dead code, this difference does not affect vulnerability
> Comparing to the current Harmony verifier, this one is supposed to be complete (Harmony currently does not support jsr/ret verification) and much faster
> So, I'm attaching 3 files:
> The first one: Verifier_bulk.zip is a bulk contribution on behalf of Intel for archiving purposes. It contains the legal files as well
> The second one: Verifier_patch is my fix to the bugs that I found while the first archive was coming thru legal
> The third archive Verifier_patched.zip is a merge for previous two. It's an up-to-date version for all the engineering purposes
> To try it out one should replace the current 'verifier' directory in vm with the new one and rebuild
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-3363) [DRLVM] contribution of alternative
bytecode verifier
Posted by "Mikhail Loenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Loenko updated HARMONY-3363:
------------------------------------
Attachment: Verifier_patched.zip
> [DRLVM] contribution of alternative bytecode verifier
> -----------------------------------------------------
>
> Key: HARMONY-3363
> URL: https://issues.apache.org/jira/browse/HARMONY-3363
> Project: Harmony
> Issue Type: New Feature
> Components: Contributions
> Reporter: Mikhail Loenko
> Attachments: Verifier_bulk.zip, Verifier_patch, Verifier_patched.zip
>
>
> This is contribution of experimental bytecode verifier on behalf of Intel.
> "Experimental" means that there is no formal proof currently available of its equivalence to the step-by-step verification algorithm described in the spec.
> The only known difference to the conventional verifier is dead code verification: RI makes stricter checks against dead code.
> Since it's about dead code, this difference does not affect vulnerability
> Comparing to the current Harmony verifier, this one is supposed to be complete (Harmony currently does not support jsr/ret verification) and much faster
> So, I'm attaching 3 files:
> The first one: Verifier_bulk.zip is a bulk contribution on behalf of Intel for archiving purposes. It contains the legal files as well
> The second one: Verifier_patch is my fix to the bugs that I found while the first archive was coming thru legal
> The third archive Verifier_patched.zip is a merge for previous two. It's an up-to-date version for all the engineering purposes
> To try it out one should replace the current 'verifier' directory in vm with the new one and rebuild
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-3363) [DRLVM] contribution of alternative
bytecode verifier
Posted by "Mikhail Loenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Loenko updated HARMONY-3363:
------------------------------------
Attachment: Verifier_bulk.zip
> [DRLVM] contribution of alternative bytecode verifier
> -----------------------------------------------------
>
> Key: HARMONY-3363
> URL: https://issues.apache.org/jira/browse/HARMONY-3363
> Project: Harmony
> Issue Type: New Feature
> Components: Contributions
> Reporter: Mikhail Loenko
> Attachments: Verifier_bulk.zip, Verifier_patch, Verifier_patched.zip
>
>
> This is contribution of experimental bytecode verifier on behalf of Intel.
> "Experimental" means that there is no formal proof currently available of its equivalence to the step-by-step verification algorithm described in the spec.
> The only known difference to the conventional verifier is dead code verification: RI makes stricter checks against dead code.
> Since it's about dead code, this difference does not affect vulnerability
> Comparing to the current Harmony verifier, this one is supposed to be complete (Harmony currently does not support jsr/ret verification) and much faster
> So, I'm attaching 3 files:
> The first one: Verifier_bulk.zip is a bulk contribution on behalf of Intel for archiving purposes. It contains the legal files as well
> The second one: Verifier_patch is my fix to the bugs that I found while the first archive was coming thru legal
> The third archive Verifier_patched.zip is a merge for previous two. It's an up-to-date version for all the engineering purposes
> To try it out one should replace the current 'verifier' directory in vm with the new one and rebuild
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (HARMONY-3363) [DRLVM] contribution of alternative
bytecode verifier
Posted by "Mikhail Loenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Loenko closed HARMONY-3363.
-----------------------------------
> [DRLVM] contribution of alternative bytecode verifier
> -----------------------------------------------------
>
> Key: HARMONY-3363
> URL: https://issues.apache.org/jira/browse/HARMONY-3363
> Project: Harmony
> Issue Type: New Feature
> Components: Contributions
> Reporter: Mikhail Loenko
> Assignee: Mikhail Loenko
> Attachments: cp-verifier.htm, Verifier_bulk.zip, Verifier_patch, Verifier_patched.zip, Verifier_patched2.zip
>
>
> This is contribution of experimental bytecode verifier on behalf of Intel.
> "Experimental" means that there is no formal proof currently available of its equivalence to the step-by-step verification algorithm described in the spec.
> The only known difference to the conventional verifier is dead code verification: RI makes stricter checks against dead code.
> Since it's about dead code, this difference does not affect vulnerability
> Comparing to the current Harmony verifier, this one is supposed to be complete (Harmony currently does not support jsr/ret verification) and much faster
> So, I'm attaching 3 files:
> The first one: Verifier_bulk.zip is a bulk contribution on behalf of Intel for archiving purposes. It contains the legal files as well
> The second one: Verifier_patch is my fix to the bugs that I found while the first archive was coming thru legal
> The third archive Verifier_patched.zip is a merge for previous two. It's an up-to-date version for all the engineering purposes
> To try it out one should replace the current 'verifier' directory in vm with the new one and rebuild
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HARMONY-3363) [DRLVM] contribution of alternative
bytecode verifier
Posted by "Mikhail Loenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Loenko reassigned HARMONY-3363:
---------------------------------------
Assignee: Mikhail Loenko
> [DRLVM] contribution of alternative bytecode verifier
> -----------------------------------------------------
>
> Key: HARMONY-3363
> URL: https://issues.apache.org/jira/browse/HARMONY-3363
> Project: Harmony
> Issue Type: New Feature
> Components: Contributions
> Reporter: Mikhail Loenko
> Assignee: Mikhail Loenko
> Attachments: cp-verifier.htm, Verifier_bulk.zip, Verifier_patch, Verifier_patched.zip, Verifier_patched2.zip
>
>
> This is contribution of experimental bytecode verifier on behalf of Intel.
> "Experimental" means that there is no formal proof currently available of its equivalence to the step-by-step verification algorithm described in the spec.
> The only known difference to the conventional verifier is dead code verification: RI makes stricter checks against dead code.
> Since it's about dead code, this difference does not affect vulnerability
> Comparing to the current Harmony verifier, this one is supposed to be complete (Harmony currently does not support jsr/ret verification) and much faster
> So, I'm attaching 3 files:
> The first one: Verifier_bulk.zip is a bulk contribution on behalf of Intel for archiving purposes. It contains the legal files as well
> The second one: Verifier_patch is my fix to the bugs that I found while the first archive was coming thru legal
> The third archive Verifier_patched.zip is a merge for previous two. It's an up-to-date version for all the engineering purposes
> To try it out one should replace the current 'verifier' directory in vm with the new one and rebuild
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-3363) [DRLVM] contribution of alternative
bytecode verifier
Posted by "Mikhail Loenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Loenko updated HARMONY-3363:
------------------------------------
Attachment: cp-verifier.htm
attached a document describing the approach in details
put site.css that we use for the website into the same dir as this document
> [DRLVM] contribution of alternative bytecode verifier
> -----------------------------------------------------
>
> Key: HARMONY-3363
> URL: https://issues.apache.org/jira/browse/HARMONY-3363
> Project: Harmony
> Issue Type: New Feature
> Components: Contributions
> Reporter: Mikhail Loenko
> Attachments: cp-verifier.htm, Verifier_bulk.zip, Verifier_patch, Verifier_patched.zip
>
>
> This is contribution of experimental bytecode verifier on behalf of Intel.
> "Experimental" means that there is no formal proof currently available of its equivalence to the step-by-step verification algorithm described in the spec.
> The only known difference to the conventional verifier is dead code verification: RI makes stricter checks against dead code.
> Since it's about dead code, this difference does not affect vulnerability
> Comparing to the current Harmony verifier, this one is supposed to be complete (Harmony currently does not support jsr/ret verification) and much faster
> So, I'm attaching 3 files:
> The first one: Verifier_bulk.zip is a bulk contribution on behalf of Intel for archiving purposes. It contains the legal files as well
> The second one: Verifier_patch is my fix to the bugs that I found while the first archive was coming thru legal
> The third archive Verifier_patched.zip is a merge for previous two. It's an up-to-date version for all the engineering purposes
> To try it out one should replace the current 'verifier' directory in vm with the new one and rebuild
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HARMONY-3363) [DRLVM] contribution of
alternative bytecode verifier
Posted by "Mikhail Loenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512871 ]
Mikhail Loenko commented on HARMONY-3363:
-----------------------------------------
committed at r556523
not yet switched as default
> [DRLVM] contribution of alternative bytecode verifier
> -----------------------------------------------------
>
> Key: HARMONY-3363
> URL: https://issues.apache.org/jira/browse/HARMONY-3363
> Project: Harmony
> Issue Type: New Feature
> Components: Contributions
> Reporter: Mikhail Loenko
> Assignee: Mikhail Loenko
> Attachments: cp-verifier.htm, Verifier_bulk.zip, Verifier_patch, Verifier_patched.zip, Verifier_patched2.zip
>
>
> This is contribution of experimental bytecode verifier on behalf of Intel.
> "Experimental" means that there is no formal proof currently available of its equivalence to the step-by-step verification algorithm described in the spec.
> The only known difference to the conventional verifier is dead code verification: RI makes stricter checks against dead code.
> Since it's about dead code, this difference does not affect vulnerability
> Comparing to the current Harmony verifier, this one is supposed to be complete (Harmony currently does not support jsr/ret verification) and much faster
> So, I'm attaching 3 files:
> The first one: Verifier_bulk.zip is a bulk contribution on behalf of Intel for archiving purposes. It contains the legal files as well
> The second one: Verifier_patch is my fix to the bugs that I found while the first archive was coming thru legal
> The third archive Verifier_patched.zip is a merge for previous two. It's an up-to-date version for all the engineering purposes
> To try it out one should replace the current 'verifier' directory in vm with the new one and rebuild
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HARMONY-3363) [DRLVM] contribution of
alternative bytecode verifier
Posted by "Mikhail Loenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501144 ]
Mikhail Loenko commented on HARMONY-3363:
-----------------------------------------
vote passed
> [DRLVM] contribution of alternative bytecode verifier
> -----------------------------------------------------
>
> Key: HARMONY-3363
> URL: https://issues.apache.org/jira/browse/HARMONY-3363
> Project: Harmony
> Issue Type: New Feature
> Components: Contributions
> Reporter: Mikhail Loenko
> Attachments: cp-verifier.htm, Verifier_bulk.zip, Verifier_patch, Verifier_patched.zip
>
>
> This is contribution of experimental bytecode verifier on behalf of Intel.
> "Experimental" means that there is no formal proof currently available of its equivalence to the step-by-step verification algorithm described in the spec.
> The only known difference to the conventional verifier is dead code verification: RI makes stricter checks against dead code.
> Since it's about dead code, this difference does not affect vulnerability
> Comparing to the current Harmony verifier, this one is supposed to be complete (Harmony currently does not support jsr/ret verification) and much faster
> So, I'm attaching 3 files:
> The first one: Verifier_bulk.zip is a bulk contribution on behalf of Intel for archiving purposes. It contains the legal files as well
> The second one: Verifier_patch is my fix to the bugs that I found while the first archive was coming thru legal
> The third archive Verifier_patched.zip is a merge for previous two. It's an up-to-date version for all the engineering purposes
> To try it out one should replace the current 'verifier' directory in vm with the new one and rebuild
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-3363) [DRLVM] contribution of alternative
bytecode verifier
Posted by "Mikhail Loenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Loenko updated HARMONY-3363:
------------------------------------
Attachment: Verifier_patched2.zip
Verifier_patched2.zip -- interfaces updated according to current state of SVN
> [DRLVM] contribution of alternative bytecode verifier
> -----------------------------------------------------
>
> Key: HARMONY-3363
> URL: https://issues.apache.org/jira/browse/HARMONY-3363
> Project: Harmony
> Issue Type: New Feature
> Components: Contributions
> Reporter: Mikhail Loenko
> Attachments: cp-verifier.htm, Verifier_bulk.zip, Verifier_patch, Verifier_patched.zip, Verifier_patched2.zip
>
>
> This is contribution of experimental bytecode verifier on behalf of Intel.
> "Experimental" means that there is no formal proof currently available of its equivalence to the step-by-step verification algorithm described in the spec.
> The only known difference to the conventional verifier is dead code verification: RI makes stricter checks against dead code.
> Since it's about dead code, this difference does not affect vulnerability
> Comparing to the current Harmony verifier, this one is supposed to be complete (Harmony currently does not support jsr/ret verification) and much faster
> So, I'm attaching 3 files:
> The first one: Verifier_bulk.zip is a bulk contribution on behalf of Intel for archiving purposes. It contains the legal files as well
> The second one: Verifier_patch is my fix to the bugs that I found while the first archive was coming thru legal
> The third archive Verifier_patched.zip is a merge for previous two. It's an up-to-date version for all the engineering purposes
> To try it out one should replace the current 'verifier' directory in vm with the new one and rebuild
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.