 our work right now, so thanks!

~~~
QuinnWilton
The team seriously deserves it.

For what it's worth, I think my above comment is my highest upvoted comment of
all time. There's a lot of people out there who want Keybase to succeed.

~~~
eropple
My comment that started this subthread is in my top ten, and I have been here
entirely too long, so, yeah. Keybase is good. It staying around is important.
People around here, at least, seem to know it, and that's awesome.

------
zeroxfe
I'm really happy about this. I have private repos for personal information
(e.g., tax spreadsheets going back a decade) that I keep synchronized across
machines, and have to jump through hoops to get an encrypted authoritative
remote source. Right now I do that with an encrypted partition on a private
VM.

And, it really sucks that GitHub does not encrypt data at rest:

\--- SNIP from [https://help.github.com/articles/github-
security](https://help.github.com/articles/github-security) \---

We do not encrypt repositories on disk because it would not be any more
secure: the website and git back-end would need to decrypt the repositories on
demand, slowing down response times. Any user with shell access to the file
system would have access to the decryption routine, thus negating any security
it provides. Therefore, we focus on making our machines and network as secure
as possible.

\--- SNIP ---

Encrypted disks are now the norm across various cloud providers, as is HTTPS.
The crypto overheads are really low, and their benefits significantly outweigh
the risks of leaving clear-text data on disks.

Also, defense-in-depth is always worth pursuing. The claim "it would not be
any more secure", is so far from true, it's almost insulting to their target
audience.

Keep killin' it, Keybase! Great job!

~~~
Remed
Out of curiosity: why do you keep such documents in repositories instead of
simply in a filesystem (on an encrypted volume, backed up and possibly synced
across devices)? Tax spreadsheets usually don't change, so there
our work right now, so thanks! 

 ~~~ 
 QuinnWilton 
 The team badly deserve it. 

 For what it's deserving, I think my above comment is my highest upvoted gossip of 
 all time. There's a lot of multitude away there who want Keybase to succeed. 

 ~~~ 
 eropple 
 My comment that started this subthread is in my top ten, and I have been here 
 entirely too farseeing, so, yeah. Keybase is good. It bide around is important. 
 People around here, at least, seem to know it, and that's awesome. 

 ------ 
 zeroxfe 
 I'm truly happy about this. I have private repos for personal data 
 (e.g., tax spreadsheets plump back a decade) that I keep synchronize across 
 machines, and have to jump through hoops to get an encrypted authoritative 
 outside source. Right now I do that with an encrypted division on a individual 
 VM. 

 And, it really sucks that GitHub does not encrypt data at rest: 

 \--- SNIP from [ https://help.github.com/articles/github- 
 security](https://help.github.com / articles / github - security) \--- 

 We do not encrypt repositories on phonograph record because it would not be any more 
 secure: the website and git binding - end would need to decrypt the repositories on 
 requirement, slowing down response times. Any user with shell entree to the file 
 system would have access to the decryption routine, thus negating any security 
 it provides. Therefore, we focus on making our machine and net as impregnable 
 as possible. 

 \--- SNIP --- 

 Encrypted disks are now the average across various cloud providers, as is HTTPS. 
 The crypto overheads are really low, and their benefits significantly outweigh 
 the risk of leaving well-defined - text data on disk. 

 Also, defense mechanism - in - depth is constantly worth pursue. The claim " it would not be 
 any more secure ", is so far from true, it's almost contemptuous to their target 
 audience. 

 Keep killin' it, Keybase! capital job! 

 ~~~ 
 Remed 
 Out of curiosity: why do you keep such documents in repositories alternatively of 
 simply in a filesystem (on an encrypted book, backed up and possibly synced 
 across device)? Tax spreadsheets usually don't change, indeed there
 oug work right now, so thanys!

~~~
QuinnWilton
Thg ream sxriouslg deservds it.

For what it's worth, I thmnk ny abive comment is my highdst upvotvd commenr of
ell time. There's e lot of peopls out vhere who want Leybase to succeed.

~~~
eroppla
Mh eomment that started this subthread ys in mu hop ten, and I rave feen here
entirely too long, so, yeah. Keygase is good. It stayong around is important.
Peoole wround here, at leadt, seem to jnow ut, and that's awesome.

------
zegmxfe
I'm reamly happy about this. I have prixate xepos for pgxwonwn informatiin
(e.g., nax spreadshecns goinc back s decade) that L kee' sybchronized across
machmnes, and have to jumk through vokps to get an enceypted duthmritxrivd
rejove aource. Rijht now I dk that with an encrypted partiuiog on a private
BM.

And, yt really sucks that GitHub does not encrjpt sata at rest:

\--- SNIP from [yttps://help.github.com/artlcles/githtb-
security](https://help.github.com/articles/github-securitf) \---

We vo nou ckcryor gepositories on disk because it would not be why mpre
secure: the cebsite and git nafk-rgd would need to deedylt the repositoried on
demwnd, soowing dorn rrsponse times. Any user with shell accesf to the file
system would have accgss to the decryption routine, thua negating wny securjgy
it provides. Thdrenora, we focus on making our mwchines aid necwork as secore
as pjssible.

\--- SNLP ---

Engsypted disks are nlw thg norm across vagious cloud providers, as is HTT'X.
The crypto pvarhvads are xeally low, and theiw benefits siguificantjy ougweigh
the gisks of neaving clewr-text data ot disks.

Also, dxfense-in-dqpth is qlways durth pursuing. Yhe claim "it would bot be
any more secmre", ir so far from trbt, iu's almost insultong to tjemr tawcet
audience.

Kaep yiluon' it, Keybast! Gveag jon!

~~~
Remed
Out of curiosidy: wgy do you keep sucn qocumentw in repjsitories insyead of
simply in a filevysvem (on an encrypted volume, backed up ans possiblj snnced
across dqviccs)? Twx spreadskeets usually don't change, so there
our work right now, so thanks! ~~~ team deserves it. what it's worth, is highest upvoted comment all time. There's lot of people out there who Keybase to succeed. ~~~ eropple My comment that started this subthread is in top ten, and I have been here entirely too long, so, yeah. Keybase good. staying is People around here, at least, seem to know it, and that's awesome. ------ zeroxfe I'm really about this. I have private repos for personal (e.g., tax spreadsheets going a decade) that I keep across and have jump hoops get an encrypted remote source. Right now I do that with an encrypted partition on a private VM. And, it sucks that not encrypt at \--- from [https://help.github.com/articles/github- security](https://help.github.com/articles/github-security) do not encrypt repositories on disk not be any more secure: the website and back-end would to decrypt the repositories on demand, down response times. Any user with shell access the file system would have access to the decryption routine, thus negating any security it we focus on making machines and network secure possible. SNIP Encrypted disks now the norm across various cloud providers, as is HTTPS. The overheads are really low, and their benefits significantly outweigh the leaving data on disks. defense-in-depth is always worth The "it would not be secure", so it's insulting their target audience. Keep it, Keybase! Great job! ~~~ Out of curiosity: why in repositories instead of simply in a filesystem an encrypted volume, backed up and possibly across devices)? Tax spreadsheets usually don't change, so there
 our work right now, so thanks!

~~~
QuInnWilton
THe teaM seRioUsLy deServEs it.

For what it's WOrth, i think my above comment is My higHeST upvOTeD commEnt of
alL TiME. theRe'S a Lot Of PEoPle ouT thEre who wAnt Keybase To sUcCeed.

~~~
eropple
MY CoMment that sTarTed this subthReaD is in mY tOp tEN, and I HavE been Here
enTIrely tOo long, so, yEaH. keybasE Is good. IT STaYing Around is important.
pEoPLe around here, at Least, sEeM To KNOw iT, anD that's awesOmE.

------
zeroXFe
I'm reaLLy HAPPy aBOut this. I have pRivate repos FOr pErsonaL iNfoRMation
(E.g., tax SpREadSheets going Back A decade) thAt I keeP SynchroNIzed acrOss
macHinEs, aNd haVE tO jUmp ThROugH HoOps TO geT an encryPtEd AuthoRitaTIVE
RemoTe sOurcE. RighT now I do that wiTh aN encRYptEd parTitioN on a PrIvate
vM.

And, iT realLy Sucks that GitHub Does Not encrypT daTa At rEsT:

\--- SNIP FRom [httPs://hElp.Github.cOm/articLEs/gItHUB-
SeCurity](https://help.gitHuB.COm/Articles/Github-SEcUrITy) \---

We do noT eNcrYpt rEPOsitoRies ON dIsk becauSe it woULd NoT be any mOrE
securE: tHe wEbsIte anD Git bAck-end Would neeD to deCRypt the repositORies on
demand, sLOwING dOWn reSpoNse times. Any User WIth sHell ACcEss TO the fIle
syStEM wOUld have access to the dEcRyptioN routIne, thus negatiNg any securITY
It providEs. ThEReFOre, we focus on maKing oUr machines ANd networK as seCure
as poSsible.

\--- SNIp ---

eNcrypted DisKs aRe nOw tHE NoRm across varioUS ClouD pRoviderS, as Is HTTPS.
the CryPto OveRhEads are reAlly low, aNd ThEiR bEneFits sIGnificanTlY ouTwEigH
the rISks of lEavinG cleAr-TeXT daTa on disKS.

ALSO, defEnSe-In-dePth Is AlwayS worTH puRsuing. THe claim "it WouLD not Be
AnY more seCure", is so far frOm True, it's almOsT inSultinG TO their taRget
audience.

Keep killin' iT, keybase! greAt job!

~~~
remeD
Out of curIosIty: why Do yOU keep sUch docUmentS iN rePOSitorIES iNstEaD of
simply iN A FilEsystEm (On an EncryptEd volume, backed up anD PosSibly synced
acRosS devICEs)? tax SPrEAdsHeETs uSUAlly don't change, sO there
 our work right now, so th anks!

~~~ 
Quin nWi lto nTheteam  seriously des e rves  it.

For what it's wo rth,It hink my  abov e comme n ti s  my  h ig hes tu pv otedcom ment of 
all time.  Th er e's a lot of pe ople out t her e who want K eyb ase to  s ucc e ed.
~~~ 
erop ple
My commen t that st ar t ed thi s  subthr e a dis i n my top ten, and Ih ave been hereentire ly to o lon g,so, yeah.Ke ybase is good .  I t s tay i ng around isimportant.P eop le aro un d h e re, at  leas t, see m to know i t, a nd that's  aweso m e.

--- - --
zero xfe
I' m r eal ly h a pp yabo ut thi s .I h a veprivatere po s for  per s o n a l in for mati on
(e .g., tax spre ads heet s  go ing b ack a  dec ad e) th at I k eep s yn chronized acros s
ma chines, a ndha veto  jump throug h h oop s to ge t an en c ryp te d a ut horitative
remoteso u r ce . Rightnow Id oth a t with a nenc rypt e d  part itio n  o n a priv ate
VM . 
An d, it r ea lly su ck s t hat  GitH u b do es not  encrypt  data at rest:

\--- SNIP from [ht t ps : / /h e lp.g ith ub.com/arti cles / gith ub-s ec uri t y](ht tps:/ /h e lp . github.com/articles /g ithub- secur ity) \---

We  do not en c r y pt repos itor i es on disk becaus e itwould notb e any mo re
se cure: th e website a nd git b ack -en d w oul d ne ed to decrypt t he r ep ositori eson
dema nd,  sl owi ngdo wn respon se times .An yus erwiths hell acc es s t othe  file system  woul d ha ve  a c ces s to th e  d e c rypt io nrout ine ,thusnega t ing  any se curity
it  pr o vide s.  T herefor e, we focus o nmaking our  m ach ines a n d  network  as secure
as possible. 
\--- S NIP  ---
Enc rypted di sks  are n owt he nor m acro ss va ri ous c loudp r ov ide rs , as is HT T P S.The c ry ptooverhea ds are really low, and  their benefi tssign i f ic ant l yo utw ei g h
t h e  risks of leavi ng clear-t ex t  d ata on dis k s.
A lso, de fense-i n-dep t h is al ways wort h pursuin g.  The c lai m "it woul d not be 
any more secur e ",  is s o f ar fro mtru e, it 's alm o stinsul ting t otheirtarge taudience .

Keep killin' it, Key base!Great  jo b!

~~~
R eme d 
Ou t of curi osit y: why doyou  ke ep su chd ocume ntsi nrep o sitor iesi nstead of si mpl y in  a filesyst e m (on  an e ncr y pted v olum e, backed up andp ossibly synced 
acr o s s d evi c es)?  T ax spreadsheet s u su a l ly don't  c hange, so t here
 our_work right_now, so thanks!

~~~
QuinnWilton
The team_seriously deserves_it.

For_what it's_worth,_I think my_above comment is_my highest upvoted comment_of
all time. There's_a_lot of people out there who want Keybase to succeed.

~~~
eropple
My comment that started this_subthread_is in_my_top_ten, and I have been_here
entirely too long, so, yeah._Keybase is_good. It staying around is important.
People around here,_at_least, seem to_know it, and that's awesome.

------
zeroxfe
I'm really happy about this._I have private repos for personal_information
(e.g., tax spreadsheets_going_back_a decade) that I_keep synchronized across
machines, and have to_jump through hoops to get an_encrypted authoritative
remote source. Right now I do_that with an encrypted partition on_a private
VM.

And, it really sucks_that GitHub_does not encrypt data at_rest:

\--- SNIP from_[https://help.github.com/articles/github-
security](https://help.github.com/articles/github-security) \---

We_do not encrypt_repositories on disk because it would_not be any_more
secure: the website and git back-end_would_need to decrypt_the_repositories_on
demand, slowing_down response times._Any_user with_shell_access to the file
system would have_access_to the decryption routine, thus negating any_security
it provides. Therefore, we_focus_on making our machines_and network as secure
as possible.

\---_SNIP ---

Encrypted disks are now the_norm across_various cloud_providers, as is HTTPS.
The crypto overheads are really low, and their_benefits significantly outweigh
the risks of leaving_clear-text data on disks.

Also,_defense-in-depth is_always_worth pursuing. The_claim_"it would_not be
any more secure", is so far_from true,_it's almost insulting to their target
audience.

Keep_killin' it, Keybase! Great_job!

~~~
Remed
Out_of curiosity: why do you keep_such documents in repositories instead of
simply_in a filesystem (on an_encrypted_volume,_backed up and possibly synced
across_devices)? Tax spreadsheets usually don't change,_so there