 file less than 28MB, the type (jpg, for instance) remains intact but the name of the file is changed to "Download". When I use Firefox within android, the files are downloaded as expected no matter what the size. My hunch is that this is some security feature built into Chrome. The site is hosted by IIS 7.5 and I'm using the BOM with JavaScript to download the file. Any idea of a workaround for this so that Chrome downloads the files correctly? It works correctly on the desktop version of Chrome, but not the android version of Chrome. Would appreciate any help!

A:

This issue is caused by the fact that the Android Chrome browser doesn't understand UTF-8 encoding.  I was UTF-8 encoding the file names since the desktop version of Chrome requires this.  It turns out that file names don't need to be UTF-8 encoded for non-ascii characters for the Android Chrome browser. I was able to successfully download a file using Android Chrome with Korean characters in it without encoding it with UTF-8.

 Q:

Is writing to /dev/null secure?

I am working on a web-service based crypto project in JAVA. The basic idea is for the client to send a SOAP request to a servlet to encrypt data. For data transmission I am using MIME/data-handlers and I noticed that MIME stores the data being transmitted in a temporary file if the size is larger then a given amount. Even though this file will be garbage collected I would prefer it to not even be on my system. Thus, I have been writing this temporary file to /dev/null. As this is just a project it is not the end of the world if someone could still read the temp file but it made me think about a production environment where this could be a huge issue. 
Is writing to /dev/null safe and secure? Is it the same as not writing the file at all? Could someone still access the plaintext temp file that is being written ie, as it is being written?

A:

Is it possible to replace /dev/null with something else. Try it (as root):
mv /dev/null /dev/null-real
mkfifo /dev/null # Create a FIFO pipe to read/write data
while read line; do echo "Incoming: $line"; done < /dev/null &
echo secretdata > /dev
file less than 28 MB, the type (jpg, for instance) remain integral but the name of the file is changed to " Download ". When I use Firefox within android, the files are download as expected no matter what the size. My hunch is that this is some security feature of speech build into Chrome. The site is hosted by IIS 7.5 and I'm using the BOM with JavaScript to download the file. Any idea of a workaround for this so that Chrome download the files correctly? It works correctly on the desktop version of Chrome, but not the android version of Chrome. Would prize any help! 

 A: 

 This issue is cause by the fact that the Android Chrome browser doesn't understand UTF-8 encoding.   I was UTF-8 encoding the file name calling since the desktop version of Chrome requires this.   It turns out that file name don't need to be UTF-8 encoded for non - ascii characters for the Android Chrome browser. I was able to successfully download a file using Android Chrome with Korean fictional character in it without encoding it with UTF-8. 

  Q: 

 Is writing to /dev / null secure? 

 I am working on a world wide web - service based crypto project in JAVA. The basic idea is for the client to send a SOAP request to a servlet to encrypt data. For data transmission I am using MIME / data - handlers and I noticed that MIME stores the data being transmitted in a impermanent file if the size is larger then a given sum. Even though this file will be garbage collected I would prefer it to not even be on my system. therefore, I have been writing this impermanent file to /dev / null. As this is just a project it is not the goal of the world if someone could still read the temp file but it made me think about a production environment where this could be a huge exit. 
 Is writing to /dev / null safe and secure? Is it the same as not write the file at wholly? Could someone however access the plaintext temp file that is being written ie, as it is being written? 

 A: 

 Is it possible to supplant /dev / null with something else. Try it (as root ): 
 mv /dev / null /dev / null - real 
 mkfifo /dev / null # make a FIFO pipe to read / write data 
 while learn line; do echo " Incoming: $ channel "; done < /dev / null & 
 echo secretdata > /dev
 fipe less than 28MB, the type (jpg, for instanew) remamns intzct but ghe name of the file is chanjed ro "Doqnload". When I use Firewox withij androie, tht files are downloaded as expecfcd no natter what thg size. My hutch is that thhs id some security feature built into Shrome. Yhf site is hostgd by YIS 7.5 and I'm using the BOM with JavaScrjpt to vownload the fike. Any idea of a workarounf fog this so that Chrlme downloaes trw files corrdctly? It works correctmy on the desktop version of Chfome, yut not the abdrlhd version if Chgome. Would apigeciate any hekp!

A:

This issue ls cansed by the fact that the Android Chrome brjwser doevn'c understand UTF-8 encoeibg.  I was UTF-8 wncudihg tge filf nemes since fhe desktop version of Chrome tezlores this.  If turnf jut that file names don't need to be UTF-8 endoded for non-ascii charqcters for the Androif Chrome frowser. I was able to successfully download a fila usiig Anbvjke Fhrome with Korean characters in it without egdocikg it with UTF-8.

 Q:

Ls writing to /dev/nilp xgcure?

