Comment 10 by Deleted This is quite problematic, I hope this is a bug to be fixed. Comment 10 Deleted. Comment 11 by soccerdu I haven't heard anything. Is there a way to re-flag this?
- instalar windows desde pendrive mac;
- ‘This type of file can harm your computer’ Chrome alert [FIX].
- windows 8 wifi mac changer;
- sonic academy ana synth mac.
- Why Does Chrome Say PDF Files Can Harm Your Computer?.
- penna usb non rilevata mac.
Comment 11 Deleted. Comment 12 by ipar Yes, a flag to let the user choose what they want would be a great option. I searched for it but i didn't found anything. Comment 12 Deleted. Comment 13 by Deleted So here is a workaround I wrote: Comment 13 Deleted.
Comment 14 by rui. This was a "recent" fix: Comment 14 Deleted.
PDF Security Has Improved
Comment 15 by goo A site whitelist should be provided to allow auto start. Comment 15 Deleted. Comment 16 by ajha chromium. Comment 16 Deleted.trucimtozungde.ml/paginas-web-para-conocer-gente-de-otros-paises.php
Working around the Google Chrome "This type of file can harm your computer" problem
Comment 17 by casp It would be nice if browser vendors stop deciding for users what is or is not safe. If a user is so inexperienced that they foolishly decide to open something they should not have, that becomes their problem. Hopefully they have a good virus scanner installed. So in the latest production version as of today , Is Google considering this a bug or expected behavior??? If this is expected behavior, I would like to know how to formally submit an enhancement request to get this behavior changes ASAP. Comment 17 Deleted. Comment 18 by martin On an air-gapped system with no internet connectivity at all.
I wish the developers would get their head around the fact that not everyone needs protection from hack. You should never remove the users ability to make the software do what they need - I am in the best position to decide what my security posture looks like and what functionality I need. Maybe you should just fork the project for Enterprise users and give us more granular options for our individual needs. Comment 18 Deleted. Comment 19 by reich. We also need to have the possibility to autostart JNLP files!
FireFox and IE have no problem with this: Comment 19 Deleted. Comment 20 by sergio. Propongo anche io almeno una whitelist che permetta l'autostart! Comment 20 Deleted. Comment 21 by quelr WTF, Google?! Impossible to use Chrome in business environment anymore as Java is still used everywhere! Comment 21 Deleted.
Comment 22 by pacu Since javaws already has a "Do you really want to run this" dialog, with code-signing support so the user can verify the creator of the program before running it, I can't imagine what threat scenario Google is thinking of in which their devoid-of-useful-information "harm your computer" warning is actually helping anybody. Comment 22 Deleted.
'This type of file can harm your computer. Do you want to keep - Microsoft Community
Comment 23 by kamikaz Today, with Google Chrome There is a small chance to revert this? Comment 23 Deleted. Comment 24 by gabboba This is so anoying, it was working and suddenly it's not working anymore: Comment 24 Deleted. Comment 25 by casp Here's a new twist to this issue. So remind me again why people want to use Chrome??? Google, you're falling down on the job. It's bad enough you refuse to support plug-in, but enough is enough - you can't take over the world.
Comment 25 Deleted. Comment 26 by jmig Same problem here: We need to autolaunch jnlp signed applications and now we can't. I'd admit a highly secure default behaviour but So sad. Comment 26 Deleted. Comment 27 by asanka chromium. Comment 27 Deleted. Comment 28 by gon JNLP file do not endangers chrome, it run in it's own sandbox,why mark it dangerous?
Comment 28 Deleted. Comment 29 by koenraad I would like to discus jnlp auto open options. My goal is to get options to enable this in my favorite browser. Java files are not runnable by themselves, but need a Java installation on the client, which makes the possibility of accidental running a lot smaller. The sources used by a jnlp file in order to run all have to be signed with a valid certificate and only run when the java installation is the current release.
After a local save the current situation of the jnlp, users tend to use only the local jnlp instead of a modified version on the server. The prefered way to distribute an application is through a browser these days. Options I can think of right now: Comment 29 Deleted. Comment 30 by phistuck chromium. Comment 30 Deleted. Comment 31 by rui. Yes, perhaps closing this is the right option. We can definitely cut all the rambles about Chrome and Java from documentation and just say "move on to other browser".
Comment 31 Deleted. Comment 32 by pacu Is Java Web Start code signing insufficient? Or are you just trying to kill Java because you don't like it? Comment 32 Deleted. Comment 33 by rdsmith chromium. Asanka's the right person to decide what to do with this, not me. Comment 33 Deleted. Comment 34 by jmig After more than 5 months since I add a request for this issue I'm sadly surprised about the slowness with it. I think there is no real reason to flag java jvm classes, to be precise code as insecure nowadays.
Ever more: In my opinion, there is no reason to forbid users choose what they need. I can understand a extremely secure default behaviour but this is far to be reasonable. In my case: Now I'll need ask them to use Firefox and loss some nice features. I'm really disapointed to feel I have to do it because political reasons, not technical.
Comment 34 Deleted. Comment 35 by casp Any chance of getting some attention on this issue? Comment 35 Deleted. Comment 36 by gad. Can this be related to the big legal fight between Google and Oracle over Java??? Comment 36 Deleted. Comment 37 by jsivagt This bug is further compounded by bug After JNLP files, the st one gives a problem - because Chrome has a limit of files of the same name.
So in a month's time - they can no longer run this because the file limit is exhausted. And our users are non-technical - who won't even be able to find the download directory and delete files. We aren't left with any other option now other than blocking Chrome for our application and asking the users to use Firefox or IE.
Comment 37 Deleted. Comment 38 by jonweis We too have to block Chrome from being used until this issue is resolved. It is disappointing to see it being ignored as this is a common use case in my industry biotech. Comment 38 Deleted. Comment 39 by gladi Apparently its time to use Firefox for this. Comment 39 Deleted. Comment 40 by massimo I'm working with many Java Web Start application too, i'm really interested for a solution. Comment 40 Deleted. Comment 41 by casp Any estimate as to when someone might be able to look into fixing this?
Comment 41 Deleted. Comment 42 by t Yes this needs to be addressed, at the very least with some sort of whitelisting ability on items from certain domains. Comment 42 Deleted. Comment 43 by whelan. We need this fixed. Comment 43 Deleted. Comment 44 by whelan. Comment 44 Deleted. Comment 45 by anderson We need this fixed too. Comment 45 Deleted. Comment 46 by huy Comment 46 Deleted. Comment 47 by alain. What was it again? I'm a bit late it would seem. Comment 47 Deleted. Comment 48 by rdsmith chromium. Comment 48 Deleted. Comment 49 by casp Any chance of getting this on the radar soon?
Comment 49 Deleted.
Comment 50 by gad. Just wanted to let you all know of a workaround for this which worked for me. It appears that the url schemes jnlp: This means that instead of downloading the jnlp file through the browser, the download can be handled by Java webstart itself. This produces a much more elegant user experience without the annoying warning messages. Hope this helps. Comment 50 Deleted. Comment 51 by rui.
Comment 51 Deleted. Comment 52 by evan. Back Up. Covert Ops. Internet Tools. Office and Finance. System Tools. Web Development. News Archive. Subscribe to our mailing list. Smart Defrag. IObit Unlocker. Windows 10 System Tweaks. Microsoft Autoruns. Wise Disk Cleaner. Working around the Google Chrome "This type of file can harm your computer" problem.
Related this type of file can harm your computer mac
Copyright 2019 - All Right Reserved