DEV Community

Cover image for Google Chrome enables file system API ... Super Cool ๐Ÿ˜
Sharad Raj (He/Him)
Sharad Raj (He/Him)

Posted on

Google Chrome enables file system API ... Super Cool ๐Ÿ˜

A new release of Google Chrome enables Native File System API so the developers can build web apps that interact with files on the userโ€™s local device.

How will you use it ? ๐Ÿ™‚

Latest comments (35)

Collapse
 
cawoodm profile image
Marc

TiddlyWiki

Collapse
 
adam_cyclones profile image
Adam Crockett ๐ŸŒ€ • Edited

Heres a diagram of Chromes new FootGun API

A diagram of the File System API

Collapse
 
alaindet profile image
Alain D'Ettorre
  • Cool: web apps take a step forward towards native
  • NOT cool: possibility of stealing data increases massively
Collapse
 
blindfish3 profile image
Ben Calder

Yet another reason to never install Chrome. I imagine many security conscious businesses who currently use it will be having serious conversations about removing it from their networks.

Collapse
 
sharadcodes profile image
Sharad Raj (He/Him)

Well it will eventually be in the chromium based browsers, it was already there in flags, just disabled for everyone.

Collapse
 
ragzzyr profile image
Raghuram Iyer "Ragzzy-R"

nice. next is kernel access to the browser followed by access to CPU Registers.

Collapse
 
sharadcodes profile image
Sharad Raj (He/Him)

๐Ÿคฃ

Collapse
 
hedgy134117 profile image
Graham Smith

Yeah... This seems like a huge security issue. Correct me if I'm wrong, but most web browsers run in a sandboxed environment, making malicious attacks through just a website pretty much impossible. But with this, some website can just ask for file permissions and totally just wipe all your stuff. There would be no way to know whether or not the website is trustworthy. That's just my two cents.

Collapse
 
genspirit profile image
Genspirit

There are security implications but what you are talking about isn't really feasible. The website needs permission and the picker is user controlled. A website can only access files/directories selected by the user. Saving/Editing is also another user prompt(once permission is provided for a single file it remains until the tab is closed).

So in order for what you are discussing to happen a user would have to give permission and open up a directory on the site then also hit confirm every time the site tried to overwrite a file. It's not impossible but there are notable safeguards in place to prevent this.

Collapse
 
sharadcodes profile image
Sharad Raj (He/Him)

You're right

Collapse
 
quangpl profile image
Quang Phan

Oh... it must observe strictly :D

Collapse
 
yoursunny profile image
Junxiao Shi

I'm make a malware that accepts "file submission", but requests write permission from the careless user, and overwrites the file when the permission was granted.

Collapse
 
sharadcodes profile image
Sharad Raj (He/Him)

๐Ÿค’

Collapse
 
alvinb profile image
Alvin Bryan

It reminds me when they disabled SharedArrayBuffer because of the massive Meltdown/Spectre stuff. I hope something similar doesn't happen with this.
I'm definitely disabling it for everything.

Collapse
 
sharadcodes profile image
Sharad Raj (He/Him)

I didn't know

Collapse
 
zilti_500 profile image
Daniel Ziltener

I won't, and this "feature" needs to disappear again. That's horrid.

Collapse
 
sharadcodes profile image
Sharad Raj (He/Him)

๐Ÿ˜