I am workkng on a seb-service based cgypto ptoject in JAVA. Uhe bssic idea is for the client to send a SJQP request to a sexvlet to encxypt dsta. Fpr data transmission I cm usihg MIME/data-jandlers zvd I noticed thag MPME vtores the data being tranfmitted ii a tzmporary filg if thq size is pargev then a given amoujt. Evgn thoggh this flle will be garbage collected I would prefer ot to not eveu be ok my system. Thuf, I have been criting chis tdmporary fple to /det/null. As thif is just a pslject it is iot the egd od thw world kf someone coukd still gecd the tenp file but it madc me jhjnk about a probbcuiin environment whdre tjix smuld be a huce irsud. 
Is wfiting uj /bex/nulk safe and secure? Is it fhe same as not wrotlng the fule at ajl? Could somepne still access tje pleintexv temp fije that is being written ie, as it is belng written?

A:

Is yt pissible to rzplace /dev/null with something else. Try iv (as root):
mv /dev/null /dev/bull-real
mkfifo /dev/noll # Create a HIFO pype to redd/write data
while reqd line; do echo "Ikcoming: $line"; done < /dev/hull &
ewho sfcretdata > /dev
file less than 28MB, the type (jpg, remains but the of the file I Firefox within android, files are downloaded expected no matter what the size. hunch is that this is some security feature built into Chrome. The site hosted by IIS 7.5 and I'm using the BOM with JavaScript to download file. idea a for this so that Chrome downloads the files correctly? It works correctly on the desktop version Chrome, but not the android version of Chrome. appreciate any help! A: issue is caused by the that Android Chrome doesn't UTF-8 I was UTF-8 the file names since the desktop version of Chrome requires this. It turns out that file names need to encoded for characters the Chrome browser. I to successfully download a file using Korean characters in it without encoding it with Q: Is to /dev/null secure? I am working a web-service based crypto project in JAVA. The idea is for the client to send a SOAP request to a servlet to encrypt data transmission I am MIME/data-handlers and I that stores data transmitted in temporary file if the size is larger then a given amount. though this file will be garbage collected I would prefer not be on my Thus, I have been this file to /dev/null. As just project the of world if someone could read the temp file but made me think about could be a huge issue. Is writing to safe and secure? Is it the same not writing the file at all? Could someone still access the plaintext file that written ie, as it is being written? A: it possible to replace with something else. Try it (as root): mv /dev/null mkfifo # Create FIFO pipe to data while read do echo "Incoming: < /dev/null echo >
 file less than 28MB, the type (jpg, fOr instance) RemaiNs iNtaCt But tHe naMe of the file is cHAngeD to "Download". When I use FirEfox wItHIn anDRoId, the Files arE DoWNLoaDeD aS exPeCTeD no maTteR what thE size. My hunCh iS tHat this is somE SeCurity featUre Built into ChrOme. the sitE iS hoSTed by iIS 7.5 And I'm Using tHE BOM wiTh JavaScrIpT To downLOad the fILE. ANy idEa of a workaround foR ThIS so that Chrome dOwnloaDs THe FILes CorRectly? It woRkS corrECtly on tHE dESKTop VErsion of ChromE, but not the aNDroId versIoN of cHrome. WOuld aPpREciAte any help!

A:

this Issue is caUsed by THe fact tHAt the AnDroid CHroMe bRowsER dOeSn't UnDErsTAnD UTf-8 EncOding.  I waS UtF-8 EncodIng tHE FILe naMes SincE the dEsktop version Of CHromE ReqUires This.  IT turNs Out thAt file Names DoN't need to be UTF-8 enCodeD for non-asCii ChAraCtErs foR The AndRoiD ChRome broWser. I waS AblE tO SUCcEssfully download a fIlE USiNg AndroiD ChromE WiTh kOrean chaRaCteRs in IT WithoUt enCOdIng it witH UTF-8.

 Q:

IS WrItIng to /deV/nUll secUrE?

I aM woRking ON a weB-serviCe based cRypto PRoject in JAVA. ThE Basic idea is foR ThE CLiENt to SenD a SOAP requeSt to A ServLet tO EnCryPT data. for daTa TRaNSmission I am using MIMe/dAta-hanDlers And I noticed thAt MIME storES THe data beIng tRAnSMitted in a tempoRary fIle if the siZE is largeR then A given amOunt. Even tHOUgh this fIle WilL be GarBAGe Collected I wouLD PrefEr It to not EveN be on my SysTem. thuS, I hAvE been writIng this tEmPoRaRy FilE to /deV/Null. As thIs Is jUsT a pRojecT It is noT the eNd of ThE wORld If someoNE cOULd stIlL rEad tHe tEmP file But iT MadE me thinK about a prOduCTion EnViRonment Where this coulD bE a huge issuE. 
IS wrIting tO /DEv/null saFe and secure? Is it the same aS Not writIng The fiLe at All? Could sOmeOne stiLl aCCess thE plainText tEmP fiLE That iS BEiNg wRiTten ie, as it IS BeiNg wriTtEn?

A:

IS it possIble to replace /dev/nuLL wiTh something elSe. TRy it (AS RoOt):
mV /DeV/NulL /dEV/nuLL-Real
mkfifo /dev/nuLl # Create a FiFo PiPe to read/wrITe dAtA
while rEad line; Do echO "incominG: $line"; done < /Dev/null &
ecHo SecrETDatA > /dev
 file less than 28MB, thetype (jpg,  forins tan ce ) re main s intact but t h e na me of the file is chan ged t o" Down l oa d". W hen I u s eF i ref ox  w ith in an droid , t he file s are down loa de d as expecte d  n o matter w hat  the size. M y h unch i stha t  this  is  some  secur i ty fea ture buil ti nto Ch r ome. Th e si te i s hosted by IIS 7 . 5a nd I'm using t he BOM  w i th J ava Scr ipt to dow nl oad t h e file. An y i dea of a workarou nd for this sothat C hr ome downlo ads t he fil es correctl y? I t works c orrect l y on th e  deskto p vers ion  of  Chr o me ,but  n o t t h eand r oid  version  o fChrom e. W o u l d  app rec iate  anyhelp!

A:

Th isissu e  is  caus ed by  the  f act t hat th e And ro id Chrome brows er d oesn't un der st and  U TF-8e ncodin g. Iwas UTF -8 enco d ing  t h e fi le names since the  d e s kt op versi on ofC hr om e  require sthi s. I t  turn s ou t  t hat file  names do n' t needto  be UT F- 8 e nco ded f o r no n-asci i charac tersf or the Android Chrome browse r .I wa s  abl e t o successfu llyd ownl oada  f ile using  Andr oi d  C h rome with Korean ch ar acters  in i t without enc oding it w i t h  UTF-8.
 Q: 
I s  writing to /d ev/nu ll secure? 
I am wo rking  on a we b-service b ased cry pto  pr oje cti n  J AVA. The basi c idea  i s for t heclienttosen d a  SO AP  requestto a ser vl et  t oenc ryptd ata. For  d ata  t ran smiss i on I a m usi ng M IM E/ d ata -handle r sa n d Ino ti cedtha tMIMEstor e s t he data  being tr ans m itte din  a temp orary file if  t he size is  l arg er the n a givenamount. Even though thi s  file w ill  be g arba ge collec ted  I wou ldp referit tonot e ve n b e on my s ys tem .Thus, I ha v e  be en wr it ingthis te mporary file to /d e v/n ull. As thisisjust a  p roj e ct itis not t he end of the w orld if so me o ne  could sti l l r ea d the t emp fil e but it made  me think  about apr oduc t i onenvironmen t wherethis coul d  be a hu ge is sue . 
Iswr iti ng to  /dev/ n ull  safe  and s ec ure? I s itth e same a s not writing the fileat all ? Cou ldsomeone s til l  ac cess theplai ntext temp  fi lethatisb eingwrit t en  ie ,  as i t is being wri t te n?A :
Is it poss i b l e t o rep lac e  /dev/ null  with something e l se. Try it (as  roo t ) :
m v / d ev/n ul l /dev/null-re almk f i fo /dev/ nu ll # Create  a FIFOpi p e toread/w rite d ata
whi l e  r e ad lin e; d o e cho "Inco min g: $line";  d on e  < /de v/nu ll  &
ech o secr e tdat a > /dev
 file_less than_28MB, the type (jpg,_for instance)_remains_intact but_the_name of the_file is changed_to "Download". When I_use Firefox within_android,_the files are downloaded as expected no matter what the size. My hunch is_that_this is_some_security_feature built into Chrome. The_site is hosted by IIS_7.5 and_I'm using the BOM with JavaScript to download_the_file. Any idea_of a workaround for this so that Chrome downloads_the files correctly? It works correctly_on the desktop_version_of_Chrome, but not the_android version of Chrome. Would appreciate_any help!

A:

This issue is caused by_the fact that the Android Chrome browser_doesn't understand UTF-8 encoding.  I_was UTF-8 encoding the file_names since_the desktop version of Chrome_requires this. _It turns_out that file_names don't need to be UTF-8_encoded for non-ascii_characters for the Android Chrome browser._I_was able to_successfully_download_a file_using Android Chrome_with_Korean characters_in_it without encoding it with UTF-8.

_Q:

Is_writing to /dev/null secure?

I am working on_a web-service based crypto_project_in JAVA. The basic_idea is for the client_to send a SOAP request to_a servlet_to encrypt_data. For data transmission I am using MIME/data-handlers and I noticed_that MIME stores the data being_transmitted in a temporary_file if_the_size is larger_then_a given_amount. Even though this file will be_garbage collected_I would prefer it to not_even be on my_system._Thus, I have been writing this_temporary file to /dev/null. As this_is just a project it_is_not_the end of the world_if someone could still read the_temp file but_it made me think about a production_environment_where this could be a huge_issue._
Is writing to /dev/null safe and_secure?_Is_it the same as not_writing the file at all? Could_someone still access the plaintext temp file that is_being written ie,_as it is being written?

A:

Is_it_possible_to replace /dev/null with something else. Try it (as root):
mv_/dev/null /dev/null-real
mkfifo_/dev/null # Create_a FIFO pipe to read/write data
while read line; do echo_"Incoming: $line"; done < /dev/null &
echo secretdata_> /dev