We are writing plugin and bundle. As part of security measure we are planning to sign the code. Issue that we are facing is we have successfully signed the plugin and bundle. When i am running this plugin and bundle those are running without any issue.
Now i have modified its content by updating one of the file in bundle and verified from terminal its giving below message
code or signature modified
but still its running without any issue. Now the question how can i make sure that code modified after signing it should fail to load ? i have read the documentation but no place this is explained. Who verifies code signature in client machine and stop loading if its fails verification.
Please advice
Related
We have a Cloud Service that we have been deploying/updating without issue. In the past two weeks every time we try to deploy the package we are getting the error "Deployment could not be created - There was an error processing your request. Try again in a few moments".
I am at a loss as to how to even debug the issue to get more detail. if anybody has any advice on how to get a better error description would be appreciated.
The only changes in this deployment are some changes to the static files in the package so it is unclear what is causing the issue. The process we use is (1) build the package, (2) upload the package, (3) deploy in the staging environment. The package gets uploaded but fails to deploy (step 3).
Any help as to what the issue is or how to get better diagnostic information woudl be great.
When uploading the wasm binary, as a compiled smart contract on the 'ink-workshop' - the canvas-ui that I am running just errors.
Canvas-ui error:
Uncaught error. Something went wrong with the query and rendering of this component.
Cannot read properties of undefined (reading 'args')
Step: 'Drag the flipper.contract file that contains the bundled wasm blob....'
The Github issues section associated is read-only, hence why I am posting here. Anyone know what might be the problem here?
Incase others are wondering what to do in this instance. I was able to deploy using the official polkadot web interface.
Connect your local running node via settings and there you can deploy your flipper contract.
This is a good article on the astar network docs on how to do it, using the basic flipper contract example.
There is a maintenance problem and they wanna fix it.
https://github.com/paritytech/canvas-ui/issues/119#issuecomment-1020114242
Because of this issue when I'm writing some new code and if there is error, I get confused if it is an actual error or is it because of this issue. So I have to build and run code again to confirm which I don't want to do again and again.
I'm trying to deploy an existing build with the "LabDefaultTemplate.11.xaml".
My problem is, that the build times out, as soon as I use an existing build. Here are the last steps including details and the timeout exception:
See http://i.stack.imgur.com/po1i6.png
I have two different servers. The first has TFS 2013 with Build Service, Controller and Agent installed on it. The second is thought to be used for Testing and has a Test-Controller and Agent on it (configured as a Standard-Environment in MS Test-Manager).
Build Service Account is a Domain-Admin
Build Connection to TFS goes with a TFS-Admin
Test Controller Service Login Account is a Local-Admin (mirrored on the Build-Server) and earlier tried with the Domain-Admin
Test Controller TFS-Connection also with a TFS-Admin
Test Controller Lab Service Account is not used, earlier also tried with the Domain-Admin
When I set the build to use the latest TFS-Build it runs into the timeout.
And when i set the path to use a Build from a specific location to the Build Directory on the Build-Server it all just works fine.
The difference between a working build and the timeout described above can be seen in this picture: http://i.stack.imgur.com/gPM07.png
Has anyone an idea where I'm struggling?
The problem was, that my previous builds only "partially succeeded" because they had some failing unit tests. The setting to use the only uses fully successful builds. So the latest build which was used had no drop folder configured.
I received no info about that, until I saw it in the logs. My fault was to never check, which build really is used as the latest.
I tried to deploy my project with capifony, becouse I found here an answer, that with capifony deployment is easy. Well I don't think it is, so my question is:
How can I deploy my project via ftp, I put all my files on the server but even if I browse to web/app.php, the only thing I get is an empty page, whatever route I write in the url. So someone please explain me how can I get this work! Thank you!
A couple of things to think of when deploying a Symfony2 project to a new server or computer (as far as I've encountered) might be:
Make sure that the server and it's PHP installation meets the Symfony2 requirements (and perhaps also the recommendations)
Check that you've somewhat followed the installation instructions (found here)
Try to clear the cache
Make sure that the web server and it's PHP process have write permissions to the cache folder
If none of these helps, try to modify the app_dev.php to temporarily allow access from your current (client) IP (instead of restraining it to localhost). Then, hopefully, you'll get a more useful and detailed error message, instead of the blank page (which often is caused by some fatal error that have occurred during the initialization of the framework and its kernel)
Update: Noticed now that you've tagged your question with 'windows', but that you don't mention which server you're trying to deploy to. I wrote the above with some *nix based server in mind, but hopefully some of it are applicable to Windows servers too (but there might be other common sources of error running under Windows that I'm not familliar with