ReleaseNotes 506 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798991001011021031041051061071081091101111121131141151161171181191201211221231241251261271281291301311321331341351361371381391401411421431441451461471481491501511521531541551561571581591601611621631641651661671681691701711721731741751761771781791801811821831841851861871881891901911921931941951961971981992002012022032042052062072082092102112122132142152162172182192202212222232242252262272282292302312322332342352362372382392402412422432442452462472482492502512522532542552562572582592602612622632642652662672682692702712722732742752762772782792802812822832842852862872882892902912922932942952962972982993003013023033043053063073083093103113123133143153163173183193203213223233243253263273283293303313323333343353363373383393403413423433443453463473483493503513523533543553563573583593603613623633643653663673683693703713723733743753763773783793803813823833843853863873883893903913923933943953963973983994004014024034044054064074084094104114124134144154164174184194204214224234244254264274284294304314324334344354364374384394404414424434444454464474484494504514524534544554564574584594604614624634644654664674684694704714724734744754764774784794804814824834844854864874884894904914924934944954964974984995005015025035045055065075085095105115125135145155165175185195205215225235245255265275285295305315325335345355365375385395405415425435445455465475485495505515525535545555565575585595605615625635645655665675685695705715725735745755765775785795805815825835845855865875885895905915925935945955965975985996006016026036046056066076086096106116126136146156166176186196206216226236246256266276286296306316326336346356366376386396406416426436446456466476486496506516526536546556566576586596606616626636646656666676686696706716726736746756766776786796806816826836846856866876886896906916926936946956966976986997007017027037047057067077087097107117127137147157167177187197207217227237247257267277287297307317327337347357367377387397407417427437447457467477487497507517527537547557567577587597607617627637647657667677687697707717727737747757767777787797807817827837847857867877887897907917927937947957967977987998008018028038048058068078088098108118128138148158168178188198208218228238248258268278288298308318328338348358368378388398408418428438448458468478488498508518528538548558568578588598608618628638648658668678688698708718728738748758768778788798808818828838848858868878888898908918928938948958968978988999009019029039049059069079089099109119129139149159169179189199209219229239249259269279289299309319329339349359369379389399409419429439449459469479489499509519529539549559569579589599609619629639649659669679689699709719729739749759769779789799809819829839849859869879889899909919929939949959969979989991000100110021003100410051006100710081009101010111012101310141015101610171018101910201021102210231024102510261027102810291030103110321033103410351036103710381039104010411042104310441045104610471048104910501051105210531054105510561057105810591060106110621063106410651066106710681069107010711072107310741075107610771078107910801081108210831084108510861087108810891090109110921093109410951096109710981099110011011102110311041105110611071108110911101111111211131114111511161117111811191120112111221123112411251126112711281129113011311132113311341135113611371138113911401141114211431144114511461147114811491150115111521153115411551156115711581159116011611162116311641165116611671168116911701171117211731174117511761177117811791180118111821183118411851186118711881189119011911192119311941195119611971198119912001201120212031204120512061207120812091210121112121213121412151216121712181219122012211222122312241225122612271228122912301231123212331234123512361237123812391240124112421243124412451246124712481249125012511252125312541255125612571258125912601261126212631264126512661267126812691270127112721273127412751276127712781279128012811282128312841285128612871288128912901291129212931294129512961297129812991300130113021303130413051306130713081309131013111312131313141315131613171318131913201321132213231324132513261327132813291330133113321333133413351336133713381339134013411342134313441345134613471348134913501351135213531354135513561357135813591360136113621363136413651366136713681369137013711372137313741375137613771378137913801381138213831384138513861387138813891390139113921393139413951396139713981399140014011402140314041405140614071408140914101411141214131414141514161417141814191420142114221423142414251426142714281429143014311432143314341435143614371438143914401441144214431444144514461447144814491450145114521453145414551456145714581459146014611462146314641465146614671468146914701471147214731474147514761477147814791480148114821483148414851486148714881489149014911492149314941495149614971498149915001501150215031504150515061507150815091510151115121513151415151516151715181519152015211522152315241525152615271528152915301531153215331534153515361537153815391540154115421543154415451546154715481549155015511552155315541555155615571558155915601561156215631564156515661567156815691570157115721573157415751576157715781579158015811582158315841585158615871588158915901591159215931594159515961597159815991600160116021603160416051606160716081609161016111612161316141615161616171618161916201621162216231624162516261627162816291630163116321633163416351636163716381639164016411642164316441645164616471648164916501651165216531654165516561657165816591660166116621663166416651666166716681669167016711672167316741675167616771678167916801681168216831684168516861687168816891690169116921693169416951696169716981699170017011702170317041705170617071708170917101711171217131714171517161717171817191720172117221723172417251726172717281729173017311732173317341735173617371738173917401741174217431744174517461747174817491750175117521753175417551756175717581759176017611762176317641765176617671768176917701771177217731774177517761777177817791780178117821783178417851786178717881789179017911792179317941795179617971798179918001801180218031804180518061807180818091810181118121813181418151816181718181819182018211822182318241825182618271828182918301831183218331834183518361837183818391840184118421843184418451846184718481849185018511852185318541855185618571858185918601861186218631864186518661867186818691870187118721873187418751876187718781879188018811882188318841885188618871888188918901891189218931894189518961897189818991900190119021903190419051906190719081909191019111912191319141915191619171918191919201921192219231924192519261927192819291930193119321933193419351936193719381939194019411942194319441945194619471948194919501951195219531954195519561957195819591960196119621963196419651966196719681969197019711972197319741975197619771978197919801981198219831984198519861987198819891990199119921993199419951996199719981999200020012002200320042005200620072008200920102011201220132014201520162017201820192020202120222023202420252026202720282029203020312032203320342035203620372038203920402041204220432044204520462047204820492050205120522053205420552056205720582059206020612062206320642065206620672068206920702071207220732074207520762077207820792080208120822083208420852086208720882089209020912092209320942095209620972098209921002101210221032104210521062107210821092110211121122113211421152116211721182119212021212122212321242125212621272128212921302131213221332134213521362137213821392140214121422143214421452146214721482149215021512152215321542155215621572158215921602161216221632164216521662167216821692170217121722173217421752176217721782179218021812182218321842185218621872188218921902191219221932194219521962197219821992200220122022203220422052206220722082209221022112212221322142215221622172218221922202221222222232224222522262227222822292230223122322233223422352236223722382239224022412242224322442245224622472248224922502251225222532254225522562257225822592260226122622263226422652266226722682269227022712272227322742275227622772278227922802281228222832284228522862287228822892290229122922293229422952296229722982299230023012302230323042305230623072308230923102311231223132314231523162317231823192320232123222323232423252326232723282329233023312332233323342335233623372338233923402341234223432344234523462347234823492350235123522353235423552356235723582359236023612362236323642365236623672368236923702371237223732374237523762377237823792380238123822383238423852386238723882389239023912392239323942395239623972398239924002401240224032404240524062407240824092410241124122413241424152416241724182419242024212422242324242425242624272428242924302431243224332434243524362437243824392440244124422443244424452446244724482449245024512452245324542455245624572458245924602461246224632464246524662467246824692470247124722473247424752476247724782479248024812482248324842485248624872488248924902491249224932494249524962497249824992500250125022503250425052506250725082509251025112512251325142515251625172518251925202521252225232524252525262527252825292530253125322533253425352536253725382539254025412542254325442545254625472548254925502551255225532554255525562557255825592560256125622563256425652566256725682569257025712572257325742575257625772578257925802581258225832584258525862587258825892590259125922593259425952596259725982599260026012602260326042605260626072608260926102611261226132614261526162617261826192620262126222623262426252626262726282629263026312632263326342635263626372638263926402641264226432644264526462647264826492650265126522653265426552656265726582659266026612662266326642665266626672668266926702671267226732674267526762677267826792680268126822683268426852686268726882689269026912692269326942695269626972698269927002701270227032704270527062707270827092710271127122713271427152716271727182719272027212722272327242725272627272728272927302731273227332734273527362737273827392740274127422743274427452746274727482749275027512752275327542755275627572758275927602761276227632764276527662767276827692770277127722773277427752776277727782779278027812782278327842785278627872788278927902791279227932794279527962797279827992800280128022803280428052806280728082809281028112812281328142815281628172818281928202821282228232824282528262827282828292830283128322833283428352836283728382839284028412842284328442845284628472848284928502851285228532854285528562857285828592860286128622863286428652866286728682869287028712872287328742875287628772878287928802881288228832884288528862887288828892890289128922893289428952896289728982899290029012902290329042905290629072908290929102911291229132914291529162917291829192920292129222923292429252926292729282929293029312932293329342935293629372938293929402941294229432944294529462947294829492950295129522953295429552956295729582959296029612962296329642965296629672968296929702971297229732974297529762977297829792980298129822983298429852986298729882989299029912992299329942995299629972998299930003001300230033004300530063007300830093010301130123013301430153016301730183019302030213022302330243025302630273028302930303031303230333034303530363037303830393040304130423043304430453046304730483049305030513052305330543055305630573058305930603061306230633064306530663067306830693070307130723073307430753076307730783079308030813082308330843085308630873088308930903091309230933094309530963097309830993100310131023103310431053106310731083109311031113112311331143115311631173118311931203121312231233124312531263127312831293130313131323133313431353136313731383139314031413142314331443145314631473148314931503151315231533154315531563157315831593160316131623163316431653166316731683169317031713172317331743175317631773178317931803181318231833184318531863187318831893190319131923193319431953196319731983199320032013202320332043205320632073208320932103211321232133214321532163217321832193220322132223223322432253226322732283229323032313232323332343235323632373238323932403241324232433244324532463247324832493250325132523253325432553256325732583259326032613262326332643265326632673268326932703271327232733274327532763277327832793280328132823283328432853286328732883289329032913292329332943295329632973298329933003301330233033304330533063307330833093310331133123313331433153316331733183319332033213322332333243325332633273328332933303331333233333334333533363337333833393340334133423343334433453346334733483349335033513352335333543355335633573358335933603361336233633364336533663367336833693370337133723373337433753376337733783379338033813382338333843385338633873388338933903391339233933394339533963397339833993400340134023403340434053406340734083409341034113412341334143415341634173418341934203421342234233424342534263427342834293430343134323433343434353436343734383439344034413442344334443445344634473448344934503451345234533454345534563457345834593460346134623463346434653466346734683469347034713472347334743475347634773478347934803481348234833484348534863487348834893490349134923493349434953496349734983499350035013502350335043505350635073508350935103511351235133514351535163517351835193520352135223523352435253526352735283529353035313532353335343535353635373538353935403541354235433544354535463547354835493550355135523553355435553556355735583559356035613562356335643565356635673568356935703571357235733574357535763577357835793580358135823583358435853586358735883589359035913592359335943595359635973598359936003601360236033604360536063607360836093610361136123613361436153616361736183619362036213622362336243625362636273628362936303631363236333634363536363637363836393640364136423643364436453646364736483649365036513652365336543655365636573658365936603661366236633664366536663667366836693670367136723673367436753676367736783679368036813682368336843685368636873688368936903691369236933694369536963697369836993700370137023703370437053706370737083709371037113712371337143715371637173718371937203721372237233724372537263727372837293730373137323733373437353736373737383739374037413742374337443745374637473748374937503751375237533754375537563757375837593760376137623763376437653766376737683769377037713772377337743775377637773778377937803781378237833784378537863787378837893790379137923793379437953796379737983799380038013802380338043805380638073808380938103811381238133814381538163817381838193820382138223823382438253826382738283829383038313832383338343835383638373838383938403841384238433844384538463847384838493850385138523853385438553856385738583859386038613862386338643865386638673868386938703871387238733874387538763877387838793880388138823883388438853886388738883889389038913892389338943895389638973898389939003901390239033904390539063907390839093910391139123913391439153916391739183919392039213922392339243925392639273928392939303931393239333934393539363937393839393940394139423943394439453946394739483949395039513952395339543955395639573958395939603961396239633964396539663967396839693970397139723973397439753976397739783979398039813982398339843985398639873988398939903991399239933994399539963997399839994000400140024003400440054006400740084009401040114012401340144015401640174018401940204021402240234024402540264027402840294030403140324033403440354036403740384039404040414042404340444045404640474048404940504051405240534054405540564057405840594060406140624063406440654066406740684069407040714072407340744075407640774078407940804081408240834084408540864087408840894090409140924093409440954096409740984099410041014102410341044105410641074108410941104111411241134114411541164117411841194120412141224123412441254126412741284129413041314132413341344135413641374138413941404141414241434144414541464147414841494150415141524153415441554156415741584159416041614162416341644165416641674168416941704171417241734174417541764177417841794180418141824183418441854186418741884189419041914192419341944195419641974198419942004201420242034204420542064207420842094210421142124213421442154216421742184219422042214222422342244225422642274228422942304231423242334234423542364237423842394240424142424243424442454246424742484249425042514252425342544255425642574258425942604261426242634264426542664267426842694270427142724273427442754276427742784279428042814282428342844285428642874288428942904291429242934294429542964297429842994300430143024303430443054306430743084309431043114312431343144315431643174318431943204321432243234324432543264327432843294330433143324333433443354336433743384339434043414342434343444345434643474348434943504351435243534354435543564357435843594360436143624363436443654366436743684369437043714372437343744375437643774378437943804381438243834384438543864387438843894390439143924393439443954396439743984399440044014402440344044405440644074408440944104411441244134414441544164417441844194420442144224423442444254426442744284429443044314432443344344435443644374438443944404441444244434444444544464447444844494450445144524453445444554456445744584459446044614462446344644465446644674468446944704471447244734474447544764477447844794480448144824483448444854486448744884489449044914492449344944495449644974498449945004501450245034504450545064507450845094510451145124513451445154516451745184519452045214522452345244525452645274528452945304531453245334534453545364537453845394540454145424543454445454546454745484549455045514552455345544555455645574558455945604561456245634564456545664567456845694570457145724573457445754576457745784579458045814582458345844585458645874588458945904591459245934594459545964597459845994600460146024603460446054606460746084609461046114612461346144615461646174618461946204621462246234624462546264627462846294630463146324633463446354636463746384639464046414642464346444645464646474648464946504651465246534654465546564657465846594660466146624663466446654666466746684669467046714672467346744675467646774678467946804681468246834684468546864687468846894690469146924693469446954696469746984699470047014702470347044705470647074708470947104711471247134714471547164717471847194720472147224723472447254726472747284729473047314732473347344735473647374738473947404741474247434744474547464747474847494750475147524753475447554756475747584759476047614762476347644765476647674768476947704771477247734774477547764777477847794780478147824783478447854786478747884789479047914792479347944795479647974798479948004801480248034804480548064807480848094810481148124813481448154816481748184819482048214822482348244825482648274828482948304831483248334834483548364837483848394840484148424843484448454846484748484849485048514852485348544855485648574858485948604861486248634864486548664867486848694870487148724873487448754876487748784879488048814882488348844885488648874888488948904891489248934894489548964897489848994900490149024903490449054906490749084909491049114912491349144915491649174918491949204921492249234924492549264927492849294930493149324933493449354936493749384939494049414942494349444945494649474948494949504951495249534954495549564957495849594960496149624963496449654966496749684969497049714972497349744975497649774978497949804981498249834984498549864987498849894990499149924993499449954996499749984999500050015002500350045005500650075008500950105011501250135014501550165017501850195020502150225023502450255026502750285029503050315032503350345035503650375038503950405041504250435044504550465047504850495050505150525053505450555056505750585059506050615062506350645065506650675068506950705071507250735074507550765077507850795080508150825083508450855086508750885089509050915092509350945095509650975098509951005101510251035104510551065107510851095110511151125113511451155116511751185119512051215122512351245125512651275128512951305131513251335134513551365137513851395140514151425143514451455146514751485149515051515152515351545155515651575158515951605161516251635164516551665167516851695170517151725173517451755176517751785179518051815182518351845185518651875188518951905191519251935194519551965197519851995200520152025203520452055206520752085209521052115212521352145215521652175218521952205221522252235224522552265227522852295230523152325233523452355236523752385239524052415242524352445245524652475248524952505251525252535254525552565257525852595260526152625263526452655266526752685269527052715272527352745275527652775278527952805281528252835284528552865287528852895290529152925293529452955296529752985299530053015302530353045305530653075308530953105311531253135314531553165317531853195320532153225323532453255326532753285329533053315332533353345335533653375338533953405341534253435344534553465347534853495350535153525353535453555356535753585359536053615362536353645365536653675368536953705371537253735374537553765377537853795380538153825383538453855386538753885389539053915392539353945395539653975398539954005401540254035404540554065407540854095410541154125413541454155416541754185419542054215422542354245425542654275428542954305431543254335434543554365437543854395440544154425443544454455446544754485449545054515452545354545455545654575458545954605461546254635464546554665467546854695470547154725473547454755476547754785479548054815482548354845485548654875488548954905491549254935494549554965497549854995500550155025503550455055506550755085509551055115512551355145515551655175518551955205521552255235524552555265527552855295530553155325533553455355536553755385539554055415542554355445545554655475548554955505551555255535554555555565557555855595560556155625563556455655566556755685569557055715572557355745575557655775578557955805581558255835584558555865587558855895590559155925593559455955596559755985599560056015602560356045605560656075608560956105611561256135614561556165617561856195620562156225623562456255626562756285629563056315632563356345635563656375638563956405641564256435644564556465647564856495650565156525653565456555656565756585659566056615662566356645665566656675668566956705671567256735674567556765677567856795680568156825683568456855686568756885689569056915692569356945695569656975698569957005701570257035704570557065707570857095710571157125713571457155716571757185719572057215722572357245725572657275728572957305731573257335734573557365737573857395740574157425743574457455746574757485749575057515752575357545755575657575758575957605761576257635764576557665767576857695770577157725773577457755776577757785779578057815782578357845785578657875788578957905791579257935794579557965797579857995800580158025803580458055806580758085809581058115812581358145815581658175818581958205821582258235824582558265827582858295830583158325833583458355836583758385839584058415842584358445845584658475848584958505851585258535854585558565857585858595860586158625863586458655866586758685869587058715872587358745875587658775878587958805881588258835884588558865887588858895890589158925893589458955896589758985899590059015902590359045905590659075908590959105911591259135914591559165917591859195920592159225923592459255926592759285929593059315932593359345935593659375938593959405941594259435944594559465947594859495950595159525953595459555956595759585959596059615962596359645965596659675968596959705971597259735974597559765977597859795980598159825983598459855986598759885989599059915992599359945995599659975998599960006001600260036004600560066007600860096010601160126013601460156016601760186019602060216022602360246025602660276028602960306031603260336034603560366037603860396040604160426043604460456046604760486049605060516052605360546055605660576058605960606061606260636064606560666067606860696070607160726073607460756076607760786079608060816082608360846085608660876088608960906091609260936094609560966097609860996100610161026103610461056106610761086109611061116112611361146115611661176118611961206121612261236124612561266127612861296130613161326133613461356136613761386139614061416142614361446145614661476148614961506151615261536154615561566157615861596160616161626163616461656166616761686169617061716172617361746175617661776178617961806181618261836184618561866187618861896190619161926193619461956196619761986199620062016202620362046205620662076208620962106211621262136214621562166217621862196220622162226223622462256226622762286229623062316232623362346235623662376238623962406241624262436244624562466247624862496250625162526253625462556256625762586259626062616262626362646265626662676268626962706271627262736274627562766277627862796280628162826283628462856286628762886289629062916292629362946295629662976298629963006301630263036304630563066307630863096310631163126313631463156316631763186319632063216322632363246325632663276328632963306331633263336334633563366337633863396340634163426343634463456346634763486349635063516352635363546355635663576358635963606361636263636364636563666367636863696370637163726373637463756376637763786379638063816382638363846385638663876388638963906391639263936394639563966397639863996400640164026403640464056406640764086409641064116412641364146415641664176418641964206421642264236424642564266427642864296430643164326433643464356436643764386439644064416442644364446445644664476448644964506451645264536454645564566457645864596460646164626463646464656466646764686469647064716472647364746475647664776478647964806481648264836484648564866487648864896490649164926493649464956496649764986499650065016502650365046505650665076508650965106511651265136514651565166517651865196520652165226523652465256526652765286529653065316532653365346535653665376538653965406541654265436544654565466547654865496550655165526553655465556556655765586559656065616562656365646565656665676568656965706571657265736574657565766577657865796580658165826583658465856586658765886589659065916592659365946595659665976598659966006601660266036604660566066607660866096610661166126613661466156616661766186619662066216622662366246625662666276628662966306631663266336634663566366637663866396640664166426643664466456646664766486649665066516652665366546655665666576658665966606661666266636664666566666667666866696670667166726673667466756676667766786679668066816682668366846685668666876688668966906691669266936694669566966697669866996700670167026703670467056706670767086709671067116712671367146715671667176718671967206721672267236724672567266727672867296730673167326733673467356736673767386739674067416742674367446745674667476748674967506751675267536754675567566757675867596760676167626763676467656766676767686769677067716772677367746775677667776778677967806781678267836784678567866787678867896790679167926793679467956796679767986799680068016802680368046805680668076808680968106811681268136814681568166817681868196820682168226823682468256826682768286829683068316832683368346835683668376838683968406841684268436844684568466847684868496850685168526853685468556856685768586859686068616862686368646865686668676868686968706871687268736874687568766877687868796880688168826883688468856886688768886889689068916892689368946895689668976898689969006901690269036904690569066907690869096910691169126913691469156916691769186919692069216922692369246925692669276928692969306931693269336934693569366937693869396940694169426943694469456946694769486949695069516952695369546955695669576958695969606961696269636964696569666967696869696970697169726973697469756976697769786979698069816982698369846985698669876988698969906991699269936994699569966997699869997000700170027003700470057006700770087009701070117012701370147015701670177018701970207021702270237024702570267027702870297030703170327033703470357036703770387039704070417042704370447045704670477048704970507051705270537054705570567057705870597060706170627063706470657066706770687069707070717072707370747075707670777078707970807081708270837084708570867087708870897090709170927093709470957096709770987099710071017102710371047105710671077108710971107111711271137114711571167117711871197120712171227123712471257126712771287129713071317132713371347135713671377138713971407141714271437144714571467147714871497150715171527153715471557156715771587159716071617162716371647165716671677168716971707171717271737174717571767177717871797180718171827183718471857186718771887189719071917192719371947195719671977198719972007201720272037204720572067207720872097210721172127213721472157216721772187219722072217222722372247225722672277228722972307231723272337234723572367237723872397240724172427243724472457246724772487249725072517252725372547255725672577258725972607261726272637264726572667267726872697270727172727273727472757276727772787279728072817282728372847285728672877288728972907291729272937294729572967297729872997300730173027303730473057306730773087309731073117312731373147315731673177318731973207321732273237324732573267327732873297330733173327333733473357336733773387339734073417342734373447345734673477348734973507351735273537354735573567357735873597360736173627363736473657366736773687369737073717372737373747375737673777378737973807381738273837384738573867387738873897390739173927393739473957396739773987399740074017402740374047405740674077408740974107411741274137414741574167417741874197420742174227423742474257426742774287429743074317432743374347435743674377438743974407441744274437444744574467447744874497450745174527453745474557456745774587459746074617462746374647465746674677468746974707471747274737474747574767477747874797480748174827483748474857486748774887489749074917492749374947495749674977498749975007501750275037504750575067507750875097510751175127513751475157516751775187519752075217522752375247525752675277528752975307531753275337534753575367537753875397540754175427543754475457546754775487549755075517552755375547555755675577558755975607561756275637564756575667567756875697570757175727573757475757576757775787579758075817582758375847585758675877588758975907591759275937594759575967597759875997600760176027603760476057606760776087609761076117612761376147615761676177618761976207621762276237624762576267627762876297630763176327633763476357636763776387639764076417642764376447645764676477648764976507651765276537654765576567657765876597660766176627663766476657666766776687669767076717672767376747675767676777678767976807681768276837684768576867687768876897690769176927693769476957696769776987699770077017702770377047705770677077708770977107711771277137714771577167717771877197720772177227723772477257726772777287729773077317732773377347735773677377738773977407741774277437744774577467747774877497750775177527753775477557756775777587759776077617762776377647765776677677768776977707771777277737774777577767777777877797780778177827783778477857786778777887789779077917792779377947795779677977798779978007801780278037804780578067807780878097810781178127813781478157816781778187819782078217822782378247825782678277828782978307831783278337834783578367837783878397840784178427843784478457846784778487849785078517852785378547855785678577858785978607861786278637864786578667867786878697870787178727873787478757876787778787879788078817882788378847885788678877888788978907891789278937894789578967897789878997900790179027903790479057906790779087909791079117912791379147915791679177918791979207921792279237924792579267927792879297930793179327933793479357936793779387939794079417942794379447945794679477948794979507951795279537954795579567957795879597960796179627963796479657966796779687969797079717972797379747975797679777978797979807981798279837984798579867987798879897990799179927993799479957996799779987999800080018002800380048005800680078008800980108011801280138014801580168017801880198020802180228023802480258026802780288029803080318032803380348035803680378038803980408041804280438044804580468047804880498050805180528053805480558056805780588059806080618062806380648065806680678068806980708071807280738074807580768077807880798080808180828083808480858086808780888089809080918092809380948095809680978098809981008101810281038104810581068107810881098110811181128113811481158116811781188119812081218122812381248125812681278128812981308131813281338134813581368137813881398140814181428143814481458146814781488149815081518152815381548155815681578158815981608161816281638164816581668167816881698170817181728173817481758176817781788179818081818182818381848185818681878188818981908191819281938194819581968197819881998200820182028203820482058206820782088209821082118212821382148215821682178218821982208221822282238224822582268227822882298230823182328233823482358236823782388239824082418242824382448245824682478248824982508251825282538254825582568257825882598260826182628263826482658266826782688269827082718272827382748275827682778278827982808281828282838284828582868287828882898290829182928293829482958296829782988299830083018302830383048305830683078308830983108311831283138314831583168317831883198320832183228323832483258326832783288329833083318332833383348335833683378338833983408341834283438344834583468347834883498350835183528353835483558356835783588359836083618362836383648365836683678368836983708371837283738374837583768377837883798380838183828383838483858386838783888389839083918392839383948395839683978398839984008401840284038404840584068407840884098410841184128413841484158416841784188419842084218422842384248425842684278428842984308431843284338434843584368437843884398440844184428443844484458446844784488449845084518452845384548455845684578458845984608461846284638464846584668467846884698470847184728473847484758476847784788479848084818482848384848485848684878488848984908491849284938494849584968497849884998500850185028503850485058506850785088509851085118512851385148515851685178518851985208521852285238524852585268527852885298530853185328533853485358536853785388539854085418542854385448545854685478548854985508551855285538554855585568557855885598560856185628563856485658566856785688569857085718572857385748575857685778578857985808581858285838584858585868587858885898590859185928593859485958596859785988599860086018602860386048605860686078608860986108611861286138614861586168617861886198620862186228623862486258626862786288629863086318632863386348635863686378638863986408641864286438644864586468647864886498650865186528653865486558656865786588659866086618662866386648665866686678668866986708671867286738674867586768677867886798680868186828683868486858686868786888689869086918692869386948695869686978698869987008701870287038704870587068707870887098710871187128713871487158716871787188719872087218722872387248725872687278728872987308731873287338734873587368737873887398740874187428743874487458746874787488749875087518752875387548755875687578758875987608761876287638764876587668767876887698770877187728773877487758776877787788779878087818782878387848785878687878788878987908791879287938794879587968797879887998800880188028803880488058806880788088809881088118812881388148815881688178818881988208821882288238824882588268827882888298830883188328833883488358836883788388839884088418842884388448845884688478848884988508851885288538854885588568857885888598860886188628863886488658866886788688869887088718872887388748875887688778878887988808881888288838884888588868887888888898890889188928893889488958896889788988899890089018902890389048905890689078908890989108911891289138914891589168917891889198920892189228923892489258926892789288929893089318932893389348935893689378938893989408941894289438944894589468947894889498950895189528953895489558956895789588959896089618962896389648965896689678968896989708971897289738974897589768977897889798980898189828983898489858986898789888989899089918992899389948995899689978998899990009001900290039004900590069007900890099010901190129013901490159016901790189019902090219022902390249025902690279028902990309031903290339034903590369037903890399040904190429043904490459046904790489049905090519052905390549055905690579058905990609061906290639064906590669067906890699070907190729073907490759076907790789079908090819082908390849085908690879088908990909091909290939094909590969097909890999100910191029103910491059106910791089109911091119112911391149115911691179118911991209121912291239124912591269127912891299130913191329133913491359136913791389139914091419142914391449145914691479148914991509151915291539154915591569157915891599160916191629163916491659166916791689169917091719172917391749175917691779178917991809181918291839184918591869187918891899190919191929193919491959196919791989199920092019202920392049205920692079208920992109211921292139214921592169217921892199220922192229223922492259226922792289229923092319232923392349235923692379238923992409241924292439244924592469247924892499250925192529253925492559256925792589259926092619262926392649265
  1. This document summarizes new features and bugfixes in each stable release
  2. of Tor. If you want to see more detailed descriptions of the changes in
  3. each development snapshot, see the ChangeLog file.
  4. Changes in version 0.2.4.20 - 2013-12-22
  5. Tor 0.2.4.20 fixes potentially poor random number generation for users
  6. who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
  7. torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
  8. and 4) have no state file in their DataDirectory (as would happen on
  9. first start). Users who generated relay or hidden service identity
  10. keys in such a situation should discard them and generate new ones.
  11. This release also fixes a logic error that caused Tor clients to build
  12. many more preemptive circuits than they actually need.
  13. o Major bugfixes:
  14. - Do not allow OpenSSL engines to replace the PRNG, even when
  15. HardwareAccel is set. The only default builtin PRNG engine uses
  16. the Intel RDRAND instruction to replace the entire PRNG, and
  17. ignores all attempts to seed it with more entropy. That's
  18. cryptographically stupid: the right response to a new alleged
  19. entropy source is never to discard all previously used entropy
  20. sources. Fixes bug 10402; works around behavior introduced in
  21. OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
  22. and "rl1987".
  23. - Avoid launching spurious extra circuits when a stream is pending.
  24. This fixes a bug where any circuit that _wasn't_ unusable for new
  25. streams would be treated as if it were, causing extra circuits to
  26. be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
  27. o Minor bugfixes:
  28. - Avoid a crash bug when starting with a corrupted microdescriptor
  29. cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
  30. - If we fail to dump a previously cached microdescriptor to disk, avoid
  31. freeing duplicate data later on. Fixes bug 10423; bugfix on
  32. 0.2.4.13-alpha. Spotted by "bobnomnom".
  33. Changes in version 0.2.4.19 - 2013-12-11
  34. The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
  35. (1986-2013). Aaron worked on diverse projects including helping to guide
  36. Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
  37. transparency to the U.S government's PACER documents, and contributing
  38. design and development for Tor and Tor2Web. Aaron was one of the latest
  39. martyrs in our collective fight for civil liberties and human rights,
  40. and his death is all the more painful because he was one of us.
  41. Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
  42. a new circuit handshake and link encryption that use ECC to provide
  43. better security and efficiency; makes relays better manage circuit
  44. creation requests; uses "directory guards" to reduce client enumeration
  45. risks; makes bridges collect and report statistics about the pluggable
  46. transports they support; cleans up and improves our geoip database;
  47. gets much closer to IPv6 support for clients, bridges, and relays; makes
  48. directory authorities use measured bandwidths rather than advertised
  49. ones when computing flags and thresholds; disables client-side DNS
  50. caching to reduce tracking risks; and fixes a big bug in bridge
  51. reachability testing. This release introduces two new design
  52. abstractions in the code: a new "channel" abstraction between circuits
  53. and or_connections to allow for implementing alternate relay-to-relay
  54. transports, and a new "circuitmux" abstraction storing the queue of
  55. circuits for a channel. The release also includes many stability,
  56. security, and privacy fixes.
  57. o Major features (new circuit handshake):
  58. - Tor now supports a new circuit extension handshake designed by Ian
  59. Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
  60. circuit extension handshake, later called "TAP", was a bit slow
  61. (especially on the relay side), had a fragile security proof, and
  62. used weaker keys than we'd now prefer. The new circuit handshake
  63. uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
  64. function, making it significantly more secure than the older
  65. handshake, and significantly faster. Tor can use one of two built-in
  66. pure-C curve25519-donna implementations by Adam Langley, or it
  67. can link against the "nacl" library for a tuned version if present.
  68. The built-in version is very fast for 64-bit systems when building
  69. with GCC. The built-in 32-bit version is still faster than the
  70. old TAP protocol, but using libnacl is better on most such hosts.
  71. Implements proposal 216; closes ticket 7202.
  72. o Major features (better link encryption):
  73. - Relays can now enable the ECDHE TLS ciphersuites when available
  74. and appropriate. These ciphersuites let us negotiate forward-secure
  75. TLS secret keys more safely and more efficiently than with our
  76. previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
  77. public relays prefer the (faster) P224 group, and bridges prefer
  78. the (more common) P256 group; you can override this with the
  79. TLSECGroup option.
  80. This feature requires clients running 0.2.3.17-beta or later,
  81. and requires both sides to be running OpenSSL 1.0.0 or later
  82. with ECC support. OpenSSL 1.0.1, with the compile-time option
  83. "enable-ec_nistp_64_gcc_128", is highly recommended.
  84. Implements the relay side of proposal 198; closes ticket 7200.
  85. - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
  86. Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
  87. 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
  88. renegotiation from working with TLS 1.1 or 1.2, so we had disabled
  89. them to solve bug 6033.)
  90. o Major features (relay performance):
  91. - Instead of limiting the number of queued onionskins (aka circuit
  92. create requests) to a fixed, hard-to-configure number, we limit
  93. the size of the queue based on how many we expect to be able to
  94. process in a given amount of time. We estimate the time it will
  95. take to process an onionskin based on average processing time
  96. of previous onionskins. Closes ticket 7291. You'll never have to
  97. configure MaxOnionsPending again.
  98. - Relays process the new "NTor" circuit-level handshake requests
  99. with higher priority than the old "TAP" circuit-level handshake
  100. requests. We still process some TAP requests to not totally starve
  101. 0.2.3 clients when NTor becomes popular. A new consensus parameter
  102. "NumNTorsPerTAP" lets us tune the balance later if we need to.
  103. Implements ticket 9574.
  104. o Major features (client bootstrapping resilience):
  105. - Add a new "FallbackDir" torrc option to use when we can't use
  106. a directory mirror from the consensus (either because we lack a
  107. consensus, or because they're all down). Currently, all authorities
  108. are fallbacks by default, and there are no other default fallbacks,
  109. but that will change. This option will allow us to give clients a
  110. longer list of servers to try to get a consensus from when first
  111. connecting to the Tor network, and thereby reduce load on the
  112. directory authorities. Implements proposal 206, "Preconfigured
  113. directory sources for bootstrapping". We also removed the old
  114. "FallbackNetworkstatus" option, since we never got it working well
  115. enough to use it. Closes bug 572.
  116. - If we have no circuits open, use a relaxed timeout (the
  117. 95th-percentile cutoff) until a circuit succeeds. This heuristic
  118. should allow Tor to succeed at building circuits even when the
  119. network connection drastically changes. Should help with bug 3443.
  120. o Major features (use of guards):
  121. - Support directory guards (proposal 207): when possible, clients now
  122. use their entry guards for non-anonymous directory requests. This
  123. can help prevent client enumeration. Note that this behavior only
  124. works when we have a usable consensus directory, and when options
  125. about what to download are more or less standard. In the future we
  126. should re-bootstrap from our guards, rather than re-bootstrapping
  127. from the preconfigured list of directory sources that ships with
  128. Tor. Resolves ticket 6526.
  129. - Raise the default time that a client keeps an entry guard from
  130. "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
  131. 2012 paper. (We would make it even longer, but we need better client
  132. load balancing first.) Also, make the guard lifetime controllable
  133. via a new GuardLifetime torrc option and a GuardLifetime consensus
  134. parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
  135. o Major features (bridges with pluggable transports):
  136. - Bridges now report the pluggable transports they support to the
  137. bridge authority, so it can pass the supported transports on to
  138. bridgedb and/or eventually do reachability testing. Implements
  139. ticket 3589.
  140. - Automatically forward the TCP ports of pluggable transport
  141. proxies using tor-fw-helper if PortForwarding is enabled. Implements
  142. ticket 4567.
  143. o Major features (geoip database):
  144. - Maxmind began labelling Tor relays as being in country "A1",
  145. which breaks by-country node selection inside Tor. Now we use a
  146. script to replace "A1" ("Anonymous Proxy") entries in our geoip
  147. file with real country codes. This script fixes about 90% of "A1"
  148. entries automatically and uses manual country code assignments to
  149. fix the remaining 10%. See src/config/README.geoip for details.
  150. Fixes bug 6266.
  151. - Add GeoIP database for IPv6 addresses. The new config option
  152. is GeoIPv6File.
  153. - Update to the October 2 2013 Maxmind GeoLite Country database.
  154. o Major features (IPv6):
  155. - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
  156. IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
  157. to happen. Implements ticket 5535.
  158. - All kind of relays, not just bridges, can now advertise an IPv6
  159. OR port. Implements ticket 6362.
  160. - Relays can now exit to IPv6 addresses: make sure that you have IPv6
  161. connectivity, then set the IPv6Exit flag to 1. Also make sure your
  162. exit policy reads as you would like: the address * applies to all
  163. address families, whereas *4 is IPv4 address only, and *6 is IPv6
  164. addresses only. On the client side, you'll need to wait for enough
  165. exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
  166. and use Socks5. Closes ticket 5547, implements proposal 117 as
  167. revised in proposal 208.
  168. - Bridge authorities now accept IPv6 bridge addresses and include
  169. them in network status documents. Implements ticket 5534.
  170. - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
  171. o Major features (directory authorities):
  172. - Directory authorities now prefer using measured bandwidths to
  173. advertised ones when computing flags and thresholds. Resolves
  174. ticket 8273.
  175. - Directory authorities that vote measured bandwidths about more
  176. than a threshold number of relays now treat relays with
  177. unmeasured bandwidths as having bandwidth 0 when computing their
  178. flags. Resolves ticket 8435.
  179. - Directory authorities now support a new consensus method (17)
  180. where they cap the published bandwidth of relays for which
  181. insufficient bandwidth measurements exist. Fixes part of bug 2286.
  182. - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
  183. serve any v2 directory information. Now we can test disabling the
  184. old deprecated v2 directory format, and see whether doing so has
  185. any effect on network load. Begins to fix bug 6783.
  186. o Major features (build and portability):
  187. - Switch to a nonrecursive Makefile structure. Now instead of each
  188. Makefile.am invoking other Makefile.am's, there is a master
  189. Makefile.am that includes the others. This change makes our build
  190. process slightly more maintainable, and improves parallelism for
  191. building with make -j. Original patch by Stewart Smith; various
  192. fixes by Jim Meyering.
  193. - Where available, we now use automake's "silent" make rules by
  194. default, so that warnings are easier to spot. You can get the old
  195. behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
  196. - Resume building correctly with MSVC and Makefile.nmake. This patch
  197. resolves numerous bugs and fixes reported by ultramage, including
  198. 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
  199. o Security features:
  200. - Switch to a completely time-invariant approach for picking nodes
  201. weighted by bandwidth. Our old approach would run through the
  202. part of the loop after it had made its choice slightly slower
  203. than it ran through the part of the loop before it had made its
  204. choice. Addresses ticket 6538.
  205. - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
  206. by tor2web clients allows hidden services to identify tor2web
  207. clients through their repeated selection of the same rendezvous
  208. and introduction point circuit endpoints (their guards). Resolves
  209. ticket 6888.
  210. o Major bugfixes (relay denial of service):
  211. - When we have too much memory queued in circuits (according to a new
  212. MaxMemInCellQueues option), close the circuits that have the oldest
  213. queued cells, on the theory that those are most responsible for
  214. us running low on memory. This prevents us from running out of
  215. memory as a relay if circuits fill up faster than they can be
  216. drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
  217. Tor. This bug is a further fix beyond bug 6252, whose fix was
  218. merged into 0.2.3.21-rc.
  219. - Reject bogus create and relay cells with 0 circuit ID or 0 stream
  220. ID: these could be used to create unexpected streams and circuits
  221. which would count as "present" to some parts of Tor but "absent"
  222. to others, leading to zombie circuits and streams or to a bandwidth
  223. denial-of-service. Fixes bug 7889; bugfix on every released version
  224. of Tor. Reported by "oftc_must_be_destroyed".
  225. - Avoid a bug where our response to TLS renegotiation under certain
  226. network conditions could lead to a busy-loop, with 100% CPU
  227. consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
  228. o Major bugfixes (asserts, crashes, leaks):
  229. - Prevent the get_freelists() function from running off the end of
  230. the list of freelists if it somehow gets an unrecognized
  231. allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
  232. eugenis.
  233. - Avoid a memory leak where we would leak a consensus body when we
  234. find that a consensus which we couldn't previously verify due to
  235. missing certificates is now verifiable. Fixes bug 8719; bugfix
  236. on 0.2.0.10-alpha.
  237. - If we are unable to save a microdescriptor to the journal, do not
  238. drop it from memory and then reattempt downloading it. Fixes bug
  239. 9645; bugfix on 0.2.2.6-alpha.
  240. - Fix an assertion failure that would occur when disabling the
  241. ORPort setting on a running Tor process while accounting was
  242. enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
  243. - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
  244. when an exit connection with optimistic data succeeds immediately
  245. rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
  246. 0.2.3.1-alpha.
  247. - Fix a memory leak that would occur whenever a configuration
  248. option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
  249. o Major bugfixes (relay rate limiting):
  250. - When a TLS write is partially successful but incomplete, remember
  251. that the flushed part has been flushed, and notice that bytes were
  252. actually written. Reported and fixed pseudonymously. Fixes bug 7708;
  253. bugfix on Tor 0.1.0.5-rc.
  254. - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
  255. to 1GB/1GB. The previous defaults were intended to be "basically
  256. infinite", but it turns out they're now limiting our 100mbit+
  257. relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
  258. last time we raised it).
  259. - No longer stop reading or writing on cpuworker connections when
  260. our rate limiting buckets go empty. Now we should handle circuit
  261. handshake requests more promptly. Resolves bug 9731.
  262. o Major bugfixes (client-side privacy):
  263. - When we mark a circuit as unusable for new circuits, have it
  264. continue to be unusable for new circuits even if MaxCircuitDirtiness
  265. is increased too much at the wrong time, or the system clock jumps
  266. backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
  267. - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
  268. which have resolved to internal addresses") is set, apply that
  269. rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
  270. - When an exit relay rejects a stream with reason "exit policy", but
  271. we only know an exit policy summary (e.g. from the microdesc
  272. consensus) for it, do not mark the relay as useless for all exiting.
  273. Instead, mark just the circuit as unsuitable for that particular
  274. address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
  275. o Major bugfixes (stream isolation):
  276. - Allow applications to get proper stream isolation with
  277. IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
  278. username/password authentication also offer "no authentication". Tor
  279. had previously preferred "no authentication", so the applications
  280. never actually sent Tor their auth details. Now Tor selects
  281. username/password authentication if it's offered. You can disable
  282. this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
  283. bug 8117; bugfix on 0.2.3.3-alpha.
  284. - Follow the socks5 protocol when offering username/password
  285. authentication. The fix for bug 8117 exposed this bug, and it
  286. turns out real-world applications like Pidgin do care. Bugfix on
  287. 0.2.3.2-alpha; fixes bug 8879.
  288. o Major bugfixes (client circuit building):
  289. - Alter circuit build timeout measurement to start at the point
  290. where we begin the CREATE/CREATE_FAST step (as opposed to circuit
  291. initialization). This should make our timeout measurements more
  292. uniform. Previously, we were sometimes including ORconn setup time
  293. in our circuit build time measurements. Should resolve bug 3443.
  294. - If the circuit build timeout logic is disabled (via the consensus,
  295. or because we are an authority), then don't build testing circuits.
  296. Fixes bug 9657; bugfix on 0.2.2.14-alpha.
  297. o Major bugfixes (client-side DNS):
  298. - Turn off the client-side DNS cache by default. Updating and using
  299. the DNS cache is now configurable on a per-client-port
  300. level. SOCKSPort, DNSPort, etc lines may now contain
  301. {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
  302. cache these types of DNS answers when we receive them from an
  303. exit node in response to an application request on this port, and
  304. {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
  305. cached DNS answers of these types, we shouldn't use them. It's
  306. potentially risky to use cached DNS answers at the client, since
  307. doing so can indicate to one exit what answers we've gotten
  308. for DNS lookups in the past. With IPv6, this becomes especially
  309. problematic. Using cached DNS answers for requests on the same
  310. circuit would present less linkability risk, since all traffic
  311. on a circuit is already linkable, but it would also provide
  312. little performance benefit: the exit node caches DNS replies
  313. too. Implements a simplified version of Proposal 205. Implements
  314. ticket 7570.
  315. o Major bugfixes (hidden service privacy):
  316. - Limit hidden service descriptors to at most ten introduction
  317. points, to slow one kind of guard enumeration. Fixes bug 9002;
  318. bugfix on 0.1.1.11-alpha.
  319. o Major bugfixes (directory fetching):
  320. - If the time to download the next old-style networkstatus is in
  321. the future, do not decline to consider whether to download the
  322. next microdescriptor networkstatus. Fixes bug 9564; bugfix on
  323. 0.2.3.14-alpha.
  324. - We used to always request authority certificates by identity digest,
  325. meaning we'd get the newest one even when we wanted one with a
  326. different signing key. Then we would complain about being given
  327. a certificate we already had, and never get the one we really
  328. wanted. Now we use the "fp-sk/" resource as well as the "fp/"
  329. resource to request the one we want. Fixes bug 5595; bugfix on
  330. 0.2.0.8-alpha.
  331. o Major bugfixes (bridge reachability):
  332. - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
  333. previously they did not, which prevented them from receiving
  334. successful connections from relays for self-test or bandwidth
  335. testing. Also, when a relay is extending a circuit to a bridge,
  336. it needs to send a NETINFO cell, even when the bridge hasn't sent
  337. an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
  338. o Major bugfixes (control interface):
  339. - When receiving a new configuration file via the control port's
  340. LOADCONF command, do not treat the defaults file as absent.
  341. Fixes bug 9122; bugfix on 0.2.3.9-alpha.
  342. o Major bugfixes (directory authorities):
  343. - Stop marking every relay as having been down for one hour every
  344. time we restart a directory authority. These artificial downtimes
  345. were messing with our Stable and Guard flag calculations. Fixes
  346. bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
  347. - When computing directory thresholds, ignore any rejected-as-sybil
  348. nodes during the computation so that they can't influence Fast,
  349. Guard, etc. (We should have done this for proposal 109.) Fixes
  350. bug 8146.
  351. - When marking a node as a likely sybil, reset its uptime metrics
  352. to zero, so that it cannot time towards getting marked as Guard,
  353. Stable, or HSDir. (We should have done this for proposal 109.) Fixes
  354. bug 8147.
  355. - Fix a bug in the voting algorithm that could yield incorrect results
  356. when a non-naming authority declared too many flags. Fixes bug 9200;
  357. bugfix on 0.2.0.3-alpha.
  358. o Internal abstraction features:
  359. - Introduce new channel_t abstraction between circuits and
  360. or_connection_t to allow for implementing alternate OR-to-OR
  361. transports. A channel_t is an abstract object which can either be a
  362. cell-bearing channel, which is responsible for authenticating and
  363. handshaking with the remote OR and transmitting cells to and from
  364. it, or a listening channel, which spawns new cell-bearing channels
  365. at the request of remote ORs. Implements part of ticket 6465.
  366. - Make a channel_tls_t subclass of channel_t, adapting it to the
  367. existing or_connection_t code. The V2/V3 protocol handshaking
  368. code which formerly resided in command.c has been moved below the
  369. channel_t abstraction layer and may be found in channeltls.c now.
  370. Implements the rest of ticket 6465.
  371. - Introduce new circuitmux_t storing the queue of circuits for
  372. a channel; this encapsulates and abstracts the queue logic and
  373. circuit selection policy, and allows the latter to be overridden
  374. easily by switching out a policy object. The existing EWMA behavior
  375. is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
  376. o New build requirements:
  377. - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
  378. strongly recommended.
  379. - Tor maintainers now require Automake version 1.9 or later to build
  380. Tor from the Git repository. (Automake is not required when building
  381. from a source distribution.)
  382. o Minor features (protocol):
  383. - No longer include the "opt" prefix when generating routerinfos
  384. or v2 directories: it has been needless since Tor 0.1.2. Closes
  385. ticket 5124.
  386. - Reject EXTEND cells sent to nonexistent streams. According to the
  387. spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
  388. we were only checking for stream IDs that were currently in use.
  389. Found while hunting for more instances of bug 6271. Bugfix on
  390. 0.0.2pre8, which introduced incremental circuit construction.
  391. - Tor relays and clients now support a better CREATE/EXTEND cell
  392. format, allowing the sender to specify multiple address, identity,
  393. and handshake types. Implements Robert Ransom's proposal 200;
  394. closes ticket 7199.
  395. - Reject as invalid most directory objects containing a NUL.
  396. Belt-and-suspender fix for bug 8037.
  397. o Minor features (security):
  398. - Clear keys and key-derived material left on the stack in
  399. rendservice.c and rendclient.c. Check return value of
  400. crypto_pk_write_private_key_to_string() in rend_service_load_keys().
  401. These fixes should make us more forward-secure against cold-boot
  402. attacks and the like. Fixes bug 2385.
  403. - Use our own weak RNG when we need a weak RNG. Windows's rand() and
  404. Irix's random() only return 15 bits; Solaris's random() returns more
  405. bits but its RAND_MAX says it only returns 15, and so on. Motivated
  406. by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
  407. o Minor features (control protocol):
  408. - Add a "GETINFO signal/names" control port command. Implements
  409. ticket 3842.
  410. - Provide default values for all options via "GETINFO config/defaults".
  411. Implements ticket 4971.
  412. - Allow an optional $ before the node identity digest in the
  413. controller command GETINFO ns/id/<identity>, for consistency with
  414. md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
  415. - Add CACHED keyword to ADDRMAP events in the control protocol
  416. to indicate whether a DNS result will be cached or not. Resolves
  417. ticket 8596.
  418. - Generate bootstrapping status update events correctly when fetching
  419. microdescriptors. Fixes bug 9927.
  420. o Minor features (path selection):
  421. - When deciding whether we have enough descriptors to build circuits,
  422. instead of looking at raw relay counts, look at which fraction
  423. of (bandwidth-weighted) paths we're able to build. This approach
  424. keeps clients from building circuits if their paths are likely to
  425. stand out statistically. The default fraction of paths needed is
  426. taken from the consensus directory; you can override it with the
  427. new PathsNeededToBuildCircuits option. Fixes ticket 5956.
  428. - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
  429. and we have GeoIP information, also exclude all nodes with unknown
  430. countries "??" and "A1". This behavior is controlled by the
  431. new GeoIPExcludeUnknown option: you can make such nodes always
  432. excluded with "GeoIPExcludeUnknown 1", and disable the feature
  433. with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
  434. gets you the default behavior. Implements feature 7706.
  435. o Minor features (hidden services):
  436. - Improve circuit build timeout handling for hidden services.
  437. In particular: adjust build timeouts more accurately depending
  438. upon the number of hop-RTTs that a particular circuit type
  439. undergoes. Additionally, launch intro circuits in parallel
  440. if they timeout, and take the first one to reply as valid.
  441. - The Tor client now ignores sub-domain components of a .onion
  442. address. This change makes HTTP "virtual" hosting
  443. possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
  444. http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
  445. hosted on the same hidden service. Implements proposal 204.
  446. - Enable Tor to read configuration, state, and key information from
  447. a FIFO. Previously Tor would only read from files with a positive
  448. stat.st_size. Code from meejah; fixes bug 6044.
  449. o Minor features (clients):
  450. - Teach bridge-using clients to avoid 0.2.2.x bridges when making
  451. microdescriptor-related dir requests, and only fall back to normal
  452. descriptors if none of their bridges can handle microdescriptors
  453. (as opposed to the fix in ticket 4013, which caused them to fall
  454. back to normal descriptors if *any* of their bridges preferred
  455. them). Resolves ticket 4994.
  456. - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
  457. TCP ports to forward. In the past it only accepted two ports:
  458. the ORPort and the DirPort.
  459. o Minor features (protecting client timestamps):
  460. - Clients no longer send timestamps in their NETINFO cells. These were
  461. not used for anything, and they provided one small way for clients
  462. to be distinguished from each other as they moved from network to
  463. network or behind NAT. Implements part of proposal 222.
  464. - Clients now round timestamps in INTRODUCE cells down to the nearest
  465. 10 minutes. If a new Support022HiddenServices option is set to 0, or
  466. if it's set to "auto" and the feature is disabled in the consensus,
  467. the timestamp is sent as 0 instead. Implements part of proposal 222.
  468. - Stop sending timestamps in AUTHENTICATE cells. This is not such
  469. a big deal from a security point of view, but it achieves no actual
  470. good purpose, and isn't needed. Implements part of proposal 222.
  471. - Reduce down accuracy of timestamps in hidden service descriptors.
  472. Implements part of proposal 222.
  473. o Minor features (bridges):
  474. - Make bridge relays check once a minute for whether their IP
  475. address has changed, rather than only every 15 minutes. Resolves
  476. bugs 1913 and 1992.
  477. - Bridge statistics now count bridge clients connecting over IPv6:
  478. bridge statistics files now list "bridge-ip-versions" and
  479. extra-info documents list "geoip6-db-digest". The control protocol
  480. "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
  481. implementation by "shkoo", addressing ticket 5055.
  482. - Add a new torrc option "ServerTransportListenAddr" to let bridge
  483. operators select the address where their pluggable transports will
  484. listen for connections. Resolves ticket 7013.
  485. - Randomize the lifetime of our SSL link certificate, so censors can't
  486. use the static value for filtering Tor flows. Resolves ticket 8443;
  487. related to ticket 4014 which was included in 0.2.2.33.
  488. o Minor features (relays):
  489. - Option OutboundBindAddress can be specified multiple times and
  490. accepts IPv6 addresses. Resolves ticket 6876.
  491. o Minor features (IPv6, client side):
  492. - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
  493. prefer to hand out virtual IPv6 addresses, since there are more of
  494. them and we can't run out. To override this behavior and make IPv4
  495. addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
  496. or DNSPort you're using for resolving. Implements ticket 7571.
  497. - AutomapHostsOnResolve responses are now randomized, to avoid
  498. annoying situations where Tor is restarted and applications
  499. connect to the wrong addresses.
  500. - Never try more than 1000 times to pick a new virtual address when
  501. AutomapHostsOnResolve is set. That's good enough so long as we
  502. aren't close to handing out our entire virtual address space;
  503. if you're getting there, it's best to switch to IPv6 virtual
  504. addresses anyway.
  505. o Minor features (IPv6, relay/authority side):
  506. - New config option "AuthDirHasIPv6Connectivity 1" that directory
  507. authorities should set if they have IPv6 connectivity and want to
  508. do reachability tests for IPv6 relays. Implements feature 5974.
  509. - A relay with an IPv6 OR port now sends that address in NETINFO
  510. cells (in addition to its other address). Implements ticket 6364.
  511. o Minor features (directory authorities):
  512. - Directory authorities no long accept descriptors for any version of
  513. Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
  514. These versions are insecure, unsupported, or both. Implements
  515. ticket 6789.
  516. - When directory authorities are computing thresholds for flags,
  517. never let the threshold for the Fast flag fall below 4096
  518. bytes. Also, do not consider nodes with extremely low bandwidths
  519. when deciding thresholds for various directory flags. This change
  520. should raise our threshold for Fast relays, possibly in turn
  521. improving overall network performance; see ticket 1854. Resolves
  522. ticket 8145.
  523. - Directory authorities now include inside each vote a statement of
  524. the performance thresholds they used when assigning flags.
  525. Implements ticket 8151.
  526. - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
  527. in directory authority votes to describe whether they have enough
  528. measured bandwidths to ignore advertised (relay descriptor)
  529. bandwidth claims. Resolves ticket 8711.
  530. o Minor features (path bias detection):
  531. - Path Use Bias: Perform separate accounting for successful circuit
  532. use. Keep separate statistics on stream attempt rates versus stream
  533. success rates for each guard. Provide configurable thresholds to
  534. determine when to emit log messages or disable use of guards that
  535. fail too many stream attempts. Resolves ticket 7802.
  536. - Create three levels of Path Bias log messages, as opposed to just
  537. two. These are configurable via consensus as well as via the torrc
  538. options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
  539. The default values are 0.70, 0.50, and 0.30 respectively.
  540. - Separate the log message levels from the decision to drop guards,
  541. which also is available via torrc option PathBiasDropGuards.
  542. PathBiasDropGuards still defaults to 0 (off).
  543. - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
  544. in combination with PathBiasExtremeRate.
  545. - Increase the default values for PathBiasScaleThreshold and
  546. PathBiasCircThreshold from (200, 20) to (300, 150).
  547. - Add in circuit usage accounting to path bias. If we try to use a
  548. built circuit but fail for any reason, it counts as path bias.
  549. Certain classes of circuits where the adversary gets to pick your
  550. destination node are exempt from this accounting. Usage accounting
  551. can be specifically disabled via consensus parameter or torrc.
  552. - Convert all internal path bias state to double-precision floating
  553. point, to avoid roundoff error and other issues.
  554. - Only record path bias information for circuits that have completed
  555. *two* hops. Assuming end-to-end tagging is the attack vector, this
  556. makes us more resilient to ambient circuit failure without any
  557. detection capability loss.
  558. o Minor features (build):
  559. - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
  560. dhill. Resolves ticket 6982.
  561. - Compile on win64 using mingw64. Fixes bug 7260; patches from
  562. "yayooo".
  563. - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
  564. separate error codes; or at least, don't break for that reason.
  565. Fixes bug 7935. Reported by "oftc_must_be_destroyed".
  566. o Build improvements (autotools):
  567. - Warn if building on a platform with an unsigned time_t: there
  568. are too many places where Tor currently assumes that time_t can
  569. hold negative values. We'd like to fix them all, but probably
  570. some will remain.
  571. - Do not report status verbosely from autogen.sh unless the -v flag
  572. is specified. Fixes issue 4664. Patch from Onizuka.
  573. - Detect and reject attempts to build Tor with threading support
  574. when OpenSSL has been compiled without threading support.
  575. Fixes bug 6673.
  576. - Try to detect if we are ever building on a platform where
  577. memset(...,0,...) does not set the value of a double to 0.0. Such
  578. platforms are permitted by the C standard, though in practice
  579. they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
  580. currently support them, but it's better to detect them and fail
  581. than to perform erroneously.
  582. - We no longer warn so much when generating manpages from their
  583. asciidoc source.
  584. - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
  585. the signs of types during autoconf. This is better than our old
  586. approach, which didn't work when cross-compiling.
  587. o Minor features (log messages, warnings):
  588. - Detect when we're running with a version of OpenSSL other than the
  589. one we compiled with. This conflict has occasionally given people
  590. hard-to-track-down errors.
  591. - Warn users who run hidden services on a Tor client with
  592. UseEntryGuards disabled that their hidden services will be
  593. vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
  594. attack which motivated Tor to support entry guards in the first
  595. place). Resolves ticket 6889.
  596. - Warn when we are binding low ports when hibernation is enabled;
  597. previously we had warned when we were _advertising_ low ports with
  598. hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
  599. - Issue a warning when running with the bufferevents backend enabled.
  600. It's still not stable, and people should know that they're likely
  601. to hit unexpected problems. Closes ticket 9147.
  602. o Minor features (log messages, notices):
  603. - Refactor resolve_my_address() so it returns the method by which we
  604. decided our public IP address (explicitly configured, resolved from
  605. explicit hostname, guessed from interfaces, learned by gethostname).
  606. Now we can provide more helpful log messages when a relay guesses
  607. its IP address incorrectly (e.g. due to unexpected lines in
  608. /etc/hosts). Resolves ticket 2267.
  609. - Track how many "TAP" and "NTor" circuit handshake requests we get,
  610. and how many we complete, and log it every hour to help relay
  611. operators follow trends in network load. Addresses ticket 9658.
  612. o Minor features (log messages, diagnostics):
  613. - If we fail to free a microdescriptor because of bug 7164, log
  614. the filename and line number from which we tried to free it.
  615. - We compute the overhead from passing onionskins back and forth to
  616. cpuworkers, and report it when dumping statistics in response to
  617. SIGUSR1. Supports ticket 7291.
  618. - Add another diagnostic to the heartbeat message: track and log
  619. overhead that TLS is adding to the data we write. If this is
  620. high, we are sending too little data to SSL_write at a time.
  621. Diagnostic for bug 7707.
  622. - Log packaged cell fullness as part of the heartbeat message.
  623. Diagnosis to try to determine the extent of bug 7743.
  624. - Add more detail to a log message about relaxed timeouts, to help
  625. track bug 7799.
  626. - When learning a fingerprint for a bridge, log its corresponding
  627. transport type. Implements ticket 7896.
  628. - Warn more aggressively when flushing microdescriptors to a
  629. microdescriptor cache fails, in an attempt to mitigate bug 8031,
  630. or at least make it more diagnosable.
  631. - Improve the log message when "Bug/attack: unexpected sendme cell
  632. from client" occurs, to help us track bug 8093.
  633. - Improve debugging output to help track down bug 8185 ("Bug:
  634. outgoing relay cell has n_chan==NULL. Dropping.")
  635. o Minor features (log messages, quieter bootstrapping):
  636. - Log fewer lines at level "notice" about our OpenSSL and Libevent
  637. versions and capabilities when everything is going right. Resolves
  638. part of ticket 6736.
  639. - Omit the first heartbeat log message, because it never has anything
  640. useful to say, and it clutters up the bootstrapping messages.
  641. Resolves ticket 6758.
  642. - Don't log about reloading the microdescriptor cache at startup. Our
  643. bootstrap warnings are supposed to tell the user when there's a
  644. problem, and our bootstrap notices say when there isn't. Resolves
  645. ticket 6759; bugfix on 0.2.2.6-alpha.
  646. - Don't log "I learned some more directory information" when we're
  647. reading cached directory information. Reserve it for when new
  648. directory information arrives in response to a fetch. Resolves
  649. ticket 6760.
  650. - Don't complain about bootstrapping problems while hibernating.
  651. These complaints reflect a general code problem, but not one
  652. with any problematic effects (no connections are actually
  653. opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
  654. o Minor features (testing):
  655. - In our testsuite, create temporary directories with a bit more
  656. entropy in their name to make name collisions less likely. Fixes
  657. bug 8638.
  658. - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
  659. (P-256) Diffie-Hellman handshakes to src/or/bench.
  660. - Add benchmark functions to test onion handshake performance.
  661. o Renamed options:
  662. - The DirServer option is now DirAuthority, for consistency with
  663. current naming patterns. You can still use the old DirServer form.
  664. o Minor bugfixes (protocol):
  665. - Fix the handling of a TRUNCATE cell when it arrives while the
  666. circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
  667. - When a Tor client gets a "truncated" relay cell, the first byte of
  668. its payload specifies why the circuit was truncated. We were
  669. ignoring this 'reason' byte when tearing down the circuit, resulting
  670. in the controller not being told why the circuit closed. Now we
  671. pass the reason from the truncated cell to the controller. Bugfix
  672. on 0.1.2.3-alpha; fixes bug 7039.
  673. - Fix a misframing issue when reading the version numbers in a
  674. VERSIONS cell. Previously we would recognize [00 01 00 02] as
  675. 'version 1, version 2, and version 0x100', when it should have
  676. only included versions 1 and 2. Fixes bug 8059; bugfix on
  677. 0.2.0.10-alpha. Reported pseudonymously.
  678. - Make the format and order of STREAM events for DNS lookups
  679. consistent among the various ways to launch DNS lookups. Fixes
  680. bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
  681. o Minor bugfixes (syscalls and disk interaction):
  682. - Always check the return values of functions fcntl() and
  683. setsockopt(). We don't believe these are ever actually failing in
  684. practice, but better safe than sorry. Also, checking these return
  685. values should please analysis tools like Coverity. Patch from
  686. 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
  687. - Avoid double-closing the listener socket in our socketpair()
  688. replacement (used on Windows) in the case where the addresses on
  689. our opened sockets don't match what we expected. Fixes bug 9400;
  690. bugfix on 0.0.2pre7. Found by Coverity.
  691. - Correctly store microdescriptors and extrainfo descriptors that
  692. include an internal NUL byte. Fixes bug 8037; bugfix on
  693. 0.2.0.1-alpha. Bug reported by "cypherpunks".
  694. - If for some reason we fail to write a microdescriptor while
  695. rebuilding the cache, do not let the annotations from that
  696. microdescriptor linger in the cache file, and do not let the
  697. microdescriptor stay recorded as present in its old location.
  698. Fixes bug 9047; bugfix on 0.2.2.6-alpha.
  699. - Use direct writes rather than stdio when building microdescriptor
  700. caches, in an attempt to mitigate bug 8031, or at least make it
  701. less common.
  702. o Minor fixes (config options):
  703. - Warn and fail if a server is configured not to advertise any
  704. ORPorts at all. (We need *something* to put in our descriptor,
  705. or we just won't work.)
  706. - Behave correctly when the user disables LearnCircuitBuildTimeout
  707. but doesn't tell us what they would like the timeout to be. Fixes
  708. bug 6304; bugfix on 0.2.2.14-alpha.
  709. - Rename the (internal-use-only) UsingTestingNetworkDefaults option
  710. to start with a triple-underscore so the controller won't touch it.
  711. Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
  712. - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
  713. so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
  714. - When autodetecting the number of CPUs, use the number of available
  715. CPUs in preference to the number of configured CPUs. Inform the
  716. user if this reduces the number of available CPUs. Fixes bug 8002;
  717. bugfix on 0.2.3.1-alpha.
  718. - Command-line option "--version" implies "--quiet". Fixes bug 6997.
  719. - Make it an error when you set EntryNodes but disable UseGuardNodes,
  720. since it will (surprisingly to some users) ignore EntryNodes. Fixes
  721. bug 8180; bugfix on 0.2.3.11-alpha.
  722. - Avoid overflows when the user sets MaxCircuitDirtiness to a
  723. ridiculously high value, by imposing a (ridiculously high) 30-day
  724. maximum on MaxCircuitDirtiness.
  725. o Minor bugfixes (control protocol):
  726. - Stop sending a stray "(null)" in some cases for the server status
  727. "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
  728. on 0.1.2.6-alpha.
  729. - The ADDRMAP command can no longer generate an ill-formed error
  730. code on a failed MAPADDRESS. It now says "internal" rather than
  731. an English sentence fragment with spaces in the middle. Bugfix on
  732. Tor 0.2.0.19-alpha.
  733. o Minor bugfixes (clients / edges):
  734. - When we receive a RELAY_END cell with the reason DONE, or with no
  735. reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
  736. status as "connection refused". Previously we reported these cases
  737. as success but then immediately closed the connection. Fixes bug
  738. 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
  739. - If the guard we choose first doesn't answer, we would try the
  740. second guard, but once we connected to the second guard we would
  741. abandon it and retry the first one, slowing down bootstrapping.
  742. The fix is to treat all our initially chosen guards as acceptable
  743. to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
  744. - When choosing which stream on a formerly stalled circuit to wake
  745. first, make better use of the platform's weak RNG. Previously,
  746. we had been using the % ("modulo") operator to try to generate a
  747. 1/N chance of picking each stream, but this behaves badly with
  748. many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
  749. 0.2.2.20-alpha.
  750. o Minor bugfixes (path bias detection):
  751. - If the state file's path bias counts are invalid (presumably from a
  752. buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
  753. additional checks and log messages to the scaling of Path Bias
  754. counts, in case there still are remaining issues with scaling.
  755. Should help resolve bug 8235.
  756. - Prevent rounding error in path bias counts when scaling
  757. them down, and use the correct scale factor default. Also demote
  758. some path bias related log messages down a level and make others
  759. less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
  760. - Remove a source of rounding error during path bias count scaling;
  761. don't count cannibalized circuits as used for path bias until we
  762. actually try to use them; and fix a circuit_package_relay_cell()
  763. warning message about n_chan==NULL. Fixes bug 7802.
  764. - Paste the description for PathBias parameters from the man
  765. page into or.h, so the code documents them too. Fixes bug 7982;
  766. bugfix on 0.2.3.17-beta.
  767. o Minor bugfixes (relays):
  768. - Stop trying to resolve our hostname so often (e.g. every time we
  769. think about doing a directory fetch). Now we reuse the cached
  770. answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
  771. and 2410 (bugfix on 0.1.2.2-alpha).
  772. - When examining the list of network interfaces to find our address,
  773. do not consider non-running or disabled network interfaces. Fixes
  774. bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
  775. o Minor bugfixes (blocking resistance):
  776. - Only disable TLS session ticket support when running as a TLS
  777. server. Now clients will blend better with regular Firefox
  778. connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
  779. o Minor bugfixes (IPv6):
  780. - Use square brackets around IPv6 addresses in numerous places
  781. that needed them, including log messages, HTTPS CONNECT proxy
  782. requests, TransportProxy statefile entries, and pluggable transport
  783. extra-info lines. Fixes bug 7011; patch by David Fifield.
  784. o Minor bugfixes (directory authorities):
  785. - Reject consensus votes with more than 64 known-flags. We aren't even
  786. close to that limit yet, and our code doesn't handle it correctly.
  787. Fixes bug 6833; bugfix on 0.2.0.1-alpha.
  788. - Correctly handle votes with more than 31 flags. Fixes bug 6853;
  789. bugfix on 0.2.0.3-alpha.
  790. o Minor bugfixes (memory leaks):
  791. - Avoid leaking memory if we fail to compute a consensus signature
  792. or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
  793. - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
  794. on 0.2.1.1-alpha; fixes bug 7816.
  795. - Fix a memory leak during safe-cookie controller authentication.
  796. Bugfix on 0.2.3.13-alpha; fixes bug 7816.
  797. - Free some more still-in-use memory at exit, to make hunting for
  798. memory leaks easier. Resolves bug 7029.
  799. o Minor bugfixes (code correctness):
  800. - Increase the width of the field used to remember a connection's
  801. link protocol version to two bytes. Harmless for now, since the
  802. only currently recognized versions are one byte long. Reported
  803. pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
  804. - Fix a crash when debugging unit tests on Windows: deallocate a
  805. shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
  806. bugfix on 0.2.2.17-alpha. Reported by "ultramage".
  807. - When detecting the largest possible file descriptor (in order to
  808. close all file descriptors when launching a new program), actually
  809. use _SC_OPEN_MAX. The old code for doing this was very, very broken.
  810. Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
  811. is CID 743383.
  812. - Avoid a crash if we fail to generate an extrainfo descriptor.
  813. Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
  814. this is CID 718634.
  815. - Avoid an off-by-one error when checking buffer boundaries when
  816. formatting the exit status of a pluggable transport helper.
  817. This is probably not an exploitable bug, but better safe than
  818. sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
  819. Pedro Ribeiro.
  820. - Get rid of a couple of harmless clang warnings, where we compared
  821. enums to ints. These warnings are newly introduced in clang 3.2.
  822. o Minor bugfixes (code cleanliness):
  823. - Avoid use of reserved identifiers in our C code. The C standard
  824. doesn't like us declaring anything that starts with an
  825. underscore, so let's knock it off before we get in trouble. Fix
  826. for bug 1031; bugfix on the first Tor commit.
  827. - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
  828. with large values. This situation was untriggered, but nevertheless
  829. incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
  830. - Fix an impossible buffer overrun in the AES unit tests. Fixes
  831. bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
  832. - Fix handling of rendezvous client authorization types over 8.
  833. Fixes bug 6861; bugfix on 0.2.1.5-alpha.
  834. - Remove a couple of extraneous semicolons that were upsetting the
  835. cparser library. Patch by Christian Grothoff. Fixes bug 7115;
  836. bugfix on 0.2.2.1-alpha.
  837. - When complaining about a client port on a public address, log
  838. which address we're complaining about. Fixes bug 4020; bugfix on
  839. 0.2.3.3-alpha. Patch by Tom Fitzhenry.
  840. o Minor bugfixes (log messages, warnings):
  841. - If we encounter a write failure on a SOCKS connection before we
  842. finish our SOCKS handshake, don't warn that we closed the
  843. connection before we could send a SOCKS reply. Fixes bug 8427;
  844. bugfix on 0.1.0.1-rc.
  845. - Fix a directory authority warn caused when we have a large amount
  846. of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
  847. - Downgrade "Failed to hand off onionskin" messages to "debug"
  848. severity, since they're typically redundant with the "Your computer
  849. is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
  850. - Avoid spurious warnings when configuring multiple client ports of
  851. which only some are nonlocal. Previously, we had claimed that some
  852. were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
  853. 0.2.3.3-alpha.
  854. o Minor bugfixes (log messages, other):
  855. - Fix log messages and comments to avoid saying "GMT" when we mean
  856. "UTC". Fixes bug 6113.
  857. - When rejecting a configuration because we were unable to parse a
  858. quoted string, log an actual error message. Fixes bug 7950; bugfix
  859. on 0.2.0.16-alpha.
  860. - Correctly recognize that [::1] is a loopback address. Fixes
  861. bug 8377; bugfix on 0.2.1.3-alpha.
  862. - Don't log inappropriate heartbeat messages when hibernating: a
  863. hibernating node is _expected_ to drop out of the consensus,
  864. decide it isn't bootstrapped, and so forth. Fixes bug 7302;
  865. bugfix on 0.2.3.1-alpha.
  866. - Eliminate several instances where we use "Nickname=ID" to refer to
  867. nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
  868. "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
  869. on 0.2.3.21-rc.
  870. o Minor bugfixes (build):
  871. - Fix some bugs in tor-fw-helper-natpmp when trying to build and
  872. run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
  873. Fixes bug 7280; bugfix on 0.2.3.1-alpha.
  874. o Documentation fixes:
  875. - Make the torify manpage no longer refer to tsocks; torify hasn't
  876. supported tsocks since 0.2.3.14-alpha.
  877. - Make the tor manpage no longer reference tsocks.
  878. - Fix the GeoIPExcludeUnknown documentation to refer to
  879. ExcludeExitNodes rather than the currently nonexistent
  880. ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
  881. - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
  882. 0.2.3.14-alpha.
  883. - Say "KBytes" rather than "KB" in the man page (for various values
  884. of K), to further reduce confusion about whether Tor counts in
  885. units of memory or fractions of units of memory. Resolves ticket 7054.
  886. - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
  887. names match. Fixes bug 7768.
  888. - Fix the documentation of HeartbeatPeriod to say that the heartbeat
  889. message is logged at notice, not at info.
  890. - Clarify the usage and risks of setting the ContactInfo torrc line
  891. for your relay or bridge. Resolves ticket 9854.
  892. - Add anchors to the manpage so we can link to the html version of
  893. the documentation for specific options. Resolves ticket 9866.
  894. - Replace remaining references to DirServer in man page and
  895. log entries. Resolves ticket 10124.
  896. o Removed features:
  897. - Stop exporting estimates of v2 and v3 directory traffic shares
  898. in extrainfo documents. They were unneeded and sometimes inaccurate.
  899. Also stop exporting any v2 directory request statistics. Resolves
  900. ticket 5823.
  901. - Drop support for detecting and warning about versions of Libevent
  902. before 1.3e. Nothing reasonable ships with them any longer; warning
  903. the user about them shouldn't be needed. Resolves ticket 6826.
  904. - Now that all versions before 0.2.2.x are disallowed, we no longer
  905. need to work around their missing features. Remove a bunch of
  906. compatibility code.
  907. o Removed files:
  908. - The tor-tsocks.conf is no longer distributed or installed. We
  909. recommend that tsocks users use torsocks instead. Resolves
  910. ticket 8290.
  911. - Remove some of the older contents of doc/ as obsolete; move others
  912. to torspec.git. Fixes bug 8965.
  913. o Code simplification:
  914. - Avoid using character buffers when constructing most directory
  915. objects: this approach was unwieldy and error-prone. Instead,
  916. build smartlists of strings, and concatenate them when done.
  917. - Rename "isin" functions to "contains", for grammar. Resolves
  918. ticket 5285.
  919. - Rename Tor's logging function log() to tor_log(), to avoid conflicts
  920. with the natural logarithm function from the system libm. Resolves
  921. ticket 7599.
  922. - Start using OpenBSD's implementation of queue.h, so that we don't
  923. need to hand-roll our own pointer and list structures whenever we
  924. need them. (We can't rely on a sys/queue.h, since some operating
  925. systems don't have them, and the ones that do have them don't all
  926. present the same extensions.)
  927. - Start using OpenBSD's implementation of queue.h (originally by
  928. Niels Provos).
  929. - Enhance our internal sscanf replacement so that we can eliminate
  930. the last remaining uses of the system sscanf. (Though those uses
  931. of sscanf were safe, sscanf itself is generally error prone, so
  932. we want to eliminate when we can.) Fixes ticket 4195 and Coverity
  933. CID 448.
  934. - Replace all calls to snprintf() outside of src/ext with
  935. tor_snprintf(). Also remove the #define to replace snprintf with
  936. _snprintf on Windows; they have different semantics, and all of
  937. our callers should be using tor_snprintf() anyway. Fixes bug 7304.
  938. o Refactoring:
  939. - Add a wrapper function for the common "log a message with a
  940. rate-limit" case.
  941. - Split the onion.c file into separate modules for the onion queue
  942. and the different handshakes it supports.
  943. - Move the client-side address-map/virtual-address/DNS-cache code
  944. out of connection_edge.c into a new addressmap.c module.
  945. - Move the entry node code from circuitbuild.c to its own file.
  946. - Move the circuit build timeout tracking code from circuitbuild.c
  947. to its own file.
  948. - Source files taken from other packages now reside in src/ext;
  949. previously they were scattered around the rest of Tor.
  950. - Move the generic "config" code into a new file, and have "config.c"
  951. hold only torrc- and state-related code. Resolves ticket 6823.
  952. - Move the core of our "choose a weighted element at random" logic
  953. into its own function, and give it unit tests. Now the logic is
  954. testable, and a little less fragile too.
  955. - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
  956. - Move last_reachable and testing_since from routerinfo_t to node_t.
  957. Implements ticket 5529.
  958. - Add replaycache_t structure, functions and unit tests, then refactor
  959. rend_service_introduce() to be more clear to read, improve, debug,
  960. and test. Resolves bug 6177.
  961. o Removed code:
  962. - Remove some now-needless code that tried to aggressively flush
  963. OR connections as data was added to them. Since 0.2.0.1-alpha, our
  964. cell queue logic has saved us from the failure mode that this code
  965. was supposed to prevent. Removing this code will limit the number
  966. of baroque control flow paths through Tor's network logic. Reported
  967. pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
  968. - Remove unused code for parsing v1 directories and "running routers"
  969. documents. Fixes bug 6887.
  970. - Remove the marshalling/unmarshalling code for sending requests to
  971. cpuworkers over a socket, and instead just send structs. The
  972. recipient will always be the same Tor binary as the sender, so
  973. any encoding is overkill.
  974. - Remove the testing_since field of node_t, which hasn't been used
  975. for anything since 0.2.0.9-alpha.
  976. - Finally remove support for malloc_good_size and malloc_usable_size.
  977. We had hoped that these functions would let us eke a little more
  978. memory out of our malloc implementation. Unfortunately, the only
  979. implementations that provided these functions are also ones that
  980. are already efficient about not overallocation: they never got us
  981. more than 7 or so bytes per allocation. Removing them saves us a
  982. little code complexity and a nontrivial amount of build complexity.
  983. Changes in version 0.2.3.25 - 2012-11-19
  984. The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
  985. Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
  986. Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
  987. programmer, and friend. Unstinting in his dedication to the cause of
  988. freedom, he inspired and helped many of us as we began our work on
  989. anonymity, and inspires us still. Please honor his memory by writing
  990. software to protect people's freedoms, and by helping others to do so.
  991. Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
  992. significantly reduced directory overhead (via microdescriptors),
  993. enormous crypto performance improvements for fast relays on new
  994. enough hardware, a new v3 TLS handshake protocol that can better
  995. resist fingerprinting, support for protocol obfuscation plugins (aka
  996. pluggable transports), better scalability for hidden services, IPv6
  997. support for bridges, performance improvements like allowing clients
  998. to skip the first round-trip on the circuit ("optimistic data") and
  999. refilling token buckets more often, a new "stream isolation" design
  1000. to isolate different applications on different circuits, and many
  1001. stability, security, and privacy fixes.
  1002. Major features (v3 directory protocol):
  1003. - Clients now use microdescriptors instead of regular descriptors
  1004. to build circuits. Microdescriptors are authority-generated
  1005. summaries of regular descriptors' contents, designed to change very
  1006. rarely (see proposal 158 for details). This feature is designed
  1007. to save bandwidth, especially for clients on slow internet
  1008. connections. Use "UseMicrodescriptors 0" to disable it.
  1009. - Caches now download, cache, and serve microdescriptors, as well
  1010. as multiple "flavors" of the consensus, including a flavor that
  1011. describes microdescriptors.
  1012. o Major features (build hardening):
  1013. - Enable gcc and ld hardening by default. Resolves ticket 5210.
  1014. o Major features (relay scaling):
  1015. - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
  1016. instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
  1017. vectorized AES implementations as appropriate. These can be much,
  1018. much faster than other AES implementations.
  1019. - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
  1020. implementation. It makes AES_CTR about 7% faster than our old one
  1021. (which was about 10% faster than the one OpenSSL used to provide).
  1022. Resolves ticket 4526.
  1023. - Use OpenSSL's EVP interface for AES encryption, so that all AES
  1024. operations can use hardware acceleration (if present). Resolves
  1025. ticket 4442.
  1026. - Unconditionally use OpenSSL's AES implementation instead of our
  1027. old built-in one. OpenSSL's AES has been better for a while, and
  1028. relatively few servers should still be on any version of OpenSSL
  1029. that doesn't have good optimized assembly AES.
  1030. o Major features (blocking resistance):
  1031. - Update TLS cipher list to match Firefox 8 and later. Resolves
  1032. ticket 4744.
  1033. - Remove support for clients falsely claiming to support standard
  1034. ciphersuites that they can actually provide. As of modern OpenSSL
  1035. versions, it's not necessary to fake any standard ciphersuite,
  1036. and doing so prevents us from using better ciphersuites in the
  1037. future, since servers can't know whether an advertised ciphersuite
  1038. is really supported or not. Some hosts -- notably, ones with very
  1039. old versions of OpenSSL or where OpenSSL has been built with ECC
  1040. disabled -- will stand out because of this change; TBB users should
  1041. not be affected. Implements the client side of proposal 198.
  1042. - Implement a new handshake protocol (v3) for authenticating Tors to
  1043. each other over TLS. It should be more resistant to fingerprinting
  1044. than previous protocols, and should require less TLS hacking for
  1045. future Tor implementations. Implements proposal 176.
  1046. - Allow variable-length padding cells, to disguise the length of
  1047. Tor's TLS records. Implements part of proposal 184.
  1048. - While we're trying to bootstrap, record how many TLS connections
  1049. fail in each state, and report which states saw the most failures
  1050. in response to any bootstrap failures. This feature may speed up
  1051. diagnosis of censorship events. Implements ticket 3116.
  1052. o Major features (pluggable transports):
  1053. - Clients and bridges can now be configured to use a separate
  1054. "transport" proxy. This approach makes the censorship arms race
  1055. easier by allowing bridges to use protocol obfuscation plugins.
  1056. Implements proposal 180 (tickets 2841 and 3472).
  1057. o Major features (DoS resistance):
  1058. - Now that Tor 0.2.0.x is completely deprecated, enable the final
  1059. part of "Proposal 110: Avoiding infinite length circuits" by
  1060. refusing all circuit-extend requests that do not use a relay_early
  1061. cell. This change helps Tor resist a class of denial-of-service
  1062. attacks by limiting the maximum circuit length.
  1063. - Tear down the circuit if we get an unexpected SENDME cell. Clients
  1064. could use this trick to make their circuits receive cells faster
  1065. than our flow control would have allowed, or to gum up the network,
  1066. or possibly to do targeted memory denial-of-service attacks on
  1067. entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
  1068. from July 2002, before the release of Tor 0.0.0.
  1069. o Major features (hidden services):
  1070. - Adjust the number of introduction points that a hidden service
  1071. will try to maintain based on how long its introduction points
  1072. remain in use and how many introductions they handle. Fixes
  1073. part of bug 3825.
  1074. - Add a "tor2web mode" for clients that want to connect to hidden
  1075. services non-anonymously (and possibly more quickly). As a safety
  1076. measure to try to keep users from turning this on without knowing
  1077. what they are doing, tor2web mode must be explicitly enabled at
  1078. compile time, and a copy of Tor compiled to run in tor2web mode
  1079. cannot be used as a normal Tor client. Implements feature 2553.
  1080. o Major features (IPv6):
  1081. - Clients can now connect to private bridges over IPv6. Bridges
  1082. still need at least one IPv4 address in order to connect to
  1083. other relays. Note that we don't yet handle the case where the
  1084. user has two bridge lines for the same bridge (one IPv4, one
  1085. IPv6). Implements parts of proposal 186.
  1086. o Major features (directory authorities):
  1087. - Use a more secure consensus parameter voting algorithm. Now at
  1088. least three directory authorities or a majority of them must
  1089. vote on a given parameter before it will be included in the
  1090. consensus. Implements proposal 178.
  1091. - Remove the artificially low cutoff of 20KB to guarantee the Fast
  1092. flag. In the past few years the average relay speed has picked
  1093. up, and while the "top 7/8 of the network get the Fast flag" and
  1094. "all relays with 20KB or more of capacity get the Fast flag" rules
  1095. used to have the same result, now the top 7/8 of the network has
  1096. a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
  1097. o Major features (performance):
  1098. - Exit nodes now accept and queue data on not-yet-connected streams.
  1099. Previously, the client wasn't allowed to send data until the
  1100. stream was connected, which slowed down all connections. This
  1101. change will enable clients to perform a "fast-start" on streams
  1102. and send data without having to wait for a confirmation that the
  1103. stream has opened. Patch from Ian Goldberg; implements the server
  1104. side of Proposal 174.
  1105. - When using an exit relay running 0.2.3.x, clients can now
  1106. "optimistically" send data before the exit relay reports that
  1107. the stream has opened. This saves a round trip when starting
  1108. connections where the client speaks first (such as web browsing).
  1109. This behavior is controlled by a consensus parameter (currently
  1110. disabled). To turn it on or off manually, use the "OptimisticData"
  1111. torrc option. Implements proposal 181; code by Ian Goldberg.
  1112. - Add a new TokenBucketRefillInterval option to refill token buckets
  1113. more frequently than once per second. This should improve network
  1114. performance, alleviate queueing problems, and make traffic less
  1115. bursty. Implements proposal 183; closes ticket 3630. Design by
  1116. Florian Tschorsch and Björn Scheuermann; implementation by
  1117. Florian Tschorsch.
  1118. - Raise the threshold of server descriptors needed (75%) and exit
  1119. server descriptors needed (50%) before we will declare ourselves
  1120. bootstrapped. This will make clients start building circuits a
  1121. little later, but makes the initially constructed circuits less
  1122. skewed and less in conflict with further directory fetches. Fixes
  1123. ticket 3196.
  1124. o Major features (relays):
  1125. - Relays now try regenerating and uploading their descriptor more
  1126. frequently if they are not listed in the consensus, or if the
  1127. version of their descriptor listed in the consensus is too
  1128. old. This fix should prevent situations where a server declines
  1129. to re-publish itself because it has done so too recently, even
  1130. though the authorities decided not to list its recent-enough
  1131. descriptor. Fix for bug 3327.
  1132. o Major features (stream isolation):
  1133. - You can now configure Tor so that streams from different
  1134. applications are isolated on different circuits, to prevent an
  1135. attacker who sees your streams as they leave an exit node from
  1136. linking your sessions to one another. To do this, choose some way
  1137. to distinguish the applications: have them connect to different
  1138. SocksPorts, or have one of them use SOCKS4 while the other uses
  1139. SOCKS5, or have them pass different authentication strings to the
  1140. SOCKS proxy. Then, use the new SocksPort syntax to configure the
  1141. degree of isolation you need. This implements Proposal 171.
  1142. - There's a new syntax for specifying multiple client ports (such as
  1143. SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
  1144. multiple *Port entries with full addr:port syntax on each.
  1145. The old *ListenAddress format is still supported, but you can't
  1146. mix it with the new *Port syntax.
  1147. o Major features (bufferevents):
  1148. - Tor can now optionally build with the "bufferevents" buffered IO
  1149. backend provided by Libevent 2. To use this feature, make sure you
  1150. have the latest possible version of Libevent, and pass the
  1151. --enable-bufferevents flag to configure when building Tor from
  1152. source. This feature will make our networking code more flexible,
  1153. let us stack layers on each other, and let us use more efficient
  1154. zero-copy transports where available.
  1155. - Add experimental support for running on Windows with IOCP and no
  1156. kernel-space socket buffers. This feature is controlled by a new
  1157. "UserspaceIOCPBuffers" config option (off by default), which has
  1158. no effect unless Tor has been built with bufferevents enabled,
  1159. you're running on Windows, and you've set "DisableIOCP 0". In the
  1160. long run, this may help solve or mitigate bug 98.
  1161. o Major features (path selection):
  1162. - The EntryNodes option can now include country codes like {de} or IP
  1163. addresses or network masks. Previously we had disallowed these
  1164. options because we didn't have an efficient way to keep the list up
  1165. to date. Addresses ticket 1982, but see bug 2798 for an unresolved
  1166. issue here.
  1167. o Major features (port forwarding):
  1168. - Add support for automatic port mapping on the many home routers
  1169. that support NAT-PMP or UPnP. To build the support code, you'll
  1170. need to have the libnatpnp library and/or the libminiupnpc library,
  1171. and you'll need to enable the feature specifically by passing
  1172. "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
  1173. it on, use the new PortForwarding option.
  1174. o Major features (logging):
  1175. - Add a new 'Heartbeat' log message type to periodically log a message
  1176. describing Tor's status at level Notice. This feature is meant for
  1177. operators who log at notice, and want to make sure that their Tor
  1178. server is still working. Implementation by George Kadianakis.
  1179. - Make logging resolution configurable with a new LogTimeGranularity
  1180. option, and change the default from 1 millisecond to 1 second.
  1181. Implements enhancement 1668.
  1182. o Major features (other):
  1183. - New "DisableNetwork" config option to prevent Tor from launching any
  1184. connections or accepting any connections except on a control port.
  1185. Bundles and controllers can set this option before letting Tor talk
  1186. to the rest of the network, for example to prevent any connections
  1187. to a non-bridge address. Packages like Orbot can also use this
  1188. option to instruct Tor to save power when the network is off.
  1189. - Try to use system facilities for enumerating local interface
  1190. addresses, before falling back to our old approach (which was
  1191. binding a UDP socket, and calling getsockname() on it). That
  1192. approach was scaring OS X users whose draconian firewall
  1193. software warned about binding to UDP sockets regardless of
  1194. whether packets were sent. Now we try to use getifaddrs(),
  1195. SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
  1196. system supports. Resolves ticket 1827.
  1197. - Add experimental support for a "defaults" torrc file to be parsed
  1198. before the regular torrc. Torrc options override the defaults file's
  1199. options in the same way that the command line overrides the torrc.
  1200. The SAVECONF controller command saves only those options which
  1201. differ between the current configuration and the defaults file. HUP
  1202. reloads both files. Implements task 4552.
  1203. o New directory authorities:
  1204. - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
  1205. authority. Closes ticket 5749.
  1206. o Security/privacy fixes:
  1207. - Avoid read-from-freed-memory and double-free bugs that could occur
  1208. when a DNS request fails while launching it. Fixes bug 6480;
  1209. bugfix on 0.2.0.1-alpha.
  1210. - Reject any attempt to extend to an internal address. Without
  1211. this fix, a router could be used to probe addresses on an internal
  1212. network to see whether they were accepting connections. Fixes bug
  1213. 6710; bugfix on 0.0.8pre1.
  1214. - Close any connection that sends unrecognized junk before the TLS
  1215. handshake. Solves an issue noted in bug 4369.
  1216. - The advertised platform of a relay now includes only its operating
  1217. system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
  1218. its service pack level (for Windows) or its CPU architecture
  1219. (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
  1220. can insert an extra string in the platform line by setting the
  1221. preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
  1222. - Disable TLS session tickets. OpenSSL's implementation was giving
  1223. our TLS session keys the lifetime of our TLS context objects, when
  1224. perfect forward secrecy would want us to discard anything that
  1225. could decrypt a link connection as soon as the link connection
  1226. was closed. Fixes bug 7139; bugfix on all versions of Tor linked
  1227. against OpenSSL 1.0.0 or later. Found by Florent Daignière.
  1228. - Tor tries to wipe potentially sensitive data after using it, so
  1229. that if some subsequent security failure exposes Tor's memory,
  1230. the damage will be limited. But we had a bug where the compiler
  1231. was eliminating these wipe operations when it decided that the
  1232. memory was no longer visible to a (correctly running) program,
  1233. hence defeating our attempt at defense in depth. We fix that
  1234. by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
  1235. is unlikely to optimize away. Future versions of Tor may use
  1236. a less ridiculously heavy approach for this. Fixes bug 7352.
  1237. Reported in an article by Andrey Karpov.
  1238. o Major bugfixes (crashes and asserts):
  1239. - Avoid a pair of double-free and use-after-mark bugs that can
  1240. occur with certain timings in canceled and re-received DNS
  1241. requests. Fixes bug 6472; bugfix on 0.0.7rc1.
  1242. - Fix a denial of service attack by which any directory authority
  1243. could crash all the others, or by which a single v2 directory
  1244. authority could crash everybody downloading v2 directory
  1245. information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
  1246. - Fix an assert that directory authorities could trigger on sighup
  1247. during some configuration state transitions. We now don't treat
  1248. it as a fatal error when the new descriptor we just generated in
  1249. init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
  1250. - Avoid segfault when starting up having run with an extremely old
  1251. version of Tor and parsing its state file. Fixes bug 6801; bugfix
  1252. on 0.2.2.23-alpha.
  1253. o Major bugfixes (clients):
  1254. - If we are unable to find any exit that supports our predicted ports,
  1255. stop calling them predicted, so that we don't loop and build
  1256. hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
  1257. which introduced predicted ports.
  1258. - Check at each new consensus whether our entry guards were picked
  1259. long enough ago that we should rotate them. Previously, we only
  1260. did this check at startup, which could lead to us holding a guard
  1261. indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
  1262. - When fetching a bridge descriptor from a bridge authority,
  1263. always do so anonymously, whether we have been able to open
  1264. circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
  1265. This behavior makes it *safer* to use UpdateBridgesFromAuthority,
  1266. but we'll need to wait for bug 6010 before it's actually usable.
  1267. o Major bugfixes (directory voting):
  1268. - Check more thoroughly to prevent a rogue authority from
  1269. double-voting on any consensus directory parameter. Previously,
  1270. authorities would crash in this case if the total number of
  1271. votes for any parameter exceeded the number of active voters,
  1272. but would let it pass otherwise. Partially fixes bug 5786; bugfix
  1273. on 0.2.2.2-alpha.
  1274. - When computing weight parameters, behave more robustly in the
  1275. presence of a bad bwweightscale value. Previously, the authorities
  1276. would crash if they agreed on a sufficiently broken weight_scale
  1277. value; now, they use a reasonable default and carry on. Fixes the
  1278. rest of bug 5786; bugfix on 0.2.2.17-alpha.
  1279. - If authorities are unable to get a v2 consensus document from other
  1280. directory authorities, they no longer fall back to fetching
  1281. them from regular directory caches. Fixes bug 5635; bugfix on
  1282. 0.2.2.26-beta, where routers stopped downloading v2 consensus
  1283. documents entirely.
  1284. o Major bugfixes (relays):
  1285. - Fix a bug handling SENDME cells on nonexistent streams that could
  1286. result in bizarre window values. Report and patch contributed
  1287. pseudonymously. Fixes part of bug 6271. This bug was introduced
  1288. before the first Tor release, in svn commit r152.
  1289. - Don't update the AccountingSoftLimitHitAt state file entry whenever
  1290. tor gets started. This prevents a wrong average bandwidth
  1291. estimate, which would cause relays to always start a new accounting
  1292. interval at the earliest possible moment. Fixes bug 2003; bugfix
  1293. on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
  1294. immensely in tracking this bug down.
  1295. - Fix a possible crash bug when checking for deactivated circuits
  1296. in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
  1297. bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
  1298. - Set the SO_REUSEADDR socket option before we call bind() on outgoing
  1299. connections. This change should allow busy exit relays to stop
  1300. running out of available sockets as quickly. Fixes bug 4950;
  1301. bugfix on 0.2.2.26-beta.
  1302. o Major bugfixes (blocking resistance):
  1303. - Bridges no longer include their address in NETINFO cells on outgoing
  1304. OR connections, to allow them to blend in better with clients.
  1305. Removes another avenue for enumerating bridges. Reported by
  1306. "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
  1307. cells were introduced.
  1308. - Warn the user when HTTPProxy, but no other proxy type, is
  1309. configured. This can cause surprising behavior: it doesn't send
  1310. all of Tor's traffic over the HTTPProxy -- it sends unencrypted
  1311. directory traffic only. Resolves ticket 4663.
  1312. o Major bugfixes (hidden services):
  1313. - Improve hidden service robustness: when an attempt to connect to
  1314. a hidden service ends, be willing to refetch its hidden service
  1315. descriptors from each of the HSDir relays responsible for them
  1316. immediately. Previously, we would not consider refetching the
  1317. service's descriptors from each HSDir for 15 minutes after the last
  1318. fetch, which was inconvenient if the hidden service was not running
  1319. during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
  1320. - Hidden services now ignore the timestamps on INTRODUCE2 cells.
  1321. They used to check that the timestamp was within 30 minutes
  1322. of their system clock, so they could cap the size of their
  1323. replay-detection cache, but that approach unnecessarily refused
  1324. service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
  1325. the v3 intro-point protocol (the first one which sent a timestamp
  1326. field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
  1327. - When one of a hidden service's introduction points appears to be
  1328. unreachable, stop trying it. Previously, we would keep trying
  1329. to build circuits to the introduction point until we lost the
  1330. descriptor, usually because the user gave up and restarted Tor.
  1331. Fixes part of bug 3825.
  1332. o Changes to default torrc file:
  1333. - Stop listing "socksport 9050" in torrc.sample. We open a socks
  1334. port on 9050 by default anyway, so this should not change anything
  1335. in practice.
  1336. - Stop mentioning the deprecated *ListenAddress options in
  1337. torrc.sample. Fixes bug 5438.
  1338. - Document unit of bandwidth-related options in sample torrc.
  1339. Fixes bug 5621.
  1340. - Fix broken URLs in the sample torrc file, and tell readers about
  1341. the OutboundBindAddress, ExitPolicyRejectPrivate, and
  1342. PublishServerDescriptor options. Addresses bug 4652.
  1343. o Minor features (directory authorities):
  1344. - Consider new, removed or changed IPv6 OR ports a non-cosmetic
  1345. change when the authority is deciding whether to accept a newly
  1346. uploaded descriptor. Implements ticket 6423.
  1347. - Directory authorities are now a little more lenient at accepting
  1348. older router descriptors, or newer router descriptors that don't
  1349. make big changes. This should help ameliorate past and future
  1350. issues where routers think they have uploaded valid descriptors,
  1351. but the authorities don't think so. Fix for ticket 2479.
  1352. - Authority operators can now vote for all relays in a given
  1353. set of countries to be BadDir/BadExit/Invalid/Rejected.
  1354. - Provide two consensus parameters (FastFlagMinThreshold and
  1355. FastFlagMaxThreshold) to control the range of allowable bandwidths
  1356. for the Fast directory flag. These allow authorities to run
  1357. experiments on appropriate requirements for being a "Fast" node.
  1358. The AuthDirFastGuarantee config value still applies. Implements
  1359. ticket 3946.
  1360. o Minor features (bridges / bridge authorities):
  1361. - Make bridge SSL certificates a bit more stealthy by using random
  1362. serial numbers, in the same fashion as OpenSSL when generating
  1363. self-signed certificates. Implements ticket 4584.
  1364. - Tag a bridge's descriptor as "never to be sent unencrypted".
  1365. This shouldn't matter, since bridges don't open non-anonymous
  1366. connections to the bridge authority and don't allow unencrypted
  1367. directory connections from clients, but we might as well make
  1368. sure. Closes bug 5139.
  1369. - The Bridge Authority now writes statistics on how many bridge
  1370. descriptors it gave out in total, and how many unique descriptors
  1371. it gave out. It also lists how often the most and least commonly
  1372. fetched descriptors were given out, as well as the median and
  1373. 25th/75th percentile. Implements tickets 4200 and 4294.
  1374. o Minor features (IPv6):
  1375. - Make the code that clients use to detect an address change be
  1376. IPv6-aware, so that it won't fill clients' logs with error
  1377. messages when trying to get the IPv4 address of an IPv6
  1378. connection. Implements ticket 5537.
  1379. - Relays now understand an IPv6 address when they get one from a
  1380. directory server. Resolves ticket 4875.
  1381. o Minor features (hidden services):
  1382. - Expire old or over-used hidden service introduction points.
  1383. Required by fix for bug 3460.
  1384. - Reduce the lifetime of elements of hidden services' Diffie-Hellman
  1385. public key replay-detection cache from 60 minutes to 5 minutes. This
  1386. replay-detection cache is now used only to detect multiple
  1387. INTRODUCE2 cells specifying the same rendezvous point, so we can
  1388. avoid launching multiple simultaneous attempts to connect to it.
  1389. - When a hidden service's introduction point times out, consider
  1390. trying it again during the next attempt to connect to the
  1391. HS. Previously, we would not try it again unless a newly fetched
  1392. descriptor contained it. Required by fixes for bugs 1297 and 3825.
  1393. o Minor features (relays):
  1394. - Relays now include a reason for regenerating their descriptors
  1395. in an HTTP header when uploading to the authorities. This will
  1396. make it easier to debug descriptor-upload issues in the future.
  1397. - Turn on directory request statistics by default and include them in
  1398. extra-info descriptors. Don't break if we have no GeoIP database.
  1399. - Replace files in stats/ rather than appending to them. Now that we
  1400. include statistics in extra-info descriptors, it makes no sense to
  1401. keep old statistics forever. Implements ticket 2930.
  1402. - Relays that set "ConnDirectionStatistics 1" write statistics on the
  1403. bidirectional use of connections to disk every 24 hours.
  1404. - Add a GeoIP file digest to the extra-info descriptor. Implements
  1405. ticket 1883.
  1406. o Minor features (new config options):
  1407. - New config option "DynamicDHGroups" (disabled by default) provides
  1408. each bridge with a unique prime DH modulus to be used during
  1409. SSL handshakes. This option attempts to help against censors
  1410. who might use the Apache DH modulus as a static identifier for
  1411. bridges. Addresses ticket 4548.
  1412. - New config option "DisableDebuggerAttachment" (on by default)
  1413. to prevent basic debugging attachment attempts by other processes.
  1414. Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
  1415. - Ordinarily, Tor does not count traffic from private addresses (like
  1416. 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
  1417. There is now a new option, CountPrivateBandwidth, to disable this
  1418. behavior. Patch from Daniel Cagara.
  1419. o Minor features (different behavior for old config options):
  1420. - Allow MapAddress directives to specify matches against super-domains,
  1421. as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
  1422. Implements issue 933.
  1423. - Don't disable the DirPort when we cannot exceed our AccountingMax
  1424. limit during this interval because the effective bandwidthrate is
  1425. low enough. This is useful in a situation where AccountMax is only
  1426. used as an additional safeguard or to provide statistics.
  1427. - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
  1428. implements ticket 3439.
  1429. - When configuring a large set of nodes in EntryNodes, and there are
  1430. enough of them listed as Guard so that we don't need to consider
  1431. the non-guard entries, prefer the ones listed with the Guard flag.
  1432. - If you set the NumCPUs option to 0, Tor will now try to detect how
  1433. many CPUs you have. This is the new default behavior.
  1434. - The NodeFamily option -- which let you declare that you want to
  1435. consider nodes to be part of a family whether they list themselves
  1436. that way or not -- now allows IP address ranges and country codes.
  1437. o Minor features (new command-line config behavior):
  1438. - Slightly change behavior of "list" options (that is, config
  1439. options that can appear more than once) when they appear both in
  1440. torrc and on the command line. Previously, the command-line options
  1441. would be appended to the ones from torrc. Now, the command-line
  1442. options override the torrc options entirely. This new behavior
  1443. allows the user to override list options (like exit policies and
  1444. ports to listen on) from the command line, rather than simply
  1445. appending to the list.
  1446. - You can get the old (appending) command-line behavior for "list"
  1447. options by prefixing the option name with a "+".
  1448. - You can remove all the values for a "list" option from the command
  1449. line without adding any new ones by prefixing the option name
  1450. with a "/".
  1451. o Minor features (controller, new events):
  1452. - Extend the control protocol to report flags that control a circuit's
  1453. path selection in CIRC events and in replies to 'GETINFO
  1454. circuit-status'. Implements part of ticket 2411.
  1455. - Extend the control protocol to report the hidden service address
  1456. and current state of a hidden-service-related circuit in CIRC
  1457. events and in replies to 'GETINFO circuit-status'. Implements part
  1458. of ticket 2411.
  1459. - Include the creation time of a circuit in CIRC and CIRC2
  1460. control-port events and the list produced by the 'GETINFO
  1461. circuit-status' control-port command.
  1462. - Add a new CONF_CHANGED event so that controllers can be notified
  1463. of any configuration changes made by other controllers, or by the
  1464. user. Implements ticket 1692.
  1465. - Add a new SIGNAL event to the controller interface so that
  1466. controllers can be notified when Tor handles a signal. Resolves
  1467. issue 1955. Patch by John Brooks.
  1468. o Minor features (controller, new getinfo options):
  1469. - Expose our view of whether we have gone dormant to the controller,
  1470. via a new "GETINFO dormant" value. Torbutton and other controllers
  1471. can use this to avoid doing periodic requests through Tor while
  1472. it's dormant (bug 4718). Resolves ticket 5954.
  1473. - Add a new GETINFO option to get total bytes read and written. Patch
  1474. from pipe, revised by atagar. Resolves ticket 2345.
  1475. - Implement new GETINFO controller fields to provide information about
  1476. the Tor process's pid, euid, username, and resource limits.
  1477. o Minor features (controller, other):
  1478. - Allow controllers to request an event notification whenever a
  1479. circuit is cannibalized or its purpose is changed. Implements
  1480. part of ticket 3457.
  1481. - Use absolute path names when reporting the torrc filename in the
  1482. control protocol, so a controller can more easily find the torrc
  1483. file. Resolves bug 1101.
  1484. - When reporting the path to the cookie file to the controller,
  1485. give an absolute path. Resolves ticket 4881.
  1486. o Minor features (log messages):
  1487. - Add more information to a log statement that might help track down
  1488. bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
  1489. non-IP address" messages (or any Bug messages, for that matter!),
  1490. please let us know about it.
  1491. - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
  1492. EntryNodes will have no effect. Resolves issue 2571.
  1493. - Try to make the introductory warning message that Tor prints on
  1494. startup more useful for actually finding help and information.
  1495. Resolves ticket 2474.
  1496. - When the system call to create a listener socket fails, log the
  1497. error message explaining why. This may help diagnose bug 4027.
  1498. o Minor features (other):
  1499. - When we fail to initialize Libevent, retry with IOCP disabled so we
  1500. don't need to turn on multi-threading support in Libevent, which in
  1501. turn requires a working socketpair(). This is a workaround for bug
  1502. 4457, which affects Libevent versions from 2.0.1-alpha through
  1503. 2.0.15-stable.
  1504. - When starting as root and then changing our UID via the User
  1505. control option, and we have a ControlSocket configured, make sure
  1506. that the ControlSocket is owned by the same account that Tor will
  1507. run under. Implements ticket 3421; fix by Jérémy Bobbio.
  1508. - Accept attempts to include a password authenticator in the
  1509. handshake, as supported by SOCKS5. This handles SOCKS clients that
  1510. don't know how to omit a password when authenticating. Resolves
  1511. bug 1666.
  1512. - Check for and recover from inconsistency in the microdescriptor
  1513. cache. This will make it harder for us to accidentally free a
  1514. microdescriptor without removing it from the appropriate data
  1515. structures. Fixes issue 3135; issue noted by "wanoskarnet".
  1516. - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
  1517. o Minor bugfixes (code security):
  1518. - Prevent a null-pointer dereference when receiving a data cell
  1519. for a nonexistent stream when the circuit in question has an
  1520. empty deliver window. We don't believe this is triggerable,
  1521. since we don't currently allow deliver windows to become empty,
  1522. but the logic is tricky enough that it's better to make the code
  1523. robust. Fixes bug 5541; bugfix on 0.0.2pre14.
  1524. - Fix a (harmless) integer overflow in cell statistics reported by
  1525. some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
  1526. - Fix our implementation of crypto_random_hostname() so it can't
  1527. overflow on ridiculously large inputs. (No Tor version has ever
  1528. provided this kind of bad inputs, but let's be correct in depth.)
  1529. Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
  1530. - Add a (probably redundant) memory clear between iterations of
  1531. the router status voting loop, to prevent future coding errors
  1532. where data might leak between iterations of the loop. Resolves
  1533. ticket 6514.
  1534. o Minor bugfixes (wrapper functions):
  1535. - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
  1536. utility function used in the control-port code). This shouldn't
  1537. ever happen unless Tor is completely out of memory, but if it did
  1538. happen and Tor somehow recovered from it, Tor could have sent a log
  1539. message to a control port in the middle of a reply to a controller
  1540. command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
  1541. - Fix some (not actually triggerable) buffer size checks in usage of
  1542. tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
  1543. by Anders Sundman.
  1544. - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
  1545. bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
  1546. - Enforce correct return behavior of tor_vsscanf() when the '%%'
  1547. pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
  1548. - Make our replacement implementation of strtok_r() compatible with
  1549. the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
  1550. bugfix on 0.2.2.1-alpha.
  1551. - Find more places in the code that should have been testing for
  1552. invalid sockets using the SOCKET_OK macro. Required for a fix
  1553. for bug 4533. Bugfix on 0.2.2.28-beta.
  1554. o Minor bugfixes (code correctness):
  1555. - Check return value of fputs() when writing authority certificate
  1556. file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
  1557. - When building Tor on Windows with -DUNICODE (not default), ensure
  1558. that error messages, filenames, and DNS server names are always
  1559. NUL-terminated when we convert them to a single-byte encoding.
  1560. Fixes bug 5909; bugfix on 0.2.2.16-alpha.
  1561. - Fix a memory leak when trying to launch a DNS request when the
  1562. nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
  1563. 0.1.2.1-alpha.
  1564. - Correct file sizes when reading binary files on Cygwin, to avoid
  1565. a bug where Tor would fail to read its state file. Fixes bug 6844;
  1566. bugfix on 0.1.2.7-alpha.
  1567. - Make sure to set *socket_error in all error cases in
  1568. connection_connect(), so it can't produce a warning about
  1569. errno being zero from errno_to_orconn_end_reason(). Bugfix on
  1570. 0.2.1.1-alpha; resolves ticket 6028.
  1571. - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
  1572. bug 4532; found by "troll_un".
  1573. o Minor bugfixes (clients):
  1574. - Allow one-hop directory-fetching circuits the full "circuit build
  1575. timeout" period, rather than just half of it, before failing them
  1576. and marking the relay down. This fix should help reduce cases where
  1577. clients declare relays (or worse, bridges) unreachable because
  1578. the TLS handshake takes a few seconds to complete. Fixes bug 6743;
  1579. bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
  1580. 30 seconds.
  1581. - Ensure we don't cannibalize circuits that are longer than three hops
  1582. already, so we don't end up making circuits with 5 or more
  1583. hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
  1584. 0.1.0.1-rc which introduced cannibalization.
  1585. o Minor bugfixes (relays):
  1586. - Don't publish a new relay descriptor when we reload our onion key,
  1587. unless the onion key has actually changed. Fixes bug 3263 and
  1588. resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
  1589. - When relays refuse a "create" cell because their queue of pending
  1590. create cells is too big (typically because their cpu can't keep up
  1591. with the arrival rate), send back reason "resource limit" rather
  1592. than reason "internal", so network measurement scripts can get a
  1593. more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
  1594. - Exit nodes don't need to fetch certificates for authorities that
  1595. they don't recognize; only directory authorities, bridges,
  1596. and caches need to do that. Fixes part of bug 2297; bugfix on
  1597. 0.2.2.11-alpha.
  1598. o Minor bugfixes (directory authority / mirrors):
  1599. - Avoid O(n^2) performance characteristics when parsing a large
  1600. extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
  1601. - Authorities no longer include any router in their microdescriptor
  1602. consensuses for which they couldn't generate or agree on a
  1603. microdescriptor. Fixes the second piece of bug 6404; fix on
  1604. 0.2.2.6-alpha.
  1605. - When checking for requested signatures on the latest consensus
  1606. before serving it to a client, make sure to check the right
  1607. consensus flavor. Bugfix on 0.2.2.6-alpha.
  1608. - Fix an edge case where TestingTorNetwork is set but the authorities
  1609. and relays all have an uptime of zero, so the private Tor network
  1610. could briefly lack support for hidden services. Fixes bug 3886;
  1611. bugfix on 0.2.2.18-alpha.
  1612. - Directory caches no longer refuse to clean out descriptors because
  1613. of missing v2 networkstatus documents, unless they're configured
  1614. to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
  1615. 0.2.2.26-beta. Patch by Daniel Bryg.
  1616. - Don't serve or accept v2 hidden service descriptors over a relay's
  1617. DirPort. It's never correct to do so, and disabling it might
  1618. make it more annoying to exploit any bugs that turn up in the
  1619. descriptor-parsing code. Fixes bug 7149.
  1620. o Minor bugfixes (hidden services, client-side):
  1621. - Assert that hidden-service-related operations are not performed
  1622. using single-hop circuits. Previously, Tor would assert that
  1623. client-side streams are not attached to single-hop circuits,
  1624. but not that other sensitive operations on the client and service
  1625. side are not performed using single-hop circuits. Fixes bug 3332;
  1626. bugfix on 0.0.6.
  1627. - Avoid undefined behaviour when parsing the list of supported
  1628. rendezvous/introduction protocols in a hidden service descriptor.
  1629. Previously, Tor would have confused (as-yet-unused) protocol version
  1630. numbers greater than 32 with lower ones on many platforms. Fixes
  1631. bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
  1632. - Don't close hidden service client circuits which have almost
  1633. finished connecting to their destination when they reach
  1634. the normal circuit-build timeout. Previously, we would close
  1635. introduction circuits which are waiting for an acknowledgement
  1636. from the introduction point, and rendezvous circuits which have
  1637. been specified in an INTRODUCE1 cell sent to a hidden service,
  1638. after the normal CBT. Now, we mark them as 'timed out', and launch
  1639. another rendezvous attempt in parallel. This behavior change can
  1640. be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
  1641. option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
  1642. o Minor bugfixes (hidden services, service-side):
  1643. - Don't close hidden-service-side rendezvous circuits when they
  1644. reach the normal circuit-build timeout. This behaviour change can
  1645. be disabled using the new
  1646. CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
  1647. remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
  1648. - Don't launch more than 10 service-side introduction-point circuits
  1649. for a hidden service in five minutes. Previously, we would consider
  1650. launching more introduction-point circuits if at least one second
  1651. had passed without any introduction-point circuits failing. Fixes
  1652. bug 4607; bugfix on 0.0.7pre1.
  1653. o Minor bugfixes (config option behavior):
  1654. - If the user tries to set MyFamily on a bridge, refuse to
  1655. do so, and warn about the security implications. Fixes bug 4657;
  1656. bugfix on 0.2.0.3-alpha.
  1657. - The "--quiet" and "--hush" options now apply not only to Tor's
  1658. behavior before logs are configured, but also to Tor's behavior in
  1659. the absense of configured logs. Fixes bug 3550; bugfix on
  1660. 0.2.0.10-alpha.
  1661. - Change the AllowDotExit rules so they should actually work.
  1662. We now enforce AllowDotExit only immediately after receiving an
  1663. address via SOCKS or DNSPort: other sources are free to provide
  1664. .exit addresses after the resolution occurs. Fixes bug 3940;
  1665. bugfix on 0.2.2.1-alpha.
  1666. - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
  1667. don't depend on the consensus parameters or compute adaptive
  1668. timeouts when it is disabled. Fixes bug 5049; bugfix on
  1669. 0.2.2.14-alpha.
  1670. - After we pick a directory mirror, we would refuse to use it if
  1671. it's in our ExcludeExitNodes list, resulting in mysterious failures
  1672. to bootstrap for people who just wanted to avoid exiting from
  1673. certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
  1674. - When told to add a bridge with the same digest as a preexisting
  1675. bridge but a different addr:port, change the addr:port as
  1676. requested. Previously we would not notice the change. Fixes half
  1677. of bug 5603; fix on 0.2.2.26-beta.
  1678. o Minor bugfixes (controller):
  1679. - Allow manual 'authenticate' commands to the controller interface
  1680. from netcat (nc) as well as telnet. We were rejecting them because
  1681. they didn't come with the expected whitespace at the end of the
  1682. command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
  1683. - Report a real bootstrap problem to the controller on router
  1684. identity mismatch. Previously we just said "foo", which probably
  1685. made a lot of sense at the time. Fixes bug 4169; bugfix on
  1686. 0.2.1.1-alpha.
  1687. - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
  1688. option is set to 0 (which Vidalia version 0.2.16 now does when
  1689. a SAVECONF attempt fails), perform other actions that SIGHUP
  1690. usually causes (like reopening the logs). Fixes bug 5095; bugfix
  1691. on 0.2.1.9-alpha.
  1692. - Correctly handle checking the permissions on the parent
  1693. directory of a control socket in the root directory. Bug found
  1694. by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
  1695. 0.2.2.26-beta.
  1696. - End AUTHCHALLENGE error messages (in the control protocol) with
  1697. a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
  1698. o Minor bugfixes (network reading/writing):
  1699. - Disable writing on marked-for-close connections when they are
  1700. blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
  1701. bug 5263; bugfix on 0.0.2pre13, where we first added a special
  1702. case for flushing marked connections.
  1703. - Make sure that there are no unhandled pending TLS errors before
  1704. reading from a TLS stream. We had checks in 0.1.0.3-rc, but
  1705. lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
  1706. Bugfix on 0.1.0.5-rc; fixes bug 4528.
  1707. - Detect SSL handshake even when the initial attempt to write the
  1708. server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
  1709. - If the client fails to set a reasonable set of ciphersuites
  1710. during its v2 handshake renegotiation, allow the renegotiation to
  1711. continue nevertheless (i.e. send all the required certificates).
  1712. Fixes bug 4591; bugfix on 0.2.0.20-rc.
  1713. o Minor bugfixes (other):
  1714. - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
  1715. resource exhaustion, so that clients can adjust their load to
  1716. try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
  1717. started using END_STREAM_REASON_RESOURCELIMIT.
  1718. - Don't check for whether the address we're using for outbound
  1719. connections has changed until after the outbound connection has
  1720. completed. On Windows, getsockname() doesn't succeed until the
  1721. connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
  1722. - Don't hold a Windows file handle open for every file mapping;
  1723. the file mapping handle is sufficient. Fixes bug 5951; bugfix on
  1724. 0.1.2.1-alpha.
  1725. - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
  1726. bugfix on 0.2.1.10-alpha.
  1727. - If we fail to write a microdescriptor to the disk cache, do not
  1728. continue replacing the old microdescriptor file. Fixes bug 2954;
  1729. bugfix on 0.2.2.6-alpha.
  1730. o Minor bugfixes (log messages, path selection):
  1731. - Downgrade "set buildtimeout to low value" messages to "info"
  1732. severity; they were never an actual problem, there was never
  1733. anything reasonable to do about them, and they tended to spam logs
  1734. from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
  1735. - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
  1736. more information to it, so that we can track it down in case it
  1737. returns again. Mitigates bug 5235.
  1738. - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
  1739. options_validate(); warn if LearnCircuitBuildTimeout is disabled and
  1740. CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
  1741. - Issue a log message if a guard completes less than 40% of your
  1742. circuits. Threshold is configurable by torrc option
  1743. PathBiasNoticeRate and consensus parameter pb_noticepct. There is
  1744. additional, off-by-default code to disable guards which fail too
  1745. many circuits. Addresses ticket 5458.
  1746. o Minor bugfixes (log messages, client):
  1747. - Downgrade "Got a certificate, but we already have it" log messages
  1748. from warning to info, except when we're a dirauth. Fixes bug 5238;
  1749. bugfix on 0.2.1.7-alpha.
  1750. - Fix the log message describing how we work around discovering
  1751. that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
  1752. 4837; bugfix on 0.2.2.9-alpha.
  1753. - When logging about a disallowed .exit name, do not also call it
  1754. an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
  1755. - Fix a log message suggesting that people contact a non-existent
  1756. email address. Fixes bug 3448.
  1757. - Rephrase the log message emitted if the TestSocks check is
  1758. successful. Patch from Fabian Keil; fixes bug 4094.
  1759. - Log (at debug level) whenever a circuit's purpose is changed.
  1760. - Log SSL state transitions at log level DEBUG, log domain
  1761. HANDSHAKE. This can be useful for debugging censorship events.
  1762. Implements ticket 3264.
  1763. - We now log which torrc file we're using on startup. Implements
  1764. ticket 2444.
  1765. - Rate-limit log messages when asked to connect anonymously to
  1766. a private address. When these hit, they tended to hit fast and
  1767. often. Also, don't bother trying to connect to addresses that we
  1768. are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
  1769. reply makes us think we have been lied to, even when the address the
  1770. client tried to connect to was "localhost." Resolves ticket 2822.
  1771. o Minor bugfixes (log messages, non-client):
  1772. - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
  1773. Fixes bug 5932; bugfix on 0.2.2.7-alpha.
  1774. - Don't log that we have "decided to publish new relay descriptor"
  1775. unless we are actually publishing a descriptor. Fixes bug 3942;
  1776. bugfix on 0.2.2.28-beta.
  1777. - Log which authority we're missing votes from when we go to fetch
  1778. them from the other auths.
  1779. - Replace "Sending publish request" log messages with "Launching
  1780. upload", so that they no longer confusingly imply that we're
  1781. sending something to a directory we might not even be connected
  1782. to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
  1783. - Warn when Tor is configured to use accounting in a way that can
  1784. link a hidden service to some other hidden service or public
  1785. address. Resolves ticket 6490.
  1786. - Fix a minor formatting issue in one of tor-gencert's error messages.
  1787. Fixes bug 4574.
  1788. o Testing:
  1789. - Update to the latest version of the tinytest unit testing framework.
  1790. This includes a couple of bugfixes that can be relevant for
  1791. running forked unit tests on Windows, and removes all reserved
  1792. identifiers.
  1793. - Avoid a false positive in the util/threads unit test by increasing
  1794. the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
  1795. - Make it possible to set the TestingTorNetwork configuration
  1796. option using AlternateDirAuthority and AlternateBridgeAuthority
  1797. as an alternative to setting DirServer. Addresses ticket 6377.
  1798. - Add a unit test for the environment_variable_names_equal() function.
  1799. - A wide variety of new unit tests by Esteban Manchado Velázquez.
  1800. - Numerous new unit tests for functions in util.c and address.c by
  1801. Anders Sundman.
  1802. - The long-disabled benchmark tests are now split into their own
  1803. ./src/test/bench binary.
  1804. - The benchmark tests can now use more accurate timers than
  1805. gettimeofday() when such timers are available.
  1806. - Use tt_assert(), not tor_assert(), for checking for test failures.
  1807. This makes the unit tests more able to go on in the event that
  1808. one of them fails.
  1809. o Build improvements:
  1810. - Use the dead_strip option when building Tor on OS X. This reduces
  1811. binary size by almost 19% when linking openssl and libevent
  1812. statically, which we do for Tor Browser Bundle.
  1813. - Provide a better error message about possible OSX Asciidoc failure
  1814. reasons. Fixes bug 6436.
  1815. - Detect attempts to build Tor on (as yet hypothetical) versions
  1816. of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
  1817. fix for bug 4533. Bugfix on 0.2.2.28-beta.
  1818. - On Windows, we now define the _WIN32_WINNT macros only if they
  1819. are not already defined. This lets the person building Tor decide,
  1820. if they want, to require a later version of Windows.
  1821. - Our autogen.sh script now uses autoreconf to launch autoconf,
  1822. automake, and so on. This is more robust against some of the failure
  1823. modes associated with running the autotools pieces on their own.
  1824. - Running "make version" now displays the version of Tor that
  1825. we're about to build. Idea from katmagic; resolves issue 4400.
  1826. - Make 'tor --digests' list hashes of all Tor source files. Bugfix
  1827. on 0.2.2.4-alpha; fixes bug 3427.
  1828. - New --enable-static-tor configure option for building Tor as
  1829. statically as possible. Idea, general hackery and thoughts from
  1830. Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
  1831. 2702.
  1832. - Limited, experimental support for building with nmake and MSVC.
  1833. o Build requirements:
  1834. - Building Tor with bufferevent support now requires Libevent
  1835. 2.0.13-stable or later. Previous versions of Libevent had bugs in
  1836. SSL-related bufferevents and related issues that would make Tor
  1837. work badly with bufferevents. Requiring 2.0.13-stable also allows
  1838. Tor with bufferevents to take advantage of Libevent APIs
  1839. introduced after 2.0.8-rc.
  1840. - Our build system requires automake 1.6 or later to create the
  1841. Makefile.in files. Previously, you could have used 1.4.
  1842. This only affects developers and people building Tor from git;
  1843. people who build Tor from the source distribution without changing
  1844. the Makefile.am files should be fine.
  1845. - Detect when we try to build on a platform that doesn't define
  1846. AF_UNSPEC to 0. We don't work there, so refuse to compile.
  1847. o Build fixes (compile/link):
  1848. - Format more doubles with %f, not %lf. Patch from grarpamp to make
  1849. Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
  1850. Tor 0.2.0.8-alpha.
  1851. - When building with --enable-static-tor on OpenBSD, do not
  1852. erroneously attempt to link -lrt. Fixes bug 5103.
  1853. - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
  1854. that IPv6 stuff will compile on MSVC, and compilation issues
  1855. will be easier to track down. Fixes bug 5861.
  1856. - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
  1857. Fixes bug 6379. Bugfix on 0.2.0.20-rc.
  1858. - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
  1859. Fixes bug 6097; bugfix on 0.2.2.16-alpha.
  1860. o Build fixes (other):
  1861. - Use the _WIN32 macro throughout our code to detect Windows.
  1862. (Previously we had used the obsolete 'WIN32' and the idiosyncratic
  1863. 'MS_WINDOWS'.)
  1864. - Properly handle the case where the build-tree is not the same
  1865. as the source tree when generating src/common/common_sha1.i,
  1866. src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
  1867. bugfix on 0.2.0.1-alpha.
  1868. - During configure, search for library containing cos function as
  1869. libm lives in libcore on some platforms (BeOS/Haiku). Linking
  1870. against libm was hard-coded before. Fixes the first part of bug
  1871. 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
  1872. Pedersen.
  1873. - Prevent a false positive from the check-spaces script, by disabling
  1874. the "whitespace between function name and (" check for functions
  1875. named 'op()'.
  1876. o Packaging (RPM) changes:
  1877. - Update our default RPM spec files to work with mock and rpmbuild
  1878. on RHEL/Fedora. They have an updated set of dependencies and
  1879. conflicts, a fix for an ancient typo when creating the "_tor"
  1880. user, and better instructions. Thanks to Ondrej Mikle for the
  1881. patch series. Fixes bug 6043.
  1882. - On OpenSUSE, create the /var/run/tor directory on startup if it
  1883. is not already created. Patch from Andreas Stieger. Fixes bug 2573.
  1884. o Code refactoring (safety):
  1885. - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
  1886. 10 lines. Also, don't nest them. Doing so in the past has
  1887. led to hard-to-debug code. The new style is to use the
  1888. SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
  1889. - Use macros to indicate OpenSSL versions, so we don't need to worry
  1890. about accidental hexadecimal bit shifts.
  1891. - Use tor_sscanf() in place of scanf() in more places through the
  1892. code. This makes us a little more locale-independent, and
  1893. should help shut up code-analysis tools that can't tell
  1894. a safe sscanf string from a dangerous one.
  1895. - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
  1896. - Use the smartlist_add_asprintf() alias more consistently.
  1897. o Code refactoring (consolidate):
  1898. - A major revision to our internal node-selecting and listing logic.
  1899. Tor already had at least two major ways to look at the question of
  1900. "which Tor servers do we know about": a list of router descriptors,
  1901. and a list of entries in the current consensus. With
  1902. microdescriptors, we're adding a third. Having so many systems
  1903. without an abstraction layer over them was hurting the codebase.
  1904. Now, we have a new "node_t" abstraction that presents a consistent
  1905. interface to a client's view of a Tor node, and holds (nearly) all
  1906. of the mutable state formerly in routerinfo_t and routerstatus_t.
  1907. - Move tor_gettimeofday_cached() into compat_libevent.c, and use
  1908. Libevent's notion of cached time when possible.
  1909. - Remove duplicate code for invoking getrlimit() from control.c.
  1910. - Use OpenSSL's built-in SSL_state_string_long() instead of our
  1911. own homebrewed ssl_state_to_string() replacement. Patch from
  1912. Emile Snyder. Fixes bug 4653.
  1913. - Change the symmetric cipher interface so that creating and
  1914. initializing a stream cipher are no longer separate functions.
  1915. o Code refactoring (separate):
  1916. - Make a new "entry connection" struct as an internal subtype of "edge
  1917. connection", to simplify the code and make exit connections smaller.
  1918. - Split connection_about_to_close() into separate functions for each
  1919. connection type.
  1920. - Rewrite the listener-selection logic so that parsing which ports
  1921. we want to listen on is now separate from binding to the ports
  1922. we want.
  1923. o Code refactoring (name changes):
  1924. - Rename a handful of old identifiers, mostly related to crypto
  1925. structures and crypto functions. By convention, our "create an
  1926. object" functions are called "type_new()", our "free an object"
  1927. functions are called "type_free()", and our types indicate that
  1928. they are types only with a final "_t". But a handful of older
  1929. types and functions broke these rules, with function names like
  1930. "type_create" or "subsystem_op_type", or with type names like
  1931. type_env_t.
  1932. - Rename Tor functions that turn strings into addresses, so that
  1933. "parse" indicates that no hostname resolution occurs, and
  1934. "lookup" indicates that hostname resolution may occur. This
  1935. should help prevent mistakes in the future. Fixes bug 3512.
  1936. - Use the name "CERTS" consistently to refer to the new cell type;
  1937. we were calling it CERT in some places and CERTS in others.
  1938. - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
  1939. invalid value, rather than just -1.
  1940. - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
  1941. can pick them up when the tests aren't disabled. Bugfix on
  1942. 0.2.2.4-alpha which introduced tinytest.
  1943. o Code refactoring (other):
  1944. - Defensively refactor rend_mid_rendezvous() so that protocol
  1945. violations and length checks happen in the beginning. Fixes
  1946. bug 5645.
  1947. - Remove the pure attribute from all functions that used it
  1948. previously. In many cases we assigned it incorrectly, because the
  1949. functions might assert or call impure functions, and we don't have
  1950. evidence that keeping the pure attribute is worthwhile. Implements
  1951. changes suggested in ticket 4421.
  1952. - Move the replay-detection cache for the RSA-encrypted parts of
  1953. INTRODUCE2 cells to the introduction point data structures.
  1954. Previously, we would use one replay-detection cache per hidden
  1955. service. Required by fix for bug 3460.
  1956. - The helper programs tor-gencert, tor-resolve, and tor-checkkey
  1957. no longer link against Libevent: they never used it, but
  1958. our library structure used to force them to link it.
  1959. o Removed features and files:
  1960. - Remove all internal support for unpadded RSA. We never used it, and
  1961. it would be a bad idea to start.
  1962. - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
  1963. supported).
  1964. - Remove some redundant #include directives throughout the code.
  1965. Patch from Andrea Gelmini.
  1966. - Remove some old code to remember statistics about which descriptors
  1967. we've served as a directory mirror. The feature wasn't used and
  1968. is outdated now that microdescriptors are around.
  1969. - Remove some old code to work around even older versions of Tor that
  1970. used forked processes to handle DNS requests. Such versions of Tor
  1971. are no longer in use as relays.
  1972. - The "torify" script no longer supports the "tsocks" socksifier
  1973. tool, since tsocks doesn't support DNS and UDP right for Tor.
  1974. Everyone should be using torsocks instead. Fixes bugs 3530 and
  1975. 5180. Based on a patch by "ugh".
  1976. - Remove the torrc.bridge file: we don't use it for anything, and
  1977. it had become badly desynchronized from torrc.sample. Resolves
  1978. bug 5622.
  1979. o Documentation:
  1980. - Begin a doc/state-contents.txt file to explain the contents of
  1981. the Tor state file. Fixes bug 2987.
  1982. - Clarify the documentation for the Alternate*Authority options.
  1983. Fixes bug 6387.
  1984. - Document the --defaults-torrc option, and the new semantics for
  1985. overriding, extending, and clearing lists of options. Closes
  1986. bug 4748.
  1987. - Add missing man page documentation for consensus and microdesc
  1988. files. Resolves ticket 6732.
  1989. - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
  1990. o Documentation fixes:
  1991. - Improve the manual's documentation for the NT Service command-line
  1992. options. Addresses ticket 3964.
  1993. - Clarify SessionGroup documentation slightly; resolves ticket 5437.
  1994. - Document the changes to the ORPort and DirPort options, and the
  1995. fact that {OR/Dir}ListenAddress is now unnecessary (and
  1996. therefore deprecated). Resolves ticket 5597.
  1997. - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
  1998. - Clarify that hidden services are TCP only. Fixes bug 6024.
  1999. Changes in version 0.2.2.39 - 2012-09-11
  2000. Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
  2001. assertions.
  2002. o Security fixes:
  2003. - Fix an assertion failure in tor_timegm() that could be triggered
  2004. by a badly formatted directory object. Bug found by fuzzing with
  2005. Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
  2006. - Do not crash when comparing an address with port value 0 to an
  2007. address policy. This bug could have been used to cause a remote
  2008. assertion failure by or against directory authorities, or to
  2009. allow some applications to crash clients. Fixes bug 6690; bugfix
  2010. on 0.2.1.10-alpha.
  2011. Changes in version 0.2.2.38 - 2012-08-12
  2012. Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
  2013. attack that could in theory leak path information.
  2014. o Security fixes:
  2015. - Avoid an uninitialized memory read when reading a vote or consensus
  2016. document that has an unrecognized flavor name. This read could
  2017. lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
  2018. - Try to leak less information about what relays a client is
  2019. choosing to a side-channel attacker. Previously, a Tor client would
  2020. stop iterating through the list of available relays as soon as it
  2021. had chosen one, thus finishing a little earlier when it picked
  2022. a router earlier in the list. If an attacker can recover this
  2023. timing information (nontrivial but not proven to be impossible),
  2024. they could learn some coarse-grained information about which relays
  2025. a client was picking (middle nodes in particular are likelier to
  2026. be affected than exits). The timing attack might be mitigated by
  2027. other factors (see bug 6537 for some discussion), but it's best
  2028. not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
  2029. Changes in version 0.2.2.37 - 2012-06-06
  2030. Tor 0.2.2.37 introduces a workaround for a critical renegotiation
  2031. bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
  2032. currently).
  2033. o Major bugfixes:
  2034. - Work around a bug in OpenSSL that broke renegotiation with TLS
  2035. 1.1 and TLS 1.2. Without this workaround, all attempts to speak
  2036. the v2 Tor connection protocol when both sides were using OpenSSL
  2037. 1.0.1 would fail. Resolves ticket 6033.
  2038. - When waiting for a client to renegotiate, don't allow it to add
  2039. any bytes to the input buffer. This fixes a potential DoS issue.
  2040. Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
  2041. - Fix an edge case where if we fetch or publish a hidden service
  2042. descriptor, we might build a 4-hop circuit and then use that circuit
  2043. for exiting afterwards -- even if the new last hop doesn't obey our
  2044. ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
  2045. o Minor bugfixes:
  2046. - Fix a build warning with Clang 3.1 related to our use of vasprintf.
  2047. Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
  2048. o Minor features:
  2049. - Tell GCC and Clang to check for any errors in format strings passed
  2050. to the tor_v*(print|scan)f functions.
  2051. Changes in version 0.2.2.36 - 2012-05-24
  2052. Tor 0.2.2.36 updates the addresses for two of the eight directory
  2053. authorities, fixes some potential anonymity and security issues,
  2054. and fixes several crash bugs.
  2055. Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
  2056. known flaws, and nobody should be using them. You should upgrade. If
  2057. you're using a Linux or BSD and its packages are obsolete, stop using
  2058. those packages and upgrade anyway.
  2059. o Directory authority changes:
  2060. - Change IP address for maatuska (v3 directory authority).
  2061. - Change IP address for ides (v3 directory authority), and rename
  2062. it to turtles.
  2063. o Security fixes:
  2064. - When building or running with any version of OpenSSL earlier
  2065. than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
  2066. versions have a bug (CVE-2011-4576) in which their block cipher
  2067. padding includes uninitialized data, potentially leaking sensitive
  2068. information to any peer with whom they make a SSLv3 connection. Tor
  2069. does not use SSL v3 by default, but a hostile client or server
  2070. could force an SSLv3 connection in order to gain information that
  2071. they shouldn't have been able to get. The best solution here is to
  2072. upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
  2073. or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
  2074. to make sure that the bug can't happen.
  2075. - Never use a bridge or a controller-supplied node as an exit, even
  2076. if its exit policy allows it. Found by wanoskarnet. Fixes bug
  2077. 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
  2078. and 0.2.0.3-alpha (for bridge-purpose descriptors).
  2079. - Only build circuits if we have a sufficient threshold of the total
  2080. descriptors that are marked in the consensus with the "Exit"
  2081. flag. This mitigates an attack proposed by wanoskarnet, in which
  2082. all of a client's bridges collude to restrict the exit nodes that
  2083. the client knows about. Fixes bug 5343.
  2084. - Provide controllers with a safer way to implement the cookie
  2085. authentication mechanism. With the old method, if another locally
  2086. running program could convince a controller that it was the Tor
  2087. process, then that program could trick the controller into telling
  2088. it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
  2089. authentication method uses a challenge-response approach to prevent
  2090. this attack. Fixes bug 5185; implements proposal 193.
  2091. o Major bugfixes:
  2092. - Avoid logging uninitialized data when unable to decode a hidden
  2093. service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
  2094. - Avoid a client-side assertion failure when receiving an INTRODUCE2
  2095. cell on a general purpose circuit. Fixes bug 5644; bugfix on
  2096. 0.2.1.6-alpha.
  2097. - Fix builds when the path to sed, openssl, or sha1sum contains
  2098. spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
  2099. on 0.2.2.1-alpha.
  2100. - Correct our replacements for the timeradd() and timersub() functions
  2101. on platforms that lack them (for example, Windows). The timersub()
  2102. function is used when expiring circuits, while timeradd() is
  2103. currently unused. Bug report and patch by Vektor. Fixes bug 4778;
  2104. bugfix on 0.2.2.24-alpha.
  2105. - Fix the SOCKET_OK test that we use to tell when socket
  2106. creation fails so that it works on Win64. Fixes part of bug 4533;
  2107. bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
  2108. o Minor bugfixes:
  2109. - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
  2110. Fixes bug 5346; bugfix on 0.0.8pre3.
  2111. - Make our number-parsing functions always treat too-large values
  2112. as an error, even when those values exceed the width of the
  2113. underlying type. Previously, if the caller provided these
  2114. functions with minima or maxima set to the extreme values of the
  2115. underlying integer type, these functions would return those
  2116. values on overflow rather than treating overflow as an error.
  2117. Fixes part of bug 5786; bugfix on 0.0.9.
  2118. - Older Linux kernels erroneously respond to strange nmap behavior
  2119. by having accept() return successfully with a zero-length
  2120. socket. When this happens, just close the connection. Previously,
  2121. we would try harder to learn the remote address: but there was
  2122. no such remote address to learn, and our method for trying to
  2123. learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
  2124. on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
  2125. - Correct parsing of certain date types in parse_http_time().
  2126. Without this patch, If-Modified-Since would behave
  2127. incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
  2128. Esteban Manchado Velázques.
  2129. - Change the BridgePassword feature (part of the "bridge community"
  2130. design, which is not yet implemented) to use a time-independent
  2131. comparison. The old behavior might have allowed an adversary
  2132. to use timing to guess the BridgePassword value. Fixes bug 5543;
  2133. bugfix on 0.2.0.14-alpha.
  2134. - Detect and reject certain misformed escape sequences in
  2135. configuration values. Previously, these values would cause us
  2136. to crash if received in a torrc file or over an authenticated
  2137. control port. Bug found by Esteban Manchado Velázquez, and
  2138. independently by Robert Connolly from Matta Consulting who further
  2139. noted that it allows a post-authentication heap overflow. Patch
  2140. by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
  2141. bugfix on 0.2.0.16-alpha.
  2142. - Fix a compile warning when using the --enable-openbsd-malloc
  2143. configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
  2144. - During configure, detect when we're building with clang version
  2145. 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
  2146. CFLAGS. clang doesn't support them yet.
  2147. - When sending an HTTP/1.1 proxy request, include a Host header.
  2148. Fixes bug 5593; bugfix on 0.2.2.1-alpha.
  2149. - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
  2150. command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
  2151. - If we hit the error case where routerlist_insert() replaces an
  2152. existing (old) server descriptor, make sure to remove that
  2153. server descriptor from the old_routers list. Fix related to bug
  2154. 1776. Bugfix on 0.2.2.18-alpha.
  2155. o Minor bugfixes (documentation and log messages):
  2156. - Fix a typo in a log message in rend_service_rendezvous_has_opened().
  2157. Fixes bug 4856; bugfix on Tor 0.0.6.
  2158. - Update "ClientOnly" man page entry to explain that there isn't
  2159. really any point to messing with it. Resolves ticket 5005.
  2160. - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
  2161. directory authority option (introduced in Tor 0.2.2.34).
  2162. - Downgrade the "We're missing a certificate" message from notice
  2163. to info: people kept mistaking it for a real problem, whereas it
  2164. is seldom the problem even when we are failing to bootstrap. Fixes
  2165. bug 5067; bugfix on 0.2.0.10-alpha.
  2166. - Correctly spell "connect" in a log message on failure to create a
  2167. controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
  2168. - Clarify the behavior of MaxCircuitDirtiness with hidden service
  2169. circuits. Fixes issue 5259.
  2170. o Minor features:
  2171. - Directory authorities now reject versions of Tor older than
  2172. 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
  2173. inclusive. These versions accounted for only a small fraction of
  2174. the Tor network, and have numerous known security issues. Resolves
  2175. issue 4788.
  2176. - Update to the May 1 2012 Maxmind GeoLite Country database.
  2177. - Feature removal:
  2178. - When sending or relaying a RELAY_EARLY cell, we used to convert
  2179. it to a RELAY cell if the connection was using the v1 link
  2180. protocol. This was a workaround for older versions of Tor, which
  2181. didn't handle RELAY_EARLY cells properly. Now that all supported
  2182. versions can handle RELAY_EARLY cells, and now that we're enforcing
  2183. the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
  2184. remove this workaround. Addresses bug 4786.
  2185. Changes in version 0.2.2.35 - 2011-12-16
  2186. Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
  2187. buffers code. Absolutely everybody should upgrade.
  2188. The bug relied on an incorrect calculation when making data continuous
  2189. in one of our IO buffers, if the first chunk of the buffer was
  2190. misaligned by just the wrong amount. The miscalculation would allow an
  2191. attacker to overflow a piece of heap-allocated memory. To mount this
  2192. attack, the attacker would need to either open a SOCKS connection to
  2193. Tor's SocksPort (usually restricted to localhost), or target a Tor
  2194. instance configured to make its connections through a SOCKS proxy
  2195. (which Tor does not do by default).
  2196. Good security practice requires that all heap-overflow bugs should be
  2197. presumed to be exploitable until proven otherwise, so we are treating
  2198. this as a potential code execution attack. Please upgrade immediately!
  2199. This bug does not affect bufferevents-based builds of Tor. Special
  2200. thanks to "Vektor" for reporting this issue to us!
  2201. Tor 0.2.2.35 also fixes several bugs in previous versions, including
  2202. crash bugs for unusual configurations, and a long-term bug that
  2203. would prevent Tor from starting on Windows machines with draconian
  2204. AV software.
  2205. With this release, we remind everyone that 0.2.0.x has reached its
  2206. formal end-of-life. Those Tor versions have many known flaws, and
  2207. nobody should be using them. You should upgrade -- ideally to the
  2208. 0.2.2.x series. If you're using a Linux or BSD and its packages are
  2209. obsolete, stop using those packages and upgrade anyway.
  2210. The Tor 0.2.1.x series is also approaching its end-of-life: it will no
  2211. longer receive support after some time in early 2012.
  2212. o Major bugfixes:
  2213. - Fix a heap overflow bug that could occur when trying to pull
  2214. data into the first chunk of a buffer, when that chunk had
  2215. already had some data drained from it. Fixes CVE-2011-2778;
  2216. bugfix on 0.2.0.16-alpha. Reported by "Vektor".
  2217. - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
  2218. that it doesn't attempt to allocate a socketpair. This could cause
  2219. some problems on Windows systems with overzealous firewalls. Fix for
  2220. bug 4457; workaround for Libevent versions 2.0.1-alpha through
  2221. 2.0.15-stable.
  2222. - If we mark an OR connection for close based on a cell we process,
  2223. don't process any further cells on it. We already avoid further
  2224. reads on marked-for-close connections, but now we also discard the
  2225. cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
  2226. which was the first version where we might mark a connection for
  2227. close based on processing a cell on it.
  2228. - Correctly sanity-check that we don't underflow on a memory
  2229. allocation (and then assert) for hidden service introduction
  2230. point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
  2231. bugfix on 0.2.1.5-alpha.
  2232. - Fix a memory leak when we check whether a hidden service
  2233. descriptor has any usable introduction points left. Fixes bug
  2234. 4424. Bugfix on 0.2.2.25-alpha.
  2235. - Don't crash when we're running as a relay and don't have a GeoIP
  2236. file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
  2237. we've had in the 0.2.3.x branch already.
  2238. - When running as a client, do not print a misleading (and plain
  2239. wrong) log message that we're collecting "directory request"
  2240. statistics: clients don't collect statistics. Also don't create a
  2241. useless (because empty) stats file in the stats/ directory. Fixes
  2242. bug 4353; bugfix on 0.2.2.34.
  2243. o Minor bugfixes:
  2244. - Detect failure to initialize Libevent. This fix provides better
  2245. detection for future instances of bug 4457.
  2246. - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
  2247. function. This was eating up hideously large amounts of time on some
  2248. busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
  2249. - Resolve an integer overflow bug in smartlist_ensure_capacity().
  2250. Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
  2251. Mansour Moufid.
  2252. - Don't warn about unused log_mutex in log.c when building with
  2253. --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
  2254. 0.1.0.6-rc which introduced --disable-threads.
  2255. - When configuring, starting, or stopping an NT service, stop
  2256. immediately after the service configuration attempt has succeeded
  2257. or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
  2258. - When sending a NETINFO cell, include the original address
  2259. received for the other side, not its canonical address. Found
  2260. by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
  2261. - Fix a typo in a hibernation-related log message. Fixes bug 4331;
  2262. bugfix on 0.2.2.23-alpha; found by "tmpname0901".
  2263. - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
  2264. occurred when a client tried to fetch a descriptor for a bridge
  2265. in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
  2266. - Backport fixes for a pair of compilation warnings on Windows.
  2267. Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
  2268. - If we had ever tried to call tor_addr_to_str on an address of
  2269. unknown type, we would have done a strdup on an uninitialized
  2270. buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
  2271. Reported by "troll_un".
  2272. - Correctly detect and handle transient lookup failures from
  2273. tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
  2274. Reported by "troll_un".
  2275. - Fix null-pointer access that could occur if TLS allocation failed.
  2276. Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
  2277. - Use tor_socket_t type for listener argument to accept(). Fixes bug
  2278. 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
  2279. o Minor features:
  2280. - Add two new config options for directory authorities:
  2281. AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
  2282. Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
  2283. that is always sufficient to satisfy the bandwidth requirement for
  2284. the Guard flag. Now it will be easier for researchers to simulate
  2285. Tor networks with different values. Resolves ticket 4484.
  2286. - When Tor ignores a hidden service specified in its configuration,
  2287. include the hidden service's directory in the warning message.
  2288. Previously, we would only tell the user that some hidden service
  2289. was ignored. Bugfix on 0.0.6; fixes bug 4426.
  2290. - Update to the December 6 2011 Maxmind GeoLite Country database.
  2291. o Packaging changes:
  2292. - Make it easier to automate expert package builds on Windows,
  2293. by removing an absolute path from makensis.exe command.
  2294. Changes in version 0.2.1.32 - 2011-12-16
  2295. Tor 0.2.1.32 backports important security and privacy fixes for
  2296. oldstable. This release is intended only for package maintainers and
  2297. others who cannot use the 0.2.2 stable series. All others should be
  2298. using Tor 0.2.2.x or newer.
  2299. The Tor 0.2.1.x series will reach formal end-of-life some time in
  2300. early 2012; we will stop releasing patches for it then.
  2301. o Major bugfixes (also included in 0.2.2.x):
  2302. - Correctly sanity-check that we don't underflow on a memory
  2303. allocation (and then assert) for hidden service introduction
  2304. point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
  2305. bugfix on 0.2.1.5-alpha.
  2306. - Fix a heap overflow bug that could occur when trying to pull
  2307. data into the first chunk of a buffer, when that chunk had
  2308. already had some data drained from it. Fixes CVE-2011-2778;
  2309. bugfix on 0.2.0.16-alpha. Reported by "Vektor".
  2310. o Minor features:
  2311. - Update to the December 6 2011 Maxmind GeoLite Country database.
  2312. Changes in version 0.2.2.34 - 2011-10-26
  2313. Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
  2314. can deanonymize Tor users. Everybody should upgrade.
  2315. The attack relies on four components: 1) Clients reuse their TLS cert
  2316. when talking to different relays, so relays can recognize a user by
  2317. the identity key in her cert. 2) An attacker who knows the client's
  2318. identity key can probe each guard relay to see if that identity key
  2319. is connected to that guard relay right now. 3) A variety of active
  2320. attacks in the literature (starting from "Low-Cost Traffic Analysis
  2321. of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
  2322. discover the guard relays that a Tor user visiting the website is using.
  2323. 4) Clients typically pick three guards at random, so the set of guards
  2324. for a given user could well be a unique fingerprint for her. This
  2325. release fixes components #1 and #2, which is enough to block the attack;
  2326. the other two remain as open research problems. Special thanks to
  2327. "frosty_un" for reporting the issue to us!
  2328. Clients should upgrade so they are no longer recognizable by the TLS
  2329. certs they present. Relays should upgrade so they no longer allow a
  2330. remote attacker to probe them to test whether unpatched clients are
  2331. currently connected to them.
  2332. This release also fixes several vulnerabilities that allow an attacker
  2333. to enumerate bridge relays. Some bridge enumeration attacks still
  2334. remain; see for example proposal 188.
  2335. o Privacy/anonymity fixes (clients):
  2336. - Clients and bridges no longer send TLS certificate chains on
  2337. outgoing OR connections. Previously, each client or bridge would
  2338. use the same cert chain for all outgoing OR connections until
  2339. its IP address changes, which allowed any relay that the client
  2340. or bridge contacted to determine which entry guards it is using.
  2341. Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
  2342. - If a relay receives a CREATE_FAST cell on a TLS connection, it
  2343. no longer considers that connection as suitable for satisfying a
  2344. circuit EXTEND request. Now relays can protect clients from the
  2345. CVE-2011-2768 issue even if the clients haven't upgraded yet.
  2346. - Directory authorities no longer assign the Guard flag to relays
  2347. that haven't upgraded to the above "refuse EXTEND requests
  2348. to client connections" fix. Now directory authorities can
  2349. protect clients from the CVE-2011-2768 issue even if neither
  2350. the clients nor the relays have upgraded yet. There's a new
  2351. "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
  2352. to let us transition smoothly, else tomorrow there would be no
  2353. guard relays.
  2354. o Privacy/anonymity fixes (bridge enumeration):
  2355. - Bridge relays now do their directory fetches inside Tor TLS
  2356. connections, like all the other clients do, rather than connecting
  2357. directly to the DirPort like public relays do. Removes another
  2358. avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
  2359. - Bridges relays now build circuits for themselves in a more similar
  2360. way to how clients build them. Removes another avenue for
  2361. enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
  2362. when bridges were introduced.
  2363. - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
  2364. that they initiated. Relays could distinguish incoming bridge
  2365. connections from client connections, creating another avenue for
  2366. enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
  2367. Found by "frosty_un".
  2368. o Major bugfixes:
  2369. - Fix a crash bug when changing node restrictions while a DNS lookup
  2370. is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
  2371. by "Tey'".
  2372. - Don't launch a useless circuit after failing to use one of a
  2373. hidden service's introduction points. Previously, we would
  2374. launch a new introduction circuit, but not set the hidden service
  2375. which that circuit was intended to connect to, so it would never
  2376. actually be used. A different piece of code would then create a
  2377. new introduction circuit correctly. Bug reported by katmagic and
  2378. found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
  2379. o Minor bugfixes:
  2380. - Change an integer overflow check in the OpenBSD_Malloc code so
  2381. that GCC is less likely to eliminate it as impossible. Patch
  2382. from Mansour Moufid. Fixes bug 4059.
  2383. - When a hidden service turns an extra service-side introduction
  2384. circuit into a general-purpose circuit, free the rend_data and
  2385. intro_key fields first, so we won't leak memory if the circuit
  2386. is cannibalized for use as another service-side introduction
  2387. circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
  2388. - Bridges now skip DNS self-tests, to act a little more stealthily.
  2389. Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
  2390. bridges. Patch by "warms0x".
  2391. - Fix internal bug-checking logic that was supposed to catch
  2392. failures in digest generation so that it will fail more robustly
  2393. if we ask for a nonexistent algorithm. Found by Coverity Scan.
  2394. Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
  2395. - Report any failure in init_keys() calls launched because our
  2396. IP address has changed. Spotted by Coverity Scan. Bugfix on
  2397. 0.1.1.4-alpha; fixes CID 484.
  2398. o Minor bugfixes (log messages and documentation):
  2399. - Remove a confusing dollar sign from the example fingerprint in the
  2400. man page, and also make the example fingerprint a valid one. Fixes
  2401. bug 4309; bugfix on 0.2.1.3-alpha.
  2402. - The next version of Windows will be called Windows 8, and it has
  2403. a major version of 6, minor version of 2. Correctly identify that
  2404. version instead of calling it "Very recent version". Resolves
  2405. ticket 4153; reported by funkstar.
  2406. - Downgrade log messages about circuit timeout calibration from
  2407. "notice" to "info": they don't require or suggest any human
  2408. intervention. Patch from Tom Lowenthal. Fixes bug 4063;
  2409. bugfix on 0.2.2.14-alpha.
  2410. o Minor features:
  2411. - Turn on directory request statistics by default and include them in
  2412. extra-info descriptors. Don't break if we have no GeoIP database.
  2413. Backported from 0.2.3.1-alpha; implements ticket 3951.
  2414. - Update to the October 4 2011 Maxmind GeoLite Country database.
  2415. Changes in version 0.2.1.31 - 2011-10-26
  2416. Tor 0.2.1.31 backports important security and privacy fixes for
  2417. oldstable. This release is intended only for package maintainers and
  2418. others who cannot use the 0.2.2 stable series. All others should be
  2419. using Tor 0.2.2.x or newer.
  2420. o Security fixes (also included in 0.2.2.x):
  2421. - Replace all potentially sensitive memory comparison operations
  2422. with versions whose runtime does not depend on the data being
  2423. compared. This will help resist a class of attacks where an
  2424. adversary can use variations in timing information to learn
  2425. sensitive data. Fix for one case of bug 3122. (Safe memcmp
  2426. implementation by Robert Ransom based partially on code by DJB.)
  2427. - Fix an assert in parsing router descriptors containing IPv6
  2428. addresses. This one took down the directory authorities when
  2429. somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
  2430. o Privacy/anonymity fixes (also included in 0.2.2.x):
  2431. - Clients and bridges no longer send TLS certificate chains on
  2432. outgoing OR connections. Previously, each client or bridge would
  2433. use the same cert chain for all outgoing OR connections until
  2434. its IP address changes, which allowed any relay that the client
  2435. or bridge contacted to determine which entry guards it is using.
  2436. Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
  2437. - If a relay receives a CREATE_FAST cell on a TLS connection, it
  2438. no longer considers that connection as suitable for satisfying a
  2439. circuit EXTEND request. Now relays can protect clients from the
  2440. CVE-2011-2768 issue even if the clients haven't upgraded yet.
  2441. - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
  2442. that they initiated. Relays could distinguish incoming bridge
  2443. connections from client connections, creating another avenue for
  2444. enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
  2445. Found by "frosty_un".
  2446. - When receiving a hidden service descriptor, check that it is for
  2447. the hidden service we wanted. Previously, Tor would store any
  2448. hidden service descriptors that a directory gave it, whether it
  2449. wanted them or not. This wouldn't have let an attacker impersonate
  2450. a hidden service, but it did let directories pre-seed a client
  2451. with descriptors that it didn't want. Bugfix on 0.0.6.
  2452. - Avoid linkability based on cached hidden service descriptors: forget
  2453. all hidden service descriptors cached as a client when processing a
  2454. SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
  2455. - Make the bridge directory authority refuse to answer directory
  2456. requests for "all" descriptors. It used to include bridge
  2457. descriptors in its answer, which was a major information leak.
  2458. Found by "piebeer". Bugfix on 0.2.0.3-alpha.
  2459. - Don't attach new streams to old rendezvous circuits after SIGNAL
  2460. NEWNYM. Previously, we would keep using an existing rendezvous
  2461. circuit if it remained open (i.e. if it were kept open by a
  2462. long-lived stream, or if a new stream were attached to it before
  2463. Tor could notice that it was old and no longer in use). Bugfix on
  2464. 0.1.1.15-rc; fixes bug 3375.
  2465. o Minor bugfixes (also included in 0.2.2.x):
  2466. - When we restart our relay, we might get a successful connection
  2467. from the outside before we've started our reachability tests,
  2468. triggering a warning: "ORPort found reachable, but I have no
  2469. routerinfo yet. Failing to inform controller of success." This
  2470. bug was harmless unless Tor is running under a controller
  2471. like Vidalia, in which case the controller would never get a
  2472. REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
  2473. fixes bug 1172.
  2474. - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
  2475. enabled. Fixes bug 1526.
  2476. - Remove undocumented option "-F" from tor-resolve: it hasn't done
  2477. anything since 0.2.1.16-rc.
  2478. - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
  2479. None of the cases where we did this before were wrong, but by making
  2480. this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
  2481. - Fix a rare crash bug that could occur when a client was configured
  2482. with a large number of bridges. Fixes bug 2629; bugfix on
  2483. 0.2.1.2-alpha. Bugfix by trac user "shitlei".
  2484. - Correct the warning displayed when a rendezvous descriptor exceeds
  2485. the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
  2486. John Brooks.
  2487. - Fix an uncommon assertion failure when running with DNSPort under
  2488. heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
  2489. - When warning about missing zlib development packages during compile,
  2490. give the correct package names. Bugfix on 0.2.0.1-alpha.
  2491. - Require that introduction point keys and onion keys have public
  2492. exponent 65537. Bugfix on 0.2.0.10-alpha.
  2493. - Do not crash when our configuration file becomes unreadable, for
  2494. example due to a permissions change, between when we start up
  2495. and when a controller calls SAVECONF. Fixes bug 3135; bugfix
  2496. on 0.0.9pre6.
  2497. - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
  2498. Fixes bug 3208.
  2499. - Always NUL-terminate the sun_path field of a sockaddr_un before
  2500. passing it to the kernel. (Not a security issue: kernels are
  2501. smart enough to reject bad sockaddr_uns.) Found by Coverity;
  2502. CID #428. Bugfix on Tor 0.2.0.3-alpha.
  2503. - Don't stack-allocate the list of supplementary GIDs when we're
  2504. about to log them. Stack-allocating NGROUPS_MAX gid_t elements
  2505. could take up to 256K, which is way too much stack. Found by
  2506. Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
  2507. o Minor bugfixes (only in 0.2.1.x):
  2508. - Resume using micro-version numbers in 0.2.1.x: our Debian packages
  2509. rely on them. Bugfix on 0.2.1.30.
  2510. - Use git revisions instead of svn revisions when generating our
  2511. micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
  2512. o Minor features (also included in 0.2.2.x):
  2513. - Adjust the expiration time on our SSL session certificates to
  2514. better match SSL certs seen in the wild. Resolves ticket 4014.
  2515. - Allow nameservers with IPv6 address. Resolves bug 2574.
  2516. - Update to the October 4 2011 Maxmind GeoLite Country database.
  2517. Changes in version 0.2.2.33 - 2011-09-13
  2518. Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
  2519. TLS handshake that makes relays and bridges that run this new version
  2520. reachable from Iran again.
  2521. o Major bugfixes:
  2522. - Avoid an assertion failure when reloading a configuration with
  2523. TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
  2524. 3923; bugfix on 0.2.2.25-alpha.
  2525. o Minor features (security):
  2526. - Check for replays of the public-key encrypted portion of an
  2527. INTRODUCE1 cell, in addition to the current check for replays of
  2528. the g^x value. This prevents a possible class of active attacks
  2529. by an attacker who controls both an introduction point and a
  2530. rendezvous point, and who uses the malleability of AES-CTR to
  2531. alter the encrypted g^x portion of the INTRODUCE1 cell. We think
  2532. that these attacks are infeasible (requiring the attacker to send
  2533. on the order of zettabytes of altered cells in a short interval),
  2534. but we'd rather block them off in case there are any classes of
  2535. this attack that we missed. Reported by Willem Pinckaers.
  2536. o Minor features:
  2537. - Adjust the expiration time on our SSL session certificates to
  2538. better match SSL certs seen in the wild. Resolves ticket 4014.
  2539. - Change the default required uptime for a relay to be accepted as
  2540. a HSDir (hidden service directory) from 24 hours to 25 hours.
  2541. Improves on 0.2.0.10-alpha; resolves ticket 2649.
  2542. - Add a VoteOnHidServDirectoriesV2 config option to allow directory
  2543. authorities to abstain from voting on assignment of the HSDir
  2544. consensus flag. Related to bug 2649.
  2545. - Update to the September 6 2011 Maxmind GeoLite Country database.
  2546. o Minor bugfixes (documentation and log messages):
  2547. - Correct the man page to explain that HashedControlPassword and
  2548. CookieAuthentication can both be set, in which case either method
  2549. is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
  2550. when we decided to allow these config options to both be set. Issue
  2551. raised by bug 3898.
  2552. - Demote the 'replay detected' log message emitted when a hidden
  2553. service receives the same Diffie-Hellman public key in two different
  2554. INTRODUCE2 cells to info level. A normal Tor client can cause that
  2555. log message during its normal operation. Bugfix on 0.2.1.6-alpha;
  2556. fixes part of bug 2442.
  2557. - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
  2558. level. There is nothing that a hidden service's operator can do
  2559. to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
  2560. of bug 2442.
  2561. - Clarify a log message specifying the characters permitted in
  2562. HiddenServiceAuthorizeClient client names. Previously, the log
  2563. message said that "[A-Za-z0-9+-_]" were permitted; that could have
  2564. given the impression that every ASCII character between "+" and "_"
  2565. was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
  2566. o Build fixes:
  2567. - Provide a substitute implementation of lround() for MSVC, which
  2568. apparently lacks it. Patch from Gisle Vanem.
  2569. - Clean up some code issues that prevented Tor from building on older
  2570. BSDs. Fixes bug 3894; reported by "grarpamp".
  2571. - Search for a platform-specific version of "ar" when cross-compiling.
  2572. Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
  2573. Changes in version 0.2.2.32 - 2011-08-27
  2574. The Tor 0.2.2 release series is dedicated to the memory of Andreas
  2575. Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
  2576. a founder of the PETS community, a leader in our field, a mentor,
  2577. and a friend. He left us with these words: "I had the possibility
  2578. to contribute to this world that is not as it should be. I hope I
  2579. could help in some areas to make the world a better place, and that
  2580. I could also encourage other people to be engaged in improving the
  2581. world. Please, stay engaged. This world needs you, your love, your
  2582. initiative -- now I cannot be part of that anymore."
  2583. Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
  2584. ready. More than two years in the making, this release features improved
  2585. client performance and hidden service reliability, better compatibility
  2586. for Android, correct behavior for bridges that listen on more than
  2587. one address, more extensible and flexible directory object handling,
  2588. better reporting of network statistics, improved code security, and
  2589. many many other features and bugfixes.
  2590. o Major features (client performance):
  2591. - When choosing which cells to relay first, relays now favor circuits
  2592. that have been quiet recently, to provide lower latency for
  2593. low-volume circuits. By default, relays enable or disable this
  2594. feature based on a setting in the consensus. They can override
  2595. this default by using the new "CircuitPriorityHalflife" config
  2596. option. Design and code by Ian Goldberg, Can Tang, and Chris
  2597. Alexander.
  2598. - Directory authorities now compute consensus weightings that instruct
  2599. clients how to weight relays flagged as Guard, Exit, Guard+Exit,
  2600. and no flag. Clients use these weightings to distribute network load
  2601. more evenly across these different relay types. The weightings are
  2602. in the consensus so we can change them globally in the future. Extra
  2603. thanks to "outofwords" for finding some nasty security bugs in
  2604. the first implementation of this feature.
  2605. o Major features (client performance, circuit build timeout):
  2606. - Tor now tracks how long it takes to build client-side circuits
  2607. over time, and adapts its timeout to local network performance.
  2608. Since a circuit that takes a long time to build will also provide
  2609. bad performance, we get significant latency improvements by
  2610. discarding the slowest 20% of circuits. Specifically, Tor creates
  2611. circuits more aggressively than usual until it has enough data
  2612. points for a good timeout estimate. Implements proposal 151.
  2613. - Circuit build timeout constants can be controlled by consensus
  2614. parameters. We set good defaults for these parameters based on
  2615. experimentation on broadband and simulated high-latency links.
  2616. - Circuit build time learning can be disabled via consensus parameter
  2617. or by the client via a LearnCircuitBuildTimeout config option. We
  2618. also automatically disable circuit build time calculation if either
  2619. AuthoritativeDirectory is set, or if we fail to write our state
  2620. file. Implements ticket 1296.
  2621. o Major features (relays use their capacity better):
  2622. - Set SO_REUSEADDR socket option on all sockets, not just
  2623. listeners. This should help busy exit nodes avoid running out of
  2624. useable ports just because all the ports have been used in the
  2625. near past. Resolves issue 2850.
  2626. - Relays now save observed peak bandwidth throughput rates to their
  2627. state file (along with total usage, which was already saved),
  2628. so that they can determine their correct estimated bandwidth on
  2629. restart. Resolves bug 1863, where Tor relays would reset their
  2630. estimated bandwidth to 0 after restarting.
  2631. - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
  2632. should give us approximately 40-50% more Guard-flagged nodes,
  2633. improving the anonymity the Tor network can provide and also
  2634. decreasing the dropoff in throughput that relays experience when
  2635. they first get the Guard flag.
  2636. - Directory authorities now take changes in router IP address and
  2637. ORPort into account when determining router stability. Previously,
  2638. if a router changed its IP or ORPort, the authorities would not
  2639. treat it as having any downtime for the purposes of stability
  2640. calculation, whereas clients would experience downtime since the
  2641. change would take a while to propagate to them. Resolves issue 1035.
  2642. - New AccelName and AccelDir options add support for dynamic OpenSSL
  2643. hardware crypto acceleration engines.
  2644. o Major features (relays control their load better):
  2645. - Exit relays now try harder to block exit attempts from unknown
  2646. relays, to make it harder for people to use them as one-hop proxies
  2647. a la tortunnel. Controlled by the refuseunknownexits consensus
  2648. parameter (currently enabled), or you can override it on your
  2649. relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
  2650. based on a variant of proposal 163.
  2651. - Add separate per-conn write limiting to go with the per-conn read
  2652. limiting. We added a global write limit in Tor 0.1.2.5-alpha,
  2653. but never per-conn write limits.
  2654. - New consensus params "bwconnrate" and "bwconnburst" to let us
  2655. rate-limit client connections as they enter the network. It's
  2656. controlled in the consensus so we can turn it on and off for
  2657. experiments. It's starting out off. Based on proposal 163.
  2658. o Major features (controllers):
  2659. - Export GeoIP information on bridge usage to controllers even if we
  2660. have not yet been running for 24 hours. Now Vidalia bridge operators
  2661. can get more accurate and immediate feedback about their
  2662. contributions to the network.
  2663. - Add an __OwningControllerProcess configuration option and a
  2664. TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
  2665. that when it exits, Tor will shut down. Implements feature 3049.
  2666. o Major features (directory authorities):
  2667. - Directory authorities now create, vote on, and serve multiple
  2668. parallel formats of directory data as part of their voting process.
  2669. Partially implements Proposal 162: "Publish the consensus in
  2670. multiple flavors".
  2671. - Directory authorities now agree on and publish small summaries
  2672. of router information that clients can use in place of regular
  2673. server descriptors. This transition will allow Tor 0.2.3 clients
  2674. to use far less bandwidth for downloading information about the
  2675. network. Begins the implementation of Proposal 158: "Clients
  2676. download consensus + microdescriptors".
  2677. - The directory voting system is now extensible to use multiple hash
  2678. algorithms for signatures and resource selection. Newer formats
  2679. are signed with SHA256, with a possibility for moving to a better
  2680. hash algorithm in the future.
  2681. - Directory authorities can now vote on arbitary integer values as
  2682. part of the consensus process. This is designed to help set
  2683. network-wide parameters. Implements proposal 167.
  2684. o Major features and bugfixes (node selection):
  2685. - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
  2686. ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
  2687. options. Previously, we had been ambiguous in describing what
  2688. counted as an "exit" node, and what operations exactly "StrictNodes
  2689. 0" would permit. This created confusion when people saw nodes built
  2690. through unexpected circuits, and made it hard to tell real bugs from
  2691. surprises. Now the intended behavior is:
  2692. . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
  2693. a node that delivers user traffic outside the Tor network.
  2694. . "Entry", in the context of EntryNodes, means a node used as the
  2695. first hop of a multihop circuit. It doesn't include direct
  2696. connections to directory servers.
  2697. . "ExcludeNodes" applies to all nodes.
  2698. . "StrictNodes" changes the behavior of ExcludeNodes only. When
  2699. StrictNodes is set, Tor should avoid all nodes listed in
  2700. ExcludeNodes, even when it will make user requests fail. When
  2701. StrictNodes is *not* set, then Tor should follow ExcludeNodes
  2702. whenever it can, except when it must use an excluded node to
  2703. perform self-tests, connect to a hidden service, provide a
  2704. hidden service, fulfill a .exit request, upload directory
  2705. information, or fetch directory information.
  2706. Collectively, the changes to implement the behavior fix bug 1090.
  2707. - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
  2708. change during a config reload, mark and discard all our origin
  2709. circuits. This fix should address edge cases where we change the
  2710. config options and but then choose a circuit that we created before
  2711. the change.
  2712. - Make EntryNodes config option much more aggressive even when
  2713. StrictNodes is not set. Before it would prepend your requested
  2714. entrynodes to your list of guard nodes, but feel free to use others
  2715. after that. Now it chooses only from your EntryNodes if any of
  2716. those are available, and only falls back to others if a) they're
  2717. all down and b) StrictNodes is not set.
  2718. - Now we refresh your entry guards from EntryNodes at each consensus
  2719. fetch -- rather than just at startup and then they slowly rot as
  2720. the network changes.
  2721. - Add support for the country code "{??}" in torrc options like
  2722. ExcludeNodes, to indicate all routers of unknown country. Closes
  2723. bug 1094.
  2724. - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
  2725. a node is listed in both, it's treated as excluded.
  2726. - ExcludeNodes now applies to directory nodes -- as a preference if
  2727. StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
  2728. Don't exclude all the directory authorities and set StrictNodes to 1
  2729. unless you really want your Tor to break.
  2730. - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
  2731. - ExcludeExitNodes now overrides .exit requests.
  2732. - We don't use bridges listed in ExcludeNodes.
  2733. - When StrictNodes is 1:
  2734. . We now apply ExcludeNodes to hidden service introduction points
  2735. and to rendezvous points selected by hidden service users. This
  2736. can make your hidden service less reliable: use it with caution!
  2737. . If we have used ExcludeNodes on ourself, do not try relay
  2738. reachability self-tests.
  2739. . If we have excluded all the directory authorities, we will not
  2740. even try to upload our descriptor if we're a relay.
  2741. . Do not honor .exit requests to an excluded node.
  2742. - When the set of permitted nodes changes, we now remove any mappings
  2743. introduced via TrackExitHosts to now-excluded nodes. Bugfix on
  2744. 0.1.0.1-rc.
  2745. - We never cannibalize a circuit that had excluded nodes on it, even
  2746. if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
  2747. - Improve log messages related to excluded nodes.
  2748. o Major features (misc):
  2749. - Numerous changes, bugfixes, and workarounds from Nathan Freitas
  2750. to help Tor build correctly for Android phones.
  2751. - The options SocksPort, ControlPort, and so on now all accept a
  2752. value "auto" that opens a socket on an OS-selected port. A
  2753. new ControlPortWriteToFile option tells Tor to write its
  2754. actual control port or ports to a chosen file. If the option
  2755. ControlPortFileGroupReadable is set, the file is created as
  2756. group-readable. Now users can run two Tor clients on the same
  2757. system without needing to manually mess with parameters. Resolves
  2758. part of ticket 3076.
  2759. - Tor now supports tunneling all of its outgoing connections over
  2760. a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
  2761. configuration options. Code by Christopher Davis.
  2762. o Code security improvements:
  2763. - Replace all potentially sensitive memory comparison operations
  2764. with versions whose runtime does not depend on the data being
  2765. compared. This will help resist a class of attacks where an
  2766. adversary can use variations in timing information to learn
  2767. sensitive data. Fix for one case of bug 3122. (Safe memcmp
  2768. implementation by Robert Ransom based partially on code by DJB.)
  2769. - Enable Address Space Layout Randomization (ASLR) and Data Execution
  2770. Prevention (DEP) by default on Windows to make it harder for
  2771. attackers to exploit vulnerabilities. Patch from John Brooks.
  2772. - New "--enable-gcc-hardening" ./configure flag (off by default)
  2773. to turn on gcc compile time hardening options. It ensures
  2774. that signed ints have defined behavior (-fwrapv), enables
  2775. -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
  2776. with canaries (-fstack-protector-all), turns on ASLR protection if
  2777. supported by the kernel (-fPIE, -pie), and adds additional security
  2778. related warnings. Verified to work on Mac OS X and Debian Lenny.
  2779. - New "--enable-linker-hardening" ./configure flag (off by default)
  2780. to turn on ELF specific hardening features (relro, now). This does
  2781. not work with Mac OS X or any other non-ELF binary format.
  2782. - Always search the Windows system directory for system DLLs, and
  2783. nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
  2784. - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
  2785. current and future memory pages via mlockall(). On supported
  2786. platforms (modern Linux and probably BSD but not Windows or OS X),
  2787. this should effectively disable any and all attempts to page out
  2788. memory. This option requires that you start your Tor as root --
  2789. if you use DisableAllSwap, please consider using the User option
  2790. to properly reduce the privileges of your Tor.
  2791. o Major bugfixes (crashes):
  2792. - Fix crash bug on platforms where gmtime and localtime can return
  2793. NULL. Windows 7 users were running into this one. Fixes part of bug
  2794. 2077. Bugfix on all versions of Tor. Found by boboper.
  2795. - Introduce minimum/maximum values that clients will believe
  2796. from the consensus. Now we'll have a better chance to avoid crashes
  2797. or worse when a consensus param has a weird value.
  2798. - Fix a rare crash bug that could occur when a client was configured
  2799. with a large number of bridges. Fixes bug 2629; bugfix on
  2800. 0.2.1.2-alpha. Bugfix by trac user "shitlei".
  2801. - Do not crash when our configuration file becomes unreadable, for
  2802. example due to a permissions change, between when we start up
  2803. and when a controller calls SAVECONF. Fixes bug 3135; bugfix
  2804. on 0.0.9pre6.
  2805. - If we're in the pathological case where there's no exit bandwidth
  2806. but there is non-exit bandwidth, or no guard bandwidth but there
  2807. is non-guard bandwidth, don't crash during path selection. Bugfix
  2808. on 0.2.0.3-alpha.
  2809. - Fix a crash bug when trying to initialize the evdns module in
  2810. Libevent 2. Bugfix on 0.2.1.16-rc.
  2811. o Major bugfixes (stability):
  2812. - Fix an assert in parsing router descriptors containing IPv6
  2813. addresses. This one took down the directory authorities when
  2814. somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
  2815. - Fix an uncommon assertion failure when running with DNSPort under
  2816. heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
  2817. - Treat an unset $HOME like an empty $HOME rather than triggering an
  2818. assert. Bugfix on 0.0.8pre1; fixes bug 1522.
  2819. - More gracefully handle corrupt state files, removing asserts
  2820. in favor of saving a backup and resetting state.
  2821. - Instead of giving an assertion failure on an internal mismatch
  2822. on estimated freelist size, just log a BUG warning and try later.
  2823. Mitigates but does not fix bug 1125.
  2824. - Fix an assert that got triggered when using the TestingTorNetwork
  2825. configuration option and then issuing a GETINFO config-text control
  2826. command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
  2827. - If the cached cert file is unparseable, warn but don't exit.
  2828. o Privacy fixes (relays/bridges):
  2829. - Don't list Windows capabilities in relay descriptors. We never made
  2830. use of them, and maybe it's a bad idea to publish them. Bugfix
  2831. on 0.1.1.8-alpha.
  2832. - If the Nickname configuration option isn't given, Tor would pick a
  2833. nickname based on the local hostname as the nickname for a relay.
  2834. Because nicknames are not very important in today's Tor and the
  2835. "Unnamed" nickname has been implemented, this is now problematic
  2836. behavior: It leaks information about the hostname without being
  2837. useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
  2838. introduced the Unnamed nickname. Reported by tagnaq.
  2839. - Maintain separate TLS contexts and certificates for incoming and
  2840. outgoing connections in bridge relays. Previously we would use the
  2841. same TLS contexts and certs for incoming and outgoing connections.
  2842. Bugfix on 0.2.0.3-alpha; addresses bug 988.
  2843. - Maintain separate identity keys for incoming and outgoing TLS
  2844. contexts in bridge relays. Previously we would use the same
  2845. identity keys for incoming and outgoing TLS contexts. Bugfix on
  2846. 0.2.0.3-alpha; addresses the other half of bug 988.
  2847. - Make the bridge directory authority refuse to answer directory
  2848. requests for "all descriptors". It used to include bridge
  2849. descriptors in its answer, which was a major information leak.
  2850. Found by "piebeer". Bugfix on 0.2.0.3-alpha.
  2851. o Privacy fixes (clients):
  2852. - When receiving a hidden service descriptor, check that it is for
  2853. the hidden service we wanted. Previously, Tor would store any
  2854. hidden service descriptors that a directory gave it, whether it
  2855. wanted them or not. This wouldn't have let an attacker impersonate
  2856. a hidden service, but it did let directories pre-seed a client
  2857. with descriptors that it didn't want. Bugfix on 0.0.6.
  2858. - Start the process of disabling ".exit" address notation, since it
  2859. can be used for a variety of esoteric application-level attacks
  2860. on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
  2861. on 0.0.9rc5.
  2862. - Reject attempts at the client side to open connections to private
  2863. IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
  2864. a randomly chosen exit node. Attempts to do so are always
  2865. ill-defined, generally prevented by exit policies, and usually
  2866. in error. This will also help to detect loops in transparent
  2867. proxy configurations. You can disable this feature by setting
  2868. "ClientRejectInternalAddresses 0" in your torrc.
  2869. - Log a notice when we get a new control connection. Now it's easier
  2870. for security-conscious users to recognize when a local application
  2871. is knocking on their controller door. Suggested by bug 1196.
  2872. o Privacy fixes (newnym):
  2873. - Avoid linkability based on cached hidden service descriptors: forget
  2874. all hidden service descriptors cached as a client when processing a
  2875. SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
  2876. - On SIGHUP, do not clear out all TrackHostExits mappings, client
  2877. DNS cache entries, and virtual address mappings: that's what
  2878. NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
  2879. - Don't attach new streams to old rendezvous circuits after SIGNAL
  2880. NEWNYM. Previously, we would keep using an existing rendezvous
  2881. circuit if it remained open (i.e. if it were kept open by a
  2882. long-lived stream, or if a new stream were attached to it before
  2883. Tor could notice that it was old and no longer in use). Bugfix on
  2884. 0.1.1.15-rc; fixes bug 3375.
  2885. o Major bugfixes (relay bandwidth accounting):
  2886. - Fix a bug that could break accounting on 64-bit systems with large
  2887. time_t values, making them hibernate for impossibly long intervals.
  2888. Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
  2889. - Fix a bug in bandwidth accounting that could make us use twice
  2890. the intended bandwidth when our interval start changes due to
  2891. daylight saving time. Now we tolerate skew in stored vs computed
  2892. interval starts: if the start of the period changes by no more than
  2893. 50% of the period's duration, we remember bytes that we transferred
  2894. in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
  2895. o Major bugfixes (bridges):
  2896. - Bridges now use "reject *:*" as their default exit policy. Bugfix
  2897. on 0.2.0.3-alpha. Fixes bug 1113.
  2898. - If you configure your bridge with a known identity fingerprint,
  2899. and the bridge authority is unreachable (as it is in at least
  2900. one country now), fall back to directly requesting the descriptor
  2901. from the bridge. Finishes the feature started in 0.2.0.10-alpha;
  2902. closes bug 1138.
  2903. - Fix a bug where bridge users who configure the non-canonical
  2904. address of a bridge automatically switch to its canonical
  2905. address. If a bridge listens at more than one address, it
  2906. should be able to advertise those addresses independently and
  2907. any non-blocked addresses should continue to work. Bugfix on Tor
  2908. 0.2.0.3-alpha. Fixes bug 2510.
  2909. - If you configure Tor to use bridge A, and then quit and
  2910. configure Tor to use bridge B instead (or if you change Tor
  2911. to use bridge B via the controller), it would happily continue
  2912. to use bridge A if it's still reachable. While this behavior is
  2913. a feature if your goal is connectivity, in some scenarios it's a
  2914. dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
  2915. - When the controller configures a new bridge, don't wait 10 to 60
  2916. seconds before trying to fetch its descriptor. Bugfix on
  2917. 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
  2918. o Major bugfixes (directory authorities):
  2919. - Many relays have been falling out of the consensus lately because
  2920. not enough authorities know about their descriptor for them to get
  2921. a majority of votes. When we deprecated the v2 directory protocol,
  2922. we got rid of the only way that v3 authorities can hear from each
  2923. other about other descriptors. Now authorities examine every v3
  2924. vote for new descriptors, and fetch them from that authority. Bugfix
  2925. on 0.2.1.23.
  2926. - Authorities could be tricked into giving out the Exit flag to relays
  2927. that didn't allow exiting to any ports. This bug could screw
  2928. with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
  2929. 1238. Bug discovered by Martin Kowalczyk.
  2930. - If all authorities restart at once right before a consensus vote,
  2931. nobody will vote about "Running", and clients will get a consensus
  2932. with no usable relays. Instead, authorities refuse to build a
  2933. consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
  2934. o Major bugfixes (stream-level fairness):
  2935. - When receiving a circuit-level SENDME for a blocked circuit, try
  2936. to package cells fairly from all the streams that had previously
  2937. been blocked on that circuit. Previously, we had started with the
  2938. oldest stream, and allowed each stream to potentially exhaust
  2939. the circuit's package window. This gave older streams on any
  2940. given circuit priority over newer ones. Fixes bug 1937. Detected
  2941. originally by Camilo Viecco. This bug was introduced before the
  2942. first Tor release, in svn commit r152: it is the new winner of
  2943. the longest-lived bug prize.
  2944. - Fix a stream fairness bug that would cause newer streams on a given
  2945. circuit to get preference when reading bytes from the origin or
  2946. destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
  2947. introduced before the first Tor release, in svn revision r152.
  2948. - When the exit relay got a circuit-level sendme cell, it started
  2949. reading on the exit streams, even if had 500 cells queued in the
  2950. circuit queue already, so the circuit queue just grew and grew in
  2951. some cases. We fix this by not re-enabling reading on receipt of a
  2952. sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
  2953. on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
  2954. "yetonetime".
  2955. - Newly created streams were allowed to read cells onto circuits,
  2956. even if the circuit's cell queue was blocked and waiting to drain.
  2957. This created potential unfairness, as older streams would be
  2958. blocked, but newer streams would gladly fill the queue completely.
  2959. We add code to detect this situation and prevent any stream from
  2960. getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
  2961. fixes bug 1298.
  2962. o Major bugfixes (hidden services):
  2963. - Apply circuit timeouts to opened hidden-service-related circuits
  2964. based on the correct start time. Previously, we would apply the
  2965. circuit build timeout based on time since the circuit's creation;
  2966. it was supposed to be applied based on time since the circuit
  2967. entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
  2968. - Improve hidden service robustness: When we find that we have
  2969. extended a hidden service's introduction circuit to a relay not
  2970. listed as an introduction point in the HS descriptor we currently
  2971. have, retry with an introduction point from the current
  2972. descriptor. Previously we would just give up. Fixes bugs 1024 and
  2973. 1930; bugfix on 0.2.0.10-alpha.
  2974. - Directory authorities now use data collected from their own
  2975. uptime observations when choosing whether to assign the HSDir flag
  2976. to relays, instead of trusting the uptime value the relay reports in
  2977. its descriptor. This change helps prevent an attack where a small
  2978. set of nodes with frequently-changing identity keys can blackhole
  2979. a hidden service. (Only authorities need upgrade; others will be
  2980. fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
  2981. - Stop assigning the HSDir flag to relays that disable their
  2982. DirPort (and thus will refuse to answer directory requests). This
  2983. fix should dramatically improve the reachability of hidden services:
  2984. hidden services and hidden service clients pick six HSDir relays
  2985. to store and retrieve the hidden service descriptor, and currently
  2986. about half of the HSDir relays will refuse to work. Bugfix on
  2987. 0.2.0.10-alpha; fixes part of bug 1693.
  2988. o Major bugfixes (misc):
  2989. - Clients now stop trying to use an exit node associated with a given
  2990. destination by TrackHostExits if they fail to reach that exit node.
  2991. Fixes bug 2999. Bugfix on 0.2.0.20-rc.
  2992. - Fix a regression that caused Tor to rebind its ports if it receives
  2993. SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
  2994. - Remove an extra pair of quotation marks around the error
  2995. message in control-port STATUS_GENERAL BUG events. Bugfix on
  2996. 0.1.2.6-alpha; fixes bug 3732.
  2997. o Minor features (relays):
  2998. - Ensure that no empty [dirreq-](read|write)-history lines are added
  2999. to an extrainfo document. Implements ticket 2497.
  3000. - When bandwidth accounting is enabled, be more generous with how
  3001. much bandwidth we'll use up before entering "soft hibernation".
  3002. Previously, we'd refuse new connections and circuits once we'd
  3003. used up 95% of our allotment. Now, we use up 95% of our allotment,
  3004. AND make sure that we have no more than 500MB (or 3 hours of
  3005. expected traffic, whichever is lower) remaining before we enter
  3006. soft hibernation.
  3007. - Relays now log the reason for publishing a new relay descriptor,
  3008. so we have a better chance of hunting down instances of bug 1810.
  3009. Resolves ticket 3252.
  3010. - Log a little more clearly about the times at which we're no longer
  3011. accepting new connections (e.g. due to hibernating). Resolves
  3012. bug 2181.
  3013. - When AllowSingleHopExits is set, print a warning to explain to the
  3014. relay operator why most clients are avoiding her relay.
  3015. - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
  3016. Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
  3017. clients are already deprecated because of security bugs.
  3018. o Minor features (network statistics):
  3019. - Directory mirrors that set "DirReqStatistics 1" write statistics
  3020. about directory requests to disk every 24 hours. As compared to the
  3021. "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
  3022. improvements: 1) stats are written to disk exactly every 24 hours;
  3023. 2) estimated shares of v2 and v3 requests are determined as mean
  3024. values, not at the end of a measurement period; 3) unresolved
  3025. requests are listed with country code '??'; 4) directories also
  3026. measure download times.
  3027. - Exit nodes that set "ExitPortStatistics 1" write statistics on the
  3028. number of exit streams and transferred bytes per port to disk every
  3029. 24 hours.
  3030. - Relays that set "CellStatistics 1" write statistics on how long
  3031. cells spend in their circuit queues to disk every 24 hours.
  3032. - Entry nodes that set "EntryStatistics 1" write statistics on the
  3033. rough number and origins of connecting clients to disk every 24
  3034. hours.
  3035. - Relays that write any of the above statistics to disk and set
  3036. "ExtraInfoStatistics 1" include the past 24 hours of statistics in
  3037. their extra-info documents. Implements proposal 166.
  3038. o Minor features (GeoIP and statistics):
  3039. - Provide a log message stating which geoip file we're parsing
  3040. instead of just stating that we're parsing the geoip file.
  3041. Implements ticket 2432.
  3042. - Make sure every relay writes a state file at least every 12 hours.
  3043. Previously, a relay could go for weeks without writing its state
  3044. file, and on a crash could lose its bandwidth history, capacity
  3045. estimates, client country statistics, and so on. Addresses bug 3012.
  3046. - Relays report the number of bytes spent on answering directory
  3047. requests in extra-info descriptors similar to {read,write}-history.
  3048. Implements enhancement 1790.
  3049. - Report only the top 10 ports in exit-port stats in order not to
  3050. exceed the maximum extra-info descriptor length of 50 KB. Implements
  3051. task 2196.
  3052. - If writing the state file to disk fails, wait up to an hour before
  3053. retrying again, rather than trying again each second. Fixes bug
  3054. 2346; bugfix on Tor 0.1.1.3-alpha.
  3055. - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
  3056. when we switch from being a public relay to a bridge. Otherwise
  3057. there will still be clients that see the relay in their consensus,
  3058. and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
  3059. bug 932.
  3060. - Update to the August 2 2011 Maxmind GeoLite Country database.
  3061. o Minor features (clients):
  3062. - When expiring circuits, use microsecond timers rather than
  3063. one-second timers. This can avoid an unpleasant situation where a
  3064. circuit is launched near the end of one second and expired right
  3065. near the beginning of the next, and prevent fluctuations in circuit
  3066. timeout values.
  3067. - If we've configured EntryNodes and our network goes away and/or all
  3068. our entrynodes get marked down, optimistically retry them all when
  3069. a new socks application request appears. Fixes bug 1882.
  3070. - Always perform router selections using weighted relay bandwidth,
  3071. even if we don't need a high capacity circuit at the time. Non-fast
  3072. circuits now only differ from fast ones in that they can use relays
  3073. not marked with the Fast flag. This "feature" could turn out to
  3074. be a horrible bug; we should investigate more before it goes into
  3075. a stable release.
  3076. - When we run out of directory information such that we can't build
  3077. circuits, but then get enough that we can build circuits, log when
  3078. we actually construct a circuit, so the user has a better chance of
  3079. knowing what's going on. Fixes bug 1362.
  3080. - Log SSL state transitions at debug level during handshake, and
  3081. include SSL states in error messages. This may help debug future
  3082. SSL handshake issues.
  3083. o Minor features (directory authorities):
  3084. - When a router changes IP address or port, authorities now launch
  3085. a new reachability test for it. Implements ticket 1899.
  3086. - Directory authorities now reject relays running any versions of
  3087. Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
  3088. known bugs that keep RELAY_EARLY cells from working on rendezvous
  3089. circuits. Followup to fix for bug 2081.
  3090. - Directory authorities now reject relays running any version of Tor
  3091. older than 0.2.0.26-rc. That version is the earliest that fetches
  3092. current directory information correctly. Fixes bug 2156.
  3093. - Directory authorities now do an immediate reachability check as soon
  3094. as they hear about a new relay. This change should slightly reduce
  3095. the time between setting up a relay and getting listed as running
  3096. in the consensus. It should also improve the time between setting
  3097. up a bridge and seeing use by bridge users.
  3098. - Directory authorities no longer launch a TLS connection to every
  3099. relay as they startup. Now that we have 2k+ descriptors cached,
  3100. the resulting network hiccup is becoming a burden. Besides,
  3101. authorities already avoid voting about Running for the first half
  3102. hour of their uptime.
  3103. - Directory authorities now log the source of a rejected POSTed v3
  3104. networkstatus vote, so we can track failures better.
  3105. - Backport code from 0.2.3.x that allows directory authorities to
  3106. clean their microdescriptor caches. Needed to resolve bug 2230.
  3107. o Minor features (hidden services):
  3108. - Use computed circuit-build timeouts to decide when to launch
  3109. parallel introduction circuits for hidden services. (Previously,
  3110. we would retry after 15 seconds.)
  3111. - Don't allow v0 hidden service authorities to act as clients.
  3112. Required by fix for bug 3000.
  3113. - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
  3114. by fix for bug 3000.
  3115. - Make hidden services work better in private Tor networks by not
  3116. requiring any uptime to join the hidden service descriptor
  3117. DHT. Implements ticket 2088.
  3118. - Log (at info level) when purging pieces of hidden-service-client
  3119. state because of SIGNAL NEWNYM.
  3120. o Minor features (controller interface):
  3121. - New "GETINFO net/listeners/(type)" controller command to return
  3122. a list of addresses and ports that are bound for listeners for a
  3123. given connection type. This is useful when the user has configured
  3124. "SocksPort auto" and the controller needs to know which port got
  3125. chosen. Resolves another part of ticket 3076.
  3126. - Have the controller interface give a more useful message than
  3127. "Internal Error" in response to failed GETINFO requests.
  3128. - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
  3129. event, to give information on the current rate of circuit timeouts
  3130. over our stored history.
  3131. - The 'EXTENDCIRCUIT' control port command can now be used with
  3132. a circ id of 0 and no path. This feature will cause Tor to build
  3133. a new 'fast' general purpose circuit using its own path selection
  3134. algorithms.
  3135. - Added a BUILDTIMEOUT_SET controller event to describe changes
  3136. to the circuit build timeout.
  3137. - New controller command "getinfo config-text". It returns the
  3138. contents that Tor would write if you send it a SAVECONF command,
  3139. so the controller can write the file to disk itself.
  3140. o Minor features (controller protocol):
  3141. - Add a new ControlSocketsGroupWritable configuration option: when
  3142. it is turned on, ControlSockets are group-writeable by the default
  3143. group of the current user. Patch by Jérémy Bobbio; implements
  3144. ticket 2972.
  3145. - Tor now refuses to create a ControlSocket in a directory that is
  3146. world-readable (or group-readable if ControlSocketsGroupWritable
  3147. is 0). This is necessary because some operating systems do not
  3148. enforce permissions on an AF_UNIX sockets. Permissions on the
  3149. directory holding the socket, however, seems to work everywhere.
  3150. - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
  3151. not. This would lead to a cookie that is still not group readable.
  3152. Closes bug 1843. Suggested by katmagic.
  3153. - Future-proof the controller protocol a bit by ignoring keyword
  3154. arguments we do not recognize.
  3155. o Minor features (more useful logging):
  3156. - Revise most log messages that refer to nodes by nickname to
  3157. instead use the "$key=nickname at address" format. This should be
  3158. more useful, especially since nicknames are less and less likely
  3159. to be unique. Resolves ticket 3045.
  3160. - When an HTTPS proxy reports "403 Forbidden", we now explain
  3161. what it means rather than calling it an unexpected status code.
  3162. Closes bug 2503. Patch from Michael Yakubovich.
  3163. - Rate-limit a warning about failures to download v2 networkstatus
  3164. documents. Resolves part of bug 1352.
  3165. - Rate-limit the "your application is giving Tor only an IP address"
  3166. warning. Addresses bug 2000; bugfix on 0.0.8pre2.
  3167. - Rate-limit "Failed to hand off onionskin" warnings.
  3168. - When logging a rate-limited warning, we now mention how many messages
  3169. got suppressed since the last warning.
  3170. - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
  3171. 2 no signature, 4 required" messages about consensus signatures
  3172. easier to read, and make sure they get logged at the same severity
  3173. as the messages explaining which keys are which. Fixes bug 1290.
  3174. - Don't warn when we have a consensus that we can't verify because
  3175. of missing certificates, unless those certificates are ones
  3176. that we have been trying and failing to download. Fixes bug 1145.
  3177. o Minor features (log domains):
  3178. - Add documentation for configuring logging at different severities in
  3179. different log domains. We've had this feature since 0.2.1.1-alpha,
  3180. but for some reason it never made it into the manpage. Fixes
  3181. bug 2215.
  3182. - Make it simpler to specify "All log domains except for A and B".
  3183. Previously you needed to say "[*,~A,~B]". Now you can just say
  3184. "[~A,~B]".
  3185. - Add a "LogMessageDomains 1" option to include the domains of log
  3186. messages along with the messages. Without this, there's no way
  3187. to use log domains without reading the source or doing a lot
  3188. of guessing.
  3189. - Add a new "Handshake" log domain for activities that happen
  3190. during the TLS handshake.
  3191. o Minor features (build process):
  3192. - Make compilation with clang possible when using
  3193. "--enable-gcc-warnings" by removing two warning options that clang
  3194. hasn't implemented yet and by fixing a few warnings. Resolves
  3195. ticket 2696.
  3196. - Detect platforms that brokenly use a signed size_t, and refuse to
  3197. build there. Found and analyzed by doorss and rransom.
  3198. - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
  3199. Resolves bug 2314.
  3200. - Add support for statically linking zlib by specifying
  3201. "--enable-static-zlib", to go with our support for statically
  3202. linking openssl and libevent. Resolves bug 1358.
  3203. - Instead of adding the svn revision to the Tor version string, report
  3204. the git commit (when we're building from a git checkout).
  3205. - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
  3206. system headers.
  3207. - New --digests command-line switch to output the digests of the
  3208. source files Tor was built with.
  3209. - Generate our manpage and HTML documentation using Asciidoc. This
  3210. change should make it easier to maintain the documentation, and
  3211. produce nicer HTML. The build process fails if asciidoc cannot
  3212. be found and building with asciidoc isn't disabled (via the
  3213. "--disable-asciidoc" argument to ./configure. Skipping the manpage
  3214. speeds up the build considerably.
  3215. o Minor features (options / torrc):
  3216. - Warn when the same option is provided more than once in a torrc
  3217. file, on the command line, or in a single SETCONF statement, and
  3218. the option is one that only accepts a single line. Closes bug 1384.
  3219. - Warn when the user configures two HiddenServiceDir lines that point
  3220. to the same directory. Bugfix on 0.0.6 (the version introducing
  3221. HiddenServiceDir); fixes bug 3289.
  3222. - Add new "perconnbwrate" and "perconnbwburst" consensus params to
  3223. do individual connection-level rate limiting of clients. The torrc
  3224. config options with the same names trump the consensus params, if
  3225. both are present. Replaces the old "bwconnrate" and "bwconnburst"
  3226. consensus params which were broken from 0.2.2.7-alpha through
  3227. 0.2.2.14-alpha. Closes bug 1947.
  3228. - New config option "WarnUnsafeSocks 0" disables the warning that
  3229. occurs whenever Tor receives a socks handshake using a version of
  3230. the socks protocol that can only provide an IP address (rather
  3231. than a hostname). Setups that do DNS locally over Tor are fine,
  3232. and we shouldn't spam the logs in that case.
  3233. - New config option "CircuitStreamTimeout" to override our internal
  3234. timeout schedule for how many seconds until we detach a stream from
  3235. a circuit and try a new circuit. If your network is particularly
  3236. slow, you might want to set this to a number like 60.
  3237. - New options for SafeLogging to allow scrubbing only log messages
  3238. generated while acting as a relay. Specify "SafeLogging relay" if
  3239. you want to ensure that only messages known to originate from
  3240. client use of the Tor process will be logged unsafely.
  3241. - Time and memory units in the configuration file can now be set to
  3242. fractional units. For example, "2.5 GB" is now a valid value for
  3243. AccountingMax.
  3244. - Support line continuations in the torrc config file. If a line
  3245. ends with a single backslash character, the newline is ignored, and
  3246. the configuration value is treated as continuing on the next line.
  3247. Resolves bug 1929.
  3248. o Minor features (unit tests):
  3249. - Revise our unit tests to use the "tinytest" framework, so we
  3250. can run tests in their own processes, have smarter setup/teardown
  3251. code, and so on. The unit test code has moved to its own
  3252. subdirectory, and has been split into multiple modules.
  3253. - Add a unit test for cross-platform directory-listing code.
  3254. - Add some forgotten return value checks during unit tests. Found
  3255. by coverity.
  3256. - Use GetTempDir to find the proper temporary directory location on
  3257. Windows when generating temporary files for the unit tests. Patch
  3258. by Gisle Vanem.
  3259. o Minor features (misc):
  3260. - The "torify" script now uses torsocks where available.
  3261. - Make Libevent log messages get delivered to controllers later,
  3262. and not from inside the Libevent log handler. This prevents unsafe
  3263. reentrant Libevent calls while still letting the log messages
  3264. get through.
  3265. - Certain Tor clients (such as those behind check.torproject.org) may
  3266. want to fetch the consensus in an extra early manner. To enable this
  3267. a user may now set FetchDirInfoExtraEarly to 1. This also depends on
  3268. setting FetchDirInfoEarly to 1. Previous behavior will stay the same
  3269. as only certain clients who must have this information sooner should
  3270. set this option.
  3271. - Expand homedirs passed to tor-checkkey. This should silence a
  3272. coverity complaint about passing a user-supplied string into
  3273. open() without checking it.
  3274. - Make sure to disable DirPort if running as a bridge. DirPorts aren't
  3275. used on bridges, and it makes bridge scanning somewhat easier.
  3276. - Create the /var/run/tor directory on startup on OpenSUSE if it is
  3277. not already created. Patch from Andreas Stieger. Fixes bug 2573.
  3278. o Minor bugfixes (relays):
  3279. - When a relay decides that its DNS is too broken for it to serve
  3280. as an exit server, it advertised itself as a non-exit, but
  3281. continued to act as an exit. This could create accidental
  3282. partitioning opportunities for users. Instead, if a relay is
  3283. going to advertise reject *:* as its exit policy, it should
  3284. really act with exit policy "reject *:*". Fixes bug 2366.
  3285. Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
  3286. - Publish a router descriptor even if generating an extra-info
  3287. descriptor fails. Previously we would not publish a router
  3288. descriptor without an extra-info descriptor; this can cause fast
  3289. exit relays collecting exit-port statistics to drop from the
  3290. consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
  3291. - When we're trying to guess whether we know our IP address as
  3292. a relay, we would log various ways that we failed to guess
  3293. our address, but never log that we ended up guessing it
  3294. successfully. Now add a log line to help confused and anxious
  3295. relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
  3296. - For bandwidth accounting, calculate our expected bandwidth rate
  3297. based on the time during which we were active and not in
  3298. soft-hibernation during the last interval. Previously, we were
  3299. also considering the time spent in soft-hibernation. If this
  3300. was a long time, we would wind up underestimating our bandwidth
  3301. by a lot, and skewing our wakeup time towards the start of the
  3302. accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
  3303. - Demote a confusing TLS warning that relay operators might get when
  3304. someone tries to talk to their ORPort. It is not the operator's
  3305. fault, nor can they do anything about it. Fixes bug 1364; bugfix
  3306. on 0.2.0.14-alpha.
  3307. - Change "Application request when we're believed to be offline."
  3308. notice to "Application request when we haven't used client
  3309. functionality lately.", to clarify that it's not an error. Bugfix
  3310. on 0.0.9.3; fixes bug 1222.
  3311. o Minor bugfixes (bridges):
  3312. - When a client starts or stops using bridges, never use a circuit
  3313. that was built before the configuration change. This behavior could
  3314. put at risk a user who uses bridges to ensure that her traffic
  3315. only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
  3316. bug 3200.
  3317. - Do not reset the bridge descriptor download status every time we
  3318. re-parse our configuration or get a configuration change. Fixes
  3319. bug 3019; bugfix on 0.2.0.3-alpha.
  3320. - Users couldn't configure a regular relay to be their bridge. It
  3321. didn't work because when Tor fetched the bridge descriptor, it found
  3322. that it already had it, and didn't realize that the purpose of the
  3323. descriptor had changed. Now we replace routers with a purpose other
  3324. than bridge with bridge descriptors when fetching them. Bugfix on
  3325. 0.1.1.9-alpha. Fixes bug 1776.
  3326. - In the special case where you configure a public exit relay as your
  3327. bridge, Tor would be willing to use that exit relay as the last
  3328. hop in your circuit as well. Now we fail that circuit instead.
  3329. Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
  3330. o Minor bugfixes (clients):
  3331. - We now ask the other side of a stream (the client or the exit)
  3332. for more data on that stream when the amount of queued data on
  3333. that stream dips low enough. Previously, we wouldn't ask the
  3334. other side for more data until either it sent us more data (which
  3335. it wasn't supposed to do if it had exhausted its window!) or we
  3336. had completely flushed all our queued data. This flow control fix
  3337. should improve throughput. Fixes bug 2756; bugfix on the earliest
  3338. released versions of Tor (svn commit r152).
  3339. - When a client finds that an origin circuit has run out of 16-bit
  3340. stream IDs, we now mark it as unusable for new streams. Previously,
  3341. we would try to close the entire circuit. Bugfix on 0.0.6.
  3342. - Make it explicit that we don't cannibalize one-hop circuits. This
  3343. happens in the wild, but doesn't turn out to be a problem because
  3344. we fortunately don't use those circuits. Many thanks to outofwords
  3345. for the initial analysis and to swissknife who confirmed that
  3346. two-hop circuits are actually created.
  3347. - Resolve an edge case in path weighting that could make us misweight
  3348. our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
  3349. - Make the DNSPort option work with libevent 2.x. Don't alter the
  3350. behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
  3351. o Minor bugfixes (directory authorities):
  3352. - Make directory authorities more accurate at recording when
  3353. relays that have failed several reachability tests became
  3354. unreachable, so we can provide more accuracy at assigning Stable,
  3355. Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
  3356. - Directory authorities are now more robust to hops back in time
  3357. when calculating router stability. Previously, if a run of uptime
  3358. or downtime appeared to be negative, the calculation could give
  3359. incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
  3360. bug 1035.
  3361. - Directory authorities will now attempt to download consensuses
  3362. if their own efforts to make a live consensus have failed. This
  3363. change means authorities that restart will fetch a valid
  3364. consensus, and it means authorities that didn't agree with the
  3365. current consensus will still fetch and serve it if it has enough
  3366. signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
  3367. - Never vote for a server as "Running" if we have a descriptor for
  3368. it claiming to be hibernating, and that descriptor was published
  3369. more recently than our last contact with the server. Bugfix on
  3370. 0.2.0.3-alpha; fixes bug 911.
  3371. - Directory authorities no longer change their opinion of, or vote on,
  3372. whether a router is Running, unless they have themselves been
  3373. online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
  3374. Fixes bug 1023.
  3375. o Minor bugfixes (hidden services):
  3376. - Log malformed requests for rendezvous descriptors as protocol
  3377. warnings, not warnings. Also, use a more informative log message
  3378. in case someone sees it at log level warning without prior
  3379. info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
  3380. - Accept hidden service descriptors if we think we might be a hidden
  3381. service directory, regardless of what our consensus says. This
  3382. helps robustness, since clients and hidden services can sometimes
  3383. have a more up-to-date view of the network consensus than we do,
  3384. and if they think that the directory authorities list us a HSDir,
  3385. we might actually be one. Related to bug 2732; bugfix on
  3386. 0.2.0.10-alpha.
  3387. - Correct the warning displayed when a rendezvous descriptor exceeds
  3388. the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
  3389. John Brooks.
  3390. - Clients and hidden services now use HSDir-flagged relays for hidden
  3391. service descriptor downloads and uploads even if the relays have no
  3392. DirPort set and the client has disabled TunnelDirConns. This will
  3393. eventually allow us to give the HSDir flag to relays with no
  3394. DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
  3395. - Only limit the lengths of single HS descriptors, even when multiple
  3396. HS descriptors are published to an HSDir relay in a single POST
  3397. operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
  3398. o Minor bugfixes (controllers):
  3399. - Allow GETINFO fingerprint to return a fingerprint even when
  3400. we have not yet built a router descriptor. Fixes bug 3577;
  3401. bugfix on 0.2.0.1-alpha.
  3402. - Send a SUCCEEDED stream event to the controller when a reverse
  3403. resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
  3404. discovered by katmagic.
  3405. - Remove a trailing asterisk from "exit-policy/default" in the
  3406. output of the control port command "GETINFO info/names". Bugfix
  3407. on 0.1.2.5-alpha.
  3408. - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
  3409. 2917. Bugfix on 0.1.1.1-alpha.
  3410. - When we restart our relay, we might get a successful connection
  3411. from the outside before we've started our reachability tests,
  3412. triggering a warning: "ORPort found reachable, but I have no
  3413. routerinfo yet. Failing to inform controller of success." This
  3414. bug was harmless unless Tor is running under a controller
  3415. like Vidalia, in which case the controller would never get a
  3416. REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
  3417. fixes bug 1172.
  3418. - When a controller changes TrackHostExits, remove mappings for
  3419. hosts that should no longer have their exits tracked. Bugfix on
  3420. 0.1.0.1-rc.
  3421. - When a controller changes VirtualAddrNetwork, remove any mappings
  3422. for hosts that were automapped to the old network. Bugfix on
  3423. 0.1.1.19-rc.
  3424. - When a controller changes one of the AutomapHosts* options, remove
  3425. any mappings for hosts that should no longer be automapped. Bugfix
  3426. on 0.2.0.1-alpha.
  3427. - Fix an off-by-one error in calculating some controller command
  3428. argument lengths. Fortunately, this mistake is harmless since
  3429. the controller code does redundant NUL termination too. Found by
  3430. boboper. Bugfix on 0.1.1.1-alpha.
  3431. - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
  3432. would return "551 Internal error" rather than "552 Unrecognized key
  3433. ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
  3434. - Don't spam the controller with events when we have no file
  3435. descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
  3436. for log messages was already solved from bug 748.)
  3437. - Emit a GUARD DROPPED controller event for a case we missed.
  3438. - Ensure DNS requests launched by "RESOLVE" commands from the
  3439. controller respect the __LeaveStreamsUnattached setconf options. The
  3440. same goes for requests launched via DNSPort or transparent
  3441. proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
  3442. o Minor bugfixes (config options):
  3443. - Tor used to limit HttpProxyAuthenticator values to 48 characters.
  3444. Change the limit to 512 characters by removing base64 newlines.
  3445. Fixes bug 2752. Fix by Michael Yakubovich.
  3446. - Complain if PublishServerDescriptor is given multiple arguments that
  3447. include 0 or 1. This configuration will be rejected in the future.
  3448. Bugfix on 0.2.0.1-alpha; closes bug 1107.
  3449. - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
  3450. Bugfix on 0.2.0.13-alpha; closes bug 928.
  3451. o Minor bugfixes (log subsystem fixes):
  3452. - When unable to format an address as a string, report its value
  3453. as "???" rather than reusing the last formatted address. Bugfix
  3454. on 0.2.1.5-alpha.
  3455. - Be more consistent in our treatment of file system paths. "~" should
  3456. get expanded to the user's home directory in the Log config option.
  3457. Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
  3458. feature for the -f and --DataDirectory options.
  3459. o Minor bugfixes (memory management):
  3460. - Don't stack-allocate the list of supplementary GIDs when we're
  3461. about to log them. Stack-allocating NGROUPS_MAX gid_t elements
  3462. could take up to 256K, which is way too much stack. Found by
  3463. Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
  3464. - Save a couple bytes in memory allocation every time we escape
  3465. certain characters in a string. Patch from Florian Zumbiehl.
  3466. o Minor bugfixes (protocol correctness):
  3467. - When checking for 1024-bit keys, check for 1024 bits, not 128
  3468. bytes. This allows Tor to correctly discard keys of length 1017
  3469. through 1023. Bugfix on 0.0.9pre5.
  3470. - Require that introduction point keys and onion handshake keys
  3471. have a public exponent of 65537. Starts to fix bug 3207; bugfix
  3472. on 0.2.0.10-alpha.
  3473. - Handle SOCKS messages longer than 128 bytes long correctly, rather
  3474. than waiting forever for them to finish. Fixes bug 2330; bugfix
  3475. on 0.2.0.16-alpha. Found by doorss.
  3476. - Never relay a cell for a circuit we have already destroyed.
  3477. Between marking a circuit as closeable and finally closing it,
  3478. it may have been possible for a few queued cells to get relayed,
  3479. even though they would have been immediately dropped by the next
  3480. OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
  3481. - Never queue a cell for a circuit that's already been marked
  3482. for close.
  3483. - Fix a spec conformance issue: the network-status-version token
  3484. must be the first token in a v3 consensus or vote. Discovered by
  3485. "parakeep". Bugfix on 0.2.0.3-alpha.
  3486. - A networkstatus vote must contain exactly one signature. Spec
  3487. conformance issue. Bugfix on 0.2.0.3-alpha.
  3488. - When asked about a DNS record type we don't support via a
  3489. client DNSPort, reply with NOTIMPL rather than an empty
  3490. reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
  3491. - Make more fields in the controller protocol case-insensitive, since
  3492. control-spec.txt said they were.
  3493. o Minor bugfixes (log messages):
  3494. - Fix a log message that said "bits" while displaying a value in
  3495. bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
  3496. 0.2.0.1-alpha.
  3497. - Downgrade "no current certificates known for authority" message from
  3498. Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
  3499. - Correctly describe errors that occur when generating a TLS object.
  3500. Previously we would attribute them to a failure while generating a
  3501. TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
  3502. bug 1994.
  3503. - Fix an instance where a Tor directory mirror might accidentally
  3504. log the IP address of a misbehaving Tor client. Bugfix on
  3505. 0.1.0.1-rc.
  3506. - Stop logging at severity 'warn' when some other Tor client tries
  3507. to establish a circuit with us using weak DH keys. It's a protocol
  3508. violation, but that doesn't mean ordinary users need to hear about
  3509. it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
  3510. - If your relay can't keep up with the number of incoming create
  3511. cells, it would log one warning per failure into your logs. Limit
  3512. warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
  3513. o Minor bugfixes (build fixes):
  3514. - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
  3515. - When warning about missing zlib development packages during compile,
  3516. give the correct package names. Bugfix on 0.2.0.1-alpha.
  3517. - Fix warnings that newer versions of autoconf produce during
  3518. ./autogen.sh. These warnings appear to be harmless in our case,
  3519. but they were extremely verbose. Fixes bug 2020.
  3520. - Squash a compile warning on OpenBSD. Reported by Tas; fixes
  3521. bug 1848.
  3522. o Minor bugfixes (portability):
  3523. - Write several files in text mode, on OSes that distinguish text
  3524. mode from binary mode (namely, Windows). These files are:
  3525. 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
  3526. that collect those statistics; 'client_keys' and 'hostname' for
  3527. hidden services that use authentication; and (in the tor-gencert
  3528. utility) newly generated identity and signing keys. Previously,
  3529. we wouldn't specify text mode or binary mode, leading to an
  3530. assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
  3531. the DirRecordUsageByCountry option which would have triggered
  3532. the assertion failure was added), although this assertion failure
  3533. would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
  3534. - Selectively disable deprecation warnings on OS X because Lion
  3535. started deprecating the shipped copy of openssl. Fixes bug 3643.
  3536. - Use a wide type to hold sockets when built for 64-bit Windows.
  3537. Fixes bug 3270.
  3538. - Fix an issue that prevented static linking of libevent on
  3539. some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
  3540. where we introduced the "--with-static-libevent" configure option.
  3541. - Fix a bug with our locking implementation on Windows that couldn't
  3542. correctly detect when a file was already locked. Fixes bug 2504,
  3543. bugfix on 0.2.1.6-alpha.
  3544. - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
  3545. enabled.
  3546. - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
  3547. Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
  3548. "piebeer".
  3549. o Minor bugfixes (code correctness):
  3550. - Always NUL-terminate the sun_path field of a sockaddr_un before
  3551. passing it to the kernel. (Not a security issue: kernels are
  3552. smart enough to reject bad sockaddr_uns.) Found by Coverity;
  3553. CID #428. Bugfix on Tor 0.2.0.3-alpha.
  3554. - Make connection_printf_to_buf()'s behaviour sane. Its callers
  3555. expect it to emit a CRLF iff the format string ends with CRLF;
  3556. it actually emitted a CRLF iff (a) the format string ended with
  3557. CRLF or (b) the resulting string was over 1023 characters long or
  3558. (c) the format string did not end with CRLF *and* the resulting
  3559. string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
  3560. fixes part of bug 3407.
  3561. - Make send_control_event_impl()'s behaviour sane. Its callers
  3562. expect it to always emit a CRLF at the end of the string; it
  3563. might have emitted extra control characters as well. Bugfix on
  3564. 0.1.1.9-alpha; fixes another part of bug 3407.
  3565. - Make crypto_rand_int() check the value of its input correctly.
  3566. Previously, it accepted values up to UINT_MAX, but could return a
  3567. negative number if given a value above INT_MAX+1. Found by George
  3568. Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
  3569. - Fix a potential null-pointer dereference while computing a
  3570. consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
  3571. clang's analyzer.
  3572. - If we fail to compute the identity digest of a v3 legacy keypair,
  3573. warn, and don't use a buffer-full of junk instead. Bugfix on
  3574. 0.2.1.1-alpha; fixes bug 3106.
  3575. - Resolve an untriggerable issue in smartlist_string_num_isin(),
  3576. where if the function had ever in the future been used to check
  3577. for the presence of a too-large number, it would have given an
  3578. incorrect result. (Fortunately, we only used it for 16-bit
  3579. values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
  3580. - Be more careful about reporting the correct error from a failed
  3581. connect() system call. Under some circumstances, it was possible to
  3582. look at an incorrect value for errno when sending the end reason.
  3583. Bugfix on 0.1.0.1-rc.
  3584. - Correctly handle an "impossible" overflow cases in connection byte
  3585. counting, where we write or read more than 4GB on an edge connection
  3586. in a single second. Bugfix on 0.1.2.8-beta.
  3587. - Avoid a double mark-for-free warning when failing to attach a
  3588. transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
  3589. bug 2279.
  3590. - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
  3591. found by "cypherpunks". This bug was introduced before the first
  3592. Tor release, in svn commit r110.
  3593. - Fix a bug in bandwidth history state parsing that could have been
  3594. triggered if a future version of Tor ever changed the timing
  3595. granularity at which bandwidth history is measured. Bugfix on
  3596. Tor 0.1.1.11-alpha.
  3597. - Add assertions to check for overflow in arguments to
  3598. base32_encode() and base32_decode(); fix a signed-unsigned
  3599. comparison there too. These bugs are not actually reachable in Tor,
  3600. but it's good to prevent future errors too. Found by doorss.
  3601. - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
  3602. "memcpyfail".
  3603. - Set target port in get_interface_address6() correctly. Bugfix
  3604. on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
  3605. - Fix an impossible-to-actually-trigger buffer overflow in relay
  3606. descriptor generation. Bugfix on 0.1.0.15.
  3607. - Fix numerous small code-flaws found by Coverity Scan Rung 3.
  3608. o Minor bugfixes (code improvements):
  3609. - After we free an internal connection structure, overwrite it
  3610. with a different memory value than we use for overwriting a freed
  3611. internal circuit structure. Should help with debugging. Suggested
  3612. by bug 1055.
  3613. - If OpenSSL fails to make a duplicate of a private or public key, log
  3614. an error message and try to exit cleanly. May help with debugging
  3615. if bug 1209 ever remanifests.
  3616. - Some options used different conventions for uppercasing of acronyms
  3617. when comparing manpage and source. Fix those in favor of the
  3618. manpage, as it makes sense to capitalize acronyms.
  3619. - Take a first step towards making or.h smaller by splitting out
  3620. function definitions for all source files in src/or/. Leave
  3621. structures and defines in or.h for now.
  3622. - Remove a few dead assignments during router parsing. Found by
  3623. coverity.
  3624. - Don't use 1-bit wide signed bit fields. Found by coverity.
  3625. - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
  3626. None of the cases where we did this before were wrong, but by making
  3627. this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
  3628. - The memarea code now uses a sentinel value at the end of each area
  3629. to make sure nothing writes beyond the end of an area. This might
  3630. help debug some conceivable causes of bug 930.
  3631. - Always treat failure to allocate an RSA key as an unrecoverable
  3632. allocation error.
  3633. - Add some more defensive programming for architectures that can't
  3634. handle unaligned integer accesses. We don't know of any actual bugs
  3635. right now, but that's the best time to fix them. Fixes bug 1943.
  3636. o Minor bugfixes (misc):
  3637. - Fix a rare bug in rend_fn unit tests: we would fail a test when
  3638. a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
  3639. on 0.2.0.10-alpha; fixes bug 1808.
  3640. - Where available, use Libevent 2.0's periodic timers so that our
  3641. once-per-second cleanup code gets called even more closely to
  3642. once per second than it would otherwise. Fixes bug 943.
  3643. - Ignore OutboundBindAddress when connecting to localhost.
  3644. Connections to localhost need to come _from_ localhost, or else
  3645. local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
  3646. refuse to listen.
  3647. - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
  3648. too.
  3649. - If any of the v3 certs we download are unparseable, we should
  3650. actually notice the failure so we don't retry indefinitely. Bugfix
  3651. on 0.2.0.x; reported by "rotator".
  3652. - When Tor fails to parse a descriptor of any kind, dump it to disk.
  3653. Might help diagnosing bug 1051.
  3654. - Make our 'torify' script more portable; if we have only one of
  3655. 'torsocks' or 'tsocks' installed, don't complain to the user;
  3656. and explain our warning about tsocks better.
  3657. - Fix some urls in the exit notice file and make it XHTML1.1 strict
  3658. compliant. Based on a patch from Christian Kujau.
  3659. o Documentation changes:
  3660. - Modernize the doxygen configuration file slightly. Fixes bug 2707.
  3661. - Resolve all doxygen warnings except those for missing documentation.
  3662. Fixes bug 2705.
  3663. - Add doxygen documentation for more functions, fields, and types.
  3664. - Convert the HACKING file to asciidoc, and add a few new sections
  3665. to it, explaining how we use Git, how we make changelogs, and
  3666. what should go in a patch.
  3667. - Document the default socks host and port (127.0.0.1:9050) for
  3668. tor-resolve.
  3669. - Removed some unnecessary files from the source distribution. The
  3670. AUTHORS file has now been merged into the people page on the
  3671. website. The roadmaps and design doc can now be found in the
  3672. projects directory in svn.
  3673. o Deprecated and removed features (config):
  3674. - Remove the torrc.complete file. It hasn't been kept up to date
  3675. and users will have better luck checking out the manpage.
  3676. - Remove the HSAuthorityRecordStats option that version 0 hidden
  3677. service authorities could use to track statistics of overall v0
  3678. hidden service usage.
  3679. - Remove the obsolete "NoPublish" option; it has been flagged
  3680. as obsolete and has produced a warning since 0.1.1.18-rc.
  3681. - Caches no longer download and serve v2 networkstatus documents
  3682. unless FetchV2Networkstatus flag is set: these documents haven't
  3683. haven't been used by clients or relays since 0.2.0.x. Resolves
  3684. bug 3022.
  3685. o Deprecated and removed features (controller):
  3686. - The controller no longer accepts the old obsolete "addr-mappings/"
  3687. or "unregistered-servers-" GETINFO values.
  3688. - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
  3689. always on; using them is necessary for correct forward-compatible
  3690. controllers.
  3691. o Deprecated and removed features (misc):
  3692. - Hidden services no longer publish version 0 descriptors, and clients
  3693. do not request or use version 0 descriptors. However, the old hidden
  3694. service authorities still accept and serve version 0 descriptors
  3695. when contacted by older hidden services/clients.
  3696. - Remove undocumented option "-F" from tor-resolve: it hasn't done
  3697. anything since 0.2.1.16-rc.
  3698. - Remove everything related to building the expert bundle for OS X.
  3699. It has confused many users, doesn't work right on OS X 10.6,
  3700. and is hard to get rid of once installed. Resolves bug 1274.
  3701. - Remove support for .noconnect style addresses. Nobody was using
  3702. them, and they provided another avenue for detecting Tor users
  3703. via application-level web tricks.
  3704. - When we fixed bug 1038 we had to put in a restriction not to send
  3705. RELAY_EARLY cells on rend circuits. This was necessary as long
  3706. as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
  3707. active. Now remove this obsolete check. Resolves bug 2081.
  3708. - Remove workaround code to handle directory responses from servers
  3709. that had bug 539 (they would send HTTP status 503 responses _and_
  3710. send a body too). Since only server versions before
  3711. 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
  3712. keep the workaround in place.
  3713. - Remove the old 'fuzzy time' logic. It was supposed to be used for
  3714. handling calculations where we have a known amount of clock skew and
  3715. an allowed amount of unknown skew. But we only used it in three
  3716. places, and we never adjusted the known/unknown skew values. This is
  3717. still something we might want to do someday, but if we do, we'll
  3718. want to do it differently.
  3719. - Remove the "--enable-iphone" option to ./configure. According to
  3720. reports from Marco Bonetti, Tor builds fine without any special
  3721. tweaking on recent iPhone SDK versions.
  3722. Changes in version 0.2.1.30 - 2011-02-23
  3723. Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
  3724. change is a slight tweak to Tor's TLS handshake that makes relays
  3725. and bridges that run this new version reachable from Iran again.
  3726. We don't expect this tweak will win the arms race long-term, but it
  3727. buys us time until we roll out a better solution.
  3728. o Major bugfixes:
  3729. - Stop sending a CLOCK_SKEW controller status event whenever
  3730. we fetch directory information from a relay that has a wrong clock.
  3731. Instead, only inform the controller when it's a trusted authority
  3732. that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
  3733. the rest of bug 1074.
  3734. - Fix a bounds-checking error that could allow an attacker to
  3735. remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
  3736. Found by "piebeer".
  3737. - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
  3738. Tor would ignore their RelayBandwidthBurst setting,
  3739. potentially using more bandwidth than expected. Bugfix on
  3740. 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
  3741. - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
  3742. hidserv" in her torrc. The 'hidserv' argument never controlled
  3743. publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
  3744. o Minor features:
  3745. - Adjust our TLS Diffie-Hellman parameters to match those used by
  3746. Apache's mod_ssl.
  3747. - Update to the February 1 2011 Maxmind GeoLite Country database.
  3748. o Minor bugfixes:
  3749. - Check for and reject overly long directory certificates and
  3750. directory tokens before they have a chance to hit any assertions.
  3751. Bugfix on 0.2.1.28. Found by "doorss".
  3752. - Bring the logic that gathers routerinfos and assesses the
  3753. acceptability of circuits into line. This prevents a Tor OP from
  3754. getting locked in a cycle of choosing its local OR as an exit for a
  3755. path (due to a .exit request) and then rejecting the circuit because
  3756. its OR is not listed yet. It also prevents Tor clients from using an
  3757. OR running in the same instance as an exit (due to a .exit request)
  3758. if the OR does not meet the same requirements expected of an OR
  3759. running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
  3760. o Packaging changes:
  3761. - Stop shipping the Tor specs files and development proposal documents
  3762. in the tarball. They are now in a separate git repository at
  3763. git://git.torproject.org/torspec.git
  3764. - Do not include Git version tags as though they are SVN tags when
  3765. generating a tarball from inside a repository that has switched
  3766. between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
  3767. Changes in version 0.2.1.29 - 2011-01-15
  3768. Tor 0.2.1.29 continues our recent code security audit work. The main
  3769. fix resolves a remote heap overflow vulnerability that can allow remote
  3770. code execution. Other fixes address a variety of assert and crash bugs,
  3771. most of which we think are hard to exploit remotely.
  3772. o Major bugfixes (security):
  3773. - Fix a heap overflow bug where an adversary could cause heap
  3774. corruption. This bug probably allows remote code execution
  3775. attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
  3776. 0.1.2.10-rc.
  3777. - Prevent a denial-of-service attack by disallowing any
  3778. zlib-compressed data whose compression factor is implausibly
  3779. high. Fixes part of bug 2324; reported by "doorss".
  3780. - Zero out a few more keys in memory before freeing them. Fixes
  3781. bug 2384 and part of bug 2385. These key instances found by
  3782. "cypherpunks", based on Andrew Case's report about being able
  3783. to find sensitive data in Tor's memory space if you have enough
  3784. permissions. Bugfix on 0.0.2pre9.
  3785. o Major bugfixes (crashes):
  3786. - Prevent calls to Libevent from inside Libevent log handlers.
  3787. This had potential to cause a nasty set of crashes, especially
  3788. if running Libevent with debug logging enabled, and running
  3789. Tor with a controller watching for low-severity log messages.
  3790. Bugfix on 0.1.0.2-rc. Fixes bug 2190.
  3791. - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
  3792. underflow errors there too. Fixes the other part of bug 2324.
  3793. - Fix a bug where we would assert if we ever had a
  3794. cached-descriptors.new file (or another file read directly into
  3795. memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
  3796. on 0.2.1.25. Found by doorss.
  3797. - Fix some potential asserts and parsing issues with grossly
  3798. malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
  3799. Found by doorss.
  3800. o Minor bugfixes (other):
  3801. - Fix a bug with handling misformed replies to reverse DNS lookup
  3802. requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
  3803. bug reported by doorss.
  3804. - Fix compilation on mingw when a pthreads compatibility library
  3805. has been installed. (We don't want to use it, so we shouldn't
  3806. be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
  3807. - Fix a bug where we would declare that we had run out of virtual
  3808. addresses when the address space was only half-exhausted. Bugfix
  3809. on 0.1.2.1-alpha.
  3810. - Correctly handle the case where AutomapHostsOnResolve is set but
  3811. no virtual addresses are available. Fixes bug 2328; bugfix on
  3812. 0.1.2.1-alpha. Bug found by doorss.
  3813. - Correctly handle wrapping around when we run out of virtual
  3814. address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
  3815. o Minor features:
  3816. - Update to the January 1 2011 Maxmind GeoLite Country database.
  3817. - Introduce output size checks on all of our decryption functions.
  3818. o Build changes:
  3819. - Tor does not build packages correctly with Automake 1.6 and earlier;
  3820. added a check to Makefile.am to make sure that we're building with
  3821. Automake 1.7 or later.
  3822. - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
  3823. because we built it with a too-old version of automake. Thus that
  3824. release broke ./configure --enable-openbsd-malloc, which is popular
  3825. among really fast exit relays on Linux.
  3826. Changes in version 0.2.1.28 - 2010-12-17
  3827. Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
  3828. exploitable bugs. We also took this opportunity to change the IP address
  3829. for one of our directory authorities, and to update the geoip database
  3830. we ship.
  3831. o Major bugfixes:
  3832. - Fix a remotely exploitable bug that could be used to crash instances
  3833. of Tor remotely by overflowing on the heap. Remote-code execution
  3834. hasn't been confirmed, but can't be ruled out. Everyone should
  3835. upgrade. Bugfix on the 0.1.1 series and later.
  3836. o Directory authority changes:
  3837. - Change IP address and ports for gabelmoo (v3 directory authority).
  3838. o Minor features:
  3839. - Update to the December 1 2010 Maxmind GeoLite Country database.
  3840. Changes in version 0.2.1.27 - 2010-11-23
  3841. Yet another OpenSSL security patch broke its compatibility with Tor:
  3842. Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
  3843. also took this opportunity to fix several crash bugs, integrate a new
  3844. directory authority, and update the bundled GeoIP database.
  3845. o Major bugfixes:
  3846. - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
  3847. No longer set the tlsext_host_name extension on server SSL objects;
  3848. but continue to set it on client SSL objects. Our goal in setting
  3849. it was to imitate a browser, not a vhosting server. Fixes bug 2204;
  3850. bugfix on 0.2.1.1-alpha.
  3851. - Do not log messages to the controller while shrinking buffer
  3852. freelists. Doing so would sometimes make the controller connection
  3853. try to allocate a buffer chunk, which would mess up the internals
  3854. of the freelist and cause an assertion failure. Fixes bug 1125;
  3855. fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
  3856. - Learn our external IP address when we're a relay or bridge, even if
  3857. we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
  3858. where we introduced bridge relays that don't need to publish to
  3859. be useful. Fixes bug 2050.
  3860. - Do even more to reject (and not just ignore) annotations on
  3861. router descriptors received anywhere but from the cache. Previously
  3862. we would ignore such annotations at first, but cache them to disk
  3863. anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
  3864. - When you're using bridges and your network goes away and your
  3865. bridges get marked as down, recover when you attempt a new socks
  3866. connection (if the network is back), rather than waiting up to an
  3867. hour to try fetching new descriptors for your bridges. Bugfix on
  3868. 0.2.0.3-alpha; fixes bug 1981.
  3869. o Major features:
  3870. - Move to the November 2010 Maxmind GeoLite country db (rather
  3871. than the June 2009 ip-to-country GeoIP db) for our statistics that
  3872. count how many users relays are seeing from each country. Now we'll
  3873. have more accurate data, especially for many African countries.
  3874. o New directory authorities:
  3875. - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
  3876. authority.
  3877. o Minor bugfixes:
  3878. - Fix an assertion failure that could occur in directory caches or
  3879. bridge users when using a very short voting interval on a testing
  3880. network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
  3881. 0.2.0.8-alpha.
  3882. - Enforce multiplicity rules when parsing annotations. Bugfix on
  3883. 0.2.0.8-alpha. Found by piebeer.
  3884. - Allow handshaking OR connections to take a full KeepalivePeriod
  3885. seconds to handshake. Previously, we would close them after
  3886. IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
  3887. were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
  3888. for analysis help.
  3889. - When building with --enable-gcc-warnings on OpenBSD, disable
  3890. warnings in system headers. This makes --enable-gcc-warnings
  3891. pass on OpenBSD 4.8.
  3892. o Minor features:
  3893. - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
  3894. and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
  3895. stream ending reason for this case: END_STREAM_REASON_NOROUTE.
  3896. Servers can start sending this code when enough clients recognize
  3897. it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
  3898. - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
  3899. Patch from mingw-san.
  3900. o Removed files:
  3901. - Remove the old debian/ directory from the main Tor distribution.
  3902. The official Tor-for-debian git repository lives at the URL
  3903. https://git.torproject.org/debian/tor.git
  3904. - Stop shipping the old doc/website/ directory in the tarball. We
  3905. changed the website format in late 2010, and what we shipped in
  3906. 0.2.1.26 really wasn't that useful anyway.
  3907. Changes in version 0.2.1.26 - 2010-05-02
  3908. Tor 0.2.1.26 addresses the recent connection and memory overload
  3909. problems we've been seeing on relays, especially relays with their
  3910. DirPort open. If your relay has been crashing, or you turned it off
  3911. because it used too many resources, give this release a try.
  3912. This release also fixes yet another instance of broken OpenSSL libraries
  3913. that was causing some relays to drop out of the consensus.
  3914. o Major bugfixes:
  3915. - Teach relays to defend themselves from connection overload. Relays
  3916. now close idle circuits early if it looks like they were intended
  3917. for directory fetches. Relays are also more aggressive about closing
  3918. TLS connections that have no circuits on them. Such circuits are
  3919. unlikely to be re-used, and tens of thousands of them were piling
  3920. up at the fast relays, causing the relays to run out of sockets
  3921. and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
  3922. their directory fetches over TLS).
  3923. - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
  3924. that claim to be earlier than 0.9.8m, but which have in reality
  3925. backported huge swaths of 0.9.8m or 0.9.8n renegotiation
  3926. behavior. Possible fix for some cases of bug 1346.
  3927. - Directory mirrors were fetching relay descriptors only from v2
  3928. directory authorities, rather than v3 authorities like they should.
  3929. Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
  3930. to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
  3931. o Minor bugfixes:
  3932. - Finally get rid of the deprecated and now harmful notion of "clique
  3933. mode", where directory authorities maintain TLS connections to
  3934. every other relay.
  3935. o Testsuite fixes:
  3936. - In the util/threads test, no longer free the test_mutex before all
  3937. worker threads have finished. Bugfix on 0.2.1.6-alpha.
  3938. - The master thread could starve the worker threads quite badly on
  3939. certain systems, causing them to run only partially in the allowed
  3940. window. This resulted in test failures. Now the master thread sleeps
  3941. occasionally for a few microseconds while the two worker-threads
  3942. compete for the mutex. Bugfix on 0.2.0.1-alpha.
  3943. Changes in version 0.2.1.25 - 2010-03-16
  3944. Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
  3945. prevent relays from guessing their IP address correctly. It also fixes
  3946. several minor potential security bugs.
  3947. o Major bugfixes:
  3948. - Fix a regression from our patch for bug 1244 that caused relays
  3949. to guess their IP address incorrectly if they didn't set Address
  3950. in their torrc and/or their address fails to resolve. Bugfix on
  3951. 0.2.1.23; fixes bug 1269.
  3952. - When freeing a session key, zero it out completely. We only zeroed
  3953. the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
  3954. patched by ekir. Fixes bug 1254.
  3955. o Minor bugfixes:
  3956. - Fix a dereference-then-NULL-check sequence when publishing
  3957. descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
  3958. bug 1255.
  3959. - Fix another dereference-then-NULL-check sequence. Bugfix on
  3960. 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
  3961. - Make sure we treat potentially not NUL-terminated strings correctly.
  3962. Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
  3963. Changes in version 0.2.1.24 - 2010-02-21
  3964. Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
  3965. for sure!
  3966. o Minor bugfixes:
  3967. - Work correctly out-of-the-box with even more vendor-patched versions
  3968. of OpenSSL. In particular, make it so Debian and OS X don't need
  3969. customized patches to run/build.
  3970. Changes in version 0.2.1.23 - 2010-02-13
  3971. Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
  3972. again on the latest OS X, and updates the location of a directory
  3973. authority.
  3974. o Major bugfixes (performance):
  3975. - We were selecting our guards uniformly at random, and then weighting
  3976. which of our guards we'd use uniformly at random. This imbalance
  3977. meant that Tor clients were severely limited on throughput (and
  3978. probably latency too) by the first hop in their circuit. Now we
  3979. select guards weighted by currently advertised bandwidth. We also
  3980. automatically discard guards picked using the old algorithm. Fixes
  3981. bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
  3982. o Major bugfixes:
  3983. - Make Tor work again on the latest OS X: when deciding whether to
  3984. use strange flags to turn TLS renegotiation on, detect the OpenSSL
  3985. version at run-time, not compile time. We need to do this because
  3986. Apple doesn't update its dev-tools headers when it updates its
  3987. libraries in a security patch.
  3988. - Fix a potential buffer overflow in lookup_last_hid_serv_request()
  3989. that could happen on 32-bit platforms with 64-bit time_t. Also fix
  3990. a memory leak when requesting a hidden service descriptor we've
  3991. requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
  3992. by aakova.
  3993. o Minor bugfixes:
  3994. - Refactor resolve_my_address() to not use gethostbyname() anymore.
  3995. Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
  3996. o Minor features:
  3997. - Avoid a mad rush at the beginning of each month when each client
  3998. rotates half of its guards. Instead we spread the rotation out
  3999. throughout the month, but we still avoid leaving a precise timestamp
  4000. in the state file about when we first picked the guard. Improves
  4001. over the behavior introduced in 0.1.2.17.
  4002. Changes in version 0.2.1.22 - 2010-01-19
  4003. Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
  4004. authorities -- it would tell you its whole history of bridge descriptors
  4005. if you make the right directory request. This stable update also
  4006. rotates two of the seven v3 directory authority keys and locations.
  4007. o Directory authority changes:
  4008. - Rotate keys (both v3 identity and relay identity) for moria1
  4009. and gabelmoo.
  4010. o Major bugfixes:
  4011. - Stop bridge directory authorities from answering dbg-stability.txt
  4012. directory queries, which would let people fetch a list of all
  4013. bridge identities they track. Bugfix on 0.2.1.6-alpha.
  4014. Changes in version 0.2.1.21 - 2009-12-21
  4015. Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
  4016. library. If you use Tor on Linux / Unix and you're getting SSL
  4017. renegotiation errors, upgrading should help. We also recommend an
  4018. upgrade if you're an exit relay.
  4019. o Major bugfixes:
  4020. - Work around a security feature in OpenSSL 0.9.8l that prevents our
  4021. handshake from working unless we explicitly tell OpenSSL that we
  4022. are using SSL renegotiation safely. We are, of course, but OpenSSL
  4023. 0.9.8l won't work unless we say we are.
  4024. - Avoid crashing if the client is trying to upload many bytes and the
  4025. circuit gets torn down at the same time, or if the flip side
  4026. happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
  4027. o Minor bugfixes:
  4028. - Do not refuse to learn about authority certs and v2 networkstatus
  4029. documents that are older than the latest consensus. This bug might
  4030. have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
  4031. Spotted and fixed by xmux.
  4032. - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
  4033. trigger platform-specific option misparsing case found by Coverity
  4034. Scan.
  4035. - Fix a compilation warning on Fedora 12 by removing an impossible-to-
  4036. trigger assert. Fixes bug 1173.
  4037. Changes in version 0.2.1.20 - 2009-10-15
  4038. Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
  4039. services at once, prepares for more performance improvements, and
  4040. fixes a bunch of smaller bugs.
  4041. The Windows and OS X bundles also include a more recent Vidalia,
  4042. and switch from Privoxy to Polipo.
  4043. The OS X installers are now drag and drop. It's best to un-install
  4044. Tor/Vidalia and then install this new bundle, rather than upgrade. If
  4045. you want to upgrade, you'll need to update the paths for Tor and Polipo
  4046. in the Vidalia Settings window.
  4047. o Major bugfixes:
  4048. - Send circuit or stream sendme cells when our window has decreased
  4049. by 100 cells, not when it has decreased by 101 cells. Bug uncovered
  4050. by Karsten when testing the "reduce circuit window" performance
  4051. patch. Bugfix on the 54th commit on Tor -- from July 2002,
  4052. before the release of Tor 0.0.0. This is the new winner of the
  4053. oldest-bug prize.
  4054. - Fix a remotely triggerable memory leak when a consensus document
  4055. contains more than one signature from the same voter. Bugfix on
  4056. 0.2.0.3-alpha.
  4057. - Avoid segfault in rare cases when finishing an introduction circuit
  4058. as a client and finding out that we don't have an introduction key
  4059. for it. Fixes bug 1073. Reported by Aaron Swartz.
  4060. o Major features:
  4061. - Tor now reads the "circwindow" parameter out of the consensus,
  4062. and uses that value for its circuit package window rather than the
  4063. default of 1000 cells. Begins the implementation of proposal 168.
  4064. o New directory authorities:
  4065. - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
  4066. authority.
  4067. - Move moria1 and tonga to alternate IP addresses.
  4068. o Minor bugfixes:
  4069. - Fix a signed/unsigned compile warning in 0.2.1.19.
  4070. - Fix possible segmentation fault on directory authorities. Bugfix on
  4071. 0.2.1.14-rc.
  4072. - Fix an extremely rare infinite recursion bug that could occur if
  4073. we tried to log a message after shutting down the log subsystem.
  4074. Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
  4075. - Fix an obscure bug where hidden services on 64-bit big-endian
  4076. systems might mis-read the timestamp in v3 introduce cells, and
  4077. refuse to connect back to the client. Discovered by "rotor".
  4078. Bugfix on 0.2.1.6-alpha.
  4079. - We were triggering a CLOCK_SKEW controller status event whenever
  4080. we connect via the v2 connection protocol to any relay that has
  4081. a wrong clock. Instead, we should only inform the controller when
  4082. it's a trusted authority that claims our clock is wrong. Bugfix
  4083. on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
  4084. - We were telling the controller about CHECKING_REACHABILITY and
  4085. REACHABILITY_FAILED status events whenever we launch a testing
  4086. circuit or notice that one has failed. Instead, only tell the
  4087. controller when we want to inform the user of overall success or
  4088. overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
  4089. by SwissTorExit.
  4090. - Don't warn when we're using a circuit that ends with a node
  4091. excluded in ExcludeExitNodes, but the circuit is not used to access
  4092. the outside world. This should help fix bug 1090. Bugfix on
  4093. 0.2.1.6-alpha.
  4094. - Work around a small memory leak in some versions of OpenSSL that
  4095. stopped the memory used by the hostname TLS extension from being
  4096. freed.
  4097. o Minor features:
  4098. - Add a "getinfo status/accepted-server-descriptor" controller
  4099. command, which is the recommended way for controllers to learn
  4100. whether our server descriptor has been successfully received by at
  4101. least on directory authority. Un-recommend good-server-descriptor
  4102. getinfo and status events until we have a better design for them.
  4103. Changes in version 0.2.1.19 - 2009-07-28
  4104. Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
  4105. services.
  4106. o Major bugfixes:
  4107. - Make accessing hidden services on 0.2.1.x work right again.
  4108. Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
  4109. part of patch provided by "optimist".
  4110. o Minor features:
  4111. - When a relay/bridge is writing out its identity key fingerprint to
  4112. the "fingerprint" file and to its logs, write it without spaces. Now
  4113. it will look like the fingerprints in our bridges documentation,
  4114. and confuse fewer users.
  4115. o Minor bugfixes:
  4116. - Relays no longer publish a new server descriptor if they change
  4117. their MaxAdvertisedBandwidth config option but it doesn't end up
  4118. changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
  4119. fixes bug 1026. Patch from Sebastian.
  4120. - Avoid leaking memory every time we get a create cell but we have
  4121. so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
  4122. fixes bug 1034. Reported by BarkerJr.
  4123. Changes in version 0.2.1.18 - 2009-07-24
  4124. Tor 0.2.1.18 lays the foundations for performance improvements,
  4125. adds status events to help users diagnose bootstrap problems, adds
  4126. optional authentication/authorization for hidden services, fixes a
  4127. variety of potential anonymity problems, and includes a huge pile of
  4128. other features and bug fixes.
  4129. o Major features (clients):
  4130. - Start sending "bootstrap phase" status events to the controller,
  4131. so it can keep the user informed of progress fetching directory
  4132. information and establishing circuits. Also inform the controller
  4133. if we think we're stuck at a particular bootstrap phase. Implements
  4134. proposal 137.
  4135. - Clients replace entry guards that were chosen more than a few months
  4136. ago. This change should significantly improve client performance,
  4137. especially once more people upgrade, since relays that have been
  4138. a guard for a long time are currently overloaded.
  4139. - Network status consensus documents and votes now contain bandwidth
  4140. information for each relay. Clients use the bandwidth values
  4141. in the consensus, rather than the bandwidth values in each
  4142. relay descriptor. This approach opens the door to more accurate
  4143. bandwidth estimates once the directory authorities start doing
  4144. active measurements. Implements part of proposal 141.
  4145. o Major features (relays):
  4146. - Disable and refactor some debugging checks that forced a linear scan
  4147. over the whole server-side DNS cache. These accounted for over 50%
  4148. of CPU time on a relatively busy exit node's gprof profile. Also,
  4149. disable some debugging checks that appeared in exit node profile
  4150. data. Found by Jacob.
  4151. - New DirPortFrontPage option that takes an html file and publishes
  4152. it as "/" on the DirPort. Now relay operators can provide a
  4153. disclaimer without needing to set up a separate webserver. There's
  4154. a sample disclaimer in contrib/tor-exit-notice.html.
  4155. o Major features (hidden services):
  4156. - Make it possible to build hidden services that only certain clients
  4157. are allowed to connect to. This is enforced at several points,
  4158. so that unauthorized clients are unable to send INTRODUCE cells
  4159. to the service, or even (depending on the type of authentication)
  4160. to learn introduction points. This feature raises the bar for
  4161. certain kinds of active attacks against hidden services. Design
  4162. and code by Karsten Loesing. Implements proposal 121.
  4163. - Relays now store and serve v2 hidden service descriptors by default,
  4164. i.e., the new default value for HidServDirectoryV2 is 1. This is
  4165. the last step in proposal 114, which aims to make hidden service
  4166. lookups more reliable.
  4167. o Major features (path selection):
  4168. - ExitNodes and Exclude*Nodes config options now allow you to restrict
  4169. by country code ("{US}") or IP address or address pattern
  4170. ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
  4171. refinement to decide what config options should take priority if
  4172. you ask to both use a particular node and exclude it.
  4173. o Major features (misc):
  4174. - When building a consensus, do not include routers that are down.
  4175. This cuts down 30% to 40% on consensus size. Implements proposal
  4176. 138.
  4177. - New TestingTorNetwork config option to allow adjustment of
  4178. previously constant values that could slow bootstrapping. Implements
  4179. proposal 135. Patch from Karsten.
  4180. - Convert many internal address representations to optionally hold
  4181. IPv6 addresses. Generate and accept IPv6 addresses in many protocol
  4182. elements. Make resolver code handle nameservers located at IPv6
  4183. addresses.
  4184. - More work on making our TLS handshake blend in: modify the list
  4185. of ciphers advertised by OpenSSL in client mode to even more
  4186. closely resemble a common web browser. We cheat a little so that
  4187. we can advertise ciphers that the locally installed OpenSSL doesn't
  4188. know about.
  4189. - Use the TLS1 hostname extension to more closely resemble browser
  4190. behavior.
  4191. o Security fixes (anonymity/entropy):
  4192. - Never use a connection with a mismatched address to extend a
  4193. circuit, unless that connection is canonical. A canonical
  4194. connection is one whose address is authenticated by the router's
  4195. identity key, either in a NETINFO cell or in a router descriptor.
  4196. - Implement most of proposal 110: The first K cells to be sent
  4197. along a circuit are marked as special "early" cells; only K "early"
  4198. cells will be allowed. Once this code is universal, we can block
  4199. certain kinds of denial-of-service attack by requiring that EXTEND
  4200. commands must be sent using an "early" cell.
  4201. - Resume using OpenSSL's RAND_poll() for better (and more portable)
  4202. cross-platform entropy collection again. We used to use it, then
  4203. stopped using it because of a bug that could crash systems that
  4204. called RAND_poll when they had a lot of fds open. It looks like the
  4205. bug got fixed in late 2006. Our new behavior is to call RAND_poll()
  4206. at startup, and to call RAND_poll() when we reseed later only if
  4207. we have a non-buggy OpenSSL version.
  4208. - When the client is choosing entry guards, now it selects at most
  4209. one guard from a given relay family. Otherwise we could end up with
  4210. all of our entry points into the network run by the same operator.
  4211. Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
  4212. - Do not use or believe expired v3 authority certificates. Patch
  4213. from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
  4214. - Drop begin cells to a hidden service if they come from the middle
  4215. of a circuit. Patch from lark.
  4216. - When we erroneously receive two EXTEND cells for the same circuit
  4217. ID on the same connection, drop the second. Patch from lark.
  4218. - Authorities now vote for the Stable flag for any router whose
  4219. weighted MTBF is at least 5 days, regardless of the mean MTBF.
  4220. - Clients now never report any stream end reason except 'MISC'.
  4221. Implements proposal 148.
  4222. o Major bugfixes (crashes):
  4223. - Parse dates and IPv4 addresses in a locale- and libc-independent
  4224. manner, to avoid platform-dependent behavior on malformed input.
  4225. - Fix a crash that occurs on exit nodes when a nameserver request
  4226. timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
  4227. been suppressing the bug since 0.1.2.10-alpha. Partial fix for
  4228. bug 929.
  4229. - Do not assume that a stack-allocated character array will be
  4230. 64-bit aligned on platforms that demand that uint64_t access is
  4231. aligned. Possible fix for bug 604.
  4232. - Resolve a very rare crash bug that could occur when the user forced
  4233. a nameserver reconfiguration during the middle of a nameserver
  4234. probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
  4235. - Avoid a "0 divided by 0" calculation when calculating router uptime
  4236. at directory authorities. Bugfix on 0.2.0.8-alpha.
  4237. - Fix an assertion bug in parsing policy-related options; possible fix
  4238. for bug 811.
  4239. - Rate-limit too-many-sockets messages: when they happen, they happen
  4240. a lot and end up filling up the disk. Resolves bug 748.
  4241. - Fix a race condition that could cause crashes or memory corruption
  4242. when running as a server with a controller listening for log
  4243. messages.
  4244. - Avoid crashing when we have a policy specified in a DirPolicy or
  4245. SocksPolicy or ReachableAddresses option with ports set on it,
  4246. and we re-load the policy. May fix bug 996.
  4247. - Fix an assertion failure on 64-bit platforms when we allocated
  4248. memory right up to the end of a memarea, then realigned the memory
  4249. one step beyond the end. Fixes a possible cause of bug 930.
  4250. - Protect the count of open sockets with a mutex, so we can't
  4251. corrupt it when two threads are closing or opening sockets at once.
  4252. Fix for bug 939. Bugfix on 0.2.0.1-alpha.
  4253. o Major bugfixes (clients):
  4254. - Discard router descriptors as we load them if they are more than
  4255. five days old. Otherwise if Tor is off for a long time and then
  4256. starts with cached descriptors, it will try to use the onion keys
  4257. in those obsolete descriptors when building circuits. Fixes bug 887.
  4258. - When we choose to abandon a new entry guard because we think our
  4259. older ones might be better, close any circuits pending on that
  4260. new entry guard connection. This fix should make us recover much
  4261. faster when our network is down and then comes back. Bugfix on
  4262. 0.1.2.8-beta; found by lodger.
  4263. - When Tor clients restart after 1-5 days, they discard all their
  4264. cached descriptors as too old, but they still use the cached
  4265. consensus document. This approach is good for robustness, but
  4266. bad for performance: since they don't know any bandwidths, they
  4267. end up choosing at random rather than weighting their choice by
  4268. speed. Fixed by the above feature of putting bandwidths in the
  4269. consensus.
  4270. o Major bugfixes (relays):
  4271. - Relays were falling out of the networkstatus consensus for
  4272. part of a day if they changed their local config but the
  4273. authorities discarded their new descriptor as "not sufficiently
  4274. different". Now directory authorities accept a descriptor as changed
  4275. if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
  4276. patch by Sebastian.
  4277. - Ensure that two circuits can never exist on the same connection
  4278. with the same circuit ID, even if one is marked for close. This
  4279. is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
  4280. - Directory authorities were neglecting to mark relays down in their
  4281. internal histories if the relays fall off the routerlist without
  4282. ever being found unreachable. So there were relays in the histories
  4283. that haven't been seen for eight months, and are listed as being
  4284. up for eight months. This wreaked havoc on the "median wfu" and
  4285. "median mtbf" calculations, in turn making Guard and Stable flags
  4286. wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
  4287. on 0.2.0.6-alpha.
  4288. o Major bugfixes (hidden services):
  4289. - When establishing a hidden service, introduction points that
  4290. originate from cannibalized circuits were completely ignored
  4291. and not included in rendezvous service descriptors. This might
  4292. have been another reason for delay in making a hidden service
  4293. available. Bugfix from long ago (0.0.9.x?)
  4294. o Major bugfixes (memory and resource management):
  4295. - Fixed some memory leaks -- some quite frequent, some almost
  4296. impossible to trigger -- based on results from Coverity.
  4297. - Speed up parsing and cut down on memory fragmentation by using
  4298. stack-style allocations for parsing directory objects. Previously,
  4299. this accounted for over 40% of allocations from within Tor's code
  4300. on a typical directory cache.
  4301. - Use a Bloom filter rather than a digest-based set to track which
  4302. descriptors we need to keep around when we're cleaning out old
  4303. router descriptors. This speeds up the computation significantly,
  4304. and may reduce fragmentation.
  4305. o New/changed config options:
  4306. - Now NodeFamily and MyFamily config options allow spaces in
  4307. identity fingerprints, so it's easier to paste them in.
  4308. Suggested by Lucky Green.
  4309. - Allow ports 465 and 587 in the default exit policy again. We had
  4310. rejected them in 0.1.0.15, because back in 2005 they were commonly
  4311. misconfigured and ended up as spam targets. We hear they are better
  4312. locked down these days.
  4313. - Make TrackHostExit mappings expire a while after their last use, not
  4314. after their creation. Patch from Robert Hogan.
  4315. - Add an ExcludeExitNodes option so users can list a set of nodes
  4316. that should be be excluded from the exit node position, but
  4317. allowed elsewhere. Implements proposal 151.
  4318. - New --hush command-line option similar to --quiet. While --quiet
  4319. disables all logging to the console on startup, --hush limits the
  4320. output to messages of warning and error severity.
  4321. - New configure/torrc options (--enable-geoip-stats,
  4322. DirRecordUsageByCountry) to record how many IPs we've served
  4323. directory info to in each country code, how many status documents
  4324. total we've sent to each country code, and what share of the total
  4325. directory requests we should expect to see.
  4326. - Make outbound DNS packets respect the OutboundBindAddress setting.
  4327. Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
  4328. - Allow separate log levels to be configured for different logging
  4329. domains. For example, this allows one to log all notices, warnings,
  4330. or errors, plus all memory management messages of level debug or
  4331. higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
  4332. - Update to the "June 3 2009" ip-to-country file.
  4333. o Minor features (relays):
  4334. - Raise the minimum rate limiting to be a relay from 20000 bytes
  4335. to 20480 bytes (aka 20KB/s), to match our documentation. Also
  4336. update directory authorities so they always assign the Fast flag
  4337. to relays with 20KB/s of capacity. Now people running relays won't
  4338. suddenly find themselves not seeing any use, if the network gets
  4339. faster on average.
  4340. - If we're a relay and we change our IP address, be more verbose
  4341. about the reason that made us change. Should help track down
  4342. further bugs for relays on dynamic IP addresses.
  4343. - Exit servers can now answer resolve requests for ip6.arpa addresses.
  4344. - Implement most of Proposal 152: allow specialized servers to permit
  4345. single-hop circuits, and clients to use those servers to build
  4346. single-hop circuits when using a specialized controller. Patch
  4347. from Josh Albrecht. Resolves feature request 768.
  4348. - When relays do their initial bandwidth measurement, don't limit
  4349. to just our entry guards for the test circuits. Otherwise we tend
  4350. to have multiple test circuits going through a single entry guard,
  4351. which makes our bandwidth test less accurate. Fixes part of bug 654;
  4352. patch contributed by Josh Albrecht.
  4353. o Minor features (directory authorities):
  4354. - Try not to open more than one descriptor-downloading connection
  4355. to an authority at once. This should reduce load on directory
  4356. authorities. Fixes bug 366.
  4357. - Add cross-certification to newly generated certificates, so that
  4358. a signing key is enough information to look up a certificate. Start
  4359. serving certificates by <identity digest, signing key digest>
  4360. pairs. Implements proposal 157.
  4361. - When a directory authority downloads a descriptor that it then
  4362. immediately rejects, do not retry downloading it right away. Should
  4363. save some bandwidth on authorities. Fix for bug 888. Patch by
  4364. Sebastian Hahn.
  4365. - Directory authorities now serve a /tor/dbg-stability.txt URL to
  4366. help debug WFU and MTBF calculations.
  4367. - In directory authorities' approved-routers files, allow
  4368. fingerprints with or without space.
  4369. o Minor features (directory mirrors):
  4370. - When a download gets us zero good descriptors, do not notify
  4371. Tor that new directory information has arrived.
  4372. - Servers support a new URL scheme for consensus downloads that
  4373. allows the client to specify which authorities are trusted.
  4374. The server then only sends the consensus if the client will trust
  4375. it. Otherwise a 404 error is sent back. Clients use this
  4376. new scheme when the server supports it (meaning it's running
  4377. 0.2.1.1-alpha or later). Implements proposal 134.
  4378. o Minor features (bridges):
  4379. - If the bridge config line doesn't specify a port, assume 443.
  4380. This makes bridge lines a bit smaller and easier for users to
  4381. understand.
  4382. - If we're using bridges and our network goes away, be more willing
  4383. to forgive our bridges and try again when we get an application
  4384. request.
  4385. o Minor features (hidden services):
  4386. - When the client launches an introduction circuit, retry with a
  4387. new circuit after 30 seconds rather than 60 seconds.
  4388. - Launch a second client-side introduction circuit in parallel
  4389. after a delay of 15 seconds (based on work by Christian Wilms).
  4390. - Hidden services start out building five intro circuits rather
  4391. than three, and when the first three finish they publish a service
  4392. descriptor using those. Now we publish our service descriptor much
  4393. faster after restart.
  4394. - Drop the requirement to have an open dir port for storing and
  4395. serving v2 hidden service descriptors.
  4396. o Minor features (build and packaging):
  4397. - On Linux, use the prctl call to re-enable core dumps when the User
  4398. option is set.
  4399. - Try to make sure that the version of Libevent we're running with
  4400. is binary-compatible with the one we built with. May address bug
  4401. 897 and others.
  4402. - Add a new --enable-local-appdata configuration switch to change
  4403. the default location of the datadir on win32 from APPDATA to
  4404. LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
  4405. entirely. Patch from coderman.
  4406. - Build correctly against versions of OpenSSL 0.9.8 or later that
  4407. are built without support for deprecated functions.
  4408. - On platforms with a maximum syslog string length, truncate syslog
  4409. messages to that length ourselves, rather than relying on the
  4410. system to do it for us.
  4411. - Automatically detect MacOSX versions earlier than 10.4.0, and
  4412. disable kqueue from inside Tor when running with these versions.
  4413. We previously did this from the startup script, but that was no
  4414. help to people who didn't use the startup script. Resolves bug 863.
  4415. - Build correctly when configured to build outside the main source
  4416. path. Patch from Michael Gold.
  4417. - Disable GCC's strict alias optimization by default, to avoid the
  4418. likelihood of its introducing subtle bugs whenever our code violates
  4419. the letter of C99's alias rules.
  4420. - Change the contrib/tor.logrotate script so it makes the new
  4421. logs as "_tor:_tor" rather than the default, which is generally
  4422. "root:wheel". Fixes bug 676, reported by Serge Koksharov.
  4423. - Change our header file guard macros to be less likely to conflict
  4424. with system headers. Adam Langley noticed that we were conflicting
  4425. with log.h on Android.
  4426. - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
  4427. and stop using a warning that had become unfixably verbose under
  4428. GCC 4.3.
  4429. - Use a lockfile to make sure that two Tor processes are not
  4430. simultaneously running with the same datadir.
  4431. - Allow OpenSSL to use dynamic locks if it wants.
  4432. - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
  4433. o Minor features (controllers):
  4434. - When generating circuit events with verbose nicknames for
  4435. controllers, try harder to look up nicknames for routers on a
  4436. circuit. (Previously, we would look in the router descriptors we had
  4437. for nicknames, but not in the consensus.) Partial fix for bug 941.
  4438. - New controller event NEWCONSENSUS that lists the networkstatus
  4439. lines for every recommended relay. Now controllers like Torflow
  4440. can keep up-to-date on which relays they should be using.
  4441. - New controller event "clients_seen" to report a geoip-based summary
  4442. of which countries we've seen clients from recently. Now controllers
  4443. like Vidalia can show bridge operators that they're actually making
  4444. a difference.
  4445. - Add a 'getinfo status/clients-seen' controller command, in case
  4446. controllers want to hear clients_seen events but connect late.
  4447. - New CONSENSUS_ARRIVED event to note when a new consensus has
  4448. been fetched and validated.
  4449. - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
  4450. controllers to prevent SIGHUP from reloading the configuration.
  4451. Fixes bug 856.
  4452. - Return circuit purposes in response to GETINFO circuit-status.
  4453. Fixes bug 858.
  4454. - Serve the latest v3 networkstatus consensus via the control
  4455. port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
  4456. - Add a "GETINFO /status/bootstrap-phase" controller option, so the
  4457. controller can query our current bootstrap state in case it attaches
  4458. partway through and wants to catch up.
  4459. - Provide circuit purposes along with circuit events to the controller.
  4460. o Minor features (tools):
  4461. - Do not have tor-resolve automatically refuse all .onion addresses;
  4462. if AutomapHostsOnResolve is set in your torrc, this will work fine.
  4463. - Add a -p option to tor-resolve for specifying the SOCKS port: some
  4464. people find host:port too confusing.
  4465. - Print the SOCKS5 error message string as well as the error code
  4466. when a tor-resolve request fails. Patch from Jacob.
  4467. o Minor bugfixes (memory and resource management):
  4468. - Clients no longer cache certificates for authorities they do not
  4469. recognize. Bugfix on 0.2.0.9-alpha.
  4470. - Do not use C's stdio library for writing to log files. This will
  4471. improve logging performance by a minute amount, and will stop
  4472. leaking fds when our disk is full. Fixes bug 861.
  4473. - Stop erroneous use of O_APPEND in cases where we did not in fact
  4474. want to re-seek to the end of a file before every last write().
  4475. - Fix a small alignment and memory-wasting bug on buffer chunks.
  4476. Spotted by rovv.
  4477. - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
  4478. to avoid unused RAM in buffer chunks and memory pools.
  4479. - Reduce the default smartlist size from 32 to 16; it turns out that
  4480. most smartlists hold around 8-12 elements tops.
  4481. - Make dumpstats() log the fullness and size of openssl-internal
  4482. buffers.
  4483. - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
  4484. patch to their OpenSSL, turn it on to save memory on servers. This
  4485. patch will (with any luck) get included in a mainline distribution
  4486. before too long.
  4487. - Fix a memory leak when v3 directory authorities load their keys
  4488. and cert from disk. Bugfix on 0.2.0.1-alpha.
  4489. - Stop using malloc_usable_size() to use more area than we had
  4490. actually allocated: it was safe, but made valgrind really unhappy.
  4491. - Make the assert_circuit_ok() function work correctly on circuits that
  4492. have already been marked for close.
  4493. - Fix uninitialized size field for memory area allocation: may improve
  4494. memory performance during directory parsing.
  4495. o Minor bugfixes (clients):
  4496. - Stop reloading the router list from disk for no reason when we
  4497. run out of reachable directory mirrors. Once upon a time reloading
  4498. it would set the 'is_running' flag back to 1 for them. It hasn't
  4499. done that for a long time.
  4500. - When we had picked an exit node for a connection, but marked it as
  4501. "optional", and it turned out we had no onion key for the exit,
  4502. stop wanting that exit and try again. This situation may not
  4503. be possible now, but will probably become feasible with proposal
  4504. 158. Spotted by rovv. Fixes another case of bug 752.
  4505. - Fix a bug in address parsing that was preventing bridges or hidden
  4506. service targets from being at IPv6 addresses.
  4507. - Do not remove routers as too old if we do not have any consensus
  4508. document. Bugfix on 0.2.0.7-alpha.
  4509. - When an exit relay resolves a stream address to a local IP address,
  4510. do not just keep retrying that same exit relay over and
  4511. over. Instead, just close the stream. Addresses bug 872. Bugfix
  4512. on 0.2.0.32. Patch from rovv.
  4513. - Made Tor a little less aggressive about deleting expired
  4514. certificates. Partial fix for bug 854.
  4515. - Treat duplicate certificate fetches as failures, so that we do
  4516. not try to re-fetch an expired certificate over and over and over.
  4517. - Do not say we're fetching a certificate when we'll in fact skip it
  4518. because of a pending download.
  4519. - If we have correct permissions on $datadir, we complain to stdout
  4520. and fail to start. But dangerous permissions on
  4521. $datadir/cached-status/ would cause us to open a log and complain
  4522. there. Now complain to stdout and fail to start in both cases. Fixes
  4523. bug 820, reported by seeess.
  4524. o Minor bugfixes (bridges):
  4525. - When we made bridge authorities stop serving bridge descriptors over
  4526. unencrypted links, we also broke DirPort reachability testing for
  4527. bridges. So bridges with a non-zero DirPort were printing spurious
  4528. warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
  4529. - Don't allow a bridge to publish its router descriptor to a
  4530. non-bridge directory authority. Fixes part of bug 932.
  4531. - When we change to or from being a bridge, reset our counts of
  4532. client usage by country. Fixes bug 932.
  4533. o Minor bugfixes (relays):
  4534. - Log correct error messages for DNS-related network errors on
  4535. Windows.
  4536. - Actually return -1 in the error case for read_bandwidth_usage().
  4537. Harmless bug, since we currently don't care about the return value
  4538. anywhere. Bugfix on 0.2.0.9-alpha.
  4539. - Provide a more useful log message if bug 977 (related to buffer
  4540. freelists) ever reappears, and do not crash right away.
  4541. - We were already rejecting relay begin cells with destination port
  4542. of 0. Now also reject extend cells with destination port or address
  4543. of 0. Suggested by lark.
  4544. - When we can't transmit a DNS request due to a network error, retry
  4545. it after a while, and eventually transmit a failing response to
  4546. the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
  4547. - Solve a bug that kept hardware crypto acceleration from getting
  4548. enabled when accounting was turned on. Fixes bug 907. Bugfix on
  4549. 0.0.9pre6.
  4550. - When a canonical connection appears later in our internal list
  4551. than a noncanonical one for a given OR ID, always use the
  4552. canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
  4553. Spotted by rovv.
  4554. - Avoid some nasty corner cases in the logic for marking connections
  4555. as too old or obsolete or noncanonical for circuits. Partial
  4556. bugfix on bug 891.
  4557. - Fix another interesting corner-case of bug 891 spotted by rovv:
  4558. Previously, if two hosts had different amounts of clock drift, and
  4559. one of them created a new connection with just the wrong timing,
  4560. the other might decide to deprecate the new connection erroneously.
  4561. Bugfix on 0.1.1.13-alpha.
  4562. - If one win32 nameserver fails to get added, continue adding the
  4563. rest, and don't automatically fail.
  4564. - Fix a bug where an unreachable relay would establish enough
  4565. reachability testing circuits to do a bandwidth test -- if
  4566. we already have a connection to the middle hop of the testing
  4567. circuit, then it could establish the last hop by using the existing
  4568. connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
  4569. circuits no longer use entry guards in 0.2.1.3-alpha.
  4570. o Minor bugfixes (directory authorities):
  4571. - Limit uploaded directory documents to be 16M rather than 500K.
  4572. The directory authorities were refusing v3 consensus votes from
  4573. other authorities, since the votes are now 504K. Fixes bug 959;
  4574. bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
  4575. - Directory authorities should never send a 503 "busy" response to
  4576. requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
  4577. bug 959.
  4578. - Fix code so authorities _actually_ send back X-Descriptor-Not-New
  4579. headers. Bugfix on 0.2.0.10-alpha.
  4580. o Minor bugfixes (hidden services):
  4581. - When we can't find an intro key for a v2 hidden service descriptor,
  4582. fall back to the v0 hidden service descriptor and log a bug message.
  4583. Workaround for bug 1024.
  4584. - In very rare situations new hidden service descriptors were
  4585. published earlier than 30 seconds after the last change to the
  4586. service. (We currently think that a hidden service descriptor
  4587. that's been stable for 30 seconds is worth publishing.)
  4588. - If a hidden service sends us an END cell, do not consider
  4589. retrying the connection; just close it. Patch from rovv.
  4590. - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
  4591. service directories if they have no advertised dir port. Bugfix
  4592. on 0.2.0.10-alpha.
  4593. o Minor bugfixes (tools):
  4594. - In the torify(1) manpage, mention that tsocks will leak your
  4595. DNS requests.
  4596. o Minor bugfixes (controllers):
  4597. - If the controller claimed responsibility for a stream, but that
  4598. stream never finished making its connection, it would live
  4599. forever in circuit_wait state. Now we close it after SocksTimeout
  4600. seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
  4601. - Make DNS resolved controller events into "CLOSED", not
  4602. "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
  4603. bug 807.
  4604. - The control port would close the connection before flushing long
  4605. replies, such as the network consensus, if a QUIT command was issued
  4606. before the reply had completed. Now, the control port flushes all
  4607. pending replies before closing the connection. Also fix a spurious
  4608. warning when a QUIT command is issued after a malformed or rejected
  4609. AUTHENTICATE command, but before the connection was closed. Patch
  4610. by Marcus Griep. Fixes bugs 1015 and 1016.
  4611. - Fix a bug that made stream bandwidth get misreported to the
  4612. controller.
  4613. o Deprecated and removed features:
  4614. - The old "tor --version --version" command, which would print out
  4615. the subversion "Id" of most of the source files, is now removed. It
  4616. turned out to be less useful than we'd expected, and harder to
  4617. maintain.
  4618. - RedirectExits has been removed. It was deprecated since
  4619. 0.2.0.3-alpha.
  4620. - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
  4621. has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
  4622. - Cell pools are now always enabled; --disable-cell-pools is ignored.
  4623. - Directory mirrors no longer fetch the v1 directory or
  4624. running-routers files. They are obsolete, and nobody asks for them
  4625. anymore. This is the first step to making v1 authorities obsolete.
  4626. - Take out the TestVia config option, since it was a workaround for
  4627. a bug that was fixed in Tor 0.1.1.21.
  4628. - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
  4629. HiddenServiceExcludeNodes as obsolete: they never worked properly,
  4630. and nobody seems to be using them. Fixes bug 754. Bugfix on
  4631. 0.1.0.1-rc. Patch from Christian Wilms.
  4632. - Remove all backward-compatibility code for relays running
  4633. versions of Tor so old that they no longer work at all on the
  4634. Tor network.
  4635. o Code simplifications and refactoring:
  4636. - Tool-assisted documentation cleanup. Nearly every function or
  4637. static variable in Tor should have its own documentation now.
  4638. - Rename the confusing or_is_obsolete field to the more appropriate
  4639. is_bad_for_new_circs, and move it to or_connection_t where it
  4640. belongs.
  4641. - Move edge-only flags from connection_t to edge_connection_t: not
  4642. only is this better coding, but on machines of plausible alignment,
  4643. it should save 4-8 bytes per connection_t. "Every little bit helps."
  4644. - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
  4645. for consistency; keep old option working for backward compatibility.
  4646. - Simplify the code for finding connections to use for a circuit.
  4647. - Revise the connection_new functions so that a more typesafe variant
  4648. exists. This will work better with Coverity, and let us find any
  4649. actual mistakes we're making here.
  4650. - Refactor unit testing logic so that dmalloc can be used sensibly
  4651. with unit tests to check for memory leaks.
  4652. - Move all hidden-service related fields from connection and circuit
  4653. structure to substructures: this way they won't eat so much memory.
  4654. - Squeeze 2-5% out of client performance (according to oprofile) by
  4655. improving the implementation of some policy-manipulation functions.
  4656. - Change the implementation of ExcludeNodes and ExcludeExitNodes to
  4657. be more efficient. Formerly it was quadratic in the number of
  4658. servers; now it should be linear. Fixes bug 509.
  4659. - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
  4660. and n_conn_id_digest fields into a separate structure that's
  4661. only needed when the circuit has not yet attached to an n_conn.
  4662. - Optimize out calls to time(NULL) that occur for every IO operation,
  4663. or for every cell. On systems like Windows where time() is a
  4664. slow syscall, this fix will be slightly helpful.
  4665. Changes in version 0.2.0.35 - 2009-06-24
  4666. o Security fix:
  4667. - Avoid crashing in the presence of certain malformed descriptors.
  4668. Found by lark, and by automated fuzzing.
  4669. - Fix an edge case where a malicious exit relay could convince a
  4670. controller that the client's DNS question resolves to an internal IP
  4671. address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
  4672. o Major bugfixes:
  4673. - Finally fix the bug where dynamic-IP relays disappear when their
  4674. IP address changes: directory mirrors were mistakenly telling
  4675. them their old address if they asked via begin_dir, so they
  4676. never got an accurate answer about their new address, so they
  4677. just vanished after a day. For belt-and-suspenders, relays that
  4678. don't set Address in their config now avoid using begin_dir for
  4679. all direct connections. Should fix bugs 827, 883, and 900.
  4680. - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
  4681. that would occur on some exit nodes when DNS failures and timeouts
  4682. occurred in certain patterns. Fix for bug 957.
  4683. o Minor bugfixes:
  4684. - When starting with a cache over a few days old, do not leak
  4685. memory for the obsolete router descriptors in it. Bugfix on
  4686. 0.2.0.33; fixes bug 672.
  4687. - Hidden service clients didn't use a cached service descriptor that
  4688. was older than 15 minutes, but wouldn't fetch a new one either,
  4689. because there was already one in the cache. Now, fetch a v2
  4690. descriptor unless the same descriptor was added to the cache within
  4691. the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
  4692. Changes in version 0.2.0.34 - 2009-02-08
  4693. Tor 0.2.0.34 features several more security-related fixes. You should
  4694. upgrade, especially if you run an exit relay (remote crash) or a
  4695. directory authority (remote infinite loop), or you're on an older
  4696. (pre-XP) or not-recently-patched Windows (remote exploit).
  4697. This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
  4698. have many known flaws, and nobody should be using them. You should
  4699. upgrade. If you're using a Linux or BSD and its packages are obsolete,
  4700. stop using those packages and upgrade anyway.
  4701. o Security fixes:
  4702. - Fix an infinite-loop bug on handling corrupt votes under certain
  4703. circumstances. Bugfix on 0.2.0.8-alpha.
  4704. - Fix a temporary DoS vulnerability that could be performed by
  4705. a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
  4706. - Avoid a potential crash on exit nodes when processing malformed
  4707. input. Remote DoS opportunity. Bugfix on 0.2.0.33.
  4708. - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
  4709. Spec conformance issue. Bugfix on Tor 0.0.2pre27.
  4710. o Minor bugfixes:
  4711. - Fix compilation on systems where time_t is a 64-bit integer.
  4712. Patch from Matthias Drochner.
  4713. - Don't consider expiring already-closed client connections. Fixes
  4714. bug 893. Bugfix on 0.0.2pre20.
  4715. Changes in version 0.2.0.33 - 2009-01-21
  4716. Tor 0.2.0.33 fixes a variety of bugs that were making relays less
  4717. useful to users. It also finally fixes a bug where a relay or client
  4718. that's been off for many days would take a long time to bootstrap.
  4719. This update also fixes an important security-related bug reported by
  4720. Ilja van Sprundel. You should upgrade. (We'll send out more details
  4721. about the bug once people have had some time to upgrade.)
  4722. o Security fixes:
  4723. - Fix a heap-corruption bug that may be remotely triggerable on
  4724. some platforms. Reported by Ilja van Sprundel.
  4725. o Major bugfixes:
  4726. - When a stream at an exit relay is in state "resolving" or
  4727. "connecting" and it receives an "end" relay cell, the exit relay
  4728. would silently ignore the end cell and not close the stream. If
  4729. the client never closes the circuit, then the exit relay never
  4730. closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
  4731. reported by "wood".
  4732. - When sending CREATED cells back for a given circuit, use a 64-bit
  4733. connection ID to find the right connection, rather than an addr:port
  4734. combination. Now that we can have multiple OR connections between
  4735. the same ORs, it is no longer possible to use addr:port to uniquely
  4736. identify a connection.
  4737. - Bridge relays that had DirPort set to 0 would stop fetching
  4738. descriptors shortly after startup, and then briefly resume
  4739. after a new bandwidth test and/or after publishing a new bridge
  4740. descriptor. Bridge users that try to bootstrap from them would
  4741. get a recent networkstatus but would get descriptors from up to
  4742. 18 hours earlier, meaning most of the descriptors were obsolete
  4743. already. Reported by Tas; bugfix on 0.2.0.13-alpha.
  4744. - Prevent bridge relays from serving their 'extrainfo' document
  4745. to anybody who asks, now that extrainfo docs include potentially
  4746. sensitive aggregated client geoip summaries. Bugfix on
  4747. 0.2.0.13-alpha.
  4748. - If the cached networkstatus consensus is more than five days old,
  4749. discard it rather than trying to use it. In theory it could be
  4750. useful because it lists alternate directory mirrors, but in practice
  4751. it just means we spend many minutes trying directory mirrors that
  4752. are long gone from the network. Also discard router descriptors as
  4753. we load them if they are more than five days old, since the onion
  4754. key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
  4755. o Minor bugfixes:
  4756. - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
  4757. could make gcc generate non-functional binary search code. Bugfix
  4758. on 0.2.0.10-alpha.
  4759. - Build correctly on platforms without socklen_t.
  4760. - Compile without warnings on solaris.
  4761. - Avoid potential crash on internal error during signature collection.
  4762. Fixes bug 864. Patch from rovv.
  4763. - Correct handling of possible malformed authority signing key
  4764. certificates with internal signature types. Fixes bug 880.
  4765. Bugfix on 0.2.0.3-alpha.
  4766. - Fix a hard-to-trigger resource leak when logging credential status.
  4767. CID 349.
  4768. - When we can't initialize DNS because the network is down, do not
  4769. automatically stop Tor from starting. Instead, we retry failed
  4770. dns_init() every 10 minutes, and change the exit policy to reject
  4771. *:* until one succeeds. Fixes bug 691.
  4772. - Use 64 bits instead of 32 bits for connection identifiers used with
  4773. the controller protocol, to greatly reduce risk of identifier reuse.
  4774. - When we're choosing an exit node for a circuit, and we have
  4775. no pending streams, choose a good general exit rather than one that
  4776. supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
  4777. - Fix another case of assuming, when a specific exit is requested,
  4778. that we know more than the user about what hosts it allows.
  4779. Fixes one case of bug 752. Patch from rovv.
  4780. - Clip the MaxCircuitDirtiness config option to a minimum of 10
  4781. seconds. Warn the user if lower values are given in the
  4782. configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
  4783. - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
  4784. user if lower values are given in the configuration. Bugfix on
  4785. 0.1.1.17-rc. Patch by Sebastian.
  4786. - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
  4787. the cache because we already had a v0 descriptor with the same ID.
  4788. Bugfix on 0.2.0.18-alpha.
  4789. - Fix a race condition when freeing keys shared between main thread
  4790. and CPU workers that could result in a memory leak. Bugfix on
  4791. 0.1.0.1-rc. Fixes bug 889.
  4792. - Send a valid END cell back when a client tries to connect to a
  4793. nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
  4794. 840. Patch from rovv.
  4795. - Check which hops rendezvous stream cells are associated with to
  4796. prevent possible guess-the-streamid injection attacks from
  4797. intermediate hops. Fixes another case of bug 446. Based on patch
  4798. from rovv.
  4799. - If a broken client asks a non-exit router to connect somewhere,
  4800. do not even do the DNS lookup before rejecting the connection.
  4801. Fixes another case of bug 619. Patch from rovv.
  4802. - When a relay gets a create cell it can't decrypt (e.g. because it's
  4803. using the wrong onion key), we were dropping it and letting the
  4804. client time out. Now actually answer with a destroy cell. Fixes
  4805. bug 904. Bugfix on 0.0.2pre8.
  4806. o Minor bugfixes (hidden services):
  4807. - Do not throw away existing introduction points on SIGHUP. Bugfix on
  4808. 0.0.6pre1. Patch by Karsten. Fixes bug 874.
  4809. o Minor features:
  4810. - Report the case where all signatures in a detached set are rejected
  4811. differently than the case where there is an error handling the
  4812. detached set.
  4813. - When we realize that another process has modified our cached
  4814. descriptors, print out a more useful error message rather than
  4815. triggering an assertion. Fixes bug 885. Patch from Karsten.
  4816. - Implement the 0x20 hack to better resist DNS poisoning: set the
  4817. case on outgoing DNS requests randomly, and reject responses that do
  4818. not match the case correctly. This logic can be disabled with the
  4819. ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
  4820. of servers that do not reliably preserve case in replies. See
  4821. "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
  4822. for more info.
  4823. - Check DNS replies for more matching fields to better resist DNS
  4824. poisoning.
  4825. - Never use OpenSSL compression: it wastes RAM and CPU trying to
  4826. compress cells, which are basically all encrypted, compressed, or
  4827. both.
  4828. Changes in version 0.2.0.32 - 2008-11-20
  4829. Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
  4830. packages (and maybe other packages) noticed by Theo de Raadt, fixes
  4831. a smaller security flaw that might allow an attacker to access local
  4832. services, further improves hidden service performance, and fixes a
  4833. variety of other issues.
  4834. o Security fixes:
  4835. - The "User" and "Group" config options did not clear the
  4836. supplementary group entries for the Tor process. The "User" option
  4837. is now more robust, and we now set the groups to the specified
  4838. user's primary group. The "Group" option is now ignored. For more
  4839. detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
  4840. in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
  4841. and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
  4842. - The "ClientDNSRejectInternalAddresses" config option wasn't being
  4843. consistently obeyed: if an exit relay refuses a stream because its
  4844. exit policy doesn't allow it, we would remember what IP address
  4845. the relay said the destination address resolves to, even if it's
  4846. an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
  4847. o Major bugfixes:
  4848. - Fix a DOS opportunity during the voting signature collection process
  4849. at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
  4850. o Major bugfixes (hidden services):
  4851. - When fetching v0 and v2 rendezvous service descriptors in parallel,
  4852. we were failing the whole hidden service request when the v0
  4853. descriptor fetch fails, even if the v2 fetch is still pending and
  4854. might succeed. Similarly, if the last v2 fetch fails, we were
  4855. failing the whole hidden service request even if a v0 fetch is
  4856. still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
  4857. - When extending a circuit to a hidden service directory to upload a
  4858. rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
  4859. requests failed, because the router descriptor has not been
  4860. downloaded yet. In these cases, do not attempt to upload the
  4861. rendezvous descriptor, but wait until the router descriptor is
  4862. downloaded and retry. Likewise, do not attempt to fetch a rendezvous
  4863. descriptor from a hidden service directory for which the router
  4864. descriptor has not yet been downloaded. Fixes bug 767. Bugfix
  4865. on 0.2.0.10-alpha.
  4866. o Minor bugfixes:
  4867. - Fix several infrequent memory leaks spotted by Coverity.
  4868. - When testing for libevent functions, set the LDFLAGS variable
  4869. correctly. Found by Riastradh.
  4870. - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
  4871. bootstrapping with tunneled directory connections. Bugfix on
  4872. 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
  4873. - When asked to connect to A.B.exit:80, if we don't know the IP for A
  4874. and we know that server B rejects most-but-not all connections to
  4875. port 80, we would previously reject the connection. Now, we assume
  4876. the user knows what they were asking for. Fixes bug 752. Bugfix
  4877. on 0.0.9rc5. Diagnosed by BarkerJr.
  4878. - If we overrun our per-second write limits a little, count this as
  4879. having used up our write allocation for the second, and choke
  4880. outgoing directory writes. Previously, we had only counted this when
  4881. we had met our limits precisely. Fixes bug 824. Patch from by rovv.
  4882. Bugfix on 0.2.0.x (??).
  4883. - Remove the old v2 directory authority 'lefkada' from the default
  4884. list. It has been gone for many months.
  4885. - Stop doing unaligned memory access that generated bus errors on
  4886. sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
  4887. - Make USR2 log-level switch take effect immediately. Bugfix on
  4888. 0.1.2.8-beta.
  4889. o Minor bugfixes (controller):
  4890. - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
  4891. 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
  4892. Changes in version 0.2.0.31 - 2008-09-03
  4893. Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
  4894. a big bug we're seeing where in rare cases traffic from one Tor stream
  4895. gets mixed into another stream, and fixes a variety of smaller issues.
  4896. o Major bugfixes:
  4897. - Make sure that two circuits can never exist on the same connection
  4898. with the same circuit ID, even if one is marked for close. This
  4899. is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
  4900. - Relays now reject risky extend cells: if the extend cell includes
  4901. a digest of all zeroes, or asks to extend back to the relay that
  4902. sent the extend cell, tear down the circuit. Ideas suggested
  4903. by rovv.
  4904. - If not enough of our entry guards are available so we add a new
  4905. one, we might use the new one even if it overlapped with the
  4906. current circuit's exit relay (or its family). Anonymity bugfix
  4907. pointed out by rovv.
  4908. o Minor bugfixes:
  4909. - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
  4910. 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
  4911. - Correctly detect the presence of the linux/netfilter_ipv4.h header
  4912. when building against recent kernels. Bugfix on 0.1.2.1-alpha.
  4913. - Pick size of default geoip filename string correctly on windows.
  4914. Fixes bug 806. Bugfix on 0.2.0.30.
  4915. - Make the autoconf script accept the obsolete --with-ssl-dir
  4916. option as an alias for the actually-working --with-openssl-dir
  4917. option. Fix the help documentation to recommend --with-openssl-dir.
  4918. Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
  4919. - When using the TransPort option on OpenBSD, and using the User
  4920. option to change UID and drop privileges, make sure to open
  4921. /dev/pf before dropping privileges. Fixes bug 782. Patch from
  4922. Christopher Davis. Bugfix on 0.1.2.1-alpha.
  4923. - Try to attach connections immediately upon receiving a RENDEZVOUS2
  4924. or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
  4925. on the client side when connecting to a hidden service. Bugfix
  4926. on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
  4927. - When closing an application-side connection because its circuit is
  4928. getting torn down, generate the stream event correctly. Bugfix on
  4929. 0.1.2.x. Anonymous patch.
  4930. Changes in version 0.2.0.30 - 2008-07-15
  4931. This new stable release switches to a more efficient directory
  4932. distribution design, adds features to make connections to the Tor
  4933. network harder to block, allows Tor to act as a DNS proxy, adds separate
  4934. rate limiting for relayed traffic to make it easier for clients to
  4935. become relays, fixes a variety of potential anonymity problems, and
  4936. includes the usual huge pile of other features and bug fixes.
  4937. o New v3 directory design:
  4938. - Tor now uses a new way to learn about and distribute information
  4939. about the network: the directory authorities vote on a common
  4940. network status document rather than each publishing their own
  4941. opinion. Now clients and caches download only one networkstatus
  4942. document to bootstrap, rather than downloading one for each
  4943. authority. Clients only download router descriptors listed in
  4944. the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
  4945. for details.
  4946. - Set up moria1, tor26, and dizum as v3 directory authorities
  4947. in addition to being v2 authorities. Also add three new ones:
  4948. ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
  4949. dannenberg (run by CCC).
  4950. - Switch to multi-level keys for directory authorities: now their
  4951. long-term identity key can be kept offline, and they periodically
  4952. generate a new signing key. Clients fetch the "key certificates"
  4953. to keep up to date on the right keys. Add a standalone tool
  4954. "tor-gencert" to generate key certificates. Implements proposal 103.
  4955. - Add a new V3AuthUseLegacyKey config option to make it easier for
  4956. v3 authorities to change their identity keys if another bug like
  4957. Debian's OpenSSL RNG flaw appears.
  4958. - Authorities and caches fetch the v2 networkstatus documents
  4959. less often, now that v3 is recommended.
  4960. o Make Tor connections stand out less on the wire:
  4961. - Use an improved TLS handshake designed by Steven Murdoch in proposal
  4962. 124, as revised in proposal 130. The new handshake is meant to
  4963. be harder for censors to fingerprint, and it adds the ability
  4964. to detect certain kinds of man-in-the-middle traffic analysis
  4965. attacks. The new handshake format includes version negotiation for
  4966. OR connections as described in proposal 105, which will allow us
  4967. to improve Tor's link protocol more safely in the future.
  4968. - Enable encrypted directory connections by default for non-relays,
  4969. so censor tools that block Tor directory connections based on their
  4970. plaintext patterns will no longer work. This means Tor works in
  4971. certain censored countries by default again.
  4972. - Stop including recognizeable strings in the commonname part of
  4973. Tor's x509 certificates.
  4974. o Implement bridge relays:
  4975. - Bridge relays (or "bridges" for short) are Tor relays that aren't
  4976. listed in the main Tor directory. Since there is no complete public
  4977. list of them, even an ISP that is filtering connections to all the
  4978. known Tor relays probably won't be able to block all the bridges.
  4979. See doc/design-paper/blocking.pdf and proposal 125 for details.
  4980. - New config option BridgeRelay that specifies you want to be a
  4981. bridge relay rather than a normal relay. When BridgeRelay is set
  4982. to 1, then a) you cache dir info even if your DirPort ins't on,
  4983. and b) the default for PublishServerDescriptor is now "bridge"
  4984. rather than "v2,v3".
  4985. - New config option "UseBridges 1" for clients that want to use bridge
  4986. relays instead of ordinary entry guards. Clients then specify
  4987. bridge relays by adding "Bridge" lines to their config file. Users
  4988. can learn about a bridge relay either manually through word of
  4989. mouth, or by one of our rate-limited mechanisms for giving out
  4990. bridge addresses without letting an attacker easily enumerate them
  4991. all. See https://www.torproject.org/bridges for details.
  4992. - Bridge relays behave like clients with respect to time intervals
  4993. for downloading new v3 consensus documents -- otherwise they
  4994. stand out. Bridge users now wait until the end of the interval,
  4995. so their bridge relay will be sure to have a new consensus document.
  4996. o Implement bridge directory authorities:
  4997. - Bridge authorities are like normal directory authorities, except
  4998. they don't serve a list of known bridges. Therefore users that know
  4999. a bridge's fingerprint can fetch a relay descriptor for that bridge,
  5000. including fetching updates e.g. if the bridge changes IP address,
  5001. yet an attacker can't just fetch a list of all the bridges.
  5002. - Set up Tonga as the default bridge directory authority.
  5003. - Bridge authorities refuse to serve bridge descriptors or other
  5004. bridge information over unencrypted connections (that is, when
  5005. responding to direct DirPort requests rather than begin_dir cells.)
  5006. - Bridge directory authorities do reachability testing on the
  5007. bridges they know. They provide router status summaries to the
  5008. controller via "getinfo ns/purpose/bridge", and also dump summaries
  5009. to a file periodically, so we can keep internal stats about which
  5010. bridges are functioning.
  5011. - If bridge users set the UpdateBridgesFromAuthority config option,
  5012. but the digest they ask for is a 404 on the bridge authority,
  5013. they fall back to contacting the bridge directly.
  5014. - Bridges always use begin_dir to publish their server descriptor to
  5015. the bridge authority using an anonymous encrypted tunnel.
  5016. - Early work on a "bridge community" design: if bridge authorities set
  5017. the BridgePassword config option, they will serve a snapshot of
  5018. known bridge routerstatuses from their DirPort to anybody who
  5019. knows that password. Unset by default.
  5020. - Tor now includes an IP-to-country GeoIP file, so bridge relays can
  5021. report sanitized aggregated summaries in their extra-info documents
  5022. privately to the bridge authority, listing which countries are
  5023. able to reach them. We hope this mechanism will let us learn when
  5024. certain countries start trying to block bridges.
  5025. - Bridge authorities write bridge descriptors to disk, so they can
  5026. reload them after a reboot. They can also export the descriptors
  5027. to other programs, so we can distribute them to blocked users via
  5028. the BridgeDB interface, e.g. via https://bridges.torproject.org/
  5029. and bridges@torproject.org.
  5030. o Tor can be a DNS proxy:
  5031. - The new client-side DNS proxy feature replaces the need for
  5032. dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
  5033. for DNS requests on port 9999, use the Tor network to resolve them
  5034. anonymously, and send the reply back like a regular DNS server.
  5035. The code still only implements a subset of DNS.
  5036. - Add a new AutomapHostsOnResolve option: when it is enabled, any
  5037. resolve request for hosts matching a given pattern causes Tor to
  5038. generate an internal virtual address mapping for that host. This
  5039. allows DNSPort to work sensibly with hidden service users. By
  5040. default, .exit and .onion addresses are remapped; the list of
  5041. patterns can be reconfigured with AutomapHostsSuffixes.
  5042. - Add an "-F" option to tor-resolve to force a resolve for a .onion
  5043. address. Thanks to the AutomapHostsOnResolve option, this is no
  5044. longer a completely silly thing to do.
  5045. o Major features (relay usability):
  5046. - New config options RelayBandwidthRate and RelayBandwidthBurst:
  5047. a separate set of token buckets for relayed traffic. Right now
  5048. relayed traffic is defined as answers to directory requests, and
  5049. OR connections that don't have any local circuits on them. See
  5050. proposal 111 for details.
  5051. - Create listener connections before we setuid to the configured
  5052. User and Group. Now non-Windows users can choose port values
  5053. under 1024, start Tor as root, and have Tor bind those ports
  5054. before it changes to another UID. (Windows users could already
  5055. pick these ports.)
  5056. - Added a new ConstrainedSockets config option to set SO_SNDBUF and
  5057. SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
  5058. on "vserver" accounts. Patch from coderman.
  5059. o Major features (directory authorities):
  5060. - Directory authorities track weighted fractional uptime and weighted
  5061. mean-time-between failures for relays. WFU is suitable for deciding
  5062. whether a node is "usually up", while MTBF is suitable for deciding
  5063. whether a node is "likely to stay up." We need both, because
  5064. "usually up" is a good requirement for guards, while "likely to
  5065. stay up" is a good requirement for long-lived connections.
  5066. - Directory authorities use a new formula for selecting which relays
  5067. to advertise as Guards: they must be in the top 7/8 in terms of
  5068. how long we have known about them, and above the median of those
  5069. nodes in terms of weighted fractional uptime.
  5070. - Directory authorities use a new formula for selecting which relays
  5071. to advertise as Stable: when we have 4 or more days of data, use
  5072. median measured MTBF rather than median declared uptime. Implements
  5073. proposal 108.
  5074. - Directory authorities accept and serve "extra info" documents for
  5075. routers. Routers now publish their bandwidth-history lines in the
  5076. extra-info docs rather than the main descriptor. This step saves
  5077. 60% (!) on compressed router descriptor downloads. Servers upload
  5078. extra-info docs to any authority that accepts them; directory
  5079. authorities now allow multiple router descriptors and/or extra
  5080. info documents to be uploaded in a single go. Authorities, and
  5081. caches that have been configured to download extra-info documents,
  5082. download them as needed. Implements proposal 104.
  5083. - Authorities now list relays who have the same nickname as
  5084. a different named relay, but list them with a new flag:
  5085. "Unnamed". Now we can make use of relays that happen to pick the
  5086. same nickname as a server that registered two years ago and then
  5087. disappeared. Implements proposal 122.
  5088. - Store routers in a file called cached-descriptors instead of in
  5089. cached-routers. Initialize cached-descriptors from cached-routers
  5090. if the old format is around. The new format allows us to store
  5091. annotations along with descriptors, to record the time we received
  5092. each descriptor, its source, and its purpose: currently one of
  5093. general, controller, or bridge.
  5094. o Major features (other):
  5095. - New config options WarnPlaintextPorts and RejectPlaintextPorts so
  5096. Tor can warn and/or refuse connections to ports commonly used with
  5097. vulnerable-plaintext protocols. Currently we warn on ports 23,
  5098. 109, 110, and 143, but we don't reject any. Based on proposal 129
  5099. by Kevin Bauer and Damon McCoy.
  5100. - Integrate Karsten Loesing's Google Summer of Code project to publish
  5101. hidden service descriptors on a set of redundant relays that are a
  5102. function of the hidden service address. Now we don't have to rely
  5103. on three central hidden service authorities for publishing and
  5104. fetching every hidden service descriptor. Implements proposal 114.
  5105. - Allow tunnelled directory connections to ask for an encrypted
  5106. "begin_dir" connection or an anonymized "uses a full Tor circuit"
  5107. connection independently. Now we can make anonymized begin_dir
  5108. connections for (e.g.) more secure hidden service posting and
  5109. fetching.
  5110. o Major bugfixes (crashes and assert failures):
  5111. - Stop imposing an arbitrary maximum on the number of file descriptors
  5112. used for busy servers. Bug reported by Olaf Selke; patch from
  5113. Sebastian Hahn.
  5114. - Avoid possible failures when generating a directory with routers
  5115. with over-long versions strings, or too many flags set.
  5116. - Fix a rare assert error when we're closing one of our threads:
  5117. use a mutex to protect the list of logs, so we never write to the
  5118. list as it's being freed. Fixes the very rare bug 575, which is
  5119. kind of the revenge of bug 222.
  5120. - Avoid segfault in the case where a badly behaved v2 versioning
  5121. directory sends a signed networkstatus with missing client-versions.
  5122. - When we hit an EOF on a log (probably because we're shutting down),
  5123. don't try to remove the log from the list: just mark it as
  5124. unusable. (Bulletproofs against bug 222.)
  5125. o Major bugfixes (code security fixes):
  5126. - Detect size overflow in zlib code. Reported by Justin Ferguson and
  5127. Dan Kaminsky.
  5128. - Rewrite directory tokenization code to never run off the end of
  5129. a string. Fixes bug 455. Patch from croup.
  5130. - Be more paranoid about overwriting sensitive memory on free(),
  5131. as a defensive programming tactic to ensure forward secrecy.
  5132. o Major bugfixes (anonymity fixes):
  5133. - Reject requests for reverse-dns lookup of names that are in
  5134. a private address space. Patch from lodger.
  5135. - Never report that we've used more bandwidth than we're willing to
  5136. relay: it leaks how much non-relay traffic we're using. Resolves
  5137. bug 516.
  5138. - As a client, do not believe any server that tells us that an
  5139. address maps to an internal address space.
  5140. - Warn about unsafe ControlPort configurations.
  5141. - Directory authorities now call routers Fast if their bandwidth is
  5142. at least 100KB/s, and consider their bandwidth adequate to be a
  5143. Guard if it is at least 250KB/s, no matter the medians. This fix
  5144. complements proposal 107.
  5145. - Directory authorities now never mark more than 2 servers per IP as
  5146. Valid and Running (or 5 on addresses shared by authorities).
  5147. Implements proposal 109, by Kevin Bauer and Damon McCoy.
  5148. - If we're a relay, avoid picking ourselves as an introduction point,
  5149. a rendezvous point, or as the final hop for internal circuits. Bug
  5150. reported by taranis and lodger.
  5151. - Exit relays that are used as a client can now reach themselves
  5152. using the .exit notation, rather than just launching an infinite
  5153. pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
  5154. - Fix a bug where, when we were choosing the 'end stream reason' to
  5155. put in our relay end cell that we send to the exit relay, Tor
  5156. clients on Windows were sometimes sending the wrong 'reason'. The
  5157. anonymity problem is that exit relays may be able to guess whether
  5158. the client is running Windows, thus helping partition the anonymity
  5159. set. Down the road we should stop sending reasons to exit relays,
  5160. or otherwise prevent future versions of this bug.
  5161. - Only update guard status (usable / not usable) once we have
  5162. enough directory information. This was causing us to discard all our
  5163. guards on startup if we hadn't been running for a few weeks. Fixes
  5164. bug 448.
  5165. - When our directory information has been expired for a while, stop
  5166. being willing to build circuits using it. Fixes bug 401.
  5167. o Major bugfixes (peace of mind for relay operators)
  5168. - Non-exit relays no longer answer "resolve" relay cells, so they
  5169. can't be induced to do arbitrary DNS requests. (Tor clients already
  5170. avoid using non-exit relays for resolve cells, but now servers
  5171. enforce this too.) Fixes bug 619. Patch from lodger.
  5172. - When we setconf ClientOnly to 1, close any current OR and Dir
  5173. listeners. Reported by mwenge.
  5174. o Major bugfixes (other):
  5175. - If we only ever used Tor for hidden service lookups or posts, we
  5176. would stop building circuits and start refusing connections after
  5177. 24 hours, since we falsely believed that Tor was dormant. Reported
  5178. by nwf.
  5179. - Add a new __HashedControlSessionPassword option for controllers
  5180. to use for one-off session password hashes that shouldn't get
  5181. saved to disk by SAVECONF --- Vidalia users were accumulating a
  5182. pile of HashedControlPassword lines in their torrc files, one for
  5183. each time they had restarted Tor and then clicked Save. Make Tor
  5184. automatically convert "HashedControlPassword" to this new option but
  5185. only when it's given on the command line. Partial fix for bug 586.
  5186. - Patch from "Andrew S. Lists" to catch when we contact a directory
  5187. mirror at IP address X and he says we look like we're coming from
  5188. IP address X. Otherwise this would screw up our address detection.
  5189. - Reject uploaded descriptors and extrainfo documents if they're
  5190. huge. Otherwise we'll cache them all over the network and it'll
  5191. clog everything up. Suggested by Aljosha Judmayer.
  5192. - When a hidden service was trying to establish an introduction point,
  5193. and Tor *did* manage to reuse one of the preemptively built
  5194. circuits, it didn't correctly remember which one it used,
  5195. so it asked for another one soon after, until there were no
  5196. more preemptive circuits, at which point it launched one from
  5197. scratch. Bugfix on 0.0.9.x.
  5198. o Rate limiting and load balancing improvements:
  5199. - When we add data to a write buffer in response to the data on that
  5200. write buffer getting low because of a flush, do not consider the
  5201. newly added data as a candidate for immediate flushing, but rather
  5202. make it wait until the next round of writing. Otherwise, we flush
  5203. and refill recursively, and a single greedy TLS connection can
  5204. eat all of our bandwidth.
  5205. - When counting the number of bytes written on a TLS connection,
  5206. look at the BIO actually used for writing to the network, not
  5207. at the BIO used (sometimes) to buffer data for the network.
  5208. Looking at different BIOs could result in write counts on the
  5209. order of ULONG_MAX. Fixes bug 614.
  5210. - If we change our MaxAdvertisedBandwidth and then reload torrc,
  5211. Tor won't realize it should publish a new relay descriptor. Fixes
  5212. bug 688, reported by mfr.
  5213. - Avoid using too little bandwidth when our clock skips a few seconds.
  5214. - Choose which bridge to use proportional to its advertised bandwidth,
  5215. rather than uniformly at random. This should speed up Tor for
  5216. bridge users. Also do this for people who set StrictEntryNodes.
  5217. o Bootstrapping faster and building circuits more intelligently:
  5218. - Fix bug 660 that was preventing us from knowing that we should
  5219. preemptively build circuits to handle expected directory requests.
  5220. - When we're checking if we have enough dir info for each relay
  5221. to begin establishing circuits, make sure that we actually have
  5222. the descriptor listed in the consensus, not just any descriptor.
  5223. - Correctly notify one-hop connections when a circuit build has
  5224. failed. Possible fix for bug 669. Found by lodger.
  5225. - Clients now hold circuitless TLS connections open for 1.5 times
  5226. MaxCircuitDirtiness (15 minutes), since it is likely that they'll
  5227. rebuild a new circuit over them within that timeframe. Previously,
  5228. they held them open only for KeepalivePeriod (5 minutes).
  5229. o Performance improvements (memory):
  5230. - Add OpenBSD malloc code from "phk" as an optional malloc
  5231. replacement on Linux: some glibc libraries do very poorly with
  5232. Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
  5233. ./configure to get the replacement malloc code.
  5234. - Switch our old ring buffer implementation for one more like that
  5235. used by free Unix kernels. The wasted space in a buffer with 1mb
  5236. of data will now be more like 8k than 1mb. The new implementation
  5237. also avoids realloc();realloc(); patterns that can contribute to
  5238. memory fragmentation.
  5239. - Change the way that Tor buffers data that it is waiting to write.
  5240. Instead of queueing data cells in an enormous ring buffer for each
  5241. client->OR or OR->OR connection, we now queue cells on a separate
  5242. queue for each circuit. This lets us use less slack memory, and
  5243. will eventually let us be smarter about prioritizing different kinds
  5244. of traffic.
  5245. - Reference-count and share copies of address policy entries; only 5%
  5246. of them were actually distinct.
  5247. - Tune parameters for cell pool allocation to minimize amount of
  5248. RAM overhead used.
  5249. - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
  5250. for every single inactive connection_t. Free items from the
  5251. 4k/16k-buffer free lists when they haven't been used for a while.
  5252. - Make memory debugging information describe more about history
  5253. of cell allocation, so we can help reduce our memory use.
  5254. - Be even more aggressive about releasing RAM from small
  5255. empty buffers. Thanks to our free-list code, this shouldn't be too
  5256. performance-intensive.
  5257. - Log malloc statistics from mallinfo() on platforms where it exists.
  5258. - Use memory pools to allocate cells with better speed and memory
  5259. efficiency, especially on platforms where malloc() is inefficient.
  5260. - Add a --with-tcmalloc option to the configure script to link
  5261. against tcmalloc (if present). Does not yet search for non-system
  5262. include paths.
  5263. o Performance improvements (socket management):
  5264. - Count the number of open sockets separately from the number of
  5265. active connection_t objects. This will let us avoid underusing
  5266. our allocated connection limit.
  5267. - We no longer use socket pairs to link an edge connection to an
  5268. anonymous directory connection or a DirPort test connection.
  5269. Instead, we track the link internally and transfer the data
  5270. in-process. This saves two sockets per "linked" connection (at the
  5271. client and at the server), and avoids the nasty Windows socketpair()
  5272. workaround.
  5273. - We were leaking a file descriptor if Tor started with a zero-length
  5274. cached-descriptors file. Patch by "freddy77".
  5275. o Performance improvements (CPU use):
  5276. - Never walk through the list of logs if we know that no log target
  5277. is interested in a given message.
  5278. - Call routerlist_remove_old_routers() much less often. This should
  5279. speed startup, especially on directory caches.
  5280. - Base64 decoding was actually showing up on our profile when parsing
  5281. the initial descriptor file; switch to an in-process all-at-once
  5282. implementation that's about 3.5x times faster than calling out to
  5283. OpenSSL.
  5284. - Use a slightly simpler string hashing algorithm (copying Python's
  5285. instead of Java's) and optimize our digest hashing algorithm to take
  5286. advantage of 64-bit platforms and to remove some possibly-costly
  5287. voodoo.
  5288. - When implementing AES counter mode, update only the portions of the
  5289. counter buffer that need to change, and don't keep separate
  5290. network-order and host-order counters on big-endian hosts (where
  5291. they are the same).
  5292. - Add an in-place version of aes_crypt() so that we can avoid doing a
  5293. needless memcpy() call on each cell payload.
  5294. - Use Critical Sections rather than Mutexes for synchronizing threads
  5295. on win32; Mutexes are heavier-weight, and designed for synchronizing
  5296. between processes.
  5297. o Performance improvements (bandwidth use):
  5298. - Don't try to launch new descriptor downloads quite so often when we
  5299. already have enough directory information to build circuits.
  5300. - Version 1 directories are no longer generated in full. Instead,
  5301. authorities generate and serve "stub" v1 directories that list
  5302. no servers. This will stop Tor versions 0.1.0.x and earlier from
  5303. working, but (for security reasons) nobody should be running those
  5304. versions anyway.
  5305. - Avoid going directly to the directory authorities even if you're a
  5306. relay, if you haven't found yourself reachable yet or if you've
  5307. decided not to advertise your dirport yet. Addresses bug 556.
  5308. - If we've gone 12 hours since our last bandwidth check, and we
  5309. estimate we have less than 50KB bandwidth capacity but we could
  5310. handle more, do another bandwidth test.
  5311. - Support "If-Modified-Since" when answering HTTP requests for
  5312. directories, running-routers documents, and v2 and v3 networkstatus
  5313. documents. (There's no need to support it for router descriptors,
  5314. since those are downloaded by descriptor digest.)
  5315. - Stop fetching directory info so aggressively if your DirPort is
  5316. on but your ORPort is off; stop fetching v2 dir info entirely.
  5317. You can override these choices with the new FetchDirInfoEarly
  5318. config option.
  5319. o Changed config option behavior (features):
  5320. - Configuration files now accept C-style strings as values. This
  5321. helps encode characters not allowed in the current configuration
  5322. file format, such as newline or #. Addresses bug 557.
  5323. - Add hidden services and DNSPorts to the list of things that make
  5324. Tor accept that it has running ports. Change starting Tor with no
  5325. ports from a fatal error to a warning; we might change it back if
  5326. this turns out to confuse anybody. Fixes bug 579.
  5327. - Make PublishServerDescriptor default to 1, so the default doesn't
  5328. have to change as we invent new directory protocol versions.
  5329. - Allow people to say PreferTunnelledDirConns rather than
  5330. PreferTunneledDirConns, for those alternate-spellers out there.
  5331. - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
  5332. accommodate the growing number of servers that use the default
  5333. and are reaching it.
  5334. - Make it possible to enable HashedControlPassword and
  5335. CookieAuthentication at the same time.
  5336. - When a TrackHostExits-chosen exit fails too many times in a row,
  5337. stop using it. Fixes bug 437.
  5338. o Changed config option behavior (bugfixes):
  5339. - Do not read the configuration file when we've only been told to
  5340. generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
  5341. based on patch from Sebastian Hahn.
  5342. - Actually validate the options passed to AuthDirReject,
  5343. AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
  5344. - Make "ClientOnly 1" config option disable directory ports too.
  5345. - Don't stop fetching descriptors when FetchUselessDescriptors is
  5346. set, even if we stop asking for circuits. Bug reported by tup
  5347. and ioerror.
  5348. - Servers used to decline to publish their DirPort if their
  5349. BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
  5350. they look only at BandwidthRate and RelayBandwidthRate.
  5351. - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
  5352. minus 1 byte: the actual maximum declared bandwidth.
  5353. - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
  5354. - Make the NodeFamilies config option work. (Reported by
  5355. lodger -- it has never actually worked, even though we added it
  5356. in Oct 2004.)
  5357. - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
  5358. now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
  5359. o New config options:
  5360. - New configuration options AuthDirMaxServersPerAddr and
  5361. AuthDirMaxServersperAuthAddr to override default maximum number
  5362. of servers allowed on a single IP address. This is important for
  5363. running a test network on a single host.
  5364. - Three new config options (AlternateDirAuthority,
  5365. AlternateBridgeAuthority, and AlternateHSAuthority) that let the
  5366. user selectively replace the default directory authorities by type,
  5367. rather than the all-or-nothing replacement that DirServer offers.
  5368. - New config options AuthDirBadDir and AuthDirListBadDirs for
  5369. authorities to mark certain relays as "bad directories" in the
  5370. networkstatus documents. Also supports the "!baddir" directive in
  5371. the approved-routers file.
  5372. - New config option V2AuthoritativeDirectory that all v2 directory
  5373. authorities must set. This lets v3 authorities choose not to serve
  5374. v2 directory information.
  5375. o Minor features (other):
  5376. - When we're not serving v2 directory information, there is no reason
  5377. to actually keep any around. Remove the obsolete files and directory
  5378. on startup if they are very old and we aren't going to serve them.
  5379. - When we negotiate a v2 link-layer connection (not yet implemented),
  5380. accept RELAY_EARLY cells and turn them into RELAY cells if we've
  5381. negotiated a v1 connection for their next step. Initial steps for
  5382. proposal 110.
  5383. - When we have no consensus, check FallbackNetworkstatusFile (defaults
  5384. to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
  5385. we can start out knowing some directory caches. We don't ship with
  5386. a fallback consensus by default though, because it was making
  5387. bootstrapping take too long while we tried many down relays.
  5388. - Authorities send back an X-Descriptor-Not-New header in response to
  5389. an accepted-but-discarded descriptor upload. Partially implements
  5390. fix for bug 535.
  5391. - If we find a cached-routers file that's been sitting around for more
  5392. than 28 days unmodified, then most likely it's a leftover from
  5393. when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
  5394. routers anyway.
  5395. - When we (as a cache) download a descriptor because it was listed
  5396. in a consensus, remember when the consensus was supposed to expire,
  5397. and don't expire the descriptor until then.
  5398. - Optionally (if built with -DEXPORTMALLINFO) export the output
  5399. of mallinfo via http, as tor/mallinfo.txt. Only accessible
  5400. from localhost.
  5401. - Tag every guard node in our state file with the version that
  5402. we believe added it, or with our own version if we add it. This way,
  5403. if a user temporarily runs an old version of Tor and then switches
  5404. back to a new one, she doesn't automatically lose her guards.
  5405. - When somebody requests a list of statuses or servers, and we have
  5406. none of those, return a 404 rather than an empty 200.
  5407. - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
  5408. from croup.)
  5409. - Add an HSAuthorityRecordStats option that hidden service authorities
  5410. can use to track statistics of overall hidden service usage without
  5411. logging information that would be as useful to an attacker.
  5412. - Allow multiple HiddenServicePort directives with the same virtual
  5413. port; when they occur, the user is sent round-robin to one
  5414. of the target ports chosen at random. Partially fixes bug 393 by
  5415. adding limited ad-hoc round-robining.
  5416. - Revamp file-writing logic so we don't need to have the entire
  5417. contents of a file in memory at once before we write to disk. Tor,
  5418. meet stdio.
  5419. o Minor bugfixes (other):
  5420. - Alter the code that tries to recover from unhandled write
  5421. errors, to not try to flush onto a socket that's given us
  5422. unhandled errors.
  5423. - Directory mirrors no longer include a guess at the client's IP
  5424. address if the connection appears to be coming from the same /24
  5425. network; it was producing too many wrong guesses.
  5426. - If we're trying to flush the last bytes on a connection (for
  5427. example, when answering a directory request), reset the
  5428. time-to-give-up timeout every time we manage to write something
  5429. on the socket.
  5430. - Reject router descriptors with out-of-range bandwidthcapacity or
  5431. bandwidthburst values.
  5432. - If we can't expand our list of entry guards (e.g. because we're
  5433. using bridges or we have StrictEntryNodes set), don't mark relays
  5434. down when they fail a directory request. Otherwise we're too quick
  5435. to mark all our entry points down.
  5436. - Authorities no longer send back "400 you're unreachable please fix
  5437. it" errors to Tor servers that aren't online all the time. We're
  5438. supposed to tolerate these servers now.
  5439. - Let directory authorities startup even when they can't generate
  5440. a descriptor immediately, e.g. because they don't know their
  5441. address.
  5442. - Correctly enforce that elements of directory objects do not appear
  5443. more often than they are allowed to appear.
  5444. - Stop allowing hibernating servers to be "stable" or "fast".
  5445. - On Windows, we were preventing other processes from reading
  5446. cached-routers while Tor was running. (Reported by janbar)
  5447. - Check return values from pthread_mutex functions.
  5448. - When opening /dev/null in finish_daemonize(), do not pass the
  5449. O_CREAT flag. Fortify was complaining, and correctly so. Fixes
  5450. bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
  5451. o Controller features:
  5452. - The GETCONF command now escapes and quotes configuration values
  5453. that don't otherwise fit into the torrc file.
  5454. - The SETCONF command now handles quoted values correctly.
  5455. - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
  5456. ask about source, timestamp of arrival, purpose, etc. We need
  5457. something like this to help Vidalia not do GeoIP lookups on bridge
  5458. addresses.
  5459. - Allow multiple HashedControlPassword config lines, to support
  5460. multiple controller passwords.
  5461. - Accept LF instead of CRLF on controller, since some software has a
  5462. hard time generating real Internet newlines.
  5463. - Add GETINFO values for the server status events
  5464. "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
  5465. Robert Hogan.
  5466. - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
  5467. GETINFO for Torstat to use until it can switch to using extrainfos.
  5468. - New config option CookieAuthFile to choose a new location for the
  5469. cookie authentication file, and config option
  5470. CookieAuthFileGroupReadable to make it group-readable.
  5471. - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
  5472. match requests to applications. Patch from Robert Hogan.
  5473. - Add a RESOLVE command to launch hostname lookups. Original patch
  5474. from Robert Hogan.
  5475. - Add GETINFO status/enough-dir-info to let controllers tell whether
  5476. Tor has downloaded sufficient directory information. Patch from Tup.
  5477. - You can now use the ControlSocket option to tell Tor to listen for
  5478. controller connections on Unix domain sockets on systems that
  5479. support them. Patch from Peter Palfrader.
  5480. - New "GETINFO address-mappings/*" command to get address mappings
  5481. with expiry information. "addr-mappings/*" is now deprecated.
  5482. Patch from Tup.
  5483. - Add a new config option __DisablePredictedCircuits designed for
  5484. use by the controller, when we don't want Tor to build any circuits
  5485. preemptively.
  5486. - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
  5487. so we can exit from the middle of the circuit.
  5488. - Implement "getinfo status/circuit-established".
  5489. - Implement "getinfo status/version/..." so a controller can tell
  5490. whether the current version is recommended, and whether any versions
  5491. are good, and how many authorities agree. Patch from "shibz".
  5492. - Controllers should now specify cache=no or cache=yes when using
  5493. the +POSTDESCRIPTOR command.
  5494. - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
  5495. Robert Hogan. Fixes the first part of bug 681.
  5496. - When reporting clock skew, and we know that the clock is _at least
  5497. as skewed_ as some value, but we don't know the actual value,
  5498. report the value as a "minimum skew."
  5499. o Controller bugfixes:
  5500. - Generate "STATUS_SERVER" events rather than misspelled
  5501. "STATUS_SEVER" events. Caught by mwenge.
  5502. - Reject controller commands over 1MB in length, so rogue
  5503. processes can't run us out of memory.
  5504. - Change the behavior of "getinfo status/good-server-descriptor"
  5505. so it doesn't return failure when any authority disappears.
  5506. - Send NAMESERVER_STATUS messages for a single failed nameserver
  5507. correctly.
  5508. - When the DANGEROUS_VERSION controller status event told us we're
  5509. running an obsolete version, it used the string "OLD" to describe
  5510. it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
  5511. "OBSOLETE" in both cases.
  5512. - Respond to INT and TERM SIGNAL commands before we execute the
  5513. signal, in case the signal shuts us down. We had a patch in
  5514. 0.1.2.1-alpha that tried to do this by queueing the response on
  5515. the connection's buffer before shutting down, but that really
  5516. isn't the same thing at all. Bug located by Matt Edman.
  5517. - Provide DNS expiry times in GMT, not in local time. For backward
  5518. compatibility, ADDRMAP events only provide GMT expiry in an extended
  5519. field. "GETINFO address-mappings" always does the right thing.
  5520. - Use CRLF line endings properly in NS events.
  5521. - Make 'getinfo fingerprint' return a 551 error if we're not a
  5522. server, so we match what the control spec claims we do. Reported
  5523. by daejees.
  5524. - Fix a typo in an error message when extendcircuit fails that
  5525. caused us to not follow the \r\n-based delimiter protocol. Reported
  5526. by daejees.
  5527. - When tunneling an encrypted directory connection, and its first
  5528. circuit fails, do not leave it unattached and ask the controller
  5529. to deal. Fixes the second part of bug 681.
  5530. - Treat some 403 responses from directory servers as INFO rather than
  5531. WARN-severity events.
  5532. o Portability / building / compiling:
  5533. - When building with --enable-gcc-warnings, check for whether Apple's
  5534. warning "-Wshorten-64-to-32" is available.
  5535. - Support compilation to target iPhone; patch from cjacker huang.
  5536. To build for iPhone, pass the --enable-iphone option to configure.
  5537. - Port Tor to build and run correctly on Windows CE systems, using
  5538. the wcecompat library. Contributed by Valerio Lupi.
  5539. - Detect non-ASCII platforms (if any still exist) and refuse to
  5540. build there: some of our code assumes that 'A' is 65 and so on.
  5541. - Clear up some MIPSPro compiler warnings.
  5542. - Make autoconf search for libevent, openssl, and zlib consistently.
  5543. - Update deprecated macros in configure.in.
  5544. - When warning about missing headers, tell the user to let us
  5545. know if the compile succeeds anyway, so we can downgrade the
  5546. warning.
  5547. - Include the current subversion revision as part of the version
  5548. string: either fetch it directly if we're in an SVN checkout, do
  5549. some magic to guess it if we're in an SVK checkout, or use
  5550. the last-detected version if we're building from a .tar.gz.
  5551. Use this version consistently in log messages.
  5552. - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
  5553. - Read resolv.conf files correctly on platforms where read() returns
  5554. partial results on small file reads.
  5555. - Build without verbose warnings even on gcc 4.2 and 4.3.
  5556. - On Windows, correctly detect errors when listing the contents of
  5557. a directory. Fix from lodger.
  5558. - Run 'make test' as part of 'make dist', so we stop releasing so
  5559. many development snapshots that fail their unit tests.
  5560. - Add support to detect Libevent versions in the 1.4.x series
  5561. on mingw.
  5562. - Add command-line arguments to unit-test executable so that we can
  5563. invoke any chosen test from the command line rather than having
  5564. to run the whole test suite at once; and so that we can turn on
  5565. logging for the unit tests.
  5566. - Do not automatically run configure from autogen.sh. This
  5567. non-standard behavior tended to annoy people who have built other
  5568. programs.
  5569. - Fix a macro/CPP interaction that was confusing some compilers:
  5570. some GCCs don't like #if/#endif pairs inside macro arguments.
  5571. Fixes bug 707.
  5572. - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
  5573. Fixes bug 704; fix from Steven Murdoch.
  5574. - Correctly detect transparent proxy support on Linux hosts that
  5575. require in.h to be included before netfilter_ipv4.h. Patch
  5576. from coderman.
  5577. o Logging improvements:
  5578. - When we haven't had any application requests lately, don't bother
  5579. logging that we have expired a bunch of descriptors.
  5580. - When attempting to open a logfile fails, tell us why.
  5581. - Only log guard node status when guard node status has changed.
  5582. - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
  5583. make "INFO" 75% less verbose.
  5584. - When SafeLogging is disabled, log addresses along with all TLS
  5585. errors.
  5586. - Report TLS "zero return" case as a "clean close" and "IO error"
  5587. as a "close". Stop calling closes "unexpected closes": existing
  5588. Tors don't use SSL_close(), so having a connection close without
  5589. the TLS shutdown handshake is hardly unexpected.
  5590. - When we receive a consensus from the future, warn about skew.
  5591. - Make "not enough dir info yet" warnings describe *why* Tor feels
  5592. it doesn't have enough directory info yet.
  5593. - On the USR1 signal, when dmalloc is in use, log the top 10 memory
  5594. consumers. (We already do this on HUP.)
  5595. - Give more descriptive well-formedness errors for out-of-range
  5596. hidden service descriptor/protocol versions.
  5597. - Stop recommending that every server operator send mail to tor-ops.
  5598. Resolves bug 597. Bugfix on 0.1.2.x.
  5599. - Improve skew reporting: try to give the user a better log message
  5600. about how skewed they are, and how much this matters.
  5601. - New --quiet command-line option to suppress the default console log.
  5602. Good in combination with --hash-password.
  5603. - Don't complain that "your server has not managed to confirm that its
  5604. ports are reachable" if we haven't been able to build any circuits
  5605. yet.
  5606. - Detect the reason for failing to mmap a descriptor file we just
  5607. wrote, and give a more useful log message. Fixes bug 533.
  5608. - Always prepend "Bug: " to any log message about a bug.
  5609. - When dumping memory usage, list bytes used in buffer memory
  5610. free-lists.
  5611. - When running with dmalloc, dump more stats on hup and on exit.
  5612. - Put a platform string (e.g. "Linux i686") in the startup log
  5613. message, so when people paste just their logs, we know if it's
  5614. OpenBSD or Windows or what.
  5615. - When logging memory usage, break down memory used in buffers by
  5616. buffer type.
  5617. - When we are reporting the DirServer line we just parsed, we were
  5618. logging the second stanza of the key fingerprint, not the first.
  5619. - Even though Windows is equally happy with / and \ as path separators,
  5620. try to use \ consistently on Windows and / consistently on Unix: it
  5621. makes the log messages nicer.
  5622. - On OSX, stop warning the user that kqueue support in libevent is
  5623. "experimental", since it seems to have worked fine for ages.
  5624. o Contributed scripts and tools:
  5625. - Update linux-tor-prio.sh script to allow QoS based on the uid of
  5626. the Tor process. Patch from Marco Bonetti with tweaks from Mike
  5627. Perry.
  5628. - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
  5629. Unix users an easy way to script their Tor process (e.g. by
  5630. adjusting bandwidth based on the time of the day).
  5631. - In the exitlist script, only consider the most recently published
  5632. server descriptor for each server. Also, when the user requests
  5633. a list of servers that _reject_ connections to a given address,
  5634. explicitly exclude the IPs that also have servers that accept
  5635. connections to that address. Resolves bug 405.
  5636. - Include a new contrib/tor-exit-notice.html file that exit relay
  5637. operators can put on their website to help reduce abuse queries.
  5638. o Newly deprecated features:
  5639. - The status/version/num-versioning and status/version/num-concurring
  5640. GETINFO controller options are no longer useful in the v3 directory
  5641. protocol: treat them as deprecated, and warn when they're used.
  5642. - The RedirectExits config option is now deprecated.
  5643. o Removed features:
  5644. - Drop the old code to choke directory connections when the
  5645. corresponding OR connections got full: thanks to the cell queue
  5646. feature, OR conns don't get full any more.
  5647. - Remove the old "dns worker" server DNS code: it hasn't been default
  5648. since 0.1.2.2-alpha, and all the servers are using the new
  5649. eventdns code.
  5650. - Remove the code to generate the oldest (v1) directory format.
  5651. - Remove support for the old bw_accounting file: we've been storing
  5652. bandwidth accounting information in the state file since
  5653. 0.1.2.5-alpha. This may result in bandwidth accounting errors
  5654. if you try to upgrade from 0.1.1.x or earlier, or if you try to
  5655. downgrade to 0.1.1.x or earlier.
  5656. - Drop support for OpenSSL version 0.9.6. Just about nobody was using
  5657. it, it had no AES, and it hasn't seen any security patches since
  5658. 2004.
  5659. - Stop overloading the circuit_t.onionskin field for both "onionskin
  5660. from a CREATE cell that we are waiting for a cpuworker to be
  5661. assigned" and "onionskin from an EXTEND cell that we are going to
  5662. send to an OR as soon as we are connected". Might help with bug 600.
  5663. - Remove the tor_strpartition() function: its logic was confused,
  5664. and it was only used for one thing that could be implemented far
  5665. more easily.
  5666. - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
  5667. and TorControl.py, as they use the old v0 controller protocol,
  5668. and are obsoleted by TorFlow anyway.
  5669. - Drop support for v1 rendezvous descriptors, since we never used
  5670. them anyway, and the code has probably rotted by now. Based on
  5671. patch from Karsten Loesing.
  5672. - Stop allowing address masks that do not correspond to bit prefixes.
  5673. We have warned about these for a really long time; now it's time
  5674. to reject them. (Patch from croup.)
  5675. - Remove an optimization in the AES counter-mode code that assumed
  5676. that the counter never exceeded 2^68. When the counter can be set
  5677. arbitrarily as an IV (as it is by Karsten's new hidden services
  5678. code), this assumption no longer holds.
  5679. - Disable the SETROUTERPURPOSE controller command: it is now
  5680. obsolete.
  5681. Changes in version 0.1.2.19 - 2008-01-17
  5682. Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
  5683. exit policy a little bit more conservative so it's safer to run an
  5684. exit relay on a home system, and fixes a variety of smaller issues.
  5685. o Security fixes:
  5686. - Exit policies now reject connections that are addressed to a
  5687. relay's public (external) IP address too, unless
  5688. ExitPolicyRejectPrivate is turned off. We do this because too
  5689. many relays are running nearby to services that trust them based
  5690. on network address.
  5691. o Major bugfixes:
  5692. - When the clock jumps forward a lot, do not allow the bandwidth
  5693. buckets to become negative. Fixes bug 544.
  5694. - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
  5695. on every successful resolve. Reported by Mike Perry.
  5696. - Purge old entries from the "rephist" database and the hidden
  5697. service descriptor database even when DirPort is zero.
  5698. - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
  5699. requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
  5700. crashing or mis-answering these requests.
  5701. - When we decide to send a 503 response to a request for servers, do
  5702. not then also send the server descriptors: this defeats the whole
  5703. purpose. Fixes bug 539.
  5704. o Minor bugfixes:
  5705. - Changing the ExitPolicyRejectPrivate setting should cause us to
  5706. rebuild our server descriptor.
  5707. - Fix handling of hex nicknames when answering controller requests for
  5708. networkstatus by name, or when deciding whether to warn about
  5709. unknown routers in a config option. (Patch from mwenge.)
  5710. - Fix a couple of hard-to-trigger autoconf problems that could result
  5711. in really weird results on platforms whose sys/types.h files define
  5712. nonstandard integer types.
  5713. - Don't try to create the datadir when running --verify-config or
  5714. --hash-password. Resolves bug 540.
  5715. - If we were having problems getting a particular descriptor from the
  5716. directory caches, and then we learned about a new descriptor for
  5717. that router, we weren't resetting our failure count. Reported
  5718. by lodger.
  5719. - Although we fixed bug 539 (where servers would send HTTP status 503
  5720. responses _and_ send a body too), there are still servers out there
  5721. that haven't upgraded. Therefore, make clients parse such bodies
  5722. when they receive them.
  5723. - Run correctly on systems where rlim_t is larger than unsigned long.
  5724. This includes some 64-bit systems.
  5725. - Run correctly on platforms (like some versions of OS X 10.5) where
  5726. the real limit for number of open files is OPEN_FILES, not rlim_max
  5727. from getrlimit(RLIMIT_NOFILES).
  5728. - Avoid a spurious free on base64 failure.
  5729. - Avoid segfaults on certain complex invocations of
  5730. router_get_by_hexdigest().
  5731. - Fix rare bug on REDIRECTSTREAM control command when called with no
  5732. port set: it could erroneously report an error when none had
  5733. happened.
  5734. Changes in version 0.1.2.18 - 2007-10-28
  5735. Tor 0.1.2.18 fixes many problems including crash bugs, problems with
  5736. hidden service introduction that were causing huge delays, and a big
  5737. bug that was causing some servers to disappear from the network status
  5738. lists for a few hours each day.
  5739. o Major bugfixes (crashes):
  5740. - If a connection is shut down abruptly because of something that
  5741. happened inside connection_flushed_some(), do not call
  5742. connection_finished_flushing(). Should fix bug 451:
  5743. "connection_stop_writing: Assertion conn->write_event failed"
  5744. Bugfix on 0.1.2.7-alpha.
  5745. - Fix possible segfaults in functions called from
  5746. rend_process_relay_cell().
  5747. o Major bugfixes (hidden services):
  5748. - Hidden services were choosing introduction points uniquely by
  5749. hexdigest, but when constructing the hidden service descriptor
  5750. they merely wrote the (potentially ambiguous) nickname.
  5751. - Clients now use the v2 intro format for hidden service
  5752. connections: they specify their chosen rendezvous point by identity
  5753. digest rather than by (potentially ambiguous) nickname. These
  5754. changes could speed up hidden service connections dramatically.
  5755. o Major bugfixes (other):
  5756. - Stop publishing a new server descriptor just because we get a
  5757. HUP signal. This led (in a roundabout way) to some servers getting
  5758. dropped from the networkstatus lists for a few hours each day.
  5759. - When looking for a circuit to cannibalize, consider family as well
  5760. as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
  5761. circuit cannibalization).
  5762. - When a router wasn't listed in a new networkstatus, we were leaving
  5763. the flags for that router alone -- meaning it remained Named,
  5764. Running, etc -- even though absence from the networkstatus means
  5765. that it shouldn't be considered to exist at all anymore. Now we
  5766. clear all the flags for routers that fall out of the networkstatus
  5767. consensus. Fixes bug 529.
  5768. o Minor bugfixes:
  5769. - Don't try to access (or alter) the state file when running
  5770. --list-fingerprint or --verify-config or --hash-password. Resolves
  5771. bug 499.
  5772. - When generating information telling us how to extend to a given
  5773. router, do not try to include the nickname if it is
  5774. absent. Resolves bug 467.
  5775. - Fix a user-triggerable segfault in expand_filename(). (There isn't
  5776. a way to trigger this remotely.)
  5777. - When sending a status event to the controller telling it that an
  5778. OR address is reachable, set the port correctly. (Previously we
  5779. were reporting the dir port.)
  5780. - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
  5781. command. Bugfix on 0.1.2.17.
  5782. - When loading bandwidth history, do not believe any information in
  5783. the future. Fixes bug 434.
  5784. - When loading entry guard information, do not believe any information
  5785. in the future.
  5786. - When we have our clock set far in the future and generate an
  5787. onion key, then re-set our clock to be correct, we should not stop
  5788. the onion key from getting rotated.
  5789. - On some platforms, accept() can return a broken address. Detect
  5790. this more quietly, and deal accordingly. Fixes bug 483.
  5791. - It's not actually an error to find a non-pending entry in the DNS
  5792. cache when canceling a pending resolve. Don't log unless stuff
  5793. is fishy. Resolves bug 463.
  5794. - Don't reset trusted dir server list when we set a configuration
  5795. option. Patch from Robert Hogan.
  5796. Changes in version 0.1.2.17 - 2007-08-30
  5797. Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
  5798. X bundles. Vidalia 0.0.14 makes authentication required for the
  5799. ControlPort in the default configuration, which addresses important
  5800. security risks. Everybody who uses Vidalia (or another controller)
  5801. should upgrade.
  5802. In addition, this Tor update fixes major load balancing problems with
  5803. path selection, which should speed things up a lot once many people
  5804. have upgraded.
  5805. o Major bugfixes (security):
  5806. - We removed support for the old (v0) control protocol. It has been
  5807. deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
  5808. become more of a headache than it's worth.
  5809. o Major bugfixes (load balancing):
  5810. - When choosing nodes for non-guard positions, weight guards
  5811. proportionally less, since they already have enough load. Patch
  5812. from Mike Perry.
  5813. - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
  5814. will allow fast Tor servers to get more attention.
  5815. - When we're upgrading from an old Tor version, forget our current
  5816. guards and pick new ones according to the new weightings. These
  5817. three load balancing patches could raise effective network capacity
  5818. by a factor of four. Thanks to Mike Perry for measurements.
  5819. o Major bugfixes (stream expiration):
  5820. - Expire not-yet-successful application streams in all cases if
  5821. they've been around longer than SocksTimeout. Right now there are
  5822. some cases where the stream will live forever, demanding a new
  5823. circuit every 15 seconds. Fixes bug 454; reported by lodger.
  5824. o Minor features (controller):
  5825. - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
  5826. is valid before any authentication has been received. It tells
  5827. a controller what kind of authentication is expected, and what
  5828. protocol is spoken. Implements proposal 119.
  5829. o Minor bugfixes (performance):
  5830. - Save on most routerlist_assert_ok() calls in routerlist.c, thus
  5831. greatly speeding up loading cached-routers from disk on startup.
  5832. - Disable sentinel-based debugging for buffer code: we squashed all
  5833. the bugs that this was supposed to detect a long time ago, and now
  5834. its only effect is to change our buffer sizes from nice powers of
  5835. two (which platform mallocs tend to like) to values slightly over
  5836. powers of two (which make some platform mallocs sad).
  5837. o Minor bugfixes (misc):
  5838. - If exit bandwidth ever exceeds one third of total bandwidth, then
  5839. use the correct formula to weight exit nodes when choosing paths.
  5840. Based on patch from Mike Perry.
  5841. - Choose perfectly fairly among routers when choosing by bandwidth and
  5842. weighting by fraction of bandwidth provided by exits. Previously, we
  5843. would choose with only approximate fairness, and correct ourselves
  5844. if we ran off the end of the list.
  5845. - If we require CookieAuthentication but we fail to write the
  5846. cookie file, we would warn but not exit, and end up in a state
  5847. where no controller could authenticate. Now we exit.
  5848. - If we require CookieAuthentication, stop generating a new cookie
  5849. every time we change any piece of our config.
  5850. - Refuse to start with certain directory authority keys, and
  5851. encourage people using them to stop.
  5852. - Terminate multi-line control events properly. Original patch
  5853. from tup.
  5854. - Fix a minor memory leak when we fail to find enough suitable
  5855. servers to choose a circuit.
  5856. - Stop leaking part of the descriptor when we run into a particularly
  5857. unparseable piece of it.
  5858. Changes in version 0.1.2.16 - 2007-08-01
  5859. Tor 0.1.2.16 fixes a critical security vulnerability that allows a
  5860. remote attacker in certain situations to rewrite the user's torrc
  5861. configuration file. This can completely compromise anonymity of users
  5862. in most configurations, including those running the Vidalia bundles,
  5863. TorK, etc. Or worse.
  5864. o Major security fixes:
  5865. - Close immediately after missing authentication on control port;
  5866. do not allow multiple authentication attempts.
  5867. Changes in version 0.1.2.15 - 2007-07-17
  5868. Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
  5869. problems, fixes compilation on BSD, and fixes a variety of other
  5870. bugs. Everybody should upgrade.
  5871. o Major bugfixes (compilation):
  5872. - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
  5873. o Major bugfixes (crashes):
  5874. - Try even harder not to dereference the first character after
  5875. an mmap(). Reported by lodger.
  5876. - Fix a crash bug in directory authorities when we re-number the
  5877. routerlist while inserting a new router.
  5878. - When the cached-routers file is an even multiple of the page size,
  5879. don't run off the end and crash. (Fixes bug 455; based on idea
  5880. from croup.)
  5881. - Fix eventdns.c behavior on Solaris: It is critical to include
  5882. orconfig.h _before_ sys/types.h, so that we can get the expected
  5883. definition of _FILE_OFFSET_BITS.
  5884. o Major bugfixes (security):
  5885. - Fix a possible buffer overrun when using BSD natd support. Bug
  5886. found by croup.
  5887. - When sending destroy cells from a circuit's origin, don't include
  5888. the reason for tearing down the circuit. The spec says we didn't,
  5889. and now we actually don't. Reported by lodger.
  5890. - Keep streamids from different exits on a circuit separate. This
  5891. bug may have allowed other routers on a given circuit to inject
  5892. cells into streams. Reported by lodger; fixes bug 446.
  5893. - If there's a never-before-connected-to guard node in our list,
  5894. never choose any guards past it. This way we don't expand our
  5895. guard list unless we need to.
  5896. o Minor bugfixes (guard nodes):
  5897. - Weight guard selection by bandwidth, so that low-bandwidth nodes
  5898. don't get overused as guards.
  5899. o Minor bugfixes (directory):
  5900. - Correctly count the number of authorities that recommend each
  5901. version. Previously, we were under-counting by 1.
  5902. - Fix a potential crash bug when we load many server descriptors at
  5903. once and some of them make others of them obsolete. Fixes bug 458.
  5904. o Minor bugfixes (hidden services):
  5905. - Stop tearing down the whole circuit when the user asks for a
  5906. connection to a port that the hidden service didn't configure.
  5907. Resolves bug 444.
  5908. o Minor bugfixes (misc):
  5909. - On Windows, we were preventing other processes from reading
  5910. cached-routers while Tor was running. Reported by janbar.
  5911. - Fix a possible (but very unlikely) bug in picking routers by
  5912. bandwidth. Add a log message to confirm that it is in fact
  5913. unlikely. Patch from lodger.
  5914. - Backport a couple of memory leak fixes.
  5915. - Backport miscellaneous cosmetic bugfixes.
  5916. Changes in version 0.1.2.14 - 2007-05-25
  5917. Tor 0.1.2.14 changes the addresses of two directory authorities (this
  5918. change especially affects those who serve or use hidden services),
  5919. and fixes several other crash- and security-related bugs.
  5920. o Directory authority changes:
  5921. - Two directory authorities (moria1 and moria2) just moved to new
  5922. IP addresses. This change will particularly affect those who serve
  5923. or use hidden services.
  5924. o Major bugfixes (crashes):
  5925. - If a directory server runs out of space in the connection table
  5926. as it's processing a begin_dir request, it will free the exit stream
  5927. but leave it attached to the circuit, leading to unpredictable
  5928. behavior. (Reported by seeess, fixes bug 425.)
  5929. - Fix a bug in dirserv_remove_invalid() that would cause authorities
  5930. to corrupt memory under some really unlikely scenarios.
  5931. - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
  5932. - Avoid segfaults when reading from mmaped descriptor file. (Reported
  5933. by lodger.)
  5934. o Major bugfixes (security):
  5935. - When choosing an entry guard for a circuit, avoid using guards
  5936. that are in the same family as the chosen exit -- not just guards
  5937. that are exactly the chosen exit. (Reported by lodger.)
  5938. o Major bugfixes (resource management):
  5939. - If a directory authority is down, skip it when deciding where to get
  5940. networkstatus objects or descriptors. Otherwise we keep asking
  5941. every 10 seconds forever. Fixes bug 384.
  5942. - Count it as a failure if we fetch a valid network-status but we
  5943. don't want to keep it. Otherwise we'll keep fetching it and keep
  5944. not wanting to keep it. Fixes part of bug 422.
  5945. - If all of our dirservers have given us bad or no networkstatuses
  5946. lately, then stop hammering them once per minute even when we
  5947. think they're failed. Fixes another part of bug 422.
  5948. o Minor bugfixes:
  5949. - Actually set the purpose correctly for descriptors inserted with
  5950. purpose=controller.
  5951. - When we have k non-v2 authorities in our DirServer config,
  5952. we ignored the last k authorities in the list when updating our
  5953. network-statuses.
  5954. - Correctly back-off from requesting router descriptors that we are
  5955. having a hard time downloading.
  5956. - Read resolv.conf files correctly on platforms where read() returns
  5957. partial results on small file reads.
  5958. - Don't rebuild the entire router store every time we get 32K of
  5959. routers: rebuild it when the journal gets very large, or when
  5960. the gaps in the store get very large.
  5961. o Minor features:
  5962. - When routers publish SVN revisions in their router descriptors,
  5963. authorities now include those versions correctly in networkstatus
  5964. documents.
  5965. - Warn when using a version of libevent before 1.3b to run a server on
  5966. OSX or BSD: these versions interact badly with userspace threads.
  5967. Changes in version 0.1.2.13 - 2007-04-24
  5968. This release features some major anonymity fixes, such as safer path
  5969. selection; better client performance; faster bootstrapping, better
  5970. address detection, and better DNS support for servers; write limiting as
  5971. well as read limiting to make servers easier to run; and a huge pile of
  5972. other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
  5973. Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
  5974. of the Freenode IRC network, remembering his patience and vision for
  5975. free speech on the Internet.
  5976. o Major features, client performance:
  5977. - Weight directory requests by advertised bandwidth. Now we can
  5978. let servers enable write limiting but still allow most clients to
  5979. succeed at their directory requests. (We still ignore weights when
  5980. choosing a directory authority; I hope this is a feature.)
  5981. - Stop overloading exit nodes -- avoid choosing them for entry or
  5982. middle hops when the total bandwidth available from non-exit nodes
  5983. is much higher than the total bandwidth available from exit nodes.
  5984. - Rather than waiting a fixed amount of time between retrying
  5985. application connections, we wait only 10 seconds for the first,
  5986. 10 seconds for the second, and 15 seconds for each retry after
  5987. that. Hopefully this will improve the expected user experience.
  5988. - Sometimes we didn't bother sending a RELAY_END cell when an attempt
  5989. to open a stream fails; now we do in more cases. This should
  5990. make clients able to find a good exit faster in some cases, since
  5991. unhandleable requests will now get an error rather than timing out.
  5992. o Major features, client functionality:
  5993. - Implement BEGIN_DIR cells, so we can connect to a directory
  5994. server via TLS to do encrypted directory requests rather than
  5995. plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
  5996. config options if you like. For now, this feature only works if
  5997. you already have a descriptor for the destination dirserver.
  5998. - Add support for transparent application connections: this basically
  5999. bundles the functionality of trans-proxy-tor into the Tor
  6000. mainline. Now hosts with compliant pf/netfilter implementations
  6001. can redirect TCP connections straight to Tor without diverting
  6002. through SOCKS. (Based on patch from tup.)
  6003. - Add support for using natd; this allows FreeBSDs earlier than
  6004. 5.1.2 to have ipfw send connections through Tor without using
  6005. SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
  6006. o Major features, servers:
  6007. - Setting up a dyndns name for your server is now optional: servers
  6008. with no hostname or IP address will learn their IP address by
  6009. asking the directory authorities. This code only kicks in when you
  6010. would normally have exited with a "no address" error. Nothing's
  6011. authenticated, so use with care.
  6012. - Directory servers now spool server descriptors, v1 directories,
  6013. and v2 networkstatus objects to buffers as needed rather than en
  6014. masse. They also mmap the cached-routers files. These steps save
  6015. lots of memory.
  6016. - Stop requiring clients to have well-formed certificates, and stop
  6017. checking nicknames in certificates. (Clients have certificates so
  6018. that they can look like Tor servers, but in the future we might want
  6019. to allow them to look like regular TLS clients instead. Nicknames
  6020. in certificates serve no purpose other than making our protocol
  6021. easier to recognize on the wire.) Implements proposal 106.
  6022. o Improvements on DNS support:
  6023. - Add "eventdns" asynchronous dns library originally based on code
  6024. from Adam Langley. Now we can discard the old rickety dnsworker
  6025. concept, and support a wider variety of DNS functions. Allows
  6026. multithreaded builds on NetBSD and OpenBSD again.
  6027. - Add server-side support for "reverse" DNS lookups (using PTR
  6028. records so clients can determine the canonical hostname for a given
  6029. IPv4 address). Only supported by servers using eventdns; servers
  6030. now announce in their descriptors if they don't support eventdns.
  6031. - Workaround for name servers (like Earthlink's) that hijack failing
  6032. DNS requests and replace the no-such-server answer with a "helpful"
  6033. redirect to an advertising-driven search portal. Also work around
  6034. DNS hijackers who "helpfully" decline to hijack known-invalid
  6035. RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
  6036. lets you turn it off.
  6037. - Servers now check for the case when common DNS requests are going to
  6038. wildcarded addresses (i.e. all getting the same answer), and change
  6039. their exit policy to reject *:* if it's happening.
  6040. - When asked to resolve a hostname, don't use non-exit servers unless
  6041. requested to do so. This allows servers with broken DNS to be
  6042. useful to the network.
  6043. - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
  6044. useless IPv6 DNS resolves.
  6045. - Specify and implement client-side SOCKS5 interface for reverse DNS
  6046. lookups (see doc/socks-extensions.txt). Also cache them.
  6047. - When we change nameservers or IP addresses, reset and re-launch
  6048. our tests for DNS hijacking.
  6049. o Improvements on reachability testing:
  6050. - Servers send out a burst of long-range padding cells once they've
  6051. established that they're reachable. Spread them over 4 circuits,
  6052. so hopefully a few will be fast. This exercises bandwidth and
  6053. bootstraps them into the directory more quickly.
  6054. - When we find our DirPort to be reachable, publish a new descriptor
  6055. so we'll tell the world (reported by pnx).
  6056. - Directory authorities now only decide that routers are reachable
  6057. if their identity keys are as expected.
  6058. - Do DirPort reachability tests less often, since a single test
  6059. chews through many circuits before giving up.
  6060. - Avoid some false positives during reachability testing: don't try
  6061. to test via a server that's on the same /24 network as us.
  6062. - Start publishing one minute or so after we find our ORPort
  6063. to be reachable. This will help reduce the number of descriptors
  6064. we have for ourselves floating around, since it's quite likely
  6065. other things (e.g. DirPort) will change during that minute too.
  6066. - Routers no longer try to rebuild long-term connections to directory
  6067. authorities, and directory authorities no longer try to rebuild
  6068. long-term connections to all servers. We still don't hang up
  6069. connections in these two cases though -- we need to look at it
  6070. more carefully to avoid flapping, and we likely need to wait til
  6071. 0.1.1.x is obsolete.
  6072. o Improvements on rate limiting:
  6073. - Enable write limiting as well as read limiting. Now we sacrifice
  6074. capacity if we're pushing out lots of directory traffic, rather
  6075. than overrunning the user's intended bandwidth limits.
  6076. - Include TLS overhead when counting bandwidth usage; previously, we
  6077. would count only the bytes sent over TLS, but not the bytes used
  6078. to send them.
  6079. - Servers decline directory requests much more aggressively when
  6080. they're low on bandwidth. Otherwise they end up queueing more and
  6081. more directory responses, which can't be good for latency.
  6082. - But never refuse directory requests from local addresses.
  6083. - Be willing to read or write on local connections (e.g. controller
  6084. connections) even when the global rate limiting buckets are empty.
  6085. - Flush local controller connection buffers periodically as we're
  6086. writing to them, so we avoid queueing 4+ megabytes of data before
  6087. trying to flush.
  6088. - Revise and clean up the torrc.sample that we ship with; add
  6089. a section for BandwidthRate and BandwidthBurst.
  6090. o Major features, NT services:
  6091. - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
  6092. command-line flag so that admins can override the default by saying
  6093. "tor --service install --user "SomeUser"". This will not affect
  6094. existing installed services. Also, warn the user that the service
  6095. will look for its configuration file in the service user's
  6096. %appdata% directory. (We can't do the "hardwire the user's appdata
  6097. directory" trick any more, since we may not have read access to that
  6098. directory.)
  6099. - Support running the Tor service with a torrc not in the same
  6100. directory as tor.exe and default to using the torrc located in
  6101. the %appdata%\Tor\ of the user who installed the service. Patch
  6102. from Matt Edman.
  6103. - Add an --ignore-missing-torrc command-line option so that we can
  6104. get the "use sensible defaults if the configuration file doesn't
  6105. exist" behavior even when specifying a torrc location on the
  6106. command line.
  6107. - When stopping an NT service, wait up to 10 sec for it to actually
  6108. stop. (Patch from Matt Edman; resolves bug 295.)
  6109. o Directory authority improvements:
  6110. - Stop letting hibernating or obsolete servers affect uptime and
  6111. bandwidth cutoffs.
  6112. - Stop listing hibernating servers in the v1 directory.
  6113. - Authorities no longer recommend exits as guards if this would shift
  6114. too much load to the exit nodes.
  6115. - Authorities now specify server versions in networkstatus. This adds
  6116. about 2% to the size of compressed networkstatus docs, and allows
  6117. clients to tell which servers support BEGIN_DIR and which don't.
  6118. The implementation is forward-compatible with a proposed future
  6119. protocol version scheme not tied to Tor versions.
  6120. - DirServer configuration lines now have an orport= option so
  6121. clients can open encrypted tunnels to the authorities without
  6122. having downloaded their descriptors yet. Enabled for moria1,
  6123. moria2, tor26, and lefkada now in the default configuration.
  6124. - Add a BadDirectory flag to network status docs so that authorities
  6125. can (eventually) tell clients about caches they believe to be
  6126. broken. Not used yet.
  6127. - Allow authorities to list nodes as bad exits in their
  6128. approved-routers file by fingerprint or by address. If most
  6129. authorities set a BadExit flag for a server, clients don't think
  6130. of it as a general-purpose exit. Clients only consider authorities
  6131. that advertise themselves as listing bad exits.
  6132. - Patch from Steve Hildrey: Generate network status correctly on
  6133. non-versioning dirservers.
  6134. - Have directory authorities allow larger amounts of drift in uptime
  6135. without replacing the server descriptor: previously, a server that
  6136. restarted every 30 minutes could have 48 "interesting" descriptors
  6137. per day.
  6138. - Reserve the nickname "Unnamed" for routers that can't pick
  6139. a hostname: any router can call itself Unnamed; directory
  6140. authorities will never allocate Unnamed to any particular router;
  6141. clients won't believe that any router is the canonical Unnamed.
  6142. o Directory mirrors and clients:
  6143. - Discard any v1 directory info that's over 1 month old (for
  6144. directories) or over 1 week old (for running-routers lists).
  6145. - Clients track responses with status 503 from dirservers. After a
  6146. dirserver has given us a 503, we try not to use it until an hour has
  6147. gone by, or until we have no dirservers that haven't given us a 503.
  6148. - When we get a 503 from a directory, and we're not a server, we no
  6149. longer count the failure against the total number of failures
  6150. allowed for the object we're trying to download.
  6151. - Prepare for servers to publish descriptors less often: never
  6152. discard a descriptor simply for being too old until either it is
  6153. recommended by no authorities, or until we get a better one for
  6154. the same router. Make caches consider retaining old recommended
  6155. routers for even longer.
  6156. - Directory servers now provide 'Pragma: no-cache' and 'Expires'
  6157. headers for content, so that we can work better in the presence of
  6158. caching HTTP proxies.
  6159. - Stop fetching descriptors if you're not a dir mirror and you
  6160. haven't tried to establish any circuits lately. (This currently
  6161. causes some dangerous behavior, because when you start up again
  6162. you'll use your ancient server descriptors.)
  6163. o Major fixes, crashes:
  6164. - Stop crashing when the controller asks us to resetconf more than
  6165. one config option at once. (Vidalia 0.0.11 does this.)
  6166. - Fix a longstanding obscure crash bug that could occur when we run
  6167. out of DNS worker processes, if we're not using eventdns. (Resolves
  6168. bug 390.)
  6169. - Fix an assert that could trigger if a controller quickly set then
  6170. cleared EntryNodes. (Bug found by Udo van den Heuvel.)
  6171. - Avoid crash when telling controller about stream-status and a
  6172. stream is detached.
  6173. - Avoid sending junk to controllers or segfaulting when a controller
  6174. uses EVENT_NEW_DESC with verbose nicknames.
  6175. - Stop triggering asserts if the controller tries to extend hidden
  6176. service circuits (reported by mwenge).
  6177. - If we start a server with ClientOnly 1, then set ClientOnly to 0
  6178. and hup, stop triggering an assert based on an empty onion_key.
  6179. - Mask out all signals in sub-threads; only the libevent signal
  6180. handler should be processing them. This should prevent some crashes
  6181. on some machines using pthreads. (Patch from coderman.)
  6182. - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
  6183. o Major fixes, anonymity/security:
  6184. - Automatically avoid picking more than one node from the same
  6185. /16 network when constructing a circuit. Add an
  6186. "EnforceDistinctSubnets" option to let people disable it if they
  6187. want to operate private test networks on a single subnet.
  6188. - When generating bandwidth history, round down to the nearest
  6189. 1k. When storing accounting data, round up to the nearest 1k.
  6190. - When we're running as a server, remember when we last rotated onion
  6191. keys, so that we will rotate keys once they're a week old even if
  6192. we never stay up for a week ourselves.
  6193. - If a client asked for a server by name, and there's a named server
  6194. in our network-status but we don't have its descriptor yet, we
  6195. could return an unnamed server instead.
  6196. - Reject (most) attempts to use Tor circuits with length one. (If
  6197. many people start using Tor as a one-hop proxy, exit nodes become
  6198. a more attractive target for compromise.)
  6199. - Just because your DirPort is open doesn't mean people should be
  6200. able to remotely teach you about hidden service descriptors. Now
  6201. only accept rendezvous posts if you've got HSAuthoritativeDir set.
  6202. - Fix a potential race condition in the rpm installer. Found by
  6203. Stefan Nordhausen.
  6204. - Do not log IPs with TLS failures for incoming TLS
  6205. connections. (Fixes bug 382.)
  6206. o Major fixes, other:
  6207. - If our system clock jumps back in time, don't publish a negative
  6208. uptime in the descriptor.
  6209. - When we start during an accounting interval before it's time to wake
  6210. up, remember to wake up at the correct time. (May fix bug 342.)
  6211. - Previously, we would cache up to 16 old networkstatus documents
  6212. indefinitely, if they came from nontrusted authorities. Now we
  6213. discard them if they are more than 10 days old.
  6214. - When we have a state file we cannot parse, tell the user and
  6215. move it aside. Now we avoid situations where the user starts
  6216. Tor in 1904, Tor writes a state file with that timestamp in it,
  6217. the user fixes her clock, and Tor refuses to start.
  6218. - Publish a new descriptor after we hup/reload. This is important
  6219. if our config has changed such that we'll want to start advertising
  6220. our DirPort now, etc.
  6221. - If we are using an exit enclave and we can't connect, e.g. because
  6222. its webserver is misconfigured to not listen on localhost, then
  6223. back off and try connecting from somewhere else before we fail.
  6224. o New config options or behaviors:
  6225. - When EntryNodes are configured, rebuild the guard list to contain,
  6226. in order: the EntryNodes that were guards before; the rest of the
  6227. EntryNodes; the nodes that were guards before.
  6228. - Do not warn when individual nodes in the configuration's EntryNodes,
  6229. ExitNodes, etc are down: warn only when all possible nodes
  6230. are down. (Fixes bug 348.)
  6231. - Put a lower-bound on MaxAdvertisedBandwidth.
  6232. - Start using the state file to store bandwidth accounting data:
  6233. the bw_accounting file is now obsolete. We'll keep generating it
  6234. for a while for people who are still using 0.1.2.4-alpha.
  6235. - Try to batch changes to the state file so that we do as few
  6236. disk writes as possible while still storing important things in
  6237. a timely fashion.
  6238. - The state file and the bw_accounting file get saved less often when
  6239. the AvoidDiskWrites config option is set.
  6240. - Make PIDFile work on Windows.
  6241. - Add internal descriptions for a bunch of configuration options:
  6242. accessible via controller interface and in comments in saved
  6243. options files.
  6244. - Reject *:563 (NNTPS) in the default exit policy. We already reject
  6245. NNTP by default, so this seems like a sensible addition.
  6246. - Clients now reject hostnames with invalid characters. This should
  6247. avoid some inadvertent info leaks. Add an option
  6248. AllowNonRFC953Hostnames to disable this behavior, in case somebody
  6249. is running a private network with hosts called @, !, and #.
  6250. - Check for addresses with invalid characters at the exit as well,
  6251. and warn less verbosely when they fail. You can override this by
  6252. setting ServerDNSAllowNonRFC953Addresses to 1.
  6253. - Remove some options that have been deprecated since at least
  6254. 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
  6255. SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
  6256. to set log options. Mark PathlenCoinWeight as obsolete.
  6257. - Stop accepting certain malformed ports in configured exit policies.
  6258. - When the user uses bad syntax in the Log config line, stop
  6259. suggesting other bad syntax as a replacement.
  6260. - Add new config option "ResolvConf" to let the server operator
  6261. choose an alternate resolve.conf file when using eventdns.
  6262. - If one of our entry guards is on the ExcludeNodes list, or the
  6263. directory authorities don't think it's a good guard, treat it as
  6264. if it were unlisted: stop using it as a guard, and throw it off
  6265. the guards list if it stays that way for a long time.
  6266. - Allow directory authorities to be marked separately as authorities
  6267. for the v1 directory protocol, the v2 directory protocol, and
  6268. as hidden service directories, to make it easier to retire old
  6269. authorities. V1 authorities should set "HSAuthoritativeDir 1"
  6270. to continue being hidden service authorities too.
  6271. - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
  6272. - Make TrackExitHosts case-insensitive, and fix the behavior of
  6273. ".suffix" TrackExitHosts items to avoid matching in the middle of
  6274. an address.
  6275. - New DirPort behavior: if you have your dirport set, you download
  6276. descriptors aggressively like a directory mirror, whether or not
  6277. your ORPort is set.
  6278. o Docs:
  6279. - Create a new file ReleaseNotes which was the old ChangeLog. The
  6280. new ChangeLog file now includes the notes for all development
  6281. versions too.
  6282. - Add a new address-spec.txt document to describe our special-case
  6283. addresses: .exit, .onion, and .noconnnect.
  6284. - Fork the v1 directory protocol into its own spec document,
  6285. and mark dir-spec.txt as the currently correct (v2) spec.
  6286. o Packaging, porting, and contrib
  6287. - "tor --verify-config" now exits with -1(255) or 0 depending on
  6288. whether the config options are bad or good.
  6289. - The Debian package now uses --verify-config when (re)starting,
  6290. to distinguish configuration errors from other errors.
  6291. - Adapt a patch from goodell to let the contrib/exitlist script
  6292. take arguments rather than require direct editing.
  6293. - Prevent the contrib/exitlist script from printing the same
  6294. result more than once.
  6295. - Add support to tor-resolve tool for reverse lookups and SOCKS5.
  6296. - In the hidden service example in torrc.sample, stop recommending
  6297. esoteric and discouraged hidden service options.
  6298. - Patch from Michael Mohr to contrib/cross.sh, so it checks more
  6299. values before failing, and always enables eventdns.
  6300. - Try to detect Windows correctly when cross-compiling.
  6301. - Libevent-1.2 exports, but does not define in its headers, strlcpy.
  6302. Try to fix this in configure.in by checking for most functions
  6303. before we check for libevent.
  6304. - Update RPMs to require libevent 1.2.
  6305. - Experimentally re-enable kqueue on OSX when using libevent 1.1b
  6306. or later. Log when we are doing this, so we can diagnose it when
  6307. it fails. (Also, recommend libevent 1.1b for kqueue and
  6308. win32 methods; deprecate libevent 1.0b harder; make libevent
  6309. recommendation system saner.)
  6310. - Build with recent (1.3+) libevents on platforms that do not
  6311. define the nonstandard types "u_int8_t" and friends.
  6312. - Remove architecture from OS X builds. The official builds are
  6313. now universal binaries.
  6314. - Run correctly on OS X platforms with case-sensitive filesystems.
  6315. - Correctly set maximum connection limit on Cygwin. (This time
  6316. for sure!)
  6317. - Start compiling on MinGW on Windows (patches from Mike Chiussi
  6318. and many others).
  6319. - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
  6320. - Finally fix the openssl warnings from newer gccs that believe that
  6321. ignoring a return value is okay, but casting a return value and
  6322. then ignoring it is a sign of madness.
  6323. - On architectures where sizeof(int)>4, still clamp declarable
  6324. bandwidth to INT32_MAX.
  6325. o Minor features, controller:
  6326. - Warn the user when an application uses the obsolete binary v0
  6327. control protocol. We're planning to remove support for it during
  6328. the next development series, so it's good to give people some
  6329. advance warning.
  6330. - Add STREAM_BW events to report per-entry-stream bandwidth
  6331. use. (Patch from Robert Hogan.)
  6332. - Rate-limit SIGNEWNYM signals in response to controllers that
  6333. impolitely generate them for every single stream. (Patch from
  6334. mwenge; closes bug 394.)
  6335. - Add a REMAP status to stream events to note that a stream's
  6336. address has changed because of a cached address or a MapAddress
  6337. directive.
  6338. - Make REMAP stream events have a SOURCE (cache or exit), and
  6339. make them generated in every case where we get a successful
  6340. connected or resolved cell.
  6341. - Track reasons for OR connection failure; make these reasons
  6342. available via the controller interface. (Patch from Mike Perry.)
  6343. - Add a SOCKS_BAD_HOSTNAME client status event so controllers
  6344. can learn when clients are sending malformed hostnames to Tor.
  6345. - Specify and implement some of the controller status events.
  6346. - Have GETINFO dir/status/* work on hosts with DirPort disabled.
  6347. - Reimplement GETINFO so that info/names stays in sync with the
  6348. actual keys.
  6349. - Implement "GETINFO fingerprint".
  6350. - Implement "SETEVENTS GUARD" so controllers can get updates on
  6351. entry guard status as it changes.
  6352. - Make all connections to addresses of the form ".noconnect"
  6353. immediately get closed. This lets application/controller combos
  6354. successfully test whether they're talking to the same Tor by
  6355. watching for STREAM events.
  6356. - Add a REASON field to CIRC events; for backward compatibility, this
  6357. field is sent only to controllers that have enabled the extended
  6358. event format. Also, add additional reason codes to explain why
  6359. a given circuit has been destroyed or truncated. (Patches from
  6360. Mike Perry)
  6361. - Add a REMOTE_REASON field to extended CIRC events to tell the
  6362. controller why a remote OR told us to close a circuit.
  6363. - Stream events also now have REASON and REMOTE_REASON fields,
  6364. working much like those for circuit events.
  6365. - There's now a GETINFO ns/... field so that controllers can ask Tor
  6366. about the current status of a router.
  6367. - A new event type "NS" to inform a controller when our opinion of
  6368. a router's status has changed.
  6369. - Add a GETINFO events/names and GETINFO features/names so controllers
  6370. can tell which events and features are supported.
  6371. - A new CLEARDNSCACHE signal to allow controllers to clear the
  6372. client-side DNS cache without expiring circuits.
  6373. - Fix CIRC controller events so that controllers can learn the
  6374. identity digests of non-Named servers used in circuit paths.
  6375. - Let controllers ask for more useful identifiers for servers. Instead
  6376. of learning identity digests for un-Named servers and nicknames
  6377. for Named servers, the new identifiers include digest, nickname,
  6378. and indication of Named status. Off by default; see control-spec.txt
  6379. for more information.
  6380. - Add a "getinfo address" controller command so it can display Tor's
  6381. best guess to the user.
  6382. - New controller event to alert the controller when our server
  6383. descriptor has changed.
  6384. - Give more meaningful errors on controller authentication failure.
  6385. - Export the default exit policy via the control port, so controllers
  6386. don't need to guess what it is / will be later.
  6387. o Minor bugfixes, controller:
  6388. - When creating a circuit via the controller, send a 'launched'
  6389. event when we're done, so we follow the spec better.
  6390. - Correct the control spec to match how the code actually responds
  6391. to 'getinfo addr-mappings/*'. Reported by daejees.
  6392. - The control spec described a GUARDS event, but the code
  6393. implemented a GUARD event. Standardize on GUARD, but let people
  6394. ask for GUARDS too. Reported by daejees.
  6395. - Give the controller END_STREAM_REASON_DESTROY events _before_ we
  6396. clear the corresponding on_circuit variable, and remember later
  6397. that we don't need to send a redundant CLOSED event. (Resolves part
  6398. 3 of bug 367.)
  6399. - Report events where a resolve succeeded or where we got a socks
  6400. protocol error correctly, rather than calling both of them
  6401. "INTERNAL".
  6402. - Change reported stream target addresses to IP consistently when
  6403. we finally get the IP from an exit node.
  6404. - Send log messages to the controller even if they happen to be very
  6405. long.
  6406. - Flush ERR-level controller status events just like we currently
  6407. flush ERR-level log events, so that a Tor shutdown doesn't prevent
  6408. the controller from learning about current events.
  6409. - Report the circuit number correctly in STREAM CLOSED events. Bug
  6410. reported by Mike Perry.
  6411. - Do not report bizarre values for results of accounting GETINFOs
  6412. when the last second's write or read exceeds the allotted bandwidth.
  6413. - Report "unrecognized key" rather than an empty string when the
  6414. controller tries to fetch a networkstatus that doesn't exist.
  6415. - When the controller does a "GETINFO network-status", tell it
  6416. about even those routers whose descriptors are very old, and use
  6417. long nicknames where appropriate.
  6418. - Fix handling of verbose nicknames with ORCONN controller events:
  6419. make them show up exactly when requested, rather than exactly when
  6420. not requested.
  6421. - Controller signals now work on non-Unix platforms that don't define
  6422. SIGUSR1 and SIGUSR2 the way we expect.
  6423. - Respond to SIGNAL command before we execute the signal, in case
  6424. the signal shuts us down. Suggested by Karsten Loesing.
  6425. - Handle reporting OR_CONN_EVENT_NEW events to the controller.
  6426. o Minor features, code performance:
  6427. - Major performance improvement on inserting descriptors: change
  6428. algorithm from O(n^2) to O(n).
  6429. - Do not rotate onion key immediately after setting it for the first
  6430. time.
  6431. - Call router_have_min_dir_info half as often. (This is showing up in
  6432. some profiles, but not others.)
  6433. - When using GCC, make log_debug never get called at all, and its
  6434. arguments never get evaluated, when no debug logs are configured.
  6435. (This is showing up in some profiles, but not others.)
  6436. - Statistics dumped by -USR2 now include a breakdown of public key
  6437. operations, for profiling.
  6438. - Make the common memory allocation path faster on machines where
  6439. malloc(0) returns a pointer.
  6440. - Split circuit_t into origin_circuit_t and or_circuit_t, and
  6441. split connection_t into edge, or, dir, control, and base structs.
  6442. These will save quite a bit of memory on busy servers, and they'll
  6443. also help us track down bugs in the code and bugs in the spec.
  6444. - Use OpenSSL's AES implementation on platforms where it's faster.
  6445. This could save us as much as 10% CPU usage.
  6446. o Minor features, descriptors and descriptor handling:
  6447. - Avoid duplicate entries on MyFamily line in server descriptor.
  6448. - When Tor receives a router descriptor that it asked for, but
  6449. no longer wants (because it has received fresh networkstatuses
  6450. in the meantime), do not warn the user. Cache the descriptor if
  6451. we're a cache; drop it if we aren't.
  6452. - Servers no longer ever list themselves in their "family" line,
  6453. even if configured to do so. This makes it easier to configure
  6454. family lists conveniently.
  6455. o Minor fixes, confusing/misleading log messages:
  6456. - Display correct results when reporting which versions are
  6457. recommended, and how recommended they are. (Resolves bug 383.)
  6458. - Inform the server operator when we decide not to advertise a
  6459. DirPort due to AccountingMax enabled or a low BandwidthRate.
  6460. - Only include function names in log messages for info/debug messages.
  6461. For notice/warn/err, the content of the message should be clear on
  6462. its own, and printing the function name only confuses users.
  6463. - Remove even more protocol-related warnings from Tor server logs,
  6464. such as bad TLS handshakes and malformed begin cells.
  6465. - Fix bug 314: Tor clients issued "unsafe socks" warnings even
  6466. when the IP address is mapped through MapAddress to a hostname.
  6467. - Fix misleading log messages: an entry guard that is "unlisted",
  6468. as well as not known to be "down" (because we've never heard
  6469. of it), is not therefore "up".
  6470. o Minor fixes, old/obsolete behavior:
  6471. - Start assuming we can use a create_fast cell if we don't know
  6472. what version a router is running.
  6473. - We no longer look for identity and onion keys in "identity.key" and
  6474. "onion.key" -- these were replaced by secret_id_key and
  6475. secret_onion_key in 0.0.8pre1.
  6476. - We no longer require unrecognized directory entries to be
  6477. preceded by "opt".
  6478. - Drop compatibility with obsolete Tors that permit create cells
  6479. to have the wrong circ_id_type.
  6480. - Remove code to special-case "-cvs" ending, since it has not
  6481. actually mattered since 0.0.9.
  6482. - Don't re-write the fingerprint file every restart, unless it has
  6483. changed.
  6484. o Minor fixes, misc client-side behavior:
  6485. - Always remove expired routers and networkstatus docs before checking
  6486. whether we have enough information to build circuits. (Fixes
  6487. bug 373.)
  6488. - When computing clock skew from directory HTTP headers, consider what
  6489. time it was when we finished asking for the directory, not what
  6490. time it is now.
  6491. - Make our socks5 handling more robust to broken socks clients:
  6492. throw out everything waiting on the buffer in between socks
  6493. handshake phases, since they can't possibly (so the theory
  6494. goes) have predicted what we plan to respond to them.
  6495. - Expire socks connections if they spend too long waiting for the
  6496. handshake to finish. Previously we would let them sit around for
  6497. days, if the connecting application didn't close them either.
  6498. - And if the socks handshake hasn't started, don't send a
  6499. "DNS resolve socks failed" handshake reply; just close it.
  6500. - If the user asks to use invalid exit nodes, be willing to use
  6501. unstable ones.
  6502. - Track unreachable entry guards correctly: don't conflate
  6503. 'unreachable by us right now' with 'listed as down by the directory
  6504. authorities'. With the old code, if a guard was unreachable by us
  6505. but listed as running, it would clog our guard list forever.
  6506. - Behave correctly in case we ever have a network with more than
  6507. 2GB/s total advertised capacity.
  6508. - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
  6509. - Fix a memory leak when we ask for "all" networkstatuses and we
  6510. get one we don't recognize.
  6511. Changes in version 0.1.1.26 - 2006-12-14
  6512. o Security bugfixes:
  6513. - Stop sending the HttpProxyAuthenticator string to directory
  6514. servers when directory connections are tunnelled through Tor.
  6515. - Clients no longer store bandwidth history in the state file.
  6516. - Do not log introduction points for hidden services if SafeLogging
  6517. is set.
  6518. o Minor bugfixes:
  6519. - Fix an assert failure when a directory authority sets
  6520. AuthDirRejectUnlisted and then receives a descriptor from an
  6521. unlisted router (reported by seeess).
  6522. Changes in version 0.1.1.25 - 2006-11-04
  6523. o Major bugfixes:
  6524. - When a client asks us to resolve (rather than connect to)
  6525. an address, and we have a cached answer, give them the cached
  6526. answer. Previously, we would give them no answer at all.
  6527. - We were building exactly the wrong circuits when we predict
  6528. hidden service requirements, meaning Tor would have to build all
  6529. its circuits on demand.
  6530. - If none of our live entry guards have a high uptime, but we
  6531. require a guard with a high uptime, try adding a new guard before
  6532. we give up on the requirement. This patch should make long-lived
  6533. connections more stable on average.
  6534. - When testing reachability of our DirPort, don't launch new
  6535. tests when there's already one in progress -- unreachable
  6536. servers were stacking up dozens of testing streams.
  6537. o Security bugfixes:
  6538. - When the user sends a NEWNYM signal, clear the client-side DNS
  6539. cache too. Otherwise we continue to act on previous information.
  6540. o Minor bugfixes:
  6541. - Avoid a memory corruption bug when creating a hash table for
  6542. the first time.
  6543. - Avoid possibility of controller-triggered crash when misusing
  6544. certain commands from a v0 controller on platforms that do not
  6545. handle printf("%s",NULL) gracefully.
  6546. - Avoid infinite loop on unexpected controller input.
  6547. - Don't log spurious warnings when we see a circuit close reason we
  6548. don't recognize; it's probably just from a newer version of Tor.
  6549. - Add Vidalia to the OS X uninstaller script, so when we uninstall
  6550. Tor/Privoxy we also uninstall Vidalia.
  6551. Changes in version 0.1.1.24 - 2006-09-29
  6552. o Major bugfixes:
  6553. - Allow really slow clients to not hang up five minutes into their
  6554. directory downloads (suggested by Adam J. Richter).
  6555. - Fix major performance regression from 0.1.0.x: instead of checking
  6556. whether we have enough directory information every time we want to
  6557. do something, only check when the directory information has changed.
  6558. This should improve client CPU usage by 25-50%.
  6559. - Don't crash if, after a server has been running for a while,
  6560. it can't resolve its hostname.
  6561. - When a client asks us to resolve (not connect to) an address,
  6562. and we have a cached answer, give them the cached answer.
  6563. Previously, we would give them no answer at all.
  6564. o Minor bugfixes:
  6565. - Allow Tor to start when RunAsDaemon is set but no logs are set.
  6566. - Don't crash when the controller receives a third argument to an
  6567. "extendcircuit" request.
  6568. - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
  6569. response; fix error code when "getinfo dir/status/" fails.
  6570. - Fix configure.in to not produce broken configure files with
  6571. more recent versions of autoconf. Thanks to Clint for his auto*
  6572. voodoo.
  6573. - Fix security bug on NetBSD that could allow someone to force
  6574. uninitialized RAM to be sent to a server's DNS resolver. This
  6575. only affects NetBSD and other platforms that do not bounds-check
  6576. tolower().
  6577. - Warn user when using libevent 1.1a or earlier with win32 or kqueue
  6578. methods: these are known to be buggy.
  6579. - If we're a directory mirror and we ask for "all" network status
  6580. documents, we would discard status documents from authorities
  6581. we don't recognize.
  6582. Changes in version 0.1.1.23 - 2006-07-30
  6583. o Major bugfixes:
  6584. - Fast Tor servers, especially exit nodes, were triggering asserts
  6585. due to a bug in handling the list of pending DNS resolves. Some
  6586. bugs still remain here; we're hunting them.
  6587. - Entry guards could crash clients by sending unexpected input.
  6588. - More fixes on reachability testing: if you find yourself reachable,
  6589. then don't ever make any client requests (so you stop predicting
  6590. circuits), then hup or have your clock jump, then later your IP
  6591. changes, you won't think circuits are working, so you won't try to
  6592. test reachability, so you won't publish.
  6593. o Minor bugfixes:
  6594. - Avoid a crash if the controller does a resetconf firewallports
  6595. and then a setconf fascistfirewall=1.
  6596. - Avoid an integer underflow when the dir authority decides whether
  6597. a router is stable: we might wrongly label it stable, and compute
  6598. a slightly wrong median stability, when a descriptor is published
  6599. later than now.
  6600. - Fix a place where we might trigger an assert if we can't build our
  6601. own server descriptor yet.
  6602. Changes in version 0.1.1.22 - 2006-07-05
  6603. o Major bugfixes:
  6604. - Fix a big bug that was causing servers to not find themselves
  6605. reachable if they changed IP addresses. Since only 0.1.1.22+
  6606. servers can do reachability testing correctly, now we automatically
  6607. make sure to test via one of these.
  6608. - Fix to allow clients and mirrors to learn directory info from
  6609. descriptor downloads that get cut off partway through.
  6610. - Directory authorities had a bug in deciding if a newly published
  6611. descriptor was novel enough to make everybody want a copy -- a few
  6612. servers seem to be publishing new descriptors many times a minute.
  6613. o Minor bugfixes:
  6614. - Fix a rare bug that was causing some servers to complain about
  6615. "closing wedged cpuworkers" and skip some circuit create requests.
  6616. - Make the Exit flag in directory status documents actually work.
  6617. Changes in version 0.1.1.21 - 2006-06-10
  6618. o Crash and assert fixes from 0.1.1.20:
  6619. - Fix a rare crash on Tor servers that have enabled hibernation.
  6620. - Fix a seg fault on startup for Tor networks that use only one
  6621. directory authority.
  6622. - Fix an assert from a race condition that occurs on Tor servers
  6623. while exiting, where various threads are trying to log that they're
  6624. exiting, and delete the logs, at the same time.
  6625. - Make our unit tests pass again on certain obscure platforms.
  6626. o Other fixes:
  6627. - Add support for building SUSE RPM packages.
  6628. - Speed up initial bootstrapping for clients: if we are making our
  6629. first ever connection to any entry guard, then don't mark it down
  6630. right after that.
  6631. - When only one Tor server in the network is labelled as a guard,
  6632. and we've already picked him, we would cycle endlessly picking him
  6633. again, being unhappy about it, etc. Now we specifically exclude
  6634. current guards when picking a new guard.
  6635. - Servers send create cells more reliably after the TLS connection
  6636. is established: we were sometimes forgetting to send half of them
  6637. when we had more than one pending.
  6638. - If we get a create cell that asks us to extend somewhere, but the
  6639. Tor server there doesn't match the expected digest, we now send
  6640. a destroy cell back, rather than silently doing nothing.
  6641. - Make options->RedirectExit work again.
  6642. - Make cookie authentication for the controller work again.
  6643. - Stop being picky about unusual characters in the arguments to
  6644. mapaddress. It's none of our business.
  6645. - Add a new config option "TestVia" that lets you specify preferred
  6646. middle hops to use for test circuits. Perhaps this will let me
  6647. debug the reachability problems better.
  6648. o Log / documentation fixes:
  6649. - If we're a server and some peer has a broken TLS certificate, don't
  6650. log about it unless ProtocolWarnings is set, i.e., we want to hear
  6651. about protocol violations by others.
  6652. - Fix spelling of VirtualAddrNetwork in man page.
  6653. - Add a better explanation at the top of the autogenerated torrc file
  6654. about what happened to our old torrc.
  6655. Changes in version 0.1.1.20 - 2006-05-23
  6656. o Crash and assert fixes from 0.1.0.17:
  6657. - Fix assert bug in close_logs() on exit: when we close and delete
  6658. logs, remove them all from the global "logfiles" list.
  6659. - Fix an assert error when we're out of space in the connection_list
  6660. and we try to post a hidden service descriptor (reported by Peter
  6661. Palfrader).
  6662. - Fix a rare assert error when we've tried all intro points for
  6663. a hidden service and we try fetching the service descriptor again:
  6664. "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
  6665. - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
  6666. out and refuse the setconf if it would fail.
  6667. - If you specify a relative torrc path and you set RunAsDaemon in
  6668. your torrc, then it chdir()'s to the new directory. If you then
  6669. HUP, it tries to load the new torrc location, fails, and exits.
  6670. The fix: no longer allow a relative path to torrc when using -f.
  6671. - Check for integer overflows in more places, when adding elements
  6672. to smartlists. This could possibly prevent a buffer overflow
  6673. on malicious huge inputs.
  6674. o Security fixes, major:
  6675. - When we're printing strings from the network, don't try to print
  6676. non-printable characters. Now we're safer against shell escape
  6677. sequence exploits, and also against attacks to fool users into
  6678. misreading their logs.
  6679. - Implement entry guards: automatically choose a handful of entry
  6680. nodes and stick with them for all circuits. Only pick new guards
  6681. when the ones you have are unsuitable, and if the old guards
  6682. become suitable again, switch back. This will increase security
  6683. dramatically against certain end-point attacks. The EntryNodes
  6684. config option now provides some hints about which entry guards you
  6685. want to use most; and StrictEntryNodes means to only use those.
  6686. Fixes CVE-2006-0414.
  6687. - Implement exit enclaves: if we know an IP address for the
  6688. destination, and there's a running Tor server at that address
  6689. which allows exit to the destination, then extend the circuit to
  6690. that exit first. This provides end-to-end encryption and end-to-end
  6691. authentication. Also, if the user wants a .exit address or enclave,
  6692. use 4 hops rather than 3, and cannibalize a general circ for it
  6693. if you can.
  6694. - Obey our firewall options more faithfully:
  6695. . If we can't get to a dirserver directly, try going via Tor.
  6696. . Don't ever try to connect (as a client) to a place our
  6697. firewall options forbid.
  6698. . If we specify a proxy and also firewall options, obey the
  6699. firewall options even when we're using the proxy: some proxies
  6700. can only proxy to certain destinations.
  6701. - Make clients regenerate their keys when their IP address changes.
  6702. - For the OS X package's modified privoxy config file, comment
  6703. out the "logfile" line so we don't log everything passed
  6704. through privoxy.
  6705. - Our TLS handshakes were generating a single public/private
  6706. keypair for the TLS context, rather than making a new one for
  6707. each new connection. Oops. (But we were still rotating them
  6708. periodically, so it's not so bad.)
  6709. - When we were cannibalizing a circuit with a particular exit
  6710. node in mind, we weren't checking to see if that exit node was
  6711. already present earlier in the circuit. Now we are.
  6712. - Require server descriptors to list IPv4 addresses -- hostnames
  6713. are no longer allowed. This also fixes potential vulnerabilities
  6714. to servers providing hostnames as their address and then
  6715. preferentially resolving them so they can partition users.
  6716. - Our logic to decide if the OR we connected to was the right guy
  6717. was brittle and maybe open to a mitm for invalid routers.
  6718. o Security fixes, minor:
  6719. - Adjust tor-spec.txt to parameterize cell and key lengths. Now
  6720. Ian Goldberg can prove things about our handshake protocol more
  6721. easily.
  6722. - Make directory authorities generate a separate "guard" flag to
  6723. mean "would make a good entry guard". Clients now honor the
  6724. is_guard flag rather than looking at is_fast or is_stable.
  6725. - Try to list MyFamily elements by key, not by nickname, and warn
  6726. if we've not heard of a server.
  6727. - Start using RAND_bytes rather than RAND_pseudo_bytes from
  6728. OpenSSL. Also, reseed our entropy every hour, not just at
  6729. startup. And add entropy in 512-bit chunks, not 160-bit chunks.
  6730. - Refuse server descriptors where the fingerprint line doesn't match
  6731. the included identity key. Tor doesn't care, but other apps (and
  6732. humans) might actually be trusting the fingerprint line.
  6733. - We used to kill the circuit when we receive a relay command we
  6734. don't recognize. Now we just drop that cell.
  6735. - Fix a bug found by Lasse Overlier: when we were making internal
  6736. circuits (intended to be cannibalized later for rendezvous and
  6737. introduction circuits), we were picking them so that they had
  6738. useful exit nodes. There was no need for this, and it actually
  6739. aids some statistical attacks.
  6740. - Start treating internal circuits and exit circuits separately.
  6741. It's important to keep them separate because internal circuits
  6742. have their last hops picked like middle hops, rather than like
  6743. exit hops. So exiting on them will break the user's expectations.
  6744. - Fix a possible way to DoS dirservers.
  6745. - When the client asked for a rendezvous port that the hidden
  6746. service didn't want to provide, we were sending an IP address
  6747. back along with the end cell. Fortunately, it was zero. But stop
  6748. that anyway.
  6749. o Packaging improvements:
  6750. - Implement --with-libevent-dir option to ./configure. Improve
  6751. search techniques to find libevent, and use those for openssl too.
  6752. - Fix a couple of bugs in OpenSSL detection. Deal better when
  6753. there are multiple SSLs installed with different versions.
  6754. - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
  6755. - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
  6756. "-Wall -g -O2".
  6757. - Make unit tests (and other invocations that aren't the real Tor)
  6758. run without launching listeners, creating subdirectories, and so on.
  6759. - The OS X installer was adding a symlink for tor_resolve but
  6760. the binary was called tor-resolve (reported by Thomas Hardly).
  6761. - Now we can target arch and OS in rpm builds (contributed by
  6762. Phobos). Also make the resulting dist-rpm filename match the
  6763. target arch.
  6764. - Apply Matt Ghali's --with-syslog-facility patch to ./configure
  6765. if you log to syslog and want something other than LOG_DAEMON.
  6766. - Fix the torify (tsocks) config file to not use Tor for localhost
  6767. connections.
  6768. - Start shipping socks-extensions.txt, tor-doc-unix.html,
  6769. tor-doc-server.html, and stylesheet.css in the tarball.
  6770. - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
  6771. They are useless now.
  6772. - Add Peter Palfrader's contributed check-tor script. It lets you
  6773. easily check whether a given server (referenced by nickname)
  6774. is reachable by you.
  6775. - Add BSD-style contributed startup script "rc.subr" from Peter
  6776. Thoenen.
  6777. o Directory improvements -- new directory protocol:
  6778. - See tor/doc/dir-spec.txt for all the juicy details. Key points:
  6779. - Authorities and caches publish individual descriptors (by
  6780. digest, by fingerprint, by "all", and by "tell me yours").
  6781. - Clients don't download or use the old directory anymore. Now they
  6782. download network-statuses from the directory authorities, and
  6783. fetch individual server descriptors as needed from mirrors.
  6784. - Clients don't download descriptors of non-running servers.
  6785. - Download descriptors by digest, not by fingerprint. Caches try to
  6786. download all listed digests from authorities; clients try to
  6787. download "best" digests from caches. This avoids partitioning
  6788. and isolating attacks better.
  6789. - Only upload a new server descriptor when options change, 18
  6790. hours have passed, uptime is reset, or bandwidth changes a lot.
  6791. - Directory authorities silently throw away new descriptors that
  6792. haven't changed much if the timestamps are similar. We do this to
  6793. tolerate older Tor servers that upload a new descriptor every 15
  6794. minutes. (It seemed like a good idea at the time.)
  6795. - Clients choose directory servers from the network status lists,
  6796. not from their internal list of router descriptors. Now they can
  6797. go to caches directly rather than needing to go to authorities
  6798. to bootstrap the first set of descriptors.
  6799. - When picking a random directory, prefer non-authorities if any
  6800. are known.
  6801. - Add a new flag to network-status indicating whether the server
  6802. can answer v2 directory requests too.
  6803. - Directory mirrors now cache up to 16 unrecognized network-status
  6804. docs, so new directory authorities will be cached too.
  6805. - Stop parsing, storing, or using running-routers output (but
  6806. mirrors still cache and serve it).
  6807. - Clients consider a threshold of "versioning" directory authorities
  6808. before deciding whether to warn the user that he's obsolete.
  6809. - Authorities publish separate sorted lists of recommended versions
  6810. for clients and for servers.
  6811. - Change DirServers config line to note which dirs are v1 authorities.
  6812. - Put nicknames on the DirServer line, so we can refer to them
  6813. without requiring all our users to memorize their IP addresses.
  6814. - Remove option when getting directory cache to see whether they
  6815. support running-routers; they all do now. Replace it with one
  6816. to see whether caches support v2 stuff.
  6817. - Stop listing down or invalid nodes in the v1 directory. This
  6818. reduces its bulk by about 1/3, and reduces load on mirrors.
  6819. - Mirrors no longer cache the v1 directory as often.
  6820. - If we as a directory mirror don't know of any v1 directory
  6821. authorities, then don't try to cache any v1 directories.
  6822. o Other directory improvements:
  6823. - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
  6824. fifth authoritative directory servers.
  6825. - Directory authorities no longer require an open connection from
  6826. a server to consider him "reachable". We need this change because
  6827. when we add new directory authorities, old servers won't know not
  6828. to hang up on them.
  6829. - Dir authorities now do their own external reachability testing
  6830. of each server, and only list as running the ones they found to
  6831. be reachable. We also send back warnings to the server's logs if
  6832. it uploads a descriptor that we already believe is unreachable.
  6833. - Spread the directory authorities' reachability testing over the
  6834. entire testing interval, so we don't try to do 500 TLS's at once
  6835. every 20 minutes.
  6836. - Make the "stable" router flag in network-status be the median of
  6837. the uptimes of running valid servers, and make clients pay
  6838. attention to the network-status flags. Thus the cutoff adapts
  6839. to the stability of the network as a whole, making IRC, IM, etc
  6840. connections more reliable.
  6841. - Make the v2 dir's "Fast" flag based on relative capacity, just
  6842. like "Stable" is based on median uptime. Name everything in the
  6843. top 7/8 Fast, and only the top 1/2 gets to be a Guard.
  6844. - Retry directory requests if we fail to get an answer we like
  6845. from a given dirserver (we were retrying before, but only if
  6846. we fail to connect).
  6847. - Return a robots.txt on our dirport to discourage google indexing.
  6848. o Controller protocol improvements:
  6849. - Revised controller protocol (version 1) that uses ascii rather
  6850. than binary: tor/doc/control-spec.txt. Add supporting libraries
  6851. in python and java and c# so you can use the controller from your
  6852. applications without caring how our protocol works.
  6853. - Allow the DEBUG controller event to work again. Mark certain log
  6854. entries as "don't tell this to controllers", so we avoid cycles.
  6855. - New controller function "getinfo accounting", to ask how
  6856. many bytes we've used in this time period.
  6857. - Add a "resetconf" command so you can set config options like
  6858. AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
  6859. a config option in the torrc with no value, then it clears it
  6860. entirely (rather than setting it to its default).
  6861. - Add a "getinfo config-file" to tell us where torrc is. Also
  6862. expose guard nodes, config options/names.
  6863. - Add a "quit" command (when when using the controller manually).
  6864. - Add a new signal "newnym" to "change pseudonyms" -- that is, to
  6865. stop using any currently-dirty circuits for new streams, so we
  6866. don't link new actions to old actions. This also occurs on HUP
  6867. or "signal reload".
  6868. - If we would close a stream early (e.g. it asks for a .exit that
  6869. we know would refuse it) but the LeaveStreamsUnattached config
  6870. option is set by the controller, then don't close it.
  6871. - Add a new controller event type "authdir_newdescs" that allows
  6872. controllers to get all server descriptors that were uploaded to
  6873. a router in its role as directory authority.
  6874. - New controller option "getinfo desc/all-recent" to fetch the
  6875. latest server descriptor for every router that Tor knows about.
  6876. - Fix the controller's "attachstream 0" command to treat conn like
  6877. it just connected, doing address remapping, handling .exit and
  6878. .onion idioms, and so on. Now we're more uniform in making sure
  6879. that the controller hears about new and closing connections.
  6880. - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
  6881. the controller. Also, rotate dns and cpu workers if the controller
  6882. changes options that will affect them; and initialize the dns
  6883. worker cache tree whether or not we start out as a server.
  6884. - Add a new circuit purpose 'controller' to let the controller ask
  6885. for a circuit that Tor won't try to use. Extend the "extendcircuit"
  6886. controller command to let you specify the purpose if you're starting
  6887. a new circuit. Add a new "setcircuitpurpose" controller command to
  6888. let you change a circuit's purpose after it's been created.
  6889. - Let the controller ask for "getinfo dir/server/foo" so it can ask
  6890. directly rather than connecting to the dir port. "getinfo
  6891. dir/status/foo" also works, but currently only if your DirPort
  6892. is enabled.
  6893. - Let the controller tell us about certain router descriptors
  6894. that it doesn't want Tor to use in circuits. Implement
  6895. "setrouterpurpose" and modify "+postdescriptor" to do this.
  6896. - If the controller's *setconf commands fail, collect an error
  6897. message in a string and hand it back to the controller -- don't
  6898. just tell them to go read their logs.
  6899. o Scalability, resource management, and performance:
  6900. - Fix a major load balance bug: we were round-robin reading in 16 KB
  6901. chunks, and servers with bandwidthrate of 20 KB, while downloading
  6902. a 600 KB directory, would starve their other connections. Now we
  6903. try to be a bit more fair.
  6904. - Be more conservative about whether to advertise our DirPort.
  6905. The main change is to not advertise if we're running at capacity
  6906. and either a) we could hibernate ever or b) our capacity is low
  6907. and we're using a default DirPort.
  6908. - We weren't cannibalizing circuits correctly for
  6909. CIRCUIT_PURPOSE_C_ESTABLISH_REND and
  6910. CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
  6911. build those from scratch. This should make hidden services faster.
  6912. - Predict required circuits better, with an eye toward making hidden
  6913. services faster on the service end.
  6914. - Compress exit policies even more: look for duplicate lines and
  6915. remove them.
  6916. - Generate 18.0.0.0/8 address policy format in descs when we can;
  6917. warn when the mask is not reducible to a bit-prefix.
  6918. - There used to be two ways to specify your listening ports in a
  6919. server descriptor: on the "router" line and with a separate "ports"
  6920. line. Remove support for the "ports" line.
  6921. - Reduce memory requirements in our structs by changing the order
  6922. of fields. Replace balanced trees with hash tables. Inline
  6923. bottleneck smartlist functions. Add a "Map from digest to void*"
  6924. abstraction so we can do less hex encoding/decoding, and use it
  6925. in router_get_by_digest(). Many other CPU and memory improvements.
  6926. - Allow tor_gzip_uncompress to extract as much as possible from
  6927. truncated compressed data. Try to extract as many
  6928. descriptors as possible from truncated http responses (when
  6929. purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
  6930. - Make circ->onionskin a pointer, not a static array. moria2 was using
  6931. 125000 circuit_t's after it had been up for a few weeks, which
  6932. translates to 20+ megs of wasted space.
  6933. - The private half of our EDH handshake keys are now chosen out
  6934. of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
  6935. - Stop doing the complex voodoo overkill checking for insecure
  6936. Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
  6937. - Do round-robin writes for TLS of at most 16 kB per write. This
  6938. might be more fair on loaded Tor servers.
  6939. - Do not use unaligned memory access on alpha, mips, or mipsel.
  6940. It *works*, but is very slow, so we treat them as if it doesn't.
  6941. o Other bugfixes and improvements:
  6942. - Start storing useful information to $DATADIR/state, so we can
  6943. remember things across invocations of Tor. Retain unrecognized
  6944. lines so we can be forward-compatible, and write a TorVersion line
  6945. so we can be backward-compatible.
  6946. - If ORPort is set, Address is not explicitly set, and our hostname
  6947. resolves to a private IP address, try to use an interface address
  6948. if it has a public address. Now Windows machines that think of
  6949. themselves as localhost can guess their address.
  6950. - Regenerate our local descriptor if it's dirty and we try to use
  6951. it locally (e.g. if it changes during reachability detection).
  6952. This was causing some Tor servers to keep publishing the same
  6953. initial descriptor forever.
  6954. - Tor servers with dynamic IP addresses were needing to wait 18
  6955. hours before they could start doing reachability testing using
  6956. the new IP address and ports. This is because they were using
  6957. the internal descriptor to learn what to test, yet they were only
  6958. rebuilding the descriptor once they decided they were reachable.
  6959. - It turns out we couldn't bootstrap a network since we added
  6960. reachability detection in 0.1.0.1-rc. Good thing the Tor network
  6961. has never gone down. Add an AssumeReachable config option to let
  6962. servers and authorities bootstrap. When we're trying to build a
  6963. high-uptime or high-bandwidth circuit but there aren't enough
  6964. suitable servers, try being less picky rather than simply failing.
  6965. - Newly bootstrapped Tor networks couldn't establish hidden service
  6966. circuits until they had nodes with high uptime. Be more tolerant.
  6967. - Really busy servers were keeping enough circuits open on stable
  6968. connections that they were wrapping around the circuit_id
  6969. space. (It's only two bytes.) This exposed a bug where we would
  6970. feel free to reuse a circuit_id even if it still exists but has
  6971. been marked for close. Try to fix this bug. Some bug remains.
  6972. - When we fail to bind or listen on an incoming or outgoing
  6973. socket, we now close it before refusing, rather than just
  6974. leaking it. (Thanks to Peter Palfrader for finding.)
  6975. - Fix a file descriptor leak in start_daemon().
  6976. - On Windows, you can't always reopen a port right after you've
  6977. closed it. So change retry_listeners() to only close and re-open
  6978. ports that have changed.
  6979. - Workaround a problem with some http proxies that refuse GET
  6980. requests that specify "Content-Length: 0". Reported by Adrian.
  6981. - Recover better from TCP connections to Tor servers that are
  6982. broken but don't tell you (it happens!); and rotate TLS
  6983. connections once a week.
  6984. - Fix a scary-looking but apparently harmless bug where circuits
  6985. would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
  6986. servers, and never switch to state CIRCUIT_STATE_OPEN.
  6987. - Check for even more Windows version flags when writing the platform
  6988. string in server descriptors, and note any we don't recognize.
  6989. - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
  6990. get a better idea of why their circuits failed. Not used yet.
  6991. - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
  6992. We don't use them yet, but maybe one day our DNS resolver will be
  6993. able to discover them.
  6994. - Let people type "tor --install" as well as "tor -install" when they
  6995. want to make it an NT service.
  6996. - Looks like we were never delivering deflated (i.e. compressed)
  6997. running-routers lists, even when asked. Oops.
  6998. - We were leaking some memory every time the client changed IPs.
  6999. - Clean up more of the OpenSSL memory when exiting, so we can detect
  7000. memory leaks better.
  7001. - Never call free() on tor_malloc()d memory. This will help us
  7002. use dmalloc to detect memory leaks.
  7003. - Some Tor servers process billions of cells per day. These
  7004. statistics are now uint64_t's.
  7005. - Check [X-]Forwarded-For headers in HTTP requests when generating
  7006. log messages. This lets people run dirservers (and caches) behind
  7007. Apache but still know which IP addresses are causing warnings.
  7008. - Fix minor integer overflow in calculating when we expect to use up
  7009. our bandwidth allocation before hibernating.
  7010. - Lower the minimum required number of file descriptors to 1000,
  7011. so we can have some overhead for Valgrind on Linux, where the
  7012. default ulimit -n is 1024.
  7013. - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
  7014. and its existence is confusing some users.
  7015. o Config option fixes:
  7016. - Add a new config option ExitPolicyRejectPrivate which defaults
  7017. to on. Now all exit policies will begin with rejecting private
  7018. addresses, unless the server operator explicitly turns it off.
  7019. - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
  7020. - Add new ReachableORAddresses and ReachableDirAddresses options
  7021. that understand address policies. FascistFirewall is now a synonym
  7022. for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
  7023. - Start calling it FooListenAddress rather than FooBindAddress,
  7024. since few of our users know what it means to bind an address
  7025. or port.
  7026. - If the user gave Tor an odd number of command-line arguments,
  7027. we were silently ignoring the last one. Now we complain and fail.
  7028. This wins the oldest-bug prize -- this bug has been present since
  7029. November 2002, as released in Tor 0.0.0.
  7030. - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
  7031. torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
  7032. it would silently ignore the 6668.
  7033. - If we get a linelist or linelist_s config option from the torrc,
  7034. e.g. ExitPolicy, and it has no value, warn and skip rather than
  7035. silently resetting it to its default.
  7036. - Setconf was appending items to linelists, not clearing them.
  7037. - Add MyFamily to torrc.sample in the server section, so operators
  7038. will be more likely to learn that it exists.
  7039. - Make ContactInfo mandatory for authoritative directory servers.
  7040. - MaxConn has been obsolete for a while now. Document the ConnLimit
  7041. config option, which is a *minimum* number of file descriptors
  7042. that must be available else Tor refuses to start.
  7043. - Get rid of IgnoreVersion undocumented config option, and make us
  7044. only warn, never exit, when we're running an obsolete version.
  7045. - Make MonthlyAccountingStart config option truly obsolete now.
  7046. - Correct the man page entry on TrackHostExitsExpire.
  7047. - Let directory authorities start even if they don't specify an
  7048. Address config option.
  7049. - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
  7050. reflect the updated flags in our v2 dir protocol.
  7051. o Config option features:
  7052. - Add a new config option FastFirstHopPK (on by default) so clients
  7053. do a trivial crypto handshake for their first hop, since TLS has
  7054. already taken care of confidentiality and authentication.
  7055. - Let the user set ControlListenAddress in the torrc. This can be
  7056. dangerous, but there are some cases (like a secured LAN) where it
  7057. makes sense.
  7058. - New config options to help controllers: FetchServerDescriptors
  7059. and FetchHidServDescriptors for whether to fetch server
  7060. info and hidserv info or let the controller do it, and
  7061. PublishServerDescriptor and PublishHidServDescriptors.
  7062. - Also let the controller set the __AllDirActionsPrivate config
  7063. option if you want all directory fetches/publishes to happen via
  7064. Tor (it assumes your controller bootstraps your circuits).
  7065. - Add "HardwareAccel" config option: support for crypto hardware
  7066. accelerators via OpenSSL. Off by default, until we find somebody
  7067. smart who can test it for us. (It appears to produce seg faults
  7068. in at least some cases.)
  7069. - New config option "AuthDirRejectUnlisted" for directory authorities
  7070. as a panic button: if we get flooded with unusable servers we can
  7071. revert to only listing servers in the approved-routers file.
  7072. - Directory authorities can now reject/invalidate by key and IP,
  7073. with the config options "AuthDirInvalid" and "AuthDirReject", or
  7074. by marking a fingerprint as "!reject" or "!invalid" (as its
  7075. nickname) in the approved-routers file. This is useful since
  7076. currently we automatically list servers as running and usable
  7077. even if we know they're jerks.
  7078. - Add a new config option TestSocks so people can see whether their
  7079. applications are using socks4, socks4a, socks5-with-ip, or
  7080. socks5-with-fqdn. This way they don't have to keep mucking
  7081. with tcpdump and wondering if something got cached somewhere.
  7082. - Add "private:*" as an alias in configuration for policies. Now
  7083. you can simplify your exit policy rather than needing to list
  7084. every single internal or nonroutable network space.
  7085. - Accept "private:*" in routerdesc exit policies; not generated yet
  7086. because older Tors do not understand it.
  7087. - Add configuration option "V1AuthoritativeDirectory 1" which
  7088. moria1, moria2, and tor26 have set.
  7089. - Implement an option, VirtualAddrMask, to set which addresses
  7090. get handed out in response to mapaddress requests. This works
  7091. around a bug in tsocks where 127.0.0.0/8 is never socksified.
  7092. - Add a new config option FetchUselessDescriptors, off by default,
  7093. for when you plan to run "exitlist" on your client and you want
  7094. to know about even the non-running descriptors.
  7095. - SocksTimeout: How long do we let a socks connection wait
  7096. unattached before we fail it?
  7097. - CircuitBuildTimeout: Cull non-open circuits that were born
  7098. at least this many seconds ago.
  7099. - CircuitIdleTimeout: Cull open clean circuits that were born
  7100. at least this many seconds ago.
  7101. - New config option SafeSocks to reject all application connections
  7102. using unsafe socks protocols. Defaults to off.
  7103. o Improved and clearer log messages:
  7104. - Reduce clutter in server logs. We're going to try to make
  7105. them actually usable now. New config option ProtocolWarnings that
  7106. lets you hear about how _other Tors_ are breaking the protocol. Off
  7107. by default.
  7108. - Divide log messages into logging domains. Once we put some sort
  7109. of interface on this, it will let people looking at more verbose
  7110. log levels specify the topics they want to hear more about.
  7111. - Log server fingerprint on startup, so new server operators don't
  7112. have to go hunting around their filesystem for it.
  7113. - Provide dire warnings to any users who set DirServer manually;
  7114. move it out of torrc.sample and into torrc.complete.
  7115. - Make the log message less scary when all the dirservers are
  7116. temporarily unreachable.
  7117. - When tor_socketpair() fails in Windows, give a reasonable
  7118. Windows-style errno back.
  7119. - Improve tor_gettimeofday() granularity on windows.
  7120. - We were printing the number of idle dns workers incorrectly when
  7121. culling them.
  7122. - Handle duplicate lines in approved-routers files without warning.
  7123. - We were whining about using socks4 or socks5-with-local-lookup
  7124. even when it's an IP address in the "virtual" range we designed
  7125. exactly for this case.
  7126. - Check for named servers when looking them up by nickname;
  7127. warn when we're calling a non-named server by its nickname;
  7128. don't warn twice about the same name.
  7129. - Downgrade the dirserver log messages when whining about
  7130. unreachability.
  7131. - Correct "your server is reachable" log entries to indicate that
  7132. it was self-testing that told us so.
  7133. - If we're trying to be a Tor server and running Windows 95/98/ME
  7134. as a server, explain that we'll likely crash.
  7135. - Provide a more useful warn message when our onion queue gets full:
  7136. the CPU is too slow or the exit policy is too liberal.
  7137. - Don't warn when we receive a 503 from a dirserver/cache -- this
  7138. will pave the way for them being able to refuse if they're busy.
  7139. - When we fail to bind a listener, try to provide a more useful
  7140. log message: e.g., "Is Tor already running?"
  7141. - Only start testing reachability once we've established a
  7142. circuit. This will make startup on dir authorities less noisy.
  7143. - Don't try to upload hidden service descriptors until we have
  7144. established a circuit.
  7145. - Tor didn't warn when it failed to open a log file.
  7146. - Warn when listening on a public address for socks. We suspect a
  7147. lot of people are setting themselves up as open socks proxies,
  7148. and they have no idea that jerks on the Internet are using them,
  7149. since they simply proxy the traffic into the Tor network.
  7150. - Give a useful message when people run Tor as the wrong user,
  7151. rather than telling them to start chowning random directories.
  7152. - Fix a harmless bug that was causing Tor servers to log
  7153. "Got an end because of misc error, but we're not an AP. Closing."
  7154. - Fix wrong log message when you add a "HiddenServiceNodes" config
  7155. line without any HiddenServiceDir line (reported by Chris Thomas).
  7156. - Directory authorities now stop whining so loudly about bad
  7157. descriptors that they fetch from other dirservers. So when there's
  7158. a log complaint, it's for sure from a freshly uploaded descriptor.
  7159. - When logging via syslog, include the pid whenever we provide
  7160. a log entry. Suggested by Todd Fries.
  7161. - When we're shutting down and we do something like try to post a
  7162. server descriptor or rendezvous descriptor, don't complain that
  7163. we seem to be unreachable. Of course we are, we're shutting down.
  7164. - Change log line for unreachability to explicitly suggest /etc/hosts
  7165. as the culprit. Also make it clearer what IP address and ports we're
  7166. testing for reachability.
  7167. - Put quotes around user-supplied strings when logging so users are
  7168. more likely to realize if they add bad characters (like quotes)
  7169. to the torrc.
  7170. - NT service patch from Matt Edman to improve error messages on Win32.
  7171. Changes in version 0.1.0.17 - 2006-02-17
  7172. o Crash bugfixes on 0.1.0.x:
  7173. - When servers with a non-zero DirPort came out of hibernation,
  7174. sometimes they would trigger an assert.
  7175. o Other important bugfixes:
  7176. - On platforms that don't have getrlimit (like Windows), we were
  7177. artificially constraining ourselves to a max of 1024
  7178. connections. Now just assume that we can handle as many as 15000
  7179. connections. Hopefully this won't cause other problems.
  7180. o Backported features:
  7181. - When we're a server, a client asks for an old-style directory,
  7182. and our write bucket is empty, don't give it to him. This way
  7183. small servers can continue to serve the directory *sometimes*,
  7184. without getting overloaded.
  7185. - Whenever you get a 503 in response to a directory fetch, try
  7186. once more. This will become important once servers start sending
  7187. 503's whenever they feel busy.
  7188. - Fetch a new directory every 120 minutes, not every 40 minutes.
  7189. Now that we have hundreds of thousands of users running the old
  7190. directory algorithm, it's starting to hurt a lot.
  7191. - Bump up the period for forcing a hidden service descriptor upload
  7192. from 20 minutes to 1 hour.
  7193. Changes in version 0.1.0.16 - 2006-01-02
  7194. o Crash bugfixes on 0.1.0.x:
  7195. - On Windows, build with a libevent patch from "I-M Weasel" to avoid
  7196. corrupting the heap, losing FDs, or crashing when we need to resize
  7197. the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
  7198. - It turns out sparc64 platforms crash on unaligned memory access
  7199. too -- so detect and avoid this.
  7200. - Handle truncated compressed data correctly (by detecting it and
  7201. giving an error).
  7202. - Fix possible-but-unlikely free(NULL) in control.c.
  7203. - When we were closing connections, there was a rare case that
  7204. stomped on memory, triggering seg faults and asserts.
  7205. - Avoid potential infinite recursion when building a descriptor. (We
  7206. don't know that it ever happened, but better to fix it anyway.)
  7207. - We were neglecting to unlink marked circuits from soon-to-close OR
  7208. connections, which caused some rare scribbling on freed memory.
  7209. - Fix a memory stomping race bug when closing the joining point of two
  7210. rendezvous circuits.
  7211. - Fix an assert in time parsing found by Steven Murdoch.
  7212. o Other bugfixes on 0.1.0.x:
  7213. - When we're doing reachability testing, provide more useful log
  7214. messages so the operator knows what to expect.
  7215. - Do not check whether DirPort is reachable when we are suppressing
  7216. advertising it because of hibernation.
  7217. - When building with -static or on Solaris, we sometimes needed -ldl.
  7218. - One of the dirservers (tor26) changed its IP address.
  7219. - When we're deciding whether a stream has enough circuits around
  7220. that can handle it, count the freshly dirty ones and not the ones
  7221. that are so dirty they won't be able to handle it.
  7222. - When we're expiring old circuits, we had a logic error that caused
  7223. us to close new rendezvous circuits rather than old ones.
  7224. - Give a more helpful log message when you try to change ORPort via
  7225. the controller: you should upgrade Tor if you want that to work.
  7226. - We were failing to parse Tor versions that start with "Tor ".
  7227. - Tolerate faulty streams better: when a stream fails for reason
  7228. exitpolicy, stop assuming that the router is lying about his exit
  7229. policy. When a stream fails for reason misc, allow it to retry just
  7230. as if it was resolvefailed. When a stream has failed three times,
  7231. reset its failure count so we can try again and get all three tries.
  7232. Changes in version 0.1.0.15 - 2005-09-23
  7233. o Bugfixes on 0.1.0.x:
  7234. - Reject ports 465 and 587 (spam targets) in default exit policy.
  7235. - Don't crash when we don't have any spare file descriptors and we
  7236. try to spawn a dns or cpu worker.
  7237. - Get rid of IgnoreVersion undocumented config option, and make us
  7238. only warn, never exit, when we're running an obsolete version.
  7239. - Don't try to print a null string when your server finds itself to
  7240. be unreachable and the Address config option is empty.
  7241. - Make the numbers in read-history and write-history into uint64s,
  7242. so they don't overflow and publish negatives in the descriptor.
  7243. - Fix a minor memory leak in smartlist_string_remove().
  7244. - We were only allowing ourselves to upload a server descriptor at
  7245. most every 20 minutes, even if it changed earlier than that.
  7246. - Clean up log entries that pointed to old URLs.
  7247. Changes in version 0.1.0.14 - 2005-08-08
  7248. o Bugfixes on 0.1.0.x:
  7249. - Fix the other half of the bug with crypto handshakes
  7250. (CVE-2005-2643).
  7251. - Fix an assert trigger if you send a 'signal term' via the
  7252. controller when it's listening for 'event info' messages.
  7253. Changes in version 0.1.0.13 - 2005-08-04
  7254. o Bugfixes on 0.1.0.x:
  7255. - Fix a critical bug in the security of our crypto handshakes.
  7256. - Fix a size_t underflow in smartlist_join_strings2() that made
  7257. it do bad things when you hand it an empty smartlist.
  7258. - Fix Windows installer to ship Tor license (thanks to Aphex for
  7259. pointing out this oversight) and put a link to the doc directory
  7260. in the start menu.
  7261. - Explicitly set no-unaligned-access for sparc: it turns out the
  7262. new gcc's let you compile broken code, but that doesn't make it
  7263. not-broken.
  7264. Changes in version 0.1.0.12 - 2005-07-18
  7265. o New directory servers:
  7266. - tor26 has changed IP address.
  7267. o Bugfixes on 0.1.0.x:
  7268. - Fix a possible double-free in tor_gzip_uncompress().
  7269. - When --disable-threads is set, do not search for or link against
  7270. pthreads libraries.
  7271. - Don't trigger an assert if an authoritative directory server
  7272. claims its dirport is 0.
  7273. - Fix bug with removing Tor as an NT service: some people were
  7274. getting "The service did not return an error." Thanks to Matt
  7275. Edman for the fix.
  7276. Changes in version 0.1.0.11 - 2005-06-30
  7277. o Bugfixes on 0.1.0.x:
  7278. - Fix major security bug: servers were disregarding their
  7279. exit policies if clients behaved unexpectedly.
  7280. - Make OS X init script check for missing argument, so we don't
  7281. confuse users who invoke it incorrectly.
  7282. - Fix a seg fault in "tor --hash-password foo".
  7283. - The MAPADDRESS control command was broken.
  7284. Changes in version 0.1.0.10 - 2005-06-14
  7285. o Fixes on Win32:
  7286. - Make NT services work and start on startup on Win32 (based on
  7287. patch by Matt Edman). See the FAQ entry for details.
  7288. - Make 'platform' string in descriptor more accurate for Win32
  7289. servers, so it's not just "unknown platform".
  7290. - REUSEADDR on normal platforms means you can rebind to the port
  7291. right after somebody else has let it go. But REUSEADDR on Win32
  7292. means you can bind to the port _even when somebody else already
  7293. has it bound_! So, don't do that on Win32.
  7294. - Clean up the log messages when starting on Win32 with no config
  7295. file.
  7296. - Allow seeding the RNG on Win32 even when you're not running as
  7297. Administrator. If seeding the RNG on Win32 fails, quit.
  7298. o Assert / crash bugs:
  7299. - Refuse relay cells that claim to have a length larger than the
  7300. maximum allowed. This prevents a potential attack that could read
  7301. arbitrary memory (e.g. keys) from an exit server's process
  7302. (CVE-2005-2050).
  7303. - If unofficial Tor clients connect and send weird TLS certs, our
  7304. Tor server triggers an assert. Stop asserting, and start handling
  7305. TLS errors better in other situations too.
  7306. - Fix a race condition that can trigger an assert when we have a
  7307. pending create cell and an OR connection attempt fails.
  7308. o Resource leaks:
  7309. - Use pthreads for worker processes rather than forking. This was
  7310. forced because when we forked, we ended up wasting a lot of
  7311. duplicate ram over time.
  7312. - Also switch to foo_r versions of some library calls to allow
  7313. reentry and threadsafeness.
  7314. - Implement --disable-threads configure option. Disable threads on
  7315. netbsd and openbsd by default, because they have no reentrant
  7316. resolver functions (!), and on solaris since it has other
  7317. threading issues.
  7318. - Fix possible bug on threading platforms (e.g. win32) which was
  7319. leaking a file descriptor whenever a cpuworker or dnsworker died.
  7320. - Fix a minor memory leak when somebody establishes an introduction
  7321. point at your Tor server.
  7322. - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
  7323. Adam Langley.)
  7324. - Add ./configure --with-dmalloc option, to track memory leaks.
  7325. - And try to free all memory on closing, so we can detect what
  7326. we're leaking.
  7327. o Protocol correctness:
  7328. - When we've connected to an OR and handshaked but didn't like
  7329. the result, we were closing the conn without sending destroy
  7330. cells back for pending circuits. Now send those destroys.
  7331. - Start sending 'truncated' cells back rather than destroy cells
  7332. if the circuit closes in front of you. This means we won't have
  7333. to abandon partially built circuits.
  7334. - Handle changed router status correctly when dirserver reloads
  7335. fingerprint file. We used to be dropping all unverified descriptors
  7336. right then. The bug was hidden because we would immediately
  7337. fetch a directory from another dirserver, which would include the
  7338. descriptors we just dropped.
  7339. - Revise tor-spec to add more/better stream end reasons.
  7340. - Revise all calls to connection_edge_end to avoid sending 'misc',
  7341. and to take errno into account where possible.
  7342. - Client now retries when streams end early for 'hibernating' or
  7343. 'resource limit' reasons, rather than failing them.
  7344. - Try to be more zealous about calling connection_edge_end when
  7345. things go bad with edge conns in connection.c.
  7346. o Robustness improvements:
  7347. - Better handling for heterogeneous / unreliable nodes:
  7348. - Annotate circuits with whether they aim to contain high uptime
  7349. nodes and/or high capacity nodes. When building circuits, choose
  7350. appropriate nodes.
  7351. - This means that every single node in an intro rend circuit,
  7352. not just the last one, will have a minimum uptime.
  7353. - New config option LongLivedPorts to indicate application streams
  7354. that will want high uptime circuits.
  7355. - Servers reset uptime when a dir fetch entirely fails. This
  7356. hopefully reflects stability of the server's network connectivity.
  7357. - If somebody starts his tor server in Jan 2004 and then fixes his
  7358. clock, don't make his published uptime be a year.
  7359. - Reset published uptime when we wake up from hibernation.
  7360. - Introduce a notion of 'internal' circs, which are chosen without
  7361. regard to the exit policy of the last hop. Intro and rendezvous
  7362. circs must be internal circs, to avoid leaking information. Resolve
  7363. and connect streams can use internal circs if they want.
  7364. - New circuit pooling algorithm: keep track of what destination ports
  7365. we've used recently (start out assuming we'll want to use 80), and
  7366. make sure to have enough circs around to satisfy these ports. Also
  7367. make sure to have 2 internal circs around if we've required internal
  7368. circs lately (and with high uptime if we've seen that lately too).
  7369. - Turn addr_policy_compare from a tristate to a quadstate; this should
  7370. help address our "Ah, you allow 1.2.3.4:80. You are a good choice
  7371. for google.com" problem.
  7372. - When a client asks us for a dir mirror and we don't have one,
  7373. launch an attempt to get a fresh one.
  7374. - First cut at support for "create-fast" cells. Clients can use
  7375. these when extending to their first hop, since the TLS already
  7376. provides forward secrecy and authentication. Not enabled on
  7377. clients yet.
  7378. o Reachability testing.
  7379. - Your Tor server will automatically try to see if its ORPort and
  7380. DirPort are reachable from the outside, and it won't upload its
  7381. descriptor until it decides at least ORPort is reachable (when
  7382. DirPort is not yet found reachable, publish it as zero).
  7383. - When building testing circs for ORPort testing, use only
  7384. high-bandwidth nodes, so fewer circuits fail.
  7385. - Notice when our IP changes, and reset stats/uptime/reachability.
  7386. - Authdirservers don't do ORPort reachability detection, since
  7387. they're in clique mode, so it will be rare to find a server not
  7388. already connected to them.
  7389. - Authdirservers now automatically approve nodes running 0.1.0.2-rc
  7390. or later.
  7391. o Dirserver fixes:
  7392. - Now we allow two unverified servers with the same nickname
  7393. but different keys. But if a nickname is verified, only that
  7394. nickname+key are allowed.
  7395. - If you're an authdirserver connecting to an address:port,
  7396. and it's not the OR you were expecting, forget about that
  7397. descriptor. If he *was* the one you were expecting, then forget
  7398. about all other descriptors for that address:port.
  7399. - Allow servers to publish descriptors from 12 hours in the future.
  7400. Corollary: only whine about clock skew from the dirserver if
  7401. he's a trusted dirserver (since now even verified servers could
  7402. have quite wrong clocks).
  7403. - Require servers that use the default dirservers to have public IP
  7404. addresses. We have too many servers that are configured with private
  7405. IPs and their admins never notice the log entries complaining that
  7406. their descriptors are being rejected.
  7407. o Efficiency improvements:
  7408. - Use libevent. Now we can use faster async cores (like epoll, kpoll,
  7409. and /dev/poll), and hopefully work better on Windows too.
  7410. - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
  7411. kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
  7412. - Find libevent even if it's hiding in /usr/local/ and your
  7413. CFLAGS and LDFLAGS don't tell you to look there.
  7414. - Be able to link with libevent as a shared library (the default
  7415. after 1.0d), even if it's hiding in /usr/local/lib and even
  7416. if you haven't added /usr/local/lib to your /etc/ld.so.conf,
  7417. assuming you're running gcc. Otherwise fail and give a useful
  7418. error message.
  7419. - Switch to a new buffer management algorithm, which tries to avoid
  7420. reallocing and copying quite as much. In first tests it looks like
  7421. it uses *more* memory on average, but less cpu.
  7422. - Switch our internal buffers implementation to use a ring buffer,
  7423. to hopefully improve performance for fast servers a lot.
  7424. - Reenable the part of the code that tries to flush as soon as an
  7425. OR outbuf has a full TLS record available. Perhaps this will make
  7426. OR outbufs not grow as huge except in rare cases, thus saving lots
  7427. of CPU time plus memory.
  7428. - Improve performance for dirservers: stop re-parsing the whole
  7429. directory every time you regenerate it.
  7430. - Keep a big splay tree of (circid,orconn)->circuit mappings to make
  7431. it much faster to look up a circuit for each relay cell.
  7432. - Remove most calls to assert_all_pending_dns_resolves_ok(),
  7433. since they're eating our cpu on exit nodes.
  7434. - Stop wasting time doing a case insensitive comparison for every
  7435. dns name every time we do any lookup. Canonicalize the names to
  7436. lowercase when you first see them.
  7437. o Hidden services:
  7438. - Handle unavailable hidden services better. Handle slow or busy
  7439. hidden services better.
  7440. - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
  7441. circ as necessary, if there are any completed ones lying around
  7442. when we try to launch one.
  7443. - Make hidden services try to establish a rendezvous for 30 seconds
  7444. after fetching the descriptor, rather than for n (where n=3)
  7445. attempts to build a circuit.
  7446. - Adjust maximum skew and age for rendezvous descriptors: let skew
  7447. be 48 hours rather than 90 minutes.
  7448. - Reject malformed .onion addresses rather then passing them on as
  7449. normal web requests.
  7450. o Controller:
  7451. - More Tor controller support. See
  7452. http://tor.eff.org/doc/control-spec.txt for all the new features,
  7453. including signals to emulate unix signals from any platform;
  7454. redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
  7455. closestream; closecircuit; etc.
  7456. - Encode hashed controller passwords in hex instead of base64,
  7457. to make it easier to write controllers.
  7458. - Revise control spec and implementation to allow all log messages to
  7459. be sent to controller with their severities intact (suggested by
  7460. Matt Edman). Disable debug-level logs while delivering a debug-level
  7461. log to the controller, to prevent loop. Update TorControl to handle
  7462. new log event types.
  7463. o New config options/defaults:
  7464. - Begin scrubbing sensitive strings from logs by default. Turn off
  7465. the config option SafeLogging if you need to do debugging.
  7466. - New exit policy: accept most low-numbered ports, rather than
  7467. rejecting most low-numbered ports.
  7468. - Put a note in the torrc about abuse potential with the default
  7469. exit policy.
  7470. - Add support for CONNECTing through https proxies, with "HttpsProxy"
  7471. config option.
  7472. - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
  7473. based on patch from Adam Langley (basic auth only).
  7474. - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
  7475. the fast servers that have been joining lately. (Clients are now
  7476. willing to load balance over up to 2 MB of advertised bandwidth
  7477. capacity too.)
  7478. - New config option MaxAdvertisedBandwidth which lets you advertise
  7479. a low bandwidthrate (to not attract as many circuits) while still
  7480. allowing a higher bandwidthrate in reality.
  7481. - Require BandwidthRate to be at least 20kB/s for servers.
  7482. - Add a NoPublish config option, so you can be a server (e.g. for
  7483. testing running Tor servers in other Tor networks) without
  7484. publishing your descriptor to the primary dirservers.
  7485. - Add a new AddressMap config directive to rewrite incoming socks
  7486. addresses. This lets you, for example, declare an implicit
  7487. required exit node for certain sites.
  7488. - Add a new TrackHostExits config directive to trigger addressmaps
  7489. for certain incoming socks addresses -- for sites that break when
  7490. your exit keeps changing (based on patch from Mike Perry).
  7491. - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
  7492. which describes how often we retry making new circuits if current
  7493. ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
  7494. how long we're willing to make use of an already-dirty circuit.
  7495. - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
  7496. a config option "ShutdownWaitLength" (when using kill -INT on
  7497. servers).
  7498. - Fix an edge case in parsing config options: if they say "--"
  7499. on the commandline, it's not a config option (thanks weasel).
  7500. - New config option DirAllowPrivateAddresses for authdirservers.
  7501. Now by default they refuse router descriptors that have non-IP or
  7502. private-IP addresses.
  7503. - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
  7504. smart" default value: low for servers and high for clients.
  7505. - Some people were putting "Address " in their torrc, and they had
  7506. a buggy resolver that resolved " " to 0.0.0.0. Oops.
  7507. - If DataDir is ~/.tor, and that expands to /.tor, then default to
  7508. LOCALSTATEDIR/tor instead.
  7509. - Implement --verify-config command-line option to check if your torrc
  7510. is valid without actually launching Tor.
  7511. o Logging improvements:
  7512. - When dirservers refuse a server descriptor, we now log its
  7513. contactinfo, platform, and the poster's IP address.
  7514. - Only warn once per nickname from add_nickname_list_to_smartlist()
  7515. per failure, so an entrynode or exitnode choice that's down won't
  7516. yell so much.
  7517. - When we're connecting to an OR and he's got a different nickname/key
  7518. than we were expecting, only complain loudly if we're an OP or a
  7519. dirserver. Complaining loudly to the OR admins just confuses them.
  7520. - Whine at you if you're a server and you don't set your contactinfo.
  7521. - Warn when exit policy implicitly allows local addresses.
  7522. - Give a better warning when some other server advertises an
  7523. ORPort that is actually an apache running ssl.
  7524. - If we get an incredibly skewed timestamp from a dirserver mirror
  7525. that isn't a verified OR, don't warn -- it's probably him that's
  7526. wrong.
  7527. - When a dirserver causes you to give a warn, mention which dirserver
  7528. it was.
  7529. - Initialize libevent later in the startup process, so the logs are
  7530. already established by the time we start logging libevent warns.
  7531. - Use correct errno on win32 if libevent fails.
  7532. - Check and warn about known-bad/slow libevent versions.
  7533. - Stop warning about sigpipes in the logs. We're going to
  7534. pretend that getting these occassionally is normal and fine.
  7535. o New contrib scripts:
  7536. - New experimental script tor/contrib/exitlist: a simple python
  7537. script to parse directories and find Tor nodes that exit to listed
  7538. addresses/ports.
  7539. - New experimental script tor/contrib/ExerciseServer.py (needs more
  7540. work) that uses the controller interface to build circuits and
  7541. fetch pages over them. This will help us bootstrap servers that
  7542. have lots of capacity but haven't noticed it yet.
  7543. - New experimental script tor/contrib/PathDemo.py (needs more work)
  7544. that uses the controller interface to let you choose whole paths
  7545. via addresses like
  7546. "<hostname>.<path,separated by dots>.<length of path>.path"
  7547. - New contributed script "privoxy-tor-toggle" to toggle whether
  7548. Privoxy uses Tor. Seems to be configured for Debian by default.
  7549. - Have torctl.in/tor.sh.in check for location of su binary (needed
  7550. on FreeBSD)
  7551. o Misc bugfixes:
  7552. - chdir() to your datadirectory at the *end* of the daemonize process,
  7553. not the beginning. This was a problem because the first time you
  7554. run tor, if your datadir isn't there, and you have runasdaemon set
  7555. to 1, it will try to chdir to it before it tries to create it. Oops.
  7556. - Fix several double-mark-for-close bugs, e.g. where we were finding
  7557. a conn for a cell even if that conn is already marked for close.
  7558. - Stop most cases of hanging up on a socks connection without sending
  7559. the socks reject.
  7560. - Fix a bug in the RPM package: set home directory for _tor to
  7561. something more reasonable when first installing.
  7562. - Stop putting nodename in the Platform string in server descriptors.
  7563. It doesn't actually help, and it is confusing/upsetting some people.
  7564. - When using preferred entry or exit nodes, ignore whether the
  7565. circuit wants uptime or capacity. They asked for the nodes, they
  7566. get the nodes.
  7567. - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
  7568. artificially capped at 500kB.
  7569. - Cache local dns resolves correctly even when they're .exit
  7570. addresses.
  7571. - If we're hibernating and we get a SIGINT, exit immediately.
  7572. - tor-resolve requests were ignoring .exit if there was a working circuit
  7573. they could use instead.
  7574. - Pay more attention to the ClientOnly config option.
  7575. - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
  7576. installer screens; and don't put stuff into StartupItems unless
  7577. the user asks you to.
  7578. o Misc features:
  7579. - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
  7580. rather than just rejecting it.
  7581. - If our clock jumps forward by 100 seconds or more, assume something
  7582. has gone wrong with our network and abandon all not-yet-used circs.
  7583. - When an application is using socks5, give him the whole variety of
  7584. potential socks5 responses (connect refused, host unreachable, etc),
  7585. rather than just "success" or "failure".
  7586. - A more sane version numbering system. See
  7587. http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
  7588. - Change version parsing logic: a version is "obsolete" if it is not
  7589. recommended and (1) there is a newer recommended version in the
  7590. same series, or (2) there are no recommended versions in the same
  7591. series, but there are some recommended versions in a newer series.
  7592. A version is "new" if it is newer than any recommended version in
  7593. the same series.
  7594. - Report HTTP reasons to client when getting a response from directory
  7595. servers -- so you can actually know what went wrong.
  7596. - Reject odd-looking addresses at the client (e.g. addresses that
  7597. contain a colon), rather than having the server drop them because
  7598. they're malformed.
  7599. - Stop publishing socksport in the directory, since it's not
  7600. actually meant to be public. For compatibility, publish a 0 there
  7601. for now.
  7602. - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
  7603. cookies to disk and doesn't log each web request to disk. (Thanks
  7604. to Brett Carrington for pointing this out.)
  7605. - Add OSX uninstall instructions. An actual uninstall script will
  7606. come later.
  7607. - Add "opt hibernating 1" to server descriptor to make it clearer
  7608. whether the server is hibernating.
  7609. Changes in version 0.0.9.10 - 2005-06-16
  7610. o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
  7611. - Refuse relay cells that claim to have a length larger than the
  7612. maximum allowed. This prevents a potential attack that could read
  7613. arbitrary memory (e.g. keys) from an exit server's process
  7614. (CVE-2005-2050).
  7615. Changes in version 0.0.9.9 - 2005-04-23
  7616. o Bugfixes on 0.0.9.x:
  7617. - If unofficial Tor clients connect and send weird TLS certs, our
  7618. Tor server triggers an assert. This release contains a minimal
  7619. backport from the broader fix that we put into 0.1.0.4-rc.
  7620. Changes in version 0.0.9.8 - 2005-04-07
  7621. o Bugfixes on 0.0.9.x:
  7622. - We have a bug that I haven't found yet. Sometimes, very rarely,
  7623. cpuworkers get stuck in the 'busy' state, even though the cpuworker
  7624. thinks of itself as idle. This meant that no new circuits ever got
  7625. established. Here's a workaround to kill any cpuworker that's been
  7626. busy for more than 100 seconds.
  7627. Changes in version 0.0.9.7 - 2005-04-01
  7628. o Bugfixes on 0.0.9.x:
  7629. - Fix another race crash bug (thanks to Glenn Fink for reporting).
  7630. - Compare identity to identity, not to nickname, when extending to
  7631. a router not already in the directory. This was preventing us from
  7632. extending to unknown routers. Oops.
  7633. - Make sure to create OS X Tor user in <500 range, so we aren't
  7634. creating actual system users.
  7635. - Note where connection-that-hasn't-sent-end was marked, and fix
  7636. a few really loud instances of this harmless bug (it's fixed more
  7637. in 0.1.0.x).
  7638. Changes in version 0.0.9.6 - 2005-03-24
  7639. o Bugfixes on 0.0.9.x (crashes and asserts):
  7640. - Add new end stream reasons to maintainance branch. Fix bug where
  7641. reason (8) could trigger an assert. Prevent bug from recurring.
  7642. - Apparently win32 stat wants paths to not end with a slash.
  7643. - Fix assert triggers in assert_cpath_layer_ok(), where we were
  7644. blowing away the circuit that conn->cpath_layer points to, then
  7645. checking to see if the circ is well-formed. Backport check to make
  7646. sure we dont use the cpath on a closed connection.
  7647. - Prevent circuit_resume_edge_reading_helper() from trying to package
  7648. inbufs for marked-for-close streams.
  7649. - Don't crash on hup if your options->address has become unresolvable.
  7650. - Some systems (like OS X) sometimes accept() a connection and tell
  7651. you the remote host is 0.0.0.0:0. If this happens, due to some
  7652. other mis-features, we get confused; so refuse the conn for now.
  7653. o Bugfixes on 0.0.9.x (other):
  7654. - Fix harmless but scary "Unrecognized content encoding" warn message.
  7655. - Add new stream error reason: TORPROTOCOL reason means "you are not
  7656. speaking a version of Tor I understand; say bye-bye to your stream."
  7657. - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
  7658. into the future, now that we are more tolerant of skew. This
  7659. resolves a bug where a Tor server would refuse to cache a directory
  7660. because all the directories it gets are too far in the future;
  7661. yet the Tor server never logs any complaints about clock skew.
  7662. - Mac packaging magic: make man pages useable, and do not overwrite
  7663. existing torrc files.
  7664. - Make OS X log happily to /var/log/tor/tor.log
  7665. Changes in version 0.0.9.5 - 2005-02-22
  7666. o Bugfixes on 0.0.9.x:
  7667. - Fix an assert race at exit nodes when resolve requests fail.
  7668. - Stop picking unverified dir mirrors--it only leads to misery.
  7669. - Patch from Matt Edman to make NT services work better. Service
  7670. support is still not compiled into the executable by default.
  7671. - Patch from Dmitri Bely so the Tor service runs better under
  7672. the win32 SYSTEM account.
  7673. - Make tor-resolve actually work (?) on Win32.
  7674. - Fix a sign bug when getrlimit claims to have 4+ billion
  7675. file descriptors available.
  7676. - Stop refusing to start when bandwidthburst == bandwidthrate.
  7677. - When create cells have been on the onion queue more than five
  7678. seconds, just send back a destroy and take them off the list.
  7679. Changes in version 0.0.9.4 - 2005-02-03
  7680. o Bugfixes on 0.0.9:
  7681. - Fix an assert bug that took down most of our servers: when
  7682. a server claims to have 1 GB of bandwidthburst, don't
  7683. freak out.
  7684. - Don't crash as badly if we have spawned the max allowed number
  7685. of dnsworkers, or we're out of file descriptors.
  7686. - Block more file-sharing ports in the default exit policy.
  7687. - MaxConn is now automatically set to the hard limit of max
  7688. file descriptors we're allowed (ulimit -n), minus a few for
  7689. logs, etc.
  7690. - Give a clearer message when servers need to raise their
  7691. ulimit -n when they start running out of file descriptors.
  7692. - SGI Compatibility patches from Jan Schaumann.
  7693. - Tolerate a corrupt cached directory better.
  7694. - When a dirserver hasn't approved your server, list which one.
  7695. - Go into soft hibernation after 95% of the bandwidth is used,
  7696. not 99%. This is especially important for daily hibernators who
  7697. have a small accounting max. Hopefully it will result in fewer
  7698. cut connections when the hard hibernation starts.
  7699. - Load-balance better when using servers that claim more than
  7700. 800kB/s of capacity.
  7701. - Make NT services work (experimental, only used if compiled in).
  7702. Changes in version 0.0.9.3 - 2005-01-21
  7703. o Bugfixes on 0.0.9:
  7704. - Backport the cpu use fixes from main branch, so busy servers won't
  7705. need as much processor time.
  7706. - Work better when we go offline and then come back, or when we
  7707. run Tor at boot before the network is up. We do this by
  7708. optimistically trying to fetch a new directory whenever an
  7709. application request comes in and we think we're offline -- the
  7710. human is hopefully a good measure of when the network is back.
  7711. - Backport some minimal hidserv bugfixes: keep rend circuits open as
  7712. long as you keep using them; actually publish hidserv descriptors
  7713. shortly after they change, rather than waiting 20-40 minutes.
  7714. - Enable Mac startup script by default.
  7715. - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
  7716. - When you update AllowUnverifiedNodes or FirewallPorts via the
  7717. controller's setconf feature, we were always appending, never
  7718. resetting.
  7719. - When you update HiddenServiceDir via setconf, it was screwing up
  7720. the order of reading the lines, making it fail.
  7721. - Do not rewrite a cached directory back to the cache; otherwise we
  7722. will think it is recent and not fetch a newer one on startup.
  7723. - Workaround for webservers that lie about Content-Encoding: Tor
  7724. now tries to autodetect compressed directories and compression
  7725. itself. This lets us Proxypass dir fetches through apache.
  7726. Changes in version 0.0.9.2 - 2005-01-04
  7727. o Bugfixes on 0.0.9 (crashes and asserts):
  7728. - Fix an assert on startup when the disk is full and you're logging
  7729. to a file.
  7730. - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
  7731. style address, then we'd crash.
  7732. - Fix an assert trigger when the running-routers string we get from
  7733. a dirserver is broken.
  7734. - Make worker threads start and run on win32. Now win32 servers
  7735. may work better.
  7736. - Bandaid (not actually fix, but now it doesn't crash) an assert
  7737. where the dns worker dies mysteriously and the main Tor process
  7738. doesn't remember anything about the address it was resolving.
  7739. o Bugfixes on 0.0.9 (Win32):
  7740. - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
  7741. name out of the warning/assert messages.
  7742. - Fix a superficial "unhandled error on read" bug on win32.
  7743. - The win32 installer no longer requires a click-through for our
  7744. license, since our Free Software license grants rights but does not
  7745. take any away.
  7746. - Win32: When connecting to a dirserver fails, try another one
  7747. immediately. (This was already working for non-win32 Tors.)
  7748. - Stop trying to parse $HOME on win32 when hunting for default
  7749. DataDirectory.
  7750. - Make tor-resolve.c work on win32 by calling network_init().
  7751. o Bugfixes on 0.0.9 (other):
  7752. - Make 0.0.9.x build on Solaris again.
  7753. - Due to a fencepost error, we were blowing away the \n when reporting
  7754. confvalue items in the controller. So asking for multiple config
  7755. values at once couldn't work.
  7756. - When listing circuits that are pending on an opening OR connection,
  7757. if we're an OR we were listing circuits that *end* at us as
  7758. being pending on every listener, dns/cpu worker, etc. Stop that.
  7759. - Dirservers were failing to create 'running-routers' or 'directory'
  7760. strings if we had more than some threshold of routers. Fix them so
  7761. they can handle any number of routers.
  7762. - Fix a superficial "Duplicate mark for close" bug.
  7763. - Stop checking for clock skew for OR connections, even for servers.
  7764. - Fix a fencepost error that was chopping off the last letter of any
  7765. nickname that is the maximum allowed nickname length.
  7766. - Update URLs in log messages so they point to the new website.
  7767. - Fix a potential problem in mangling server private keys while
  7768. writing to disk (not triggered yet, as far as we know).
  7769. - Include the licenses for other free software we include in Tor,
  7770. now that we're shipping binary distributions more regularly.
  7771. Changes in version 0.0.9.1 - 2004-12-15
  7772. o Bugfixes on 0.0.9:
  7773. - Make hibernation actually work.
  7774. - Make HashedControlPassword config option work.
  7775. - When we're reporting event circuit status to a controller,
  7776. don't use the stream status code.
  7777. Changes in version 0.0.9 - 2004-12-12
  7778. o Bugfixes on 0.0.8.1 (Crashes and asserts):
  7779. - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
  7780. write() call will fail and we handle it there.
  7781. - When we run out of disk space, or other log writing error, don't
  7782. crash. Just stop logging to that log and continue.
  7783. - Fix isspace() and friends so they still make Solaris happy
  7784. but also so they don't trigger asserts on win32.
  7785. - Fix assert failure on malformed socks4a requests.
  7786. - Fix an assert bug where a hidden service provider would fail if
  7787. the first hop of his rendezvous circuit was down.
  7788. - Better handling of size_t vs int, so we're more robust on 64
  7789. bit platforms.
  7790. o Bugfixes on 0.0.8.1 (Win32):
  7791. - Make windows sockets actually non-blocking (oops), and handle
  7792. win32 socket errors better.
  7793. - Fix parse_iso_time on platforms without strptime (eg win32).
  7794. - win32: when being multithreaded, leave parent fdarray open.
  7795. - Better handling of winsock includes on non-MSV win32 compilers.
  7796. - Change our file IO stuff (especially wrt OpenSSL) so win32 is
  7797. happier.
  7798. - Make unit tests work on win32.
  7799. o Bugfixes on 0.0.8.1 (Path selection and streams):
  7800. - Calculate timeout for waiting for a connected cell from the time
  7801. we sent the begin cell, not from the time the stream started. If
  7802. it took a long time to establish the circuit, we would time out
  7803. right after sending the begin cell.
  7804. - Fix router_compare_addr_to_addr_policy: it was not treating a port
  7805. of * as always matching, so we were picking reject *:* nodes as
  7806. exit nodes too. Oops.
  7807. - When read() failed on a stream, we would close it without sending
  7808. back an end. So 'connection refused' would simply be ignored and
  7809. the user would get no response.
  7810. - Stop a sigpipe: when an 'end' cell races with eof from the app,
  7811. we shouldn't hold-open-until-flush if the eof arrived first.
  7812. - Let resolve conns retry/expire also, rather than sticking around
  7813. forever.
  7814. - Fix more dns related bugs: send back resolve_failed and end cells
  7815. more reliably when the resolve fails, rather than closing the
  7816. circuit and then trying to send the cell. Also attach dummy resolve
  7817. connections to a circuit *before* calling dns_resolve(), to fix
  7818. a bug where cached answers would never be sent in RESOLVED cells.
  7819. o Bugfixes on 0.0.8.1 (Circuits):
  7820. - Finally fix a bug that's been plaguing us for a year:
  7821. With high load, circuit package window was reaching 0. Whenever
  7822. we got a circuit-level sendme, we were reading a lot on each
  7823. socket, but only writing out a bit. So we would eventually reach
  7824. eof. This would be noticed and acted on even when there were still
  7825. bytes sitting in the inbuf.
  7826. - Use identity comparison, not nickname comparison, to choose which
  7827. half of circuit-ID-space each side gets to use. This is needed
  7828. because sometimes we think of a router as a nickname, and sometimes
  7829. as a hex ID, and we can't predict what the other side will do.
  7830. o Bugfixes on 0.0.8.1 (Other):
  7831. - Fix a whole slew of memory leaks.
  7832. - Disallow NDEBUG. We don't ever want anybody to turn off debug.
  7833. - If we are using select, make sure we stay within FD_SETSIZE.
  7834. - When poll() is interrupted, we shouldn't believe the revents values.
  7835. - Add a FAST_SMARTLIST define to optionally inline smartlist_get
  7836. and smartlist_len, which are two major profiling offenders.
  7837. - If do_hup fails, actually notice.
  7838. - Flush the log file descriptor after we print "Tor opening log file",
  7839. so we don't see those messages days later.
  7840. - Hidden service operators now correctly handle version 1 style
  7841. INTRODUCE1 cells (nobody generates them still, so not a critical
  7842. bug).
  7843. - Handle more errnos from accept() without closing the listener.
  7844. Some OpenBSD machines were closing their listeners because
  7845. they ran out of file descriptors.
  7846. - Some people had wrapped their tor client/server in a script
  7847. that would restart it whenever it died. This did not play well
  7848. with our "shut down if your version is obsolete" code. Now people
  7849. don't fetch a new directory if their local cached version is
  7850. recent enough.
  7851. - Make our autogen.sh work on ksh as well as bash.
  7852. - Better torrc example lines for dirbindaddress and orbindaddress.
  7853. - Improved bounds checking on parsed ints (e.g. config options and
  7854. the ones we find in directories.)
  7855. - Stop using separate defaults for no-config-file and
  7856. empty-config-file. Now you have to explicitly turn off SocksPort,
  7857. if you don't want it open.
  7858. - We were starting to daemonize before we opened our logs, so if
  7859. there were any problems opening logs, we would complain to stderr,
  7860. which wouldn't work, and then mysteriously exit.
  7861. - If a verified OR connects to us before he's uploaded his descriptor,
  7862. or we verify him and hup but he still has the original TLS
  7863. connection, then conn->nickname is still set like he's unverified.
  7864. o Code security improvements, inspired by Ilja:
  7865. - tor_snprintf wrapper over snprintf with consistent (though not C99)
  7866. overflow behavior.
  7867. - Replace sprintf with tor_snprintf. (I think they were all safe, but
  7868. hey.)
  7869. - Replace strcpy/strncpy with strlcpy in more places.
  7870. - Avoid strcat; use tor_snprintf or strlcat instead.
  7871. o Features (circuits and streams):
  7872. - New circuit building strategy: keep a list of ports that we've
  7873. used in the past 6 hours, and always try to have 2 circuits open
  7874. or on the way that will handle each such port. Seed us with port
  7875. 80 so web users won't complain that Tor is "slow to start up".
  7876. - Make kill -USR1 dump more useful stats about circuits.
  7877. - When warning about retrying or giving up, print the address, so
  7878. the user knows which one it's talking about.
  7879. - If you haven't used a clean circuit in an hour, throw it away,
  7880. just to be on the safe side. (This means after 6 hours a totally
  7881. unused Tor client will have no circuits open.)
  7882. - Support "foo.nickname.exit" addresses, to let Alice request the
  7883. address "foo" as viewed by exit node "nickname". Based on a patch
  7884. from Geoff Goodell.
  7885. - If your requested entry or exit node has advertised bandwidth 0,
  7886. pick it anyway.
  7887. - Be more greedy about filling up relay cells -- we try reading again
  7888. once we've processed the stuff we read, in case enough has arrived
  7889. to fill the last cell completely.
  7890. - Refuse application socks connections to port 0.
  7891. - Use only 0.0.9pre1 and later servers for resolve cells.
  7892. o Features (bandwidth):
  7893. - Hibernation: New config option "AccountingMax" lets you
  7894. set how many bytes per month (in each direction) you want to
  7895. allow your server to consume. Rather than spreading those
  7896. bytes out evenly over the month, we instead hibernate for some
  7897. of the month and pop up at a deterministic time, work until
  7898. the bytes are consumed, then hibernate again. Config option
  7899. "MonthlyAccountingStart" lets you specify which day of the month
  7900. your billing cycle starts on.
  7901. - Implement weekly/monthly/daily accounting: now you specify your
  7902. hibernation properties by
  7903. AccountingMax N bytes|KB|MB|GB|TB
  7904. AccountingStart day|week|month [day] HH:MM
  7905. Defaults to "month 1 0:00".
  7906. - Let bandwidth and interval config options be specified as 5 bytes,
  7907. kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
  7908. o Features (directories):
  7909. - New "router-status" line in directory, to better bind each verified
  7910. nickname to its identity key.
  7911. - Clients can ask dirservers for /dir.z to get a compressed version
  7912. of the directory. Only works for servers running 0.0.9, of course.
  7913. - Make clients cache directories and use them to seed their router
  7914. lists at startup. This means clients have a datadir again.
  7915. - Respond to content-encoding headers by trying to uncompress as
  7916. appropriate.
  7917. - Clients and servers now fetch running-routers; cache
  7918. running-routers; compress running-routers; serve compressed
  7919. running-routers.z
  7920. - Make moria2 advertise a dirport of 80, so people behind firewalls
  7921. will be able to get a directory.
  7922. - Http proxy support
  7923. - Dirservers translate requests for http://%s:%d/x to /x
  7924. - You can specify "HttpProxy %s[:%d]" and all dir fetches will
  7925. be routed through this host.
  7926. - Clients ask for /tor/x rather than /x for new enough dirservers.
  7927. This way we can one day coexist peacefully with apache.
  7928. - Clients specify a "Host: %s%d" http header, to be compatible
  7929. with more proxies, and so running squid on an exit node can work.
  7930. - Protect dirservers from overzealous descriptor uploading -- wait
  7931. 10 seconds after directory gets dirty, before regenerating.
  7932. o Features (packages and install):
  7933. - Add NSI installer contributed by J Doe.
  7934. - Apply NT service patch from Osamu Fujino. Still needs more work.
  7935. - Commit VC6 and VC7 workspace/project files.
  7936. - Commit a tor.spec for making RPM files, with help from jbash.
  7937. - Add contrib/torctl.in contributed by Glenn Fink.
  7938. - Make expand_filename handle ~ and ~username.
  7939. - Use autoconf to enable largefile support where necessary. Use
  7940. ftello where available, since ftell can fail at 2GB.
  7941. - Ship src/win32/ in the tarball, so people can use it to build.
  7942. - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
  7943. is broken.
  7944. o Features (ui controller):
  7945. - Control interface: a separate program can now talk to your
  7946. client/server over a socket, and get/set config options, receive
  7947. notifications of circuits and streams starting/finishing/dying,
  7948. bandwidth used, etc. The next step is to get some GUIs working.
  7949. Let us know if you want to help out. See doc/control-spec.txt .
  7950. - Ship a contrib/tor-control.py as an example script to interact
  7951. with the control port.
  7952. - "tor --hash-password zzyxz" will output a salted password for
  7953. use in authenticating to the control interface.
  7954. - Implement the control-spec's SAVECONF command, to write your
  7955. configuration to torrc.
  7956. - Get cookie authentication for the controller closer to working.
  7957. - When set_conf changes our server descriptor, upload a new copy.
  7958. But don't upload it too often if there are frequent changes.
  7959. o Features (config and command-line):
  7960. - Deprecate unofficial config option abbreviations, and abbreviations
  7961. not on the command line.
  7962. - Configuration infrastructure support for warning on obsolete
  7963. options.
  7964. - Give a slightly more useful output for "tor -h".
  7965. - Break DirFetchPostPeriod into:
  7966. - DirFetchPeriod for fetching full directory,
  7967. - StatusFetchPeriod for fetching running-routers,
  7968. - DirPostPeriod for posting server descriptor,
  7969. - RendPostPeriod for posting hidden service descriptors.
  7970. - New log format in config:
  7971. "Log minsev[-maxsev] stdout|stderr|syslog" or
  7972. "Log minsev[-maxsev] file /var/foo"
  7973. - DirPolicy config option, to let people reject incoming addresses
  7974. from their dirserver.
  7975. - "tor --list-fingerprint" will list your identity key fingerprint
  7976. and then exit.
  7977. - Make tor --version --version dump the cvs Id of every file.
  7978. - New 'MyFamily nick1,...' config option for a server to
  7979. specify other servers that shouldn't be used in the same circuit
  7980. with it. Only believed if nick1 also specifies us.
  7981. - New 'NodeFamily nick1,nick2,...' config option for a client to
  7982. specify nodes that it doesn't want to use in the same circuit.
  7983. - New 'Redirectexit pattern address:port' config option for a
  7984. server to redirect exit connections, e.g. to a local squid.
  7985. - Add "pass" target for RedirectExit, to make it easier to break
  7986. out of a sequence of RedirectExit rules.
  7987. - Make the dirservers file obsolete.
  7988. - Include a dir-signing-key token in directories to tell the
  7989. parsing entity which key is being used to sign.
  7990. - Remove the built-in bulky default dirservers string.
  7991. - New config option "Dirserver %s:%d [fingerprint]", which can be
  7992. repeated as many times as needed. If no dirservers specified,
  7993. default to moria1,moria2,tor26.
  7994. - Make 'Routerfile' config option obsolete.
  7995. - Discourage people from setting their dirfetchpostperiod more often
  7996. than once per minute.
  7997. o Features (other):
  7998. - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
  7999. get back to normal.)
  8000. - Accept *:706 (silc) in default exit policy.
  8001. - Implement new versioning format for post 0.1.
  8002. - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
  8003. log more informatively.
  8004. - Check clock skew for verified servers, but allow unverified
  8005. servers and clients to have any clock skew.
  8006. - Make sure the hidden service descriptors are at a random offset
  8007. from each other, to hinder linkability.
  8008. - Clients now generate a TLS cert too, in preparation for having
  8009. them act more like real nodes.
  8010. - Add a pure-C tor-resolve implementation.
  8011. - Use getrlimit and friends to ensure we can reach MaxConn (currently
  8012. 1024) file descriptors.
  8013. - Raise the max dns workers from 50 to 100.
  8014. Changes in version 0.0.8.1 - 2004-10-13
  8015. o Bugfixes:
  8016. - Fix a seg fault that can be triggered remotely for Tor
  8017. clients/servers with an open dirport.
  8018. - Fix a rare assert trigger, where routerinfos for entries in
  8019. our cpath would expire while we're building the path.
  8020. - Fix a bug in OutboundBindAddress so it (hopefully) works.
  8021. - Fix a rare seg fault for people running hidden services on
  8022. intermittent connections.
  8023. - Fix a bug in parsing opt keywords with objects.
  8024. - Fix a stale pointer assert bug when a stream detaches and
  8025. reattaches.
  8026. - Fix a string format vulnerability (probably not exploitable)
  8027. in reporting stats locally.
  8028. - Fix an assert trigger: sometimes launching circuits can fail
  8029. immediately, e.g. because too many circuits have failed recently.
  8030. - Fix a compile warning on 64 bit platforms.
  8031. Changes in version 0.0.8 - 2004-08-25
  8032. o Bugfixes:
  8033. - Made our unit tests compile again on OpenBSD 3.5, and tor
  8034. itself compile again on OpenBSD on a sparc64.
  8035. - We were neglecting milliseconds when logging on win32, so
  8036. everything appeared to happen at the beginning of each second.
  8037. - Check directory signature _before_ you decide whether you're
  8038. you're running an obsolete version and should exit.
  8039. - Check directory signature _before_ you parse the running-routers
  8040. list to decide who's running.
  8041. - Check return value of fclose while writing to disk, so we don't
  8042. end up with broken files when servers run out of disk space.
  8043. - Port it to SunOS 5.9 / Athena
  8044. - Fix two bugs in saving onion keys to disk when rotating, so
  8045. hopefully we'll get fewer people using old onion keys.
  8046. - Remove our mostly unused -- and broken -- hex_encode()
  8047. function. Use base16_encode() instead. (Thanks to Timo Lindfors
  8048. for pointing out this bug.)
  8049. - Only pick and establish intro points after we've gotten a
  8050. directory.
  8051. - Fix assert triggers: if the other side returns an address 0.0.0.0,
  8052. don't put it into the client dns cache.
  8053. - If a begin failed due to exit policy, but we believe the IP
  8054. address should have been allowed, switch that router to exitpolicy
  8055. reject *:* until we get our next directory.
  8056. o Protocol changes:
  8057. - 'Extend' relay cell payloads now include the digest of the
  8058. intended next hop's identity key. Now we can verify that we're
  8059. extending to the right router, and also extend to routers we
  8060. hadn't heard of before.
  8061. o Features:
  8062. - Tor nodes can now act as relays (with an advertised ORPort)
  8063. without being manually verified by the dirserver operators.
  8064. - Uploaded descriptors of unverified routers are now accepted
  8065. by the dirservers, and included in the directory.
  8066. - Verified routers are listed by nickname in the running-routers
  8067. list; unverified routers are listed as "$<fingerprint>".
  8068. - We now use hash-of-identity-key in most places rather than
  8069. nickname or addr:port, for improved security/flexibility.
  8070. - AllowUnverifiedNodes config option to let circuits choose no-name
  8071. routers in entry,middle,exit,introduction,rendezvous positions.
  8072. Allow middle and rendezvous positions by default.
  8073. - When picking unverified routers, skip those with low uptime and/or
  8074. low bandwidth, depending on what properties you care about.
  8075. - ClientOnly option for nodes that never want to become servers.
  8076. - Directory caching.
  8077. - "AuthoritativeDir 1" option for the official dirservers.
  8078. - Now other nodes (clients and servers) will cache the latest
  8079. directory they've pulled down.
  8080. - They can enable their DirPort to serve it to others.
  8081. - Clients will pull down a directory from any node with an open
  8082. DirPort, and check the signature/timestamp correctly.
  8083. - Authoritative dirservers now fetch directories from other
  8084. authdirservers, to stay better synced.
  8085. - Running-routers list tells who's down also, along with noting
  8086. if they're verified (listed by nickname) or unverified (listed
  8087. by hash-of-key).
  8088. - Allow dirservers to serve running-router list separately.
  8089. This isn't used yet.
  8090. - You can now fetch $DIRURL/running-routers to get just the
  8091. running-routers line, not the whole descriptor list. (But
  8092. clients don't use this yet.)
  8093. - Clients choose nodes proportional to advertised bandwidth.
  8094. - Clients avoid using nodes with low uptime as introduction points.
  8095. - Handle servers with dynamic IP addresses: don't just replace
  8096. options->Address with the resolved one at startup, and
  8097. detect our address right before we make a routerinfo each time.
  8098. - 'FascistFirewall' option to pick dirservers and ORs on specific
  8099. ports; plus 'FirewallPorts' config option to tell FascistFirewall
  8100. which ports are open. (Defaults to 80,443)
  8101. - Try other dirservers immediately if the one you try is down. This
  8102. should tolerate down dirservers better now.
  8103. - ORs connect-on-demand to other ORs
  8104. - If you get an extend cell to an OR you're not connected to,
  8105. connect, handshake, and forward the create cell.
  8106. - The authoritative dirservers stay connected to everybody,
  8107. and everybody stays connected to 0.0.7 servers, but otherwise
  8108. clients/servers expire unused connections after 5 minutes.
  8109. - When servers get a sigint, they delay 30 seconds (refusing new
  8110. connections) then exit. A second sigint causes immediate exit.
  8111. - File and name management:
  8112. - Look for .torrc if no CONFDIR "torrc" is found.
  8113. - If no datadir is defined, then choose, make, and secure ~/.tor
  8114. as datadir.
  8115. - If torrc not found, exitpolicy reject *:*.
  8116. - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
  8117. - If no nickname is defined, derive default from hostname.
  8118. - Rename secret key files, e.g. identity.key -> secret_id_key,
  8119. to discourage people from mailing their identity key to tor-ops.
  8120. - Refuse to build a circuit before the directory has arrived --
  8121. it won't work anyway, since you won't know the right onion keys
  8122. to use.
  8123. - Parse tor version numbers so we can do an is-newer-than check
  8124. rather than an is-in-the-list check.
  8125. - New socks command 'resolve', to let us shim gethostbyname()
  8126. locally.
  8127. - A 'tor_resolve' script to access the socks resolve functionality.
  8128. - A new socks-extensions.txt doc file to describe our
  8129. interpretation and extensions to the socks protocols.
  8130. - Add a ContactInfo option, which gets published in descriptor.
  8131. - Write tor version at the top of each log file
  8132. - New docs in the tarball:
  8133. - tor-doc.html.
  8134. - Document that you should proxy your SSL traffic too.
  8135. - Log a warning if the user uses an unsafe socks variant, so people
  8136. are more likely to learn about privoxy or socat.
  8137. - Log a warning if you're running an unverified server, to let you
  8138. know you might want to get it verified.
  8139. - Change the default exit policy to reject the default edonkey,
  8140. kazaa, gnutella ports.
  8141. - Add replace_file() to util.[ch] to handle win32's rename().
  8142. - Publish OR uptime in descriptor (and thus in directory) too.
  8143. - Remember used bandwidth (both in and out), and publish 15-minute
  8144. snapshots for the past day into our descriptor.
  8145. - Be more aggressive about trying to make circuits when the network
  8146. has changed (e.g. when you unsuspend your laptop).
  8147. - Check for time skew on http headers; report date in response to
  8148. "GET /".
  8149. - If the entrynode config line has only one node, don't pick it as
  8150. an exitnode.
  8151. - Add strict{entry|exit}nodes config options. If set to 1, then
  8152. we refuse to build circuits that don't include the specified entry
  8153. or exit nodes.
  8154. - OutboundBindAddress config option, to bind to a specific
  8155. IP address for outgoing connect()s.
  8156. - End truncated log entries (e.g. directories) with "[truncated]".
  8157. Changes in version 0.0.7.3 - 2004-08-12
  8158. o Stop dnsworkers from triggering an assert failure when you
  8159. ask them to resolve the host "".
  8160. Changes in version 0.0.7.2 - 2004-07-07
  8161. o A better fix for the 0.0.0.0 problem, that will hopefully
  8162. eliminate the remaining related assertion failures.
  8163. Changes in version 0.0.7.1 - 2004-07-04
  8164. o When an address resolves to 0.0.0.0, treat it as a failed resolve,
  8165. since internally we use 0.0.0.0 to signify "not yet resolved".
  8166. Changes in version 0.0.7 - 2004-06-07
  8167. o Fixes for crashes and other obnoxious bugs:
  8168. - Fix an epipe bug: sometimes when directory connections failed
  8169. to connect, we would give them a chance to flush before closing
  8170. them.
  8171. - When we detached from a circuit because of resolvefailed, we
  8172. would immediately try the same circuit twice more, and then
  8173. give up on the resolve thinking we'd tried three different
  8174. exit nodes.
  8175. - Limit the number of intro circuits we'll attempt to build for a
  8176. hidden service per 15-minute period.
  8177. - Check recommended-software string *early*, before actually parsing
  8178. the directory. Thus we can detect an obsolete version and exit,
  8179. even if the new directory format doesn't parse.
  8180. o Fixes for security bugs:
  8181. - Remember which nodes are dirservers when you startup, and if a
  8182. random OR enables his dirport, don't automatically assume he's
  8183. a trusted dirserver.
  8184. o Other bugfixes:
  8185. - Directory connections were asking the wrong poll socket to
  8186. start writing, and not asking themselves to start writing.
  8187. - When we detached from a circuit because we sent a begin but
  8188. didn't get a connected, we would use it again the first time;
  8189. but after that we would correctly switch to a different one.
  8190. - Stop warning when the first onion decrypt attempt fails; they
  8191. will sometimes legitimately fail now that we rotate keys.
  8192. - Override unaligned-access-ok check when $host_cpu is ia64 or
  8193. arm. Apparently they allow it but the kernel whines.
  8194. - Dirservers try to reconnect periodically too, in case connections
  8195. have failed.
  8196. - Fix some memory leaks in directory servers.
  8197. - Allow backslash in Win32 filenames.
  8198. - Made Tor build complain-free on FreeBSD, hopefully without
  8199. breaking other BSD builds. We'll see.
  8200. - Check directory signatures based on name of signer, not on whom
  8201. we got the directory from. This will let us cache directories more
  8202. easily.
  8203. - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
  8204. settings too.
  8205. o Features:
  8206. - Doxygen markup on all functions and global variables.
  8207. - Make directory functions update routerlist, not replace it. So
  8208. now directory disagreements are not so critical a problem.
  8209. - Remove the upper limit on number of descriptors in a dirserver's
  8210. directory (not that we were anywhere close).
  8211. - Allow multiple logfiles at different severity ranges.
  8212. - Allow *BindAddress to specify ":port" rather than setting *Port
  8213. separately. Allow multiple instances of each BindAddress config
  8214. option, so you can bind to multiple interfaces if you want.
  8215. - Allow multiple exit policy lines, which are processed in order.
  8216. Now we don't need that huge line with all the commas in it.
  8217. - Enable accept/reject policies on SOCKS connections, so you can bind
  8218. to 0.0.0.0 but still control who can use your OP.
  8219. - Updated the man page to reflect these features.
  8220. Changes in version 0.0.6.2 - 2004-05-16
  8221. o Our integrity-checking digest was checking only the most recent cell,
  8222. not the previous cells like we'd thought.
  8223. Thanks to Stefan Mark for finding the flaw!
  8224. Changes in version 0.0.6.1 - 2004-05-06
  8225. o Fix two bugs in our AES counter-mode implementation (this affected
  8226. onion-level stream encryption, but not TLS-level). It turns
  8227. out we were doing something much more akin to a 16-character
  8228. polyalphabetic cipher. Oops.
  8229. Thanks to Stefan Mark for finding the flaw!
  8230. o Retire moria3 as a directory server, and add tor26 as a directory
  8231. server.
  8232. Changes in version 0.0.6 - 2004-05-02
  8233. o Features:
  8234. - Hidden services and rendezvous points are implemented. Go to
  8235. http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
  8236. hidden services. (This only works via a socks4a proxy such as
  8237. Privoxy, and currently it's quite slow.)
  8238. - We now rotate link (tls context) keys and onion keys.
  8239. - CREATE cells now include oaep padding, so you can tell
  8240. if you decrypted them correctly.
  8241. - Retry stream correctly when we fail to connect because of
  8242. exit-policy-reject (should try another) or can't-resolve-address.
  8243. - When we hup a dirserver and we've *removed* a server from the
  8244. approved-routers list, now we remove that server from the
  8245. in-memory directories too.
  8246. - Add bandwidthburst to server descriptor.
  8247. - Directories now say which dirserver signed them.
  8248. - Use a tor_assert macro that logs failed assertions too.
  8249. - Since we don't support truncateds much, don't bother sending them;
  8250. just close the circ.
  8251. - Fetch randomness from /dev/urandom better (not via fopen/fread)
  8252. - Better debugging for tls errors
  8253. - Set Content-Type on the directory and hidserv descriptor.
  8254. - Remove IVs from cipher code, since AES-ctr has none.
  8255. o Bugfixes:
  8256. - Fix an assert trigger for exit nodes that's been plaguing us since
  8257. the days of 0.0.2prexx (thanks weasel!)
  8258. - Fix a bug where we were closing tls connections intermittently.
  8259. It turns out openssl keeps its errors around -- so if an error
  8260. happens, and you don't ask about it, and then another openssl
  8261. operation happens and succeeds, and you ask if there was an error,
  8262. it tells you about the first error.
  8263. - Fix a bug that's been lurking since 27 may 03 (!)
  8264. When passing back a destroy cell, we would use the wrong circ id.
  8265. - Don't crash if a conn that sent a begin has suddenly lost its circuit.
  8266. - Some versions of openssl have an SSL_pending function that erroneously
  8267. returns bytes when there is a non-application record pending.
  8268. - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
  8269. o We were using an array of length zero in a few places.
  8270. o Win32's gethostbyname can't resolve an IP to an IP.
  8271. o Win32's close can't close a socket.
  8272. o Handle windows socket errors correctly.
  8273. o Portability:
  8274. - check for <sys/limits.h> so we build on FreeBSD again, and
  8275. <machine/limits.h> for NetBSD.
  8276. Changes in version 0.0.5 - 2004-03-30
  8277. o Install torrc as torrc.sample -- we no longer clobber your
  8278. torrc. (Woo!)
  8279. o Fix mangled-state bug in directory fetching (was causing sigpipes).
  8280. o Only build circuits after we've fetched the directory: clients were
  8281. using only the directory servers before they'd fetched a directory.
  8282. This also means longer startup time; so it goes.
  8283. o Fix an assert trigger where an OP would fail to handshake, and we'd
  8284. expect it to have a nickname.
  8285. o Work around a tsocks bug: do a socks reject when AP connection dies
  8286. early, else tsocks goes into an infinite loop.
  8287. o Hold socks connection open until reply is flushed (if possible)
  8288. o Make exit nodes resolve IPs to IPs immediately, rather than asking
  8289. the dns farm to do it.
  8290. o Fix c99 aliasing warnings in rephist.c
  8291. o Don't include server descriptors that are older than 24 hours in the
  8292. directory.
  8293. o Give socks 'reject' replies their whole 15s to attempt to flush,
  8294. rather than seeing the 60s timeout and assuming the flush had failed.
  8295. o Clean automake droppings from the cvs repository
  8296. o Add in a 'notice' log level for things the operator should hear
  8297. but that aren't warnings
  8298. Changes in version 0.0.4 - 2004-03-26
  8299. o When connecting to a dirserver or OR and the network is down,
  8300. we would crash.
  8301. Changes in version 0.0.3 - 2004-03-26
  8302. o Warn and fail if server chose a nickname with illegal characters
  8303. o Port to Solaris and Sparc:
  8304. - include missing header fcntl.h
  8305. - have autoconf find -lsocket -lnsl automatically
  8306. - deal with hardware word alignment
  8307. - make uname() work (solaris has a different return convention)
  8308. - switch from using signal() to sigaction()
  8309. o Preliminary work on reputation system:
  8310. - Keep statistics on success/fail of connect attempts; they're published
  8311. by kill -USR1 currently.
  8312. - Add a RunTesting option to try to learn link state by creating test
  8313. circuits, even when SocksPort is off.
  8314. - Remove unused open circuits when there are too many.
  8315. Changes in version 0.0.2 - 2004-03-19
  8316. - Include strlcpy and strlcat for safer string ops
  8317. - define INADDR_NONE so we compile (but still not run) on solaris
  8318. Changes in version 0.0.2pre27 - 2004-03-14
  8319. o Bugfixes:
  8320. - Allow internal tor networks (we were rejecting internal IPs,
  8321. now we allow them if they're set explicitly).
  8322. - And fix a few endian issues.
  8323. Changes in version 0.0.2pre26 - 2004-03-14
  8324. o New features:
  8325. - If a stream times out after 15s without a connected cell, don't
  8326. try that circuit again: try a new one.
  8327. - Retry streams at most 4 times. Then give up.
  8328. - When a dirserver gets a descriptor from an unknown router, it
  8329. logs its fingerprint (so the dirserver operator can choose to
  8330. accept it even without mail from the server operator).
  8331. - Inform unapproved servers when we reject their descriptors.
  8332. - Make tor build on Windows again. It works as a client, who knows
  8333. about as a server.
  8334. - Clearer instructions in the torrc for how to set up a server.
  8335. - Be more efficient about reading fd's when our global token bucket
  8336. (used for rate limiting) becomes empty.
  8337. o Bugfixes:
  8338. - Stop asserting that computers always go forward in time. It's
  8339. simply not true.
  8340. - When we sent a cell (e.g. destroy) and then marked an OR connection
  8341. expired, we might close it before finishing a flush if the other
  8342. side isn't reading right then.
  8343. - Don't allow dirservers to start if they haven't defined
  8344. RecommendedVersions
  8345. - We were caching transient dns failures. Oops.
  8346. - Prevent servers from publishing an internal IP as their address.
  8347. - Address a strcat vulnerability in circuit.c
  8348. Changes in version 0.0.2pre25 - 2004-03-04
  8349. o New features:
  8350. - Put the OR's IP in its router descriptor, not its fqdn. That way
  8351. we'll stop being stalled by gethostbyname for nodes with flaky dns,
  8352. e.g. poblano.
  8353. o Bugfixes:
  8354. - If the user typed in an address that didn't resolve, the server
  8355. crashed.
  8356. Changes in version 0.0.2pre24 - 2004-03-03
  8357. o Bugfixes:
  8358. - Fix an assertion failure in dns.c, where we were trying to dequeue
  8359. a pending dns resolve even if it wasn't pending
  8360. - Fix a spurious socks5 warning about still trying to write after the
  8361. connection is finished.
  8362. - Hold certain marked_for_close connections open until they're finished
  8363. flushing, rather than losing bytes by closing them too early.
  8364. - Correctly report the reason for ending a stream
  8365. - Remove some duplicate calls to connection_mark_for_close
  8366. - Put switch_id and start_daemon earlier in the boot sequence, so it
  8367. will actually try to chdir() to options.DataDirectory
  8368. - Make 'make test' exit(1) if a test fails; fix some unit tests
  8369. - Make tor fail when you use a config option it doesn't know about,
  8370. rather than warn and continue.
  8371. - Make --version work
  8372. - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
  8373. Changes in version 0.0.2pre23 - 2004-02-29
  8374. o New features:
  8375. - Print a statement when the first circ is finished, so the user
  8376. knows it's working.
  8377. - If a relay cell is unrecognized at the end of the circuit,
  8378. send back a destroy. (So attacks to mutate cells are more
  8379. clearly thwarted.)
  8380. - New config option 'excludenodes' to avoid certain nodes for circuits.
  8381. - When it daemonizes, it chdir's to the DataDirectory rather than "/",
  8382. so you can collect coredumps there.
  8383. o Bugfixes:
  8384. - Fix a bug in tls flushing where sometimes data got wedged and
  8385. didn't flush until more data got sent. Hopefully this bug was
  8386. a big factor in the random delays we were seeing.
  8387. - Make 'connected' cells include the resolved IP, so the client
  8388. dns cache actually gets populated.
  8389. - Disallow changing from ORPort=0 to ORPort>0 on hup.
  8390. - When we time-out on a stream and detach from the circuit, send an
  8391. end cell down it first.
  8392. - Only warn about an unknown router (in exitnodes, entrynodes,
  8393. excludenodes) after we've fetched a directory.
  8394. Changes in version 0.0.2pre22 - 2004-02-26
  8395. o New features:
  8396. - Servers publish less revealing uname information in descriptors.
  8397. - More memory tracking and assertions, to crash more usefully when
  8398. errors happen.
  8399. - If the default torrc isn't there, just use some default defaults.
  8400. Plus provide an internal dirservers file if they don't have one.
  8401. - When the user tries to use Tor as an http proxy, give them an http
  8402. 501 failure explaining that we're a socks proxy.
  8403. - Dump a new router.desc on hup, to help confused people who change
  8404. their exit policies and then wonder why router.desc doesn't reflect
  8405. it.
  8406. - Clean up the generic tor.sh init script that we ship with.
  8407. o Bugfixes:
  8408. - If the exit stream is pending on the resolve, and a destroy arrives,
  8409. then the stream wasn't getting removed from the pending list. I
  8410. think this was the one causing recent server crashes.
  8411. - Use a more robust poll on OSX 10.3, since their poll is flaky.
  8412. - When it couldn't resolve any dirservers, it was useless from then on.
  8413. Now it reloads the RouterFile (or default dirservers) if it has no
  8414. dirservers.
  8415. - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
  8416. many users don't even *have* a /usr/local/sbin/.
  8417. Changes in version 0.0.2pre21 - 2004-02-18
  8418. o New features:
  8419. - There's a ChangeLog file that actually reflects the changelog.
  8420. - There's a 'torify' wrapper script, with an accompanying
  8421. tor-tsocks.conf, that simplifies the process of using tsocks for
  8422. tor. It even has a man page.
  8423. - The tor binary gets installed to sbin rather than bin now.
  8424. - Retry streams where the connected cell hasn't arrived in 15 seconds
  8425. - Clean up exit policy handling -- get the default out of the torrc,
  8426. so we can update it without forcing each server operator to fix
  8427. his/her torrc.
  8428. - Allow imaps and pop3s in default exit policy
  8429. o Bugfixes:
  8430. - Prevent picking middleman nodes as the last node in the circuit
  8431. Changes in version 0.0.2pre20 - 2004-01-30
  8432. o New features:
  8433. - We now have a deb package, and it's in debian unstable. Go to
  8434. it, apt-getters. :)
  8435. - I've split the TotalBandwidth option into BandwidthRate (how many
  8436. bytes per second you want to allow, long-term) and
  8437. BandwidthBurst (how many bytes you will allow at once before the cap
  8438. kicks in). This better token bucket approach lets you, say, set
  8439. BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
  8440. performance while not exceeding your monthly bandwidth quota.
  8441. - Push out a tls record's worth of data once you've got it, rather
  8442. than waiting until you've read everything waiting to be read. This
  8443. may improve performance by pipelining better. We'll see.
  8444. - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
  8445. from failed circuits (if they haven't been connected yet) and attach
  8446. to new ones.
  8447. - Expire old streams that haven't managed to connect. Some day we'll
  8448. have them reattach to new circuits instead.
  8449. o Bugfixes:
  8450. - Fix several memory leaks that were causing servers to become bloated
  8451. after a while.
  8452. - Fix a few very rare assert triggers. A few more remain.
  8453. - Setuid to User _before_ complaining about running as root.
  8454. Changes in version 0.0.2pre19 - 2004-01-07
  8455. o Bugfixes:
  8456. - Fix deadlock condition in dns farm. We were telling a child to die by
  8457. closing the parent's file descriptor to him. But newer children were
  8458. inheriting the open file descriptor from the parent, and since they
  8459. weren't closing it, the socket never closed, so the child never read
  8460. eof, so he never knew to exit. Similarly, dns workers were holding
  8461. open other sockets, leading to all sorts of chaos.
  8462. - New cleaner daemon() code for forking and backgrounding.
  8463. - If you log to a file, it now prints an entry at the top of the
  8464. logfile so you know it's working.
  8465. - The onionskin challenge length was 30 bytes longer than necessary.
  8466. - Started to patch up the spec so it's not quite so out of date.
  8467. Changes in version 0.0.2pre18 - 2004-01-02
  8468. o Bugfixes:
  8469. - Fix endian issues with the 'integrity' field in the relay header.
  8470. - Fix a potential bug where connections in state
  8471. AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
  8472. Changes in version 0.0.2pre17 - 2003-12-30
  8473. o Bugfixes:
  8474. - Made --debuglogfile (or any second log file, actually) work.
  8475. - Resolved an edge case in get_unique_circ_id_by_conn where a smart
  8476. adversary could force us into an infinite loop.
  8477. o Features:
  8478. - Each onionskin handshake now includes a hash of the computed key,
  8479. to prove the server's identity and help perfect forward secrecy.
  8480. - Changed cell size from 256 to 512 bytes (working toward compatibility
  8481. with MorphMix).
  8482. - Changed cell length to 2 bytes, and moved it to the relay header.
  8483. - Implemented end-to-end integrity checking for the payloads of
  8484. relay cells.
  8485. - Separated streamid from 'recognized' (otherwise circuits will get
  8486. messed up when we try to have streams exit from the middle). We
  8487. use the integrity-checking to confirm that a cell is addressed to
  8488. this hop.
  8489. - Randomize the initial circid and streamid values, so an adversary who
  8490. breaks into a node can't learn how many circuits or streams have
  8491. been made so far.
  8492. Changes in version 0.0.2pre16 - 2003-12-14
  8493. o Bugfixes:
  8494. - Fixed a bug that made HUP trigger an assert
  8495. - Fixed a bug where a circuit that immediately failed wasn't being
  8496. counted as a failed circuit in counting retries.
  8497. o Features:
  8498. - Now we close the circuit when we get a truncated cell: otherwise we're
  8499. open to an anonymity attack where a bad node in the path truncates
  8500. the circuit and then we open streams at him.
  8501. - Add port ranges to exit policies
  8502. - Add a conservative default exit policy
  8503. - Warn if you're running tor as root
  8504. - on HUP, retry OR connections and close/rebind listeners
  8505. - options.EntryNodes: try these nodes first when picking the first node
  8506. - options.ExitNodes: if your best choices happen to include any of
  8507. your preferred exit nodes, you choose among just those preferred
  8508. exit nodes.
  8509. - options.ExcludedNodes: nodes that are never picked in path building
  8510. Changes in version 0.0.2pre15 - 2003-12-03
  8511. o Robustness and bugfixes:
  8512. - Sometimes clients would cache incorrect DNS resolves, which would
  8513. really screw things up.
  8514. - An OP that goes offline would slowly leak all its sockets and stop
  8515. working.
  8516. - A wide variety of bugfixes in exit node selection, exit policy
  8517. handling, and processing pending streams when a new circuit is
  8518. established.
  8519. - Pick nodes for a path only from those the directory says are up
  8520. - Choose randomly from all running dirservers, not always the first one
  8521. - Increase allowed http header size for directory fetch.
  8522. - Stop writing to stderr (if we're daemonized it will be closed).
  8523. - Enable -g always, so cores will be more useful to me.
  8524. - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
  8525. o Documentation:
  8526. - Wrote a man page. It lists commonly used options.
  8527. o Configuration:
  8528. - Change default loglevel to warn.
  8529. - Make PidFile default to null rather than littering in your CWD.
  8530. - OnionRouter config option is now obsolete. Instead it just checks
  8531. ORPort>0.
  8532. - Moved to a single unified torrc file for both clients and servers.
  8533. Changes in version 0.0.2pre14 - 2003-11-29
  8534. o Robustness and bugfixes:
  8535. - Force the admin to make the DataDirectory himself
  8536. - to get ownership/permissions right
  8537. - so clients no longer make a DataDirectory and then never use it
  8538. - fix bug where a client who was offline for 45 minutes would never
  8539. pull down a directory again
  8540. - fix (or at least hide really well) the dns assert bug that was
  8541. causing server crashes
  8542. - warnings and improved robustness wrt clockskew for certs
  8543. - use the native daemon(3) to daemonize, when available
  8544. - exit if bind() fails
  8545. - exit if neither socksport nor orport is defined
  8546. - include our own tor_timegm (Win32 doesn't have its own)
  8547. - bugfix for win32 with lots of connections
  8548. - fix minor bias in PRNG
  8549. - make dirserver more robust to corrupt cached directory
  8550. o Documentation:
  8551. - Wrote the design document (woo)
  8552. o Circuit building and exit policies:
  8553. - Circuits no longer try to use nodes that the directory has told them
  8554. are down.
  8555. - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
  8556. bitcounts (18.0.0.0/8).
  8557. - Make AP connections standby for a circuit if no suitable circuit
  8558. exists, rather than failing
  8559. - Circuits choose exit node based on addr/port, exit policies, and
  8560. which AP connections are standing by
  8561. - Bump min pathlen from 2 to 3
  8562. - Relay end cells have a payload to describe why the stream ended.
  8563. - If the stream failed because of exit policy, try again with a new
  8564. circuit.
  8565. - Clients have a dns cache to remember resolved addresses.
  8566. - Notice more quickly when we have no working circuits
  8567. o Configuration:
  8568. - APPort is now called SocksPort
  8569. - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
  8570. where to bind
  8571. - RecommendedVersions is now a config variable rather than
  8572. hardcoded (for dirservers)
  8573. - Reloads config on HUP
  8574. - Usage info on -h or --help
  8575. - If you set User and Group config vars, it'll setu/gid to them.
  8576. Changes in version 0.0.2pre13 - 2003-10-19
  8577. o General stability:
  8578. - SSL_write no longer fails when it returns WANTWRITE and the number
  8579. of bytes in the buf has changed by the next SSL_write call.
  8580. - Fix segfault fetching directory when network is down
  8581. - Fix a variety of minor memory leaks
  8582. - Dirservers reload the fingerprints file on HUP, so I don't have
  8583. to take down the network when I approve a new router
  8584. - Default server config file has explicit Address line to specify fqdn
  8585. o Buffers:
  8586. - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
  8587. - Make listener connections not ever alloc bufs
  8588. o Autoconf improvements:
  8589. - don't clobber an external CFLAGS in ./configure
  8590. - Make install now works
  8591. - create var/lib/tor on make install
  8592. - autocreate a tor.sh initscript to help distribs
  8593. - autocreate the torrc and sample-server-torrc with correct paths
  8594. o Log files and Daemonizing now work:
  8595. - If --DebugLogFile is specified, log to it at -l debug
  8596. - If --LogFile is specified, use it instead of commandline
  8597. - If --RunAsDaemon is set, tor forks and backgrounds on startup