ReleaseNotes 381 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994995996997998999100010011002100310041005100610071008100910101011101210131014101510161017101810191020102110221023102410251026102710281029103010311032103310341035103610371038103910401041104210431044104510461047104810491050105110521053105410551056105710581059106010611062106310641065106610671068106910701071107210731074107510761077107810791080108110821083108410851086108710881089109010911092109310941095109610971098109911001101110211031104110511061107110811091110111111121113111411151116111711181119112011211122112311241125112611271128112911301131113211331134113511361137113811391140114111421143114411451146114711481149115011511152115311541155115611571158115911601161116211631164116511661167116811691170117111721173117411751176117711781179118011811182118311841185118611871188118911901191119211931194119511961197119811991200120112021203120412051206120712081209121012111212121312141215121612171218121912201221122212231224122512261227122812291230123112321233123412351236123712381239124012411242124312441245124612471248124912501251125212531254125512561257125812591260126112621263126412651266126712681269127012711272127312741275127612771278127912801281128212831284128512861287128812891290129112921293129412951296129712981299130013011302130313041305130613071308130913101311131213131314131513161317131813191320132113221323132413251326132713281329133013311332133313341335133613371338133913401341134213431344134513461347134813491350135113521353135413551356135713581359136013611362136313641365136613671368136913701371137213731374137513761377137813791380138113821383138413851386138713881389139013911392139313941395139613971398139914001401140214031404140514061407140814091410141114121413141414151416141714181419142014211422142314241425142614271428142914301431143214331434143514361437143814391440144114421443144414451446144714481449145014511452145314541455145614571458145914601461146214631464146514661467146814691470147114721473147414751476147714781479148014811482148314841485148614871488148914901491149214931494149514961497149814991500150115021503150415051506150715081509151015111512151315141515151615171518151915201521152215231524152515261527152815291530153115321533153415351536153715381539154015411542154315441545154615471548154915501551155215531554155515561557155815591560156115621563156415651566156715681569157015711572157315741575157615771578157915801581158215831584158515861587158815891590159115921593159415951596159715981599160016011602160316041605160616071608160916101611161216131614161516161617161816191620162116221623162416251626162716281629163016311632163316341635163616371638163916401641164216431644164516461647164816491650165116521653165416551656165716581659166016611662166316641665166616671668166916701671167216731674167516761677167816791680168116821683168416851686168716881689169016911692169316941695169616971698169917001701170217031704170517061707170817091710171117121713171417151716171717181719172017211722172317241725172617271728172917301731173217331734173517361737173817391740174117421743174417451746174717481749175017511752175317541755175617571758175917601761176217631764176517661767176817691770177117721773177417751776177717781779178017811782178317841785178617871788178917901791179217931794179517961797179817991800180118021803180418051806180718081809181018111812181318141815181618171818181918201821182218231824182518261827182818291830183118321833183418351836183718381839184018411842184318441845184618471848184918501851185218531854185518561857185818591860186118621863186418651866186718681869187018711872187318741875187618771878187918801881188218831884188518861887188818891890189118921893189418951896189718981899190019011902190319041905190619071908190919101911191219131914191519161917191819191920192119221923192419251926192719281929193019311932193319341935193619371938193919401941194219431944194519461947194819491950195119521953195419551956195719581959196019611962196319641965196619671968196919701971197219731974197519761977197819791980198119821983198419851986198719881989199019911992199319941995199619971998199920002001200220032004200520062007200820092010201120122013201420152016201720182019202020212022202320242025202620272028202920302031203220332034203520362037203820392040204120422043204420452046204720482049205020512052205320542055205620572058205920602061206220632064206520662067206820692070207120722073207420752076207720782079208020812082208320842085208620872088208920902091209220932094209520962097209820992100210121022103210421052106210721082109211021112112211321142115211621172118211921202121212221232124212521262127212821292130213121322133213421352136213721382139214021412142214321442145214621472148214921502151215221532154215521562157215821592160216121622163216421652166216721682169217021712172217321742175217621772178217921802181218221832184218521862187218821892190219121922193219421952196219721982199220022012202220322042205220622072208220922102211221222132214221522162217221822192220222122222223222422252226222722282229223022312232223322342235223622372238223922402241224222432244224522462247224822492250225122522253225422552256225722582259226022612262226322642265226622672268226922702271227222732274227522762277227822792280228122822283228422852286228722882289229022912292229322942295229622972298229923002301230223032304230523062307230823092310231123122313231423152316231723182319232023212322232323242325232623272328232923302331233223332334233523362337233823392340234123422343234423452346234723482349235023512352235323542355235623572358235923602361236223632364236523662367236823692370237123722373237423752376237723782379238023812382238323842385238623872388238923902391239223932394239523962397239823992400240124022403240424052406240724082409241024112412241324142415241624172418241924202421242224232424242524262427242824292430243124322433243424352436243724382439244024412442244324442445244624472448244924502451245224532454245524562457245824592460246124622463246424652466246724682469247024712472247324742475247624772478247924802481248224832484248524862487248824892490249124922493249424952496249724982499250025012502250325042505250625072508250925102511251225132514251525162517251825192520252125222523252425252526252725282529253025312532253325342535253625372538253925402541254225432544254525462547254825492550255125522553255425552556255725582559256025612562256325642565256625672568256925702571257225732574257525762577257825792580258125822583258425852586258725882589259025912592259325942595259625972598259926002601260226032604260526062607260826092610261126122613261426152616261726182619262026212622262326242625262626272628262926302631263226332634263526362637263826392640264126422643264426452646264726482649265026512652265326542655265626572658265926602661266226632664266526662667266826692670267126722673267426752676267726782679268026812682268326842685268626872688268926902691269226932694269526962697269826992700270127022703270427052706270727082709271027112712271327142715271627172718271927202721272227232724272527262727272827292730273127322733273427352736273727382739274027412742274327442745274627472748274927502751275227532754275527562757275827592760276127622763276427652766276727682769277027712772277327742775277627772778277927802781278227832784278527862787278827892790279127922793279427952796279727982799280028012802280328042805280628072808280928102811281228132814281528162817281828192820282128222823282428252826282728282829283028312832283328342835283628372838283928402841284228432844284528462847284828492850285128522853285428552856285728582859286028612862286328642865286628672868286928702871287228732874287528762877287828792880288128822883288428852886288728882889289028912892289328942895289628972898289929002901290229032904290529062907290829092910291129122913291429152916291729182919292029212922292329242925292629272928292929302931293229332934293529362937293829392940294129422943294429452946294729482949295029512952295329542955295629572958295929602961296229632964296529662967296829692970297129722973297429752976297729782979298029812982298329842985298629872988298929902991299229932994299529962997299829993000300130023003300430053006300730083009301030113012301330143015301630173018301930203021302230233024302530263027302830293030303130323033303430353036303730383039304030413042304330443045304630473048304930503051305230533054305530563057305830593060306130623063306430653066306730683069307030713072307330743075307630773078307930803081308230833084308530863087308830893090309130923093309430953096309730983099310031013102310331043105310631073108310931103111311231133114311531163117311831193120312131223123312431253126312731283129313031313132313331343135313631373138313931403141314231433144314531463147314831493150315131523153315431553156315731583159316031613162316331643165316631673168316931703171317231733174317531763177317831793180318131823183318431853186318731883189319031913192319331943195319631973198319932003201320232033204320532063207320832093210321132123213321432153216321732183219322032213222322332243225322632273228322932303231323232333234323532363237323832393240324132423243324432453246324732483249325032513252325332543255325632573258325932603261326232633264326532663267326832693270327132723273327432753276327732783279328032813282328332843285328632873288328932903291329232933294329532963297329832993300330133023303330433053306330733083309331033113312331333143315331633173318331933203321332233233324332533263327332833293330333133323333333433353336333733383339334033413342334333443345334633473348334933503351335233533354335533563357335833593360336133623363336433653366336733683369337033713372337333743375337633773378337933803381338233833384338533863387338833893390339133923393339433953396339733983399340034013402340334043405340634073408340934103411341234133414341534163417341834193420342134223423342434253426342734283429343034313432343334343435343634373438343934403441344234433444344534463447344834493450345134523453345434553456345734583459346034613462346334643465346634673468346934703471347234733474347534763477347834793480348134823483348434853486348734883489349034913492349334943495349634973498349935003501350235033504350535063507350835093510351135123513351435153516351735183519352035213522352335243525352635273528352935303531353235333534353535363537353835393540354135423543354435453546354735483549355035513552355335543555355635573558355935603561356235633564356535663567356835693570357135723573357435753576357735783579358035813582358335843585358635873588358935903591359235933594359535963597359835993600360136023603360436053606360736083609361036113612361336143615361636173618361936203621362236233624362536263627362836293630363136323633363436353636363736383639364036413642364336443645364636473648364936503651365236533654365536563657365836593660366136623663366436653666366736683669367036713672367336743675367636773678367936803681368236833684368536863687368836893690369136923693369436953696369736983699370037013702370337043705370637073708370937103711371237133714371537163717371837193720372137223723372437253726372737283729373037313732373337343735373637373738373937403741374237433744374537463747374837493750375137523753375437553756375737583759376037613762376337643765376637673768376937703771377237733774377537763777377837793780378137823783378437853786378737883789379037913792379337943795379637973798379938003801380238033804380538063807380838093810381138123813381438153816381738183819382038213822382338243825382638273828382938303831383238333834383538363837383838393840384138423843384438453846384738483849385038513852385338543855385638573858385938603861386238633864386538663867386838693870387138723873387438753876387738783879388038813882388338843885388638873888388938903891389238933894389538963897389838993900390139023903390439053906390739083909391039113912391339143915391639173918391939203921392239233924392539263927392839293930393139323933393439353936393739383939394039413942394339443945394639473948394939503951395239533954395539563957395839593960396139623963396439653966396739683969397039713972397339743975397639773978397939803981398239833984398539863987398839893990399139923993399439953996399739983999400040014002400340044005400640074008400940104011401240134014401540164017401840194020402140224023402440254026402740284029403040314032403340344035403640374038403940404041404240434044404540464047404840494050405140524053405440554056405740584059406040614062406340644065406640674068406940704071407240734074407540764077407840794080408140824083408440854086408740884089409040914092409340944095409640974098409941004101410241034104410541064107410841094110411141124113411441154116411741184119412041214122412341244125412641274128412941304131413241334134413541364137413841394140414141424143414441454146414741484149415041514152415341544155415641574158415941604161416241634164416541664167416841694170417141724173417441754176417741784179418041814182418341844185418641874188418941904191419241934194419541964197419841994200420142024203420442054206420742084209421042114212421342144215421642174218421942204221422242234224422542264227422842294230423142324233423442354236423742384239424042414242424342444245424642474248424942504251425242534254425542564257425842594260426142624263426442654266426742684269427042714272427342744275427642774278427942804281428242834284428542864287428842894290429142924293429442954296429742984299430043014302430343044305430643074308430943104311431243134314431543164317431843194320432143224323432443254326432743284329433043314332433343344335433643374338433943404341434243434344434543464347434843494350435143524353435443554356435743584359436043614362436343644365436643674368436943704371437243734374437543764377437843794380438143824383438443854386438743884389439043914392439343944395439643974398439944004401440244034404440544064407440844094410441144124413441444154416441744184419442044214422442344244425442644274428442944304431443244334434443544364437443844394440444144424443444444454446444744484449445044514452445344544455445644574458445944604461446244634464446544664467446844694470447144724473447444754476447744784479448044814482448344844485448644874488448944904491449244934494449544964497449844994500450145024503450445054506450745084509451045114512451345144515451645174518451945204521452245234524452545264527452845294530453145324533453445354536453745384539454045414542454345444545454645474548454945504551455245534554455545564557455845594560456145624563456445654566456745684569457045714572457345744575457645774578457945804581458245834584458545864587458845894590459145924593459445954596459745984599460046014602460346044605460646074608460946104611461246134614461546164617461846194620462146224623462446254626462746284629463046314632463346344635463646374638463946404641464246434644464546464647464846494650465146524653465446554656465746584659466046614662466346644665466646674668466946704671467246734674467546764677467846794680468146824683468446854686468746884689469046914692469346944695469646974698469947004701470247034704470547064707470847094710471147124713471447154716471747184719472047214722472347244725472647274728472947304731473247334734473547364737473847394740474147424743474447454746474747484749475047514752475347544755475647574758475947604761476247634764476547664767476847694770477147724773477447754776477747784779478047814782478347844785478647874788478947904791479247934794479547964797479847994800480148024803480448054806480748084809481048114812481348144815481648174818481948204821482248234824482548264827482848294830483148324833483448354836483748384839484048414842484348444845484648474848484948504851485248534854485548564857485848594860486148624863486448654866486748684869487048714872487348744875487648774878487948804881488248834884488548864887488848894890489148924893489448954896489748984899490049014902490349044905490649074908490949104911491249134914491549164917491849194920492149224923492449254926492749284929493049314932493349344935493649374938493949404941494249434944494549464947494849494950495149524953495449554956495749584959496049614962496349644965496649674968496949704971497249734974497549764977497849794980498149824983498449854986498749884989499049914992499349944995499649974998499950005001500250035004500550065007500850095010501150125013501450155016501750185019502050215022502350245025502650275028502950305031503250335034503550365037503850395040504150425043504450455046504750485049505050515052505350545055505650575058505950605061506250635064506550665067506850695070507150725073507450755076507750785079508050815082508350845085508650875088508950905091509250935094509550965097509850995100510151025103510451055106510751085109511051115112511351145115511651175118511951205121512251235124512551265127512851295130513151325133513451355136513751385139514051415142514351445145514651475148514951505151515251535154515551565157515851595160516151625163516451655166516751685169517051715172517351745175517651775178517951805181518251835184518551865187518851895190519151925193519451955196519751985199520052015202520352045205520652075208520952105211521252135214521552165217521852195220522152225223522452255226522752285229523052315232523352345235523652375238523952405241524252435244524552465247524852495250525152525253525452555256525752585259526052615262526352645265526652675268526952705271527252735274527552765277527852795280528152825283528452855286528752885289529052915292529352945295529652975298529953005301530253035304530553065307530853095310531153125313531453155316531753185319532053215322532353245325532653275328532953305331533253335334533553365337533853395340534153425343534453455346534753485349535053515352535353545355535653575358535953605361536253635364536553665367536853695370537153725373537453755376537753785379538053815382538353845385538653875388538953905391539253935394539553965397539853995400540154025403540454055406540754085409541054115412541354145415541654175418541954205421542254235424542554265427542854295430543154325433543454355436543754385439544054415442544354445445544654475448544954505451545254535454545554565457545854595460546154625463546454655466546754685469547054715472547354745475547654775478547954805481548254835484548554865487548854895490549154925493549454955496549754985499550055015502550355045505550655075508550955105511551255135514551555165517551855195520552155225523552455255526552755285529553055315532553355345535553655375538553955405541554255435544554555465547554855495550555155525553555455555556555755585559556055615562556355645565556655675568556955705571557255735574557555765577557855795580558155825583558455855586558755885589559055915592559355945595559655975598559956005601560256035604560556065607560856095610561156125613561456155616561756185619562056215622562356245625562656275628562956305631563256335634563556365637563856395640564156425643564456455646564756485649565056515652565356545655565656575658565956605661566256635664566556665667566856695670567156725673567456755676567756785679568056815682568356845685568656875688568956905691569256935694569556965697569856995700570157025703570457055706570757085709571057115712571357145715571657175718571957205721572257235724572557265727572857295730573157325733573457355736573757385739574057415742574357445745574657475748574957505751575257535754575557565757575857595760576157625763576457655766576757685769577057715772577357745775577657775778577957805781578257835784578557865787578857895790579157925793579457955796579757985799580058015802580358045805580658075808580958105811581258135814581558165817581858195820582158225823582458255826582758285829583058315832583358345835583658375838583958405841584258435844584558465847584858495850585158525853585458555856585758585859586058615862586358645865586658675868586958705871587258735874587558765877587858795880588158825883588458855886588758885889589058915892589358945895589658975898589959005901590259035904590559065907590859095910591159125913591459155916591759185919592059215922592359245925592659275928592959305931593259335934593559365937593859395940594159425943594459455946594759485949595059515952595359545955595659575958595959605961596259635964596559665967596859695970597159725973597459755976597759785979598059815982598359845985598659875988598959905991599259935994599559965997599859996000600160026003600460056006600760086009601060116012601360146015601660176018601960206021602260236024602560266027602860296030603160326033603460356036603760386039604060416042604360446045604660476048604960506051605260536054605560566057605860596060606160626063606460656066606760686069607060716072607360746075607660776078607960806081608260836084608560866087608860896090609160926093609460956096609760986099610061016102610361046105610661076108610961106111611261136114611561166117611861196120612161226123612461256126612761286129613061316132613361346135613661376138613961406141614261436144614561466147614861496150615161526153615461556156615761586159616061616162616361646165616661676168616961706171617261736174617561766177617861796180618161826183618461856186618761886189619061916192619361946195619661976198619962006201620262036204620562066207620862096210621162126213621462156216621762186219622062216222622362246225622662276228622962306231623262336234623562366237623862396240624162426243624462456246624762486249625062516252625362546255625662576258625962606261626262636264626562666267626862696270627162726273627462756276627762786279628062816282628362846285628662876288628962906291629262936294629562966297629862996300630163026303630463056306630763086309631063116312631363146315631663176318631963206321632263236324632563266327632863296330633163326333633463356336633763386339634063416342634363446345634663476348634963506351635263536354635563566357635863596360636163626363636463656366636763686369637063716372637363746375637663776378637963806381638263836384638563866387638863896390639163926393639463956396639763986399640064016402640364046405640664076408640964106411641264136414641564166417641864196420642164226423642464256426642764286429643064316432643364346435643664376438643964406441644264436444644564466447644864496450645164526453645464556456645764586459646064616462646364646465646664676468646964706471647264736474647564766477647864796480648164826483648464856486648764886489649064916492649364946495649664976498649965006501650265036504650565066507650865096510651165126513651465156516651765186519652065216522652365246525652665276528652965306531653265336534653565366537653865396540654165426543654465456546654765486549655065516552655365546555655665576558655965606561656265636564656565666567656865696570657165726573657465756576657765786579658065816582658365846585658665876588658965906591659265936594659565966597659865996600660166026603660466056606660766086609661066116612661366146615661666176618661966206621662266236624662566266627662866296630663166326633663466356636663766386639664066416642664366446645664666476648664966506651665266536654665566566657665866596660666166626663666466656666666766686669667066716672667366746675667666776678667966806681668266836684668566866687668866896690669166926693669466956696669766986699670067016702670367046705670667076708670967106711671267136714671567166717671867196720672167226723672467256726672767286729673067316732673367346735673667376738673967406741674267436744674567466747674867496750675167526753675467556756675767586759676067616762676367646765676667676768676967706771677267736774677567766777677867796780678167826783678467856786678767886789679067916792679367946795679667976798679968006801680268036804680568066807680868096810681168126813681468156816681768186819682068216822682368246825682668276828682968306831683268336834683568366837683868396840684168426843684468456846684768486849685068516852685368546855685668576858685968606861686268636864686568666867686868696870687168726873687468756876687768786879688068816882688368846885688668876888688968906891689268936894689568966897689868996900690169026903690469056906690769086909691069116912691369146915691669176918691969206921692269236924692569266927692869296930693169326933693469356936693769386939694069416942694369446945694669476948694969506951695269536954695569566957695869596960696169626963696469656966696769686969697069716972697369746975697669776978697969806981698269836984698569866987698869896990699169926993699469956996699769986999700070017002700370047005700670077008700970107011701270137014701570167017701870197020702170227023702470257026702770287029703070317032
  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.2.36 - 2012-05-24
  5. Tor 0.2.2.36 updates the addresses for two of the eight directory
  6. authorities, fixes some potential anonymity and security issues,
  7. and fixes several crash bugs.
  8. Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
  9. known flaws, and nobody should be using them. You should upgrade. If
  10. you're using a Linux or BSD and its packages are obsolete, stop using
  11. those packages and upgrade anyway.
  12. o Directory authority changes:
  13. - Change IP address for maatuska (v3 directory authority).
  14. - Change IP address for ides (v3 directory authority), and rename
  15. it to turtles.
  16. o Security fixes:
  17. - When building or running with any version of OpenSSL earlier
  18. than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
  19. versions have a bug (CVE-2011-4576) in which their block cipher
  20. padding includes uninitialized data, potentially leaking sensitive
  21. information to any peer with whom they make a SSLv3 connection. Tor
  22. does not use SSL v3 by default, but a hostile client or server
  23. could force an SSLv3 connection in order to gain information that
  24. they shouldn't have been able to get. The best solution here is to
  25. upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
  26. or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
  27. to make sure that the bug can't happen.
  28. - Never use a bridge or a controller-supplied node as an exit, even
  29. if its exit policy allows it. Found by wanoskarnet. Fixes bug
  30. 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
  31. and 0.2.0.3-alpha (for bridge-purpose descriptors).
  32. - Only build circuits if we have a sufficient threshold of the total
  33. descriptors that are marked in the consensus with the "Exit"
  34. flag. This mitigates an attack proposed by wanoskarnet, in which
  35. all of a client's bridges collude to restrict the exit nodes that
  36. the client knows about. Fixes bug 5343.
  37. - Provide controllers with a safer way to implement the cookie
  38. authentication mechanism. With the old method, if another locally
  39. running program could convince a controller that it was the Tor
  40. process, then that program could trick the controller into telling
  41. it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
  42. authentication method uses a challenge-response approach to prevent
  43. this attack. Fixes bug 5185; implements proposal 193.
  44. o Major bugfixes:
  45. - Avoid logging uninitialized data when unable to decode a hidden
  46. service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
  47. - Avoid a client-side assertion failure when receiving an INTRODUCE2
  48. cell on a general purpose circuit. Fixes bug 5644; bugfix on
  49. 0.2.1.6-alpha.
  50. - Fix builds when the path to sed, openssl, or sha1sum contains
  51. spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
  52. on 0.2.2.1-alpha.
  53. - Correct our replacements for the timeradd() and timersub() functions
  54. on platforms that lack them (for example, Windows). The timersub()
  55. function is used when expiring circuits, while timeradd() is
  56. currently unused. Bug report and patch by Vektor. Fixes bug 4778;
  57. bugfix on 0.2.2.24-alpha.
  58. - Fix the SOCKET_OK test that we use to tell when socket
  59. creation fails so that it works on Win64. Fixes part of bug 4533;
  60. bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
  61. o Minor bugfixes:
  62. - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
  63. Fixes bug 5346; bugfix on 0.0.8pre3.
  64. - Make our number-parsing functions always treat too-large values
  65. as an error, even when those values exceed the width of the
  66. underlying type. Previously, if the caller provided these
  67. functions with minima or maxima set to the extreme values of the
  68. underlying integer type, these functions would return those
  69. values on overflow rather than treating overflow as an error.
  70. Fixes part of bug 5786; bugfix on 0.0.9.
  71. - Older Linux kernels erroneously respond to strange nmap behavior
  72. by having accept() return successfully with a zero-length
  73. socket. When this happens, just close the connection. Previously,
  74. we would try harder to learn the remote address: but there was
  75. no such remote address to learn, and our method for trying to
  76. learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
  77. on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
  78. - Correct parsing of certain date types in parse_http_time().
  79. Without this patch, If-Modified-Since would behave
  80. incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
  81. Esteban Manchado Velázques.
  82. - Change the BridgePassword feature (part of the "bridge community"
  83. design, which is not yet implemented) to use a time-independent
  84. comparison. The old behavior might have allowed an adversary
  85. to use timing to guess the BridgePassword value. Fixes bug 5543;
  86. bugfix on 0.2.0.14-alpha.
  87. - Detect and reject certain misformed escape sequences in
  88. configuration values. Previously, these values would cause us
  89. to crash if received in a torrc file or over an authenticated
  90. control port. Bug found by Esteban Manchado Velázquez, and
  91. independently by Robert Connolly from Matta Consulting who further
  92. noted that it allows a post-authentication heap overflow. Patch
  93. by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
  94. bugfix on 0.2.0.16-alpha.
  95. - Fix a compile warning when using the --enable-openbsd-malloc
  96. configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
  97. - During configure, detect when we're building with clang version
  98. 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
  99. CFLAGS. clang doesn't support them yet.
  100. - When sending an HTTP/1.1 proxy request, include a Host header.
  101. Fixes bug 5593; bugfix on 0.2.2.1-alpha.
  102. - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
  103. command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
  104. - If we hit the error case where routerlist_insert() replaces an
  105. existing (old) server descriptor, make sure to remove that
  106. server descriptor from the old_routers list. Fix related to bug
  107. 1776. Bugfix on 0.2.2.18-alpha.
  108. o Minor bugfixes (documentation and log messages):
  109. - Fix a typo in a log message in rend_service_rendezvous_has_opened().
  110. Fixes bug 4856; bugfix on Tor 0.0.6.
  111. - Update "ClientOnly" man page entry to explain that there isn't
  112. really any point to messing with it. Resolves ticket 5005.
  113. - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
  114. directory authority option (introduced in Tor 0.2.2.34).
  115. - Downgrade the "We're missing a certificate" message from notice
  116. to info: people kept mistaking it for a real problem, whereas it
  117. is seldom the problem even when we are failing to bootstrap. Fixes
  118. bug 5067; bugfix on 0.2.0.10-alpha.
  119. - Correctly spell "connect" in a log message on failure to create a
  120. controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
  121. - Clarify the behavior of MaxCircuitDirtiness with hidden service
  122. circuits. Fixes issue 5259.
  123. o Minor features:
  124. - Directory authorities now reject versions of Tor older than
  125. 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
  126. inclusive. These versions accounted for only a small fraction of
  127. the Tor network, and have numerous known security issues. Resolves
  128. issue 4788.
  129. - Update to the May 1 2012 Maxmind GeoLite Country database.
  130. - Feature removal:
  131. - When sending or relaying a RELAY_EARLY cell, we used to convert
  132. it to a RELAY cell if the connection was using the v1 link
  133. protocol. This was a workaround for older versions of Tor, which
  134. didn't handle RELAY_EARLY cells properly. Now that all supported
  135. versions can handle RELAY_EARLY cells, and now that we're enforcing
  136. the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
  137. remove this workaround. Addresses bug 4786.
  138. Changes in version 0.2.2.35 - 2011-12-16
  139. Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
  140. buffers code. Absolutely everybody should upgrade.
  141. The bug relied on an incorrect calculation when making data continuous
  142. in one of our IO buffers, if the first chunk of the buffer was
  143. misaligned by just the wrong amount. The miscalculation would allow an
  144. attacker to overflow a piece of heap-allocated memory. To mount this
  145. attack, the attacker would need to either open a SOCKS connection to
  146. Tor's SocksPort (usually restricted to localhost), or target a Tor
  147. instance configured to make its connections through a SOCKS proxy
  148. (which Tor does not do by default).
  149. Good security practice requires that all heap-overflow bugs should be
  150. presumed to be exploitable until proven otherwise, so we are treating
  151. this as a potential code execution attack. Please upgrade immediately!
  152. This bug does not affect bufferevents-based builds of Tor. Special
  153. thanks to "Vektor" for reporting this issue to us!
  154. Tor 0.2.2.35 also fixes several bugs in previous versions, including
  155. crash bugs for unusual configurations, and a long-term bug that
  156. would prevent Tor from starting on Windows machines with draconian
  157. AV software.
  158. With this release, we remind everyone that 0.2.0.x has reached its
  159. formal end-of-life. Those Tor versions have many known flaws, and
  160. nobody should be using them. You should upgrade -- ideally to the
  161. 0.2.2.x series. If you're using a Linux or BSD and its packages are
  162. obsolete, stop using those packages and upgrade anyway.
  163. The Tor 0.2.1.x series is also approaching its end-of-life: it will no
  164. longer receive support after some time in early 2012.
  165. o Major bugfixes:
  166. - Fix a heap overflow bug that could occur when trying to pull
  167. data into the first chunk of a buffer, when that chunk had
  168. already had some data drained from it. Fixes CVE-2011-2778;
  169. bugfix on 0.2.0.16-alpha. Reported by "Vektor".
  170. - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
  171. that it doesn't attempt to allocate a socketpair. This could cause
  172. some problems on Windows systems with overzealous firewalls. Fix for
  173. bug 4457; workaround for Libevent versions 2.0.1-alpha through
  174. 2.0.15-stable.
  175. - If we mark an OR connection for close based on a cell we process,
  176. don't process any further cells on it. We already avoid further
  177. reads on marked-for-close connections, but now we also discard the
  178. cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
  179. which was the first version where we might mark a connection for
  180. close based on processing a cell on it.
  181. - Correctly sanity-check that we don't underflow on a memory
  182. allocation (and then assert) for hidden service introduction
  183. point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
  184. bugfix on 0.2.1.5-alpha.
  185. - Fix a memory leak when we check whether a hidden service
  186. descriptor has any usable introduction points left. Fixes bug
  187. 4424. Bugfix on 0.2.2.25-alpha.
  188. - Don't crash when we're running as a relay and don't have a GeoIP
  189. file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
  190. we've had in the 0.2.3.x branch already.
  191. - When running as a client, do not print a misleading (and plain
  192. wrong) log message that we're collecting "directory request"
  193. statistics: clients don't collect statistics. Also don't create a
  194. useless (because empty) stats file in the stats/ directory. Fixes
  195. bug 4353; bugfix on 0.2.2.34.
  196. o Minor bugfixes:
  197. - Detect failure to initialize Libevent. This fix provides better
  198. detection for future instances of bug 4457.
  199. - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
  200. function. This was eating up hideously large amounts of time on some
  201. busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
  202. - Resolve an integer overflow bug in smartlist_ensure_capacity().
  203. Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
  204. Mansour Moufid.
  205. - Don't warn about unused log_mutex in log.c when building with
  206. --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
  207. 0.1.0.6-rc which introduced --disable-threads.
  208. - When configuring, starting, or stopping an NT service, stop
  209. immediately after the service configuration attempt has succeeded
  210. or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
  211. - When sending a NETINFO cell, include the original address
  212. received for the other side, not its canonical address. Found
  213. by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
  214. - Fix a typo in a hibernation-related log message. Fixes bug 4331;
  215. bugfix on 0.2.2.23-alpha; found by "tmpname0901".
  216. - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
  217. occurred when a client tried to fetch a descriptor for a bridge
  218. in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
  219. - Backport fixes for a pair of compilation warnings on Windows.
  220. Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
  221. - If we had ever tried to call tor_addr_to_str on an address of
  222. unknown type, we would have done a strdup on an uninitialized
  223. buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
  224. Reported by "troll_un".
  225. - Correctly detect and handle transient lookup failures from
  226. tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
  227. Reported by "troll_un".
  228. - Fix null-pointer access that could occur if TLS allocation failed.
  229. Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
  230. - Use tor_socket_t type for listener argument to accept(). Fixes bug
  231. 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
  232. o Minor features:
  233. - Add two new config options for directory authorities:
  234. AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
  235. Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
  236. that is always sufficient to satisfy the bandwidth requirement for
  237. the Guard flag. Now it will be easier for researchers to simulate
  238. Tor networks with different values. Resolves ticket 4484.
  239. - When Tor ignores a hidden service specified in its configuration,
  240. include the hidden service's directory in the warning message.
  241. Previously, we would only tell the user that some hidden service
  242. was ignored. Bugfix on 0.0.6; fixes bug 4426.
  243. - Update to the December 6 2011 Maxmind GeoLite Country database.
  244. o Packaging changes:
  245. - Make it easier to automate expert package builds on Windows,
  246. by removing an absolute path from makensis.exe command.
  247. Changes in version 0.2.2.34 - 2011-10-26
  248. Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
  249. can deanonymize Tor users. Everybody should upgrade.
  250. The attack relies on four components: 1) Clients reuse their TLS cert
  251. when talking to different relays, so relays can recognize a user by
  252. the identity key in her cert. 2) An attacker who knows the client's
  253. identity key can probe each guard relay to see if that identity key
  254. is connected to that guard relay right now. 3) A variety of active
  255. attacks in the literature (starting from "Low-Cost Traffic Analysis
  256. of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
  257. discover the guard relays that a Tor user visiting the website is using.
  258. 4) Clients typically pick three guards at random, so the set of guards
  259. for a given user could well be a unique fingerprint for her. This
  260. release fixes components #1 and #2, which is enough to block the attack;
  261. the other two remain as open research problems. Special thanks to
  262. "frosty_un" for reporting the issue to us!
  263. Clients should upgrade so they are no longer recognizable by the TLS
  264. certs they present. Relays should upgrade so they no longer allow a
  265. remote attacker to probe them to test whether unpatched clients are
  266. currently connected to them.
  267. This release also fixes several vulnerabilities that allow an attacker
  268. to enumerate bridge relays. Some bridge enumeration attacks still
  269. remain; see for example proposal 188.
  270. o Privacy/anonymity fixes (clients):
  271. - Clients and bridges no longer send TLS certificate chains on
  272. outgoing OR connections. Previously, each client or bridge would
  273. use the same cert chain for all outgoing OR connections until
  274. its IP address changes, which allowed any relay that the client
  275. or bridge contacted to determine which entry guards it is using.
  276. Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
  277. - If a relay receives a CREATE_FAST cell on a TLS connection, it
  278. no longer considers that connection as suitable for satisfying a
  279. circuit EXTEND request. Now relays can protect clients from the
  280. CVE-2011-2768 issue even if the clients haven't upgraded yet.
  281. - Directory authorities no longer assign the Guard flag to relays
  282. that haven't upgraded to the above "refuse EXTEND requests
  283. to client connections" fix. Now directory authorities can
  284. protect clients from the CVE-2011-2768 issue even if neither
  285. the clients nor the relays have upgraded yet. There's a new
  286. "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
  287. to let us transition smoothly, else tomorrow there would be no
  288. guard relays.
  289. o Privacy/anonymity fixes (bridge enumeration):
  290. - Bridge relays now do their directory fetches inside Tor TLS
  291. connections, like all the other clients do, rather than connecting
  292. directly to the DirPort like public relays do. Removes another
  293. avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
  294. - Bridges relays now build circuits for themselves in a more similar
  295. way to how clients build them. Removes another avenue for
  296. enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
  297. when bridges were introduced.
  298. - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
  299. that they initiated. Relays could distinguish incoming bridge
  300. connections from client connections, creating another avenue for
  301. enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
  302. Found by "frosty_un".
  303. o Major bugfixes:
  304. - Fix a crash bug when changing node restrictions while a DNS lookup
  305. is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
  306. by "Tey'".
  307. - Don't launch a useless circuit after failing to use one of a
  308. hidden service's introduction points. Previously, we would
  309. launch a new introduction circuit, but not set the hidden service
  310. which that circuit was intended to connect to, so it would never
  311. actually be used. A different piece of code would then create a
  312. new introduction circuit correctly. Bug reported by katmagic and
  313. found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
  314. o Minor bugfixes:
  315. - Change an integer overflow check in the OpenBSD_Malloc code so
  316. that GCC is less likely to eliminate it as impossible. Patch
  317. from Mansour Moufid. Fixes bug 4059.
  318. - When a hidden service turns an extra service-side introduction
  319. circuit into a general-purpose circuit, free the rend_data and
  320. intro_key fields first, so we won't leak memory if the circuit
  321. is cannibalized for use as another service-side introduction
  322. circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
  323. - Bridges now skip DNS self-tests, to act a little more stealthily.
  324. Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
  325. bridges. Patch by "warms0x".
  326. - Fix internal bug-checking logic that was supposed to catch
  327. failures in digest generation so that it will fail more robustly
  328. if we ask for a nonexistent algorithm. Found by Coverity Scan.
  329. Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
  330. - Report any failure in init_keys() calls launched because our
  331. IP address has changed. Spotted by Coverity Scan. Bugfix on
  332. 0.1.1.4-alpha; fixes CID 484.
  333. o Minor bugfixes (log messages and documentation):
  334. - Remove a confusing dollar sign from the example fingerprint in the
  335. man page, and also make the example fingerprint a valid one. Fixes
  336. bug 4309; bugfix on 0.2.1.3-alpha.
  337. - The next version of Windows will be called Windows 8, and it has
  338. a major version of 6, minor version of 2. Correctly identify that
  339. version instead of calling it "Very recent version". Resolves
  340. ticket 4153; reported by funkstar.
  341. - Downgrade log messages about circuit timeout calibration from
  342. "notice" to "info": they don't require or suggest any human
  343. intervention. Patch from Tom Lowenthal. Fixes bug 4063;
  344. bugfix on 0.2.2.14-alpha.
  345. o Minor features:
  346. - Turn on directory request statistics by default and include them in
  347. extra-info descriptors. Don't break if we have no GeoIP database.
  348. Backported from 0.2.3.1-alpha; implements ticket 3951.
  349. - Update to the October 4 2011 Maxmind GeoLite Country database.
  350. Changes in version 0.2.1.31 - 2011-10-26
  351. Tor 0.2.1.31 backports important security and privacy fixes for
  352. oldstable. This release is intended only for package maintainers and
  353. others who cannot use the 0.2.2 stable series. All others should be
  354. using Tor 0.2.2.x or newer.
  355. o Security fixes (also included in 0.2.2.x):
  356. - Replace all potentially sensitive memory comparison operations
  357. with versions whose runtime does not depend on the data being
  358. compared. This will help resist a class of attacks where an
  359. adversary can use variations in timing information to learn
  360. sensitive data. Fix for one case of bug 3122. (Safe memcmp
  361. implementation by Robert Ransom based partially on code by DJB.)
  362. - Fix an assert in parsing router descriptors containing IPv6
  363. addresses. This one took down the directory authorities when
  364. somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
  365. o Privacy/anonymity fixes (also included in 0.2.2.x):
  366. - Clients and bridges no longer send TLS certificate chains on
  367. outgoing OR connections. Previously, each client or bridge would
  368. use the same cert chain for all outgoing OR connections until
  369. its IP address changes, which allowed any relay that the client
  370. or bridge contacted to determine which entry guards it is using.
  371. Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
  372. - If a relay receives a CREATE_FAST cell on a TLS connection, it
  373. no longer considers that connection as suitable for satisfying a
  374. circuit EXTEND request. Now relays can protect clients from the
  375. CVE-2011-2768 issue even if the clients haven't upgraded yet.
  376. - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
  377. that they initiated. Relays could distinguish incoming bridge
  378. connections from client connections, creating another avenue for
  379. enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
  380. Found by "frosty_un".
  381. - When receiving a hidden service descriptor, check that it is for
  382. the hidden service we wanted. Previously, Tor would store any
  383. hidden service descriptors that a directory gave it, whether it
  384. wanted them or not. This wouldn't have let an attacker impersonate
  385. a hidden service, but it did let directories pre-seed a client
  386. with descriptors that it didn't want. Bugfix on 0.0.6.
  387. - Avoid linkability based on cached hidden service descriptors: forget
  388. all hidden service descriptors cached as a client when processing a
  389. SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
  390. - Make the bridge directory authority refuse to answer directory
  391. requests for "all" descriptors. It used to include bridge
  392. descriptors in its answer, which was a major information leak.
  393. Found by "piebeer". Bugfix on 0.2.0.3-alpha.
  394. - Don't attach new streams to old rendezvous circuits after SIGNAL
  395. NEWNYM. Previously, we would keep using an existing rendezvous
  396. circuit if it remained open (i.e. if it were kept open by a
  397. long-lived stream, or if a new stream were attached to it before
  398. Tor could notice that it was old and no longer in use). Bugfix on
  399. 0.1.1.15-rc; fixes bug 3375.
  400. o Minor bugfixes (also included in 0.2.2.x):
  401. - When we restart our relay, we might get a successful connection
  402. from the outside before we've started our reachability tests,
  403. triggering a warning: "ORPort found reachable, but I have no
  404. routerinfo yet. Failing to inform controller of success." This
  405. bug was harmless unless Tor is running under a controller
  406. like Vidalia, in which case the controller would never get a
  407. REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
  408. fixes bug 1172.
  409. - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
  410. enabled. Fixes bug 1526.
  411. - Remove undocumented option "-F" from tor-resolve: it hasn't done
  412. anything since 0.2.1.16-rc.
  413. - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
  414. None of the cases where we did this before were wrong, but by making
  415. this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
  416. - Fix a rare crash bug that could occur when a client was configured
  417. with a large number of bridges. Fixes bug 2629; bugfix on
  418. 0.2.1.2-alpha. Bugfix by trac user "shitlei".
  419. - Correct the warning displayed when a rendezvous descriptor exceeds
  420. the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
  421. John Brooks.
  422. - Fix an uncommon assertion failure when running with DNSPort under
  423. heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
  424. - When warning about missing zlib development packages during compile,
  425. give the correct package names. Bugfix on 0.2.0.1-alpha.
  426. - Require that introduction point keys and onion keys have public
  427. exponent 65537. Bugfix on 0.2.0.10-alpha.
  428. - Do not crash when our configuration file becomes unreadable, for
  429. example due to a permissions change, between when we start up
  430. and when a controller calls SAVECONF. Fixes bug 3135; bugfix
  431. on 0.0.9pre6.
  432. - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
  433. Fixes bug 3208.
  434. - Always NUL-terminate the sun_path field of a sockaddr_un before
  435. passing it to the kernel. (Not a security issue: kernels are
  436. smart enough to reject bad sockaddr_uns.) Found by Coverity;
  437. CID #428. Bugfix on Tor 0.2.0.3-alpha.
  438. - Don't stack-allocate the list of supplementary GIDs when we're
  439. about to log them. Stack-allocating NGROUPS_MAX gid_t elements
  440. could take up to 256K, which is way too much stack. Found by
  441. Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
  442. o Minor bugfixes (only in 0.2.1.x):
  443. - Resume using micro-version numbers in 0.2.1.x: our Debian packages
  444. rely on them. Bugfix on 0.2.1.30.
  445. - Use git revisions instead of svn revisions when generating our
  446. micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
  447. o Minor features (also included in 0.2.2.x):
  448. - Adjust the expiration time on our SSL session certificates to
  449. better match SSL certs seen in the wild. Resolves ticket 4014.
  450. - Allow nameservers with IPv6 address. Resolves bug 2574.
  451. - Update to the October 4 2011 Maxmind GeoLite Country database.
  452. Changes in version 0.2.2.33 - 2011-09-13
  453. Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
  454. TLS handshake that makes relays and bridges that run this new version
  455. reachable from Iran again.
  456. o Major bugfixes:
  457. - Avoid an assertion failure when reloading a configuration with
  458. TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
  459. 3923; bugfix on 0.2.2.25-alpha.
  460. o Minor features (security):
  461. - Check for replays of the public-key encrypted portion of an
  462. INTRODUCE1 cell, in addition to the current check for replays of
  463. the g^x value. This prevents a possible class of active attacks
  464. by an attacker who controls both an introduction point and a
  465. rendezvous point, and who uses the malleability of AES-CTR to
  466. alter the encrypted g^x portion of the INTRODUCE1 cell. We think
  467. that these attacks are infeasible (requiring the attacker to send
  468. on the order of zettabytes of altered cells in a short interval),
  469. but we'd rather block them off in case there are any classes of
  470. this attack that we missed. Reported by Willem Pinckaers.
  471. o Minor features:
  472. - Adjust the expiration time on our SSL session certificates to
  473. better match SSL certs seen in the wild. Resolves ticket 4014.
  474. - Change the default required uptime for a relay to be accepted as
  475. a HSDir (hidden service directory) from 24 hours to 25 hours.
  476. Improves on 0.2.0.10-alpha; resolves ticket 2649.
  477. - Add a VoteOnHidServDirectoriesV2 config option to allow directory
  478. authorities to abstain from voting on assignment of the HSDir
  479. consensus flag. Related to bug 2649.
  480. - Update to the September 6 2011 Maxmind GeoLite Country database.
  481. o Minor bugfixes (documentation and log messages):
  482. - Correct the man page to explain that HashedControlPassword and
  483. CookieAuthentication can both be set, in which case either method
  484. is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
  485. when we decided to allow these config options to both be set. Issue
  486. raised by bug 3898.
  487. - Demote the 'replay detected' log message emitted when a hidden
  488. service receives the same Diffie-Hellman public key in two different
  489. INTRODUCE2 cells to info level. A normal Tor client can cause that
  490. log message during its normal operation. Bugfix on 0.2.1.6-alpha;
  491. fixes part of bug 2442.
  492. - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
  493. level. There is nothing that a hidden service's operator can do
  494. to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
  495. of bug 2442.
  496. - Clarify a log message specifying the characters permitted in
  497. HiddenServiceAuthorizeClient client names. Previously, the log
  498. message said that "[A-Za-z0-9+-_]" were permitted; that could have
  499. given the impression that every ASCII character between "+" and "_"
  500. was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
  501. o Build fixes:
  502. - Provide a substitute implementation of lround() for MSVC, which
  503. apparently lacks it. Patch from Gisle Vanem.
  504. - Clean up some code issues that prevented Tor from building on older
  505. BSDs. Fixes bug 3894; reported by "grarpamp".
  506. - Search for a platform-specific version of "ar" when cross-compiling.
  507. Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
  508. Changes in version 0.2.2.32 - 2011-08-27
  509. The Tor 0.2.2 release series is dedicated to the memory of Andreas
  510. Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
  511. a founder of the PETS community, a leader in our field, a mentor,
  512. and a friend. He left us with these words: "I had the possibility
  513. to contribute to this world that is not as it should be. I hope I
  514. could help in some areas to make the world a better place, and that
  515. I could also encourage other people to be engaged in improving the
  516. world. Please, stay engaged. This world needs you, your love, your
  517. initiative -- now I cannot be part of that anymore."
  518. Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
  519. ready. More than two years in the making, this release features improved
  520. client performance and hidden service reliability, better compatibility
  521. for Android, correct behavior for bridges that listen on more than
  522. one address, more extensible and flexible directory object handling,
  523. better reporting of network statistics, improved code security, and
  524. many many other features and bugfixes.
  525. o Major features (client performance):
  526. - When choosing which cells to relay first, relays now favor circuits
  527. that have been quiet recently, to provide lower latency for
  528. low-volume circuits. By default, relays enable or disable this
  529. feature based on a setting in the consensus. They can override
  530. this default by using the new "CircuitPriorityHalflife" config
  531. option. Design and code by Ian Goldberg, Can Tang, and Chris
  532. Alexander.
  533. - Directory authorities now compute consensus weightings that instruct
  534. clients how to weight relays flagged as Guard, Exit, Guard+Exit,
  535. and no flag. Clients use these weightings to distribute network load
  536. more evenly across these different relay types. The weightings are
  537. in the consensus so we can change them globally in the future. Extra
  538. thanks to "outofwords" for finding some nasty security bugs in
  539. the first implementation of this feature.
  540. o Major features (client performance, circuit build timeout):
  541. - Tor now tracks how long it takes to build client-side circuits
  542. over time, and adapts its timeout to local network performance.
  543. Since a circuit that takes a long time to build will also provide
  544. bad performance, we get significant latency improvements by
  545. discarding the slowest 20% of circuits. Specifically, Tor creates
  546. circuits more aggressively than usual until it has enough data
  547. points for a good timeout estimate. Implements proposal 151.
  548. - Circuit build timeout constants can be controlled by consensus
  549. parameters. We set good defaults for these parameters based on
  550. experimentation on broadband and simulated high-latency links.
  551. - Circuit build time learning can be disabled via consensus parameter
  552. or by the client via a LearnCircuitBuildTimeout config option. We
  553. also automatically disable circuit build time calculation if either
  554. AuthoritativeDirectory is set, or if we fail to write our state
  555. file. Implements ticket 1296.
  556. o Major features (relays use their capacity better):
  557. - Set SO_REUSEADDR socket option on all sockets, not just
  558. listeners. This should help busy exit nodes avoid running out of
  559. useable ports just because all the ports have been used in the
  560. near past. Resolves issue 2850.
  561. - Relays now save observed peak bandwidth throughput rates to their
  562. state file (along with total usage, which was already saved),
  563. so that they can determine their correct estimated bandwidth on
  564. restart. Resolves bug 1863, where Tor relays would reset their
  565. estimated bandwidth to 0 after restarting.
  566. - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
  567. should give us approximately 40-50% more Guard-flagged nodes,
  568. improving the anonymity the Tor network can provide and also
  569. decreasing the dropoff in throughput that relays experience when
  570. they first get the Guard flag.
  571. - Directory authorities now take changes in router IP address and
  572. ORPort into account when determining router stability. Previously,
  573. if a router changed its IP or ORPort, the authorities would not
  574. treat it as having any downtime for the purposes of stability
  575. calculation, whereas clients would experience downtime since the
  576. change would take a while to propagate to them. Resolves issue 1035.
  577. - New AccelName and AccelDir options add support for dynamic OpenSSL
  578. hardware crypto acceleration engines.
  579. o Major features (relays control their load better):
  580. - Exit relays now try harder to block exit attempts from unknown
  581. relays, to make it harder for people to use them as one-hop proxies
  582. a la tortunnel. Controlled by the refuseunknownexits consensus
  583. parameter (currently enabled), or you can override it on your
  584. relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
  585. based on a variant of proposal 163.
  586. - Add separate per-conn write limiting to go with the per-conn read
  587. limiting. We added a global write limit in Tor 0.1.2.5-alpha,
  588. but never per-conn write limits.
  589. - New consensus params "bwconnrate" and "bwconnburst" to let us
  590. rate-limit client connections as they enter the network. It's
  591. controlled in the consensus so we can turn it on and off for
  592. experiments. It's starting out off. Based on proposal 163.
  593. o Major features (controllers):
  594. - Export GeoIP information on bridge usage to controllers even if we
  595. have not yet been running for 24 hours. Now Vidalia bridge operators
  596. can get more accurate and immediate feedback about their
  597. contributions to the network.
  598. - Add an __OwningControllerProcess configuration option and a
  599. TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
  600. that when it exits, Tor will shut down. Implements feature 3049.
  601. o Major features (directory authorities):
  602. - Directory authorities now create, vote on, and serve multiple
  603. parallel formats of directory data as part of their voting process.
  604. Partially implements Proposal 162: "Publish the consensus in
  605. multiple flavors".
  606. - Directory authorities now agree on and publish small summaries
  607. of router information that clients can use in place of regular
  608. server descriptors. This transition will allow Tor 0.2.3 clients
  609. to use far less bandwidth for downloading information about the
  610. network. Begins the implementation of Proposal 158: "Clients
  611. download consensus + microdescriptors".
  612. - The directory voting system is now extensible to use multiple hash
  613. algorithms for signatures and resource selection. Newer formats
  614. are signed with SHA256, with a possibility for moving to a better
  615. hash algorithm in the future.
  616. - Directory authorities can now vote on arbitary integer values as
  617. part of the consensus process. This is designed to help set
  618. network-wide parameters. Implements proposal 167.
  619. o Major features and bugfixes (node selection):
  620. - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
  621. ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
  622. options. Previously, we had been ambiguous in describing what
  623. counted as an "exit" node, and what operations exactly "StrictNodes
  624. 0" would permit. This created confusion when people saw nodes built
  625. through unexpected circuits, and made it hard to tell real bugs from
  626. surprises. Now the intended behavior is:
  627. . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
  628. a node that delivers user traffic outside the Tor network.
  629. . "Entry", in the context of EntryNodes, means a node used as the
  630. first hop of a multihop circuit. It doesn't include direct
  631. connections to directory servers.
  632. . "ExcludeNodes" applies to all nodes.
  633. . "StrictNodes" changes the behavior of ExcludeNodes only. When
  634. StrictNodes is set, Tor should avoid all nodes listed in
  635. ExcludeNodes, even when it will make user requests fail. When
  636. StrictNodes is *not* set, then Tor should follow ExcludeNodes
  637. whenever it can, except when it must use an excluded node to
  638. perform self-tests, connect to a hidden service, provide a
  639. hidden service, fulfill a .exit request, upload directory
  640. information, or fetch directory information.
  641. Collectively, the changes to implement the behavior fix bug 1090.
  642. - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
  643. change during a config reload, mark and discard all our origin
  644. circuits. This fix should address edge cases where we change the
  645. config options and but then choose a circuit that we created before
  646. the change.
  647. - Make EntryNodes config option much more aggressive even when
  648. StrictNodes is not set. Before it would prepend your requested
  649. entrynodes to your list of guard nodes, but feel free to use others
  650. after that. Now it chooses only from your EntryNodes if any of
  651. those are available, and only falls back to others if a) they're
  652. all down and b) StrictNodes is not set.
  653. - Now we refresh your entry guards from EntryNodes at each consensus
  654. fetch -- rather than just at startup and then they slowly rot as
  655. the network changes.
  656. - Add support for the country code "{??}" in torrc options like
  657. ExcludeNodes, to indicate all routers of unknown country. Closes
  658. bug 1094.
  659. - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
  660. a node is listed in both, it's treated as excluded.
  661. - ExcludeNodes now applies to directory nodes -- as a preference if
  662. StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
  663. Don't exclude all the directory authorities and set StrictNodes to 1
  664. unless you really want your Tor to break.
  665. - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
  666. - ExcludeExitNodes now overrides .exit requests.
  667. - We don't use bridges listed in ExcludeNodes.
  668. - When StrictNodes is 1:
  669. . We now apply ExcludeNodes to hidden service introduction points
  670. and to rendezvous points selected by hidden service users. This
  671. can make your hidden service less reliable: use it with caution!
  672. . If we have used ExcludeNodes on ourself, do not try relay
  673. reachability self-tests.
  674. . If we have excluded all the directory authorities, we will not
  675. even try to upload our descriptor if we're a relay.
  676. . Do not honor .exit requests to an excluded node.
  677. - When the set of permitted nodes changes, we now remove any mappings
  678. introduced via TrackExitHosts to now-excluded nodes. Bugfix on
  679. 0.1.0.1-rc.
  680. - We never cannibalize a circuit that had excluded nodes on it, even
  681. if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
  682. - Improve log messages related to excluded nodes.
  683. o Major features (misc):
  684. - Numerous changes, bugfixes, and workarounds from Nathan Freitas
  685. to help Tor build correctly for Android phones.
  686. - The options SocksPort, ControlPort, and so on now all accept a
  687. value "auto" that opens a socket on an OS-selected port. A
  688. new ControlPortWriteToFile option tells Tor to write its
  689. actual control port or ports to a chosen file. If the option
  690. ControlPortFileGroupReadable is set, the file is created as
  691. group-readable. Now users can run two Tor clients on the same
  692. system without needing to manually mess with parameters. Resolves
  693. part of ticket 3076.
  694. - Tor now supports tunneling all of its outgoing connections over
  695. a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
  696. configuration options. Code by Christopher Davis.
  697. o Code security improvements:
  698. - Replace all potentially sensitive memory comparison operations
  699. with versions whose runtime does not depend on the data being
  700. compared. This will help resist a class of attacks where an
  701. adversary can use variations in timing information to learn
  702. sensitive data. Fix for one case of bug 3122. (Safe memcmp
  703. implementation by Robert Ransom based partially on code by DJB.)
  704. - Enable Address Space Layout Randomization (ASLR) and Data Execution
  705. Prevention (DEP) by default on Windows to make it harder for
  706. attackers to exploit vulnerabilities. Patch from John Brooks.
  707. - New "--enable-gcc-hardening" ./configure flag (off by default)
  708. to turn on gcc compile time hardening options. It ensures
  709. that signed ints have defined behavior (-fwrapv), enables
  710. -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
  711. with canaries (-fstack-protector-all), turns on ASLR protection if
  712. supported by the kernel (-fPIE, -pie), and adds additional security
  713. related warnings. Verified to work on Mac OS X and Debian Lenny.
  714. - New "--enable-linker-hardening" ./configure flag (off by default)
  715. to turn on ELF specific hardening features (relro, now). This does
  716. not work with Mac OS X or any other non-ELF binary format.
  717. - Always search the Windows system directory for system DLLs, and
  718. nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
  719. - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
  720. current and future memory pages via mlockall(). On supported
  721. platforms (modern Linux and probably BSD but not Windows or OS X),
  722. this should effectively disable any and all attempts to page out
  723. memory. This option requires that you start your Tor as root --
  724. if you use DisableAllSwap, please consider using the User option
  725. to properly reduce the privileges of your Tor.
  726. o Major bugfixes (crashes):
  727. - Fix crash bug on platforms where gmtime and localtime can return
  728. NULL. Windows 7 users were running into this one. Fixes part of bug
  729. 2077. Bugfix on all versions of Tor. Found by boboper.
  730. - Introduce minimum/maximum values that clients will believe
  731. from the consensus. Now we'll have a better chance to avoid crashes
  732. or worse when a consensus param has a weird value.
  733. - Fix a rare crash bug that could occur when a client was configured
  734. with a large number of bridges. Fixes bug 2629; bugfix on
  735. 0.2.1.2-alpha. Bugfix by trac user "shitlei".
  736. - Do not crash when our configuration file becomes unreadable, for
  737. example due to a permissions change, between when we start up
  738. and when a controller calls SAVECONF. Fixes bug 3135; bugfix
  739. on 0.0.9pre6.
  740. - If we're in the pathological case where there's no exit bandwidth
  741. but there is non-exit bandwidth, or no guard bandwidth but there
  742. is non-guard bandwidth, don't crash during path selection. Bugfix
  743. on 0.2.0.3-alpha.
  744. - Fix a crash bug when trying to initialize the evdns module in
  745. Libevent 2. Bugfix on 0.2.1.16-rc.
  746. o Major bugfixes (stability):
  747. - Fix an assert in parsing router descriptors containing IPv6
  748. addresses. This one took down the directory authorities when
  749. somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
  750. - Fix an uncommon assertion failure when running with DNSPort under
  751. heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
  752. - Treat an unset $HOME like an empty $HOME rather than triggering an
  753. assert. Bugfix on 0.0.8pre1; fixes bug 1522.
  754. - More gracefully handle corrupt state files, removing asserts
  755. in favor of saving a backup and resetting state.
  756. - Instead of giving an assertion failure on an internal mismatch
  757. on estimated freelist size, just log a BUG warning and try later.
  758. Mitigates but does not fix bug 1125.
  759. - Fix an assert that got triggered when using the TestingTorNetwork
  760. configuration option and then issuing a GETINFO config-text control
  761. command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
  762. - If the cached cert file is unparseable, warn but don't exit.
  763. o Privacy fixes (relays/bridges):
  764. - Don't list Windows capabilities in relay descriptors. We never made
  765. use of them, and maybe it's a bad idea to publish them. Bugfix
  766. on 0.1.1.8-alpha.
  767. - If the Nickname configuration option isn't given, Tor would pick a
  768. nickname based on the local hostname as the nickname for a relay.
  769. Because nicknames are not very important in today's Tor and the
  770. "Unnamed" nickname has been implemented, this is now problematic
  771. behavior: It leaks information about the hostname without being
  772. useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
  773. introduced the Unnamed nickname. Reported by tagnaq.
  774. - Maintain separate TLS contexts and certificates for incoming and
  775. outgoing connections in bridge relays. Previously we would use the
  776. same TLS contexts and certs for incoming and outgoing connections.
  777. Bugfix on 0.2.0.3-alpha; addresses bug 988.
  778. - Maintain separate identity keys for incoming and outgoing TLS
  779. contexts in bridge relays. Previously we would use the same
  780. identity keys for incoming and outgoing TLS contexts. Bugfix on
  781. 0.2.0.3-alpha; addresses the other half of bug 988.
  782. - Make the bridge directory authority refuse to answer directory
  783. requests for "all descriptors". It used to include bridge
  784. descriptors in its answer, which was a major information leak.
  785. Found by "piebeer". Bugfix on 0.2.0.3-alpha.
  786. o Privacy fixes (clients):
  787. - When receiving a hidden service descriptor, check that it is for
  788. the hidden service we wanted. Previously, Tor would store any
  789. hidden service descriptors that a directory gave it, whether it
  790. wanted them or not. This wouldn't have let an attacker impersonate
  791. a hidden service, but it did let directories pre-seed a client
  792. with descriptors that it didn't want. Bugfix on 0.0.6.
  793. - Start the process of disabling ".exit" address notation, since it
  794. can be used for a variety of esoteric application-level attacks
  795. on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
  796. on 0.0.9rc5.
  797. - Reject attempts at the client side to open connections to private
  798. IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
  799. a randomly chosen exit node. Attempts to do so are always
  800. ill-defined, generally prevented by exit policies, and usually
  801. in error. This will also help to detect loops in transparent
  802. proxy configurations. You can disable this feature by setting
  803. "ClientRejectInternalAddresses 0" in your torrc.
  804. - Log a notice when we get a new control connection. Now it's easier
  805. for security-conscious users to recognize when a local application
  806. is knocking on their controller door. Suggested by bug 1196.
  807. o Privacy fixes (newnym):
  808. - Avoid linkability based on cached hidden service descriptors: forget
  809. all hidden service descriptors cached as a client when processing a
  810. SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
  811. - On SIGHUP, do not clear out all TrackHostExits mappings, client
  812. DNS cache entries, and virtual address mappings: that's what
  813. NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
  814. - Don't attach new streams to old rendezvous circuits after SIGNAL
  815. NEWNYM. Previously, we would keep using an existing rendezvous
  816. circuit if it remained open (i.e. if it were kept open by a
  817. long-lived stream, or if a new stream were attached to it before
  818. Tor could notice that it was old and no longer in use). Bugfix on
  819. 0.1.1.15-rc; fixes bug 3375.
  820. o Major bugfixes (relay bandwidth accounting):
  821. - Fix a bug that could break accounting on 64-bit systems with large
  822. time_t values, making them hibernate for impossibly long intervals.
  823. Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
  824. - Fix a bug in bandwidth accounting that could make us use twice
  825. the intended bandwidth when our interval start changes due to
  826. daylight saving time. Now we tolerate skew in stored vs computed
  827. interval starts: if the start of the period changes by no more than
  828. 50% of the period's duration, we remember bytes that we transferred
  829. in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
  830. o Major bugfixes (bridges):
  831. - Bridges now use "reject *:*" as their default exit policy. Bugfix
  832. on 0.2.0.3-alpha. Fixes bug 1113.
  833. - If you configure your bridge with a known identity fingerprint,
  834. and the bridge authority is unreachable (as it is in at least
  835. one country now), fall back to directly requesting the descriptor
  836. from the bridge. Finishes the feature started in 0.2.0.10-alpha;
  837. closes bug 1138.
  838. - Fix a bug where bridge users who configure the non-canonical
  839. address of a bridge automatically switch to its canonical
  840. address. If a bridge listens at more than one address, it
  841. should be able to advertise those addresses independently and
  842. any non-blocked addresses should continue to work. Bugfix on Tor
  843. 0.2.0.3-alpha. Fixes bug 2510.
  844. - If you configure Tor to use bridge A, and then quit and
  845. configure Tor to use bridge B instead (or if you change Tor
  846. to use bridge B via the controller), it would happily continue
  847. to use bridge A if it's still reachable. While this behavior is
  848. a feature if your goal is connectivity, in some scenarios it's a
  849. dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
  850. - When the controller configures a new bridge, don't wait 10 to 60
  851. seconds before trying to fetch its descriptor. Bugfix on
  852. 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
  853. o Major bugfixes (directory authorities):
  854. - Many relays have been falling out of the consensus lately because
  855. not enough authorities know about their descriptor for them to get
  856. a majority of votes. When we deprecated the v2 directory protocol,
  857. we got rid of the only way that v3 authorities can hear from each
  858. other about other descriptors. Now authorities examine every v3
  859. vote for new descriptors, and fetch them from that authority. Bugfix
  860. on 0.2.1.23.
  861. - Authorities could be tricked into giving out the Exit flag to relays
  862. that didn't allow exiting to any ports. This bug could screw
  863. with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
  864. 1238. Bug discovered by Martin Kowalczyk.
  865. - If all authorities restart at once right before a consensus vote,
  866. nobody will vote about "Running", and clients will get a consensus
  867. with no usable relays. Instead, authorities refuse to build a
  868. consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
  869. o Major bugfixes (stream-level fairness):
  870. - When receiving a circuit-level SENDME for a blocked circuit, try
  871. to package cells fairly from all the streams that had previously
  872. been blocked on that circuit. Previously, we had started with the
  873. oldest stream, and allowed each stream to potentially exhaust
  874. the circuit's package window. This gave older streams on any
  875. given circuit priority over newer ones. Fixes bug 1937. Detected
  876. originally by Camilo Viecco. This bug was introduced before the
  877. first Tor release, in svn commit r152: it is the new winner of
  878. the longest-lived bug prize.
  879. - Fix a stream fairness bug that would cause newer streams on a given
  880. circuit to get preference when reading bytes from the origin or
  881. destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
  882. introduced before the first Tor release, in svn revision r152.
  883. - When the exit relay got a circuit-level sendme cell, it started
  884. reading on the exit streams, even if had 500 cells queued in the
  885. circuit queue already, so the circuit queue just grew and grew in
  886. some cases. We fix this by not re-enabling reading on receipt of a
  887. sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
  888. on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
  889. "yetonetime".
  890. - Newly created streams were allowed to read cells onto circuits,
  891. even if the circuit's cell queue was blocked and waiting to drain.
  892. This created potential unfairness, as older streams would be
  893. blocked, but newer streams would gladly fill the queue completely.
  894. We add code to detect this situation and prevent any stream from
  895. getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
  896. fixes bug 1298.
  897. o Major bugfixes (hidden services):
  898. - Apply circuit timeouts to opened hidden-service-related circuits
  899. based on the correct start time. Previously, we would apply the
  900. circuit build timeout based on time since the circuit's creation;
  901. it was supposed to be applied based on time since the circuit
  902. entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
  903. - Improve hidden service robustness: When we find that we have
  904. extended a hidden service's introduction circuit to a relay not
  905. listed as an introduction point in the HS descriptor we currently
  906. have, retry with an introduction point from the current
  907. descriptor. Previously we would just give up. Fixes bugs 1024 and
  908. 1930; bugfix on 0.2.0.10-alpha.
  909. - Directory authorities now use data collected from their own
  910. uptime observations when choosing whether to assign the HSDir flag
  911. to relays, instead of trusting the uptime value the relay reports in
  912. its descriptor. This change helps prevent an attack where a small
  913. set of nodes with frequently-changing identity keys can blackhole
  914. a hidden service. (Only authorities need upgrade; others will be
  915. fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
  916. - Stop assigning the HSDir flag to relays that disable their
  917. DirPort (and thus will refuse to answer directory requests). This
  918. fix should dramatically improve the reachability of hidden services:
  919. hidden services and hidden service clients pick six HSDir relays
  920. to store and retrieve the hidden service descriptor, and currently
  921. about half of the HSDir relays will refuse to work. Bugfix on
  922. 0.2.0.10-alpha; fixes part of bug 1693.
  923. o Major bugfixes (misc):
  924. - Clients now stop trying to use an exit node associated with a given
  925. destination by TrackHostExits if they fail to reach that exit node.
  926. Fixes bug 2999. Bugfix on 0.2.0.20-rc.
  927. - Fix a regression that caused Tor to rebind its ports if it receives
  928. SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
  929. - Remove an extra pair of quotation marks around the error
  930. message in control-port STATUS_GENERAL BUG events. Bugfix on
  931. 0.1.2.6-alpha; fixes bug 3732.
  932. o Minor features (relays):
  933. - Ensure that no empty [dirreq-](read|write)-history lines are added
  934. to an extrainfo document. Implements ticket 2497.
  935. - When bandwidth accounting is enabled, be more generous with how
  936. much bandwidth we'll use up before entering "soft hibernation".
  937. Previously, we'd refuse new connections and circuits once we'd
  938. used up 95% of our allotment. Now, we use up 95% of our allotment,
  939. AND make sure that we have no more than 500MB (or 3 hours of
  940. expected traffic, whichever is lower) remaining before we enter
  941. soft hibernation.
  942. - Relays now log the reason for publishing a new relay descriptor,
  943. so we have a better chance of hunting down instances of bug 1810.
  944. Resolves ticket 3252.
  945. - Log a little more clearly about the times at which we're no longer
  946. accepting new connections (e.g. due to hibernating). Resolves
  947. bug 2181.
  948. - When AllowSingleHopExits is set, print a warning to explain to the
  949. relay operator why most clients are avoiding her relay.
  950. - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
  951. Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
  952. clients are already deprecated because of security bugs.
  953. o Minor features (network statistics):
  954. - Directory mirrors that set "DirReqStatistics 1" write statistics
  955. about directory requests to disk every 24 hours. As compared to the
  956. "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
  957. improvements: 1) stats are written to disk exactly every 24 hours;
  958. 2) estimated shares of v2 and v3 requests are determined as mean
  959. values, not at the end of a measurement period; 3) unresolved
  960. requests are listed with country code '??'; 4) directories also
  961. measure download times.
  962. - Exit nodes that set "ExitPortStatistics 1" write statistics on the
  963. number of exit streams and transferred bytes per port to disk every
  964. 24 hours.
  965. - Relays that set "CellStatistics 1" write statistics on how long
  966. cells spend in their circuit queues to disk every 24 hours.
  967. - Entry nodes that set "EntryStatistics 1" write statistics on the
  968. rough number and origins of connecting clients to disk every 24
  969. hours.
  970. - Relays that write any of the above statistics to disk and set
  971. "ExtraInfoStatistics 1" include the past 24 hours of statistics in
  972. their extra-info documents. Implements proposal 166.
  973. o Minor features (GeoIP and statistics):
  974. - Provide a log message stating which geoip file we're parsing
  975. instead of just stating that we're parsing the geoip file.
  976. Implements ticket 2432.
  977. - Make sure every relay writes a state file at least every 12 hours.
  978. Previously, a relay could go for weeks without writing its state
  979. file, and on a crash could lose its bandwidth history, capacity
  980. estimates, client country statistics, and so on. Addresses bug 3012.
  981. - Relays report the number of bytes spent on answering directory
  982. requests in extra-info descriptors similar to {read,write}-history.
  983. Implements enhancement 1790.
  984. - Report only the top 10 ports in exit-port stats in order not to
  985. exceed the maximum extra-info descriptor length of 50 KB. Implements
  986. task 2196.
  987. - If writing the state file to disk fails, wait up to an hour before
  988. retrying again, rather than trying again each second. Fixes bug
  989. 2346; bugfix on Tor 0.1.1.3-alpha.
  990. - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
  991. when we switch from being a public relay to a bridge. Otherwise
  992. there will still be clients that see the relay in their consensus,
  993. and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
  994. bug 932.
  995. - Update to the August 2 2011 Maxmind GeoLite Country database.
  996. o Minor features (clients):
  997. - When expiring circuits, use microsecond timers rather than
  998. one-second timers. This can avoid an unpleasant situation where a
  999. circuit is launched near the end of one second and expired right
  1000. near the beginning of the next, and prevent fluctuations in circuit
  1001. timeout values.
  1002. - If we've configured EntryNodes and our network goes away and/or all
  1003. our entrynodes get marked down, optimistically retry them all when
  1004. a new socks application request appears. Fixes bug 1882.
  1005. - Always perform router selections using weighted relay bandwidth,
  1006. even if we don't need a high capacity circuit at the time. Non-fast
  1007. circuits now only differ from fast ones in that they can use relays
  1008. not marked with the Fast flag. This "feature" could turn out to
  1009. be a horrible bug; we should investigate more before it goes into
  1010. a stable release.
  1011. - When we run out of directory information such that we can't build
  1012. circuits, but then get enough that we can build circuits, log when
  1013. we actually construct a circuit, so the user has a better chance of
  1014. knowing what's going on. Fixes bug 1362.
  1015. - Log SSL state transitions at debug level during handshake, and
  1016. include SSL states in error messages. This may help debug future
  1017. SSL handshake issues.
  1018. o Minor features (directory authorities):
  1019. - When a router changes IP address or port, authorities now launch
  1020. a new reachability test for it. Implements ticket 1899.
  1021. - Directory authorities now reject relays running any versions of
  1022. Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
  1023. known bugs that keep RELAY_EARLY cells from working on rendezvous
  1024. circuits. Followup to fix for bug 2081.
  1025. - Directory authorities now reject relays running any version of Tor
  1026. older than 0.2.0.26-rc. That version is the earliest that fetches
  1027. current directory information correctly. Fixes bug 2156.
  1028. - Directory authorities now do an immediate reachability check as soon
  1029. as they hear about a new relay. This change should slightly reduce
  1030. the time between setting up a relay and getting listed as running
  1031. in the consensus. It should also improve the time between setting
  1032. up a bridge and seeing use by bridge users.
  1033. - Directory authorities no longer launch a TLS connection to every
  1034. relay as they startup. Now that we have 2k+ descriptors cached,
  1035. the resulting network hiccup is becoming a burden. Besides,
  1036. authorities already avoid voting about Running for the first half
  1037. hour of their uptime.
  1038. - Directory authorities now log the source of a rejected POSTed v3
  1039. networkstatus vote, so we can track failures better.
  1040. - Backport code from 0.2.3.x that allows directory authorities to
  1041. clean their microdescriptor caches. Needed to resolve bug 2230.
  1042. o Minor features (hidden services):
  1043. - Use computed circuit-build timeouts to decide when to launch
  1044. parallel introduction circuits for hidden services. (Previously,
  1045. we would retry after 15 seconds.)
  1046. - Don't allow v0 hidden service authorities to act as clients.
  1047. Required by fix for bug 3000.
  1048. - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
  1049. by fix for bug 3000.
  1050. - Make hidden services work better in private Tor networks by not
  1051. requiring any uptime to join the hidden service descriptor
  1052. DHT. Implements ticket 2088.
  1053. - Log (at info level) when purging pieces of hidden-service-client
  1054. state because of SIGNAL NEWNYM.
  1055. o Minor features (controller interface):
  1056. - New "GETINFO net/listeners/(type)" controller command to return
  1057. a list of addresses and ports that are bound for listeners for a
  1058. given connection type. This is useful when the user has configured
  1059. "SocksPort auto" and the controller needs to know which port got
  1060. chosen. Resolves another part of ticket 3076.
  1061. - Have the controller interface give a more useful message than
  1062. "Internal Error" in response to failed GETINFO requests.
  1063. - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
  1064. event, to give information on the current rate of circuit timeouts
  1065. over our stored history.
  1066. - The 'EXTENDCIRCUIT' control port command can now be used with
  1067. a circ id of 0 and no path. This feature will cause Tor to build
  1068. a new 'fast' general purpose circuit using its own path selection
  1069. algorithms.
  1070. - Added a BUILDTIMEOUT_SET controller event to describe changes
  1071. to the circuit build timeout.
  1072. - New controller command "getinfo config-text". It returns the
  1073. contents that Tor would write if you send it a SAVECONF command,
  1074. so the controller can write the file to disk itself.
  1075. o Minor features (controller protocol):
  1076. - Add a new ControlSocketsGroupWritable configuration option: when
  1077. it is turned on, ControlSockets are group-writeable by the default
  1078. group of the current user. Patch by Jérémy Bobbio; implements
  1079. ticket 2972.
  1080. - Tor now refuses to create a ControlSocket in a directory that is
  1081. world-readable (or group-readable if ControlSocketsGroupWritable
  1082. is 0). This is necessary because some operating systems do not
  1083. enforce permissions on an AF_UNIX sockets. Permissions on the
  1084. directory holding the socket, however, seems to work everywhere.
  1085. - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
  1086. not. This would lead to a cookie that is still not group readable.
  1087. Closes bug 1843. Suggested by katmagic.
  1088. - Future-proof the controller protocol a bit by ignoring keyword
  1089. arguments we do not recognize.
  1090. o Minor features (more useful logging):
  1091. - Revise most log messages that refer to nodes by nickname to
  1092. instead use the "$key=nickname at address" format. This should be
  1093. more useful, especially since nicknames are less and less likely
  1094. to be unique. Resolves ticket 3045.
  1095. - When an HTTPS proxy reports "403 Forbidden", we now explain
  1096. what it means rather than calling it an unexpected status code.
  1097. Closes bug 2503. Patch from Michael Yakubovich.
  1098. - Rate-limit a warning about failures to download v2 networkstatus
  1099. documents. Resolves part of bug 1352.
  1100. - Rate-limit the "your application is giving Tor only an IP address"
  1101. warning. Addresses bug 2000; bugfix on 0.0.8pre2.
  1102. - Rate-limit "Failed to hand off onionskin" warnings.
  1103. - When logging a rate-limited warning, we now mention how many messages
  1104. got suppressed since the last warning.
  1105. - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
  1106. 2 no signature, 4 required" messages about consensus signatures
  1107. easier to read, and make sure they get logged at the same severity
  1108. as the messages explaining which keys are which. Fixes bug 1290.
  1109. - Don't warn when we have a consensus that we can't verify because
  1110. of missing certificates, unless those certificates are ones
  1111. that we have been trying and failing to download. Fixes bug 1145.
  1112. o Minor features (log domains):
  1113. - Add documentation for configuring logging at different severities in
  1114. different log domains. We've had this feature since 0.2.1.1-alpha,
  1115. but for some reason it never made it into the manpage. Fixes
  1116. bug 2215.
  1117. - Make it simpler to specify "All log domains except for A and B".
  1118. Previously you needed to say "[*,~A,~B]". Now you can just say
  1119. "[~A,~B]".
  1120. - Add a "LogMessageDomains 1" option to include the domains of log
  1121. messages along with the messages. Without this, there's no way
  1122. to use log domains without reading the source or doing a lot
  1123. of guessing.
  1124. - Add a new "Handshake" log domain for activities that happen
  1125. during the TLS handshake.
  1126. o Minor features (build process):
  1127. - Make compilation with clang possible when using
  1128. "--enable-gcc-warnings" by removing two warning options that clang
  1129. hasn't implemented yet and by fixing a few warnings. Resolves
  1130. ticket 2696.
  1131. - Detect platforms that brokenly use a signed size_t, and refuse to
  1132. build there. Found and analyzed by doorss and rransom.
  1133. - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
  1134. Resolves bug 2314.
  1135. - Add support for statically linking zlib by specifying
  1136. "--enable-static-zlib", to go with our support for statically
  1137. linking openssl and libevent. Resolves bug 1358.
  1138. - Instead of adding the svn revision to the Tor version string, report
  1139. the git commit (when we're building from a git checkout).
  1140. - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
  1141. system headers.
  1142. - New --digests command-line switch to output the digests of the
  1143. source files Tor was built with.
  1144. - Generate our manpage and HTML documentation using Asciidoc. This
  1145. change should make it easier to maintain the documentation, and
  1146. produce nicer HTML. The build process fails if asciidoc cannot
  1147. be found and building with asciidoc isn't disabled (via the
  1148. "--disable-asciidoc" argument to ./configure. Skipping the manpage
  1149. speeds up the build considerably.
  1150. o Minor features (options / torrc):
  1151. - Warn when the same option is provided more than once in a torrc
  1152. file, on the command line, or in a single SETCONF statement, and
  1153. the option is one that only accepts a single line. Closes bug 1384.
  1154. - Warn when the user configures two HiddenServiceDir lines that point
  1155. to the same directory. Bugfix on 0.0.6 (the version introducing
  1156. HiddenServiceDir); fixes bug 3289.
  1157. - Add new "perconnbwrate" and "perconnbwburst" consensus params to
  1158. do individual connection-level rate limiting of clients. The torrc
  1159. config options with the same names trump the consensus params, if
  1160. both are present. Replaces the old "bwconnrate" and "bwconnburst"
  1161. consensus params which were broken from 0.2.2.7-alpha through
  1162. 0.2.2.14-alpha. Closes bug 1947.
  1163. - New config option "WarnUnsafeSocks 0" disables the warning that
  1164. occurs whenever Tor receives a socks handshake using a version of
  1165. the socks protocol that can only provide an IP address (rather
  1166. than a hostname). Setups that do DNS locally over Tor are fine,
  1167. and we shouldn't spam the logs in that case.
  1168. - New config option "CircuitStreamTimeout" to override our internal
  1169. timeout schedule for how many seconds until we detach a stream from
  1170. a circuit and try a new circuit. If your network is particularly
  1171. slow, you might want to set this to a number like 60.
  1172. - New options for SafeLogging to allow scrubbing only log messages
  1173. generated while acting as a relay. Specify "SafeLogging relay" if
  1174. you want to ensure that only messages known to originate from
  1175. client use of the Tor process will be logged unsafely.
  1176. - Time and memory units in the configuration file can now be set to
  1177. fractional units. For example, "2.5 GB" is now a valid value for
  1178. AccountingMax.
  1179. - Support line continuations in the torrc config file. If a line
  1180. ends with a single backslash character, the newline is ignored, and
  1181. the configuration value is treated as continuing on the next line.
  1182. Resolves bug 1929.
  1183. o Minor features (unit tests):
  1184. - Revise our unit tests to use the "tinytest" framework, so we
  1185. can run tests in their own processes, have smarter setup/teardown
  1186. code, and so on. The unit test code has moved to its own
  1187. subdirectory, and has been split into multiple modules.
  1188. - Add a unit test for cross-platform directory-listing code.
  1189. - Add some forgotten return value checks during unit tests. Found
  1190. by coverity.
  1191. - Use GetTempDir to find the proper temporary directory location on
  1192. Windows when generating temporary files for the unit tests. Patch
  1193. by Gisle Vanem.
  1194. o Minor features (misc):
  1195. - The "torify" script now uses torsocks where available.
  1196. - Make Libevent log messages get delivered to controllers later,
  1197. and not from inside the Libevent log handler. This prevents unsafe
  1198. reentrant Libevent calls while still letting the log messages
  1199. get through.
  1200. - Certain Tor clients (such as those behind check.torproject.org) may
  1201. want to fetch the consensus in an extra early manner. To enable this
  1202. a user may now set FetchDirInfoExtraEarly to 1. This also depends on
  1203. setting FetchDirInfoEarly to 1. Previous behavior will stay the same
  1204. as only certain clients who must have this information sooner should
  1205. set this option.
  1206. - Expand homedirs passed to tor-checkkey. This should silence a
  1207. coverity complaint about passing a user-supplied string into
  1208. open() without checking it.
  1209. - Make sure to disable DirPort if running as a bridge. DirPorts aren't
  1210. used on bridges, and it makes bridge scanning somewhat easier.
  1211. - Create the /var/run/tor directory on startup on OpenSUSE if it is
  1212. not already created. Patch from Andreas Stieger. Fixes bug 2573.
  1213. o Minor bugfixes (relays):
  1214. - When a relay decides that its DNS is too broken for it to serve
  1215. as an exit server, it advertised itself as a non-exit, but
  1216. continued to act as an exit. This could create accidental
  1217. partitioning opportunities for users. Instead, if a relay is
  1218. going to advertise reject *:* as its exit policy, it should
  1219. really act with exit policy "reject *:*". Fixes bug 2366.
  1220. Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
  1221. - Publish a router descriptor even if generating an extra-info
  1222. descriptor fails. Previously we would not publish a router
  1223. descriptor without an extra-info descriptor; this can cause fast
  1224. exit relays collecting exit-port statistics to drop from the
  1225. consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
  1226. - When we're trying to guess whether we know our IP address as
  1227. a relay, we would log various ways that we failed to guess
  1228. our address, but never log that we ended up guessing it
  1229. successfully. Now add a log line to help confused and anxious
  1230. relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
  1231. - For bandwidth accounting, calculate our expected bandwidth rate
  1232. based on the time during which we were active and not in
  1233. soft-hibernation during the last interval. Previously, we were
  1234. also considering the time spent in soft-hibernation. If this
  1235. was a long time, we would wind up underestimating our bandwidth
  1236. by a lot, and skewing our wakeup time towards the start of the
  1237. accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
  1238. - Demote a confusing TLS warning that relay operators might get when
  1239. someone tries to talk to their ORPort. It is not the operator's
  1240. fault, nor can they do anything about it. Fixes bug 1364; bugfix
  1241. on 0.2.0.14-alpha.
  1242. - Change "Application request when we're believed to be offline."
  1243. notice to "Application request when we haven't used client
  1244. functionality lately.", to clarify that it's not an error. Bugfix
  1245. on 0.0.9.3; fixes bug 1222.
  1246. o Minor bugfixes (bridges):
  1247. - When a client starts or stops using bridges, never use a circuit
  1248. that was built before the configuration change. This behavior could
  1249. put at risk a user who uses bridges to ensure that her traffic
  1250. only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
  1251. bug 3200.
  1252. - Do not reset the bridge descriptor download status every time we
  1253. re-parse our configuration or get a configuration change. Fixes
  1254. bug 3019; bugfix on 0.2.0.3-alpha.
  1255. - Users couldn't configure a regular relay to be their bridge. It
  1256. didn't work because when Tor fetched the bridge descriptor, it found
  1257. that it already had it, and didn't realize that the purpose of the
  1258. descriptor had changed. Now we replace routers with a purpose other
  1259. than bridge with bridge descriptors when fetching them. Bugfix on
  1260. 0.1.1.9-alpha. Fixes bug 1776.
  1261. - In the special case where you configure a public exit relay as your
  1262. bridge, Tor would be willing to use that exit relay as the last
  1263. hop in your circuit as well. Now we fail that circuit instead.
  1264. Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
  1265. o Minor bugfixes (clients):
  1266. - We now ask the other side of a stream (the client or the exit)
  1267. for more data on that stream when the amount of queued data on
  1268. that stream dips low enough. Previously, we wouldn't ask the
  1269. other side for more data until either it sent us more data (which
  1270. it wasn't supposed to do if it had exhausted its window!) or we
  1271. had completely flushed all our queued data. This flow control fix
  1272. should improve throughput. Fixes bug 2756; bugfix on the earliest
  1273. released versions of Tor (svn commit r152).
  1274. - When a client finds that an origin circuit has run out of 16-bit
  1275. stream IDs, we now mark it as unusable for new streams. Previously,
  1276. we would try to close the entire circuit. Bugfix on 0.0.6.
  1277. - Make it explicit that we don't cannibalize one-hop circuits. This
  1278. happens in the wild, but doesn't turn out to be a problem because
  1279. we fortunately don't use those circuits. Many thanks to outofwords
  1280. for the initial analysis and to swissknife who confirmed that
  1281. two-hop circuits are actually created.
  1282. - Resolve an edge case in path weighting that could make us misweight
  1283. our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
  1284. - Make the DNSPort option work with libevent 2.x. Don't alter the
  1285. behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
  1286. o Minor bugfixes (directory authorities):
  1287. - Make directory authorities more accurate at recording when
  1288. relays that have failed several reachability tests became
  1289. unreachable, so we can provide more accuracy at assigning Stable,
  1290. Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
  1291. - Directory authorities are now more robust to hops back in time
  1292. when calculating router stability. Previously, if a run of uptime
  1293. or downtime appeared to be negative, the calculation could give
  1294. incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
  1295. bug 1035.
  1296. - Directory authorities will now attempt to download consensuses
  1297. if their own efforts to make a live consensus have failed. This
  1298. change means authorities that restart will fetch a valid
  1299. consensus, and it means authorities that didn't agree with the
  1300. current consensus will still fetch and serve it if it has enough
  1301. signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
  1302. - Never vote for a server as "Running" if we have a descriptor for
  1303. it claiming to be hibernating, and that descriptor was published
  1304. more recently than our last contact with the server. Bugfix on
  1305. 0.2.0.3-alpha; fixes bug 911.
  1306. - Directory authorities no longer change their opinion of, or vote on,
  1307. whether a router is Running, unless they have themselves been
  1308. online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
  1309. Fixes bug 1023.
  1310. o Minor bugfixes (hidden services):
  1311. - Log malformed requests for rendezvous descriptors as protocol
  1312. warnings, not warnings. Also, use a more informative log message
  1313. in case someone sees it at log level warning without prior
  1314. info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
  1315. - Accept hidden service descriptors if we think we might be a hidden
  1316. service directory, regardless of what our consensus says. This
  1317. helps robustness, since clients and hidden services can sometimes
  1318. have a more up-to-date view of the network consensus than we do,
  1319. and if they think that the directory authorities list us a HSDir,
  1320. we might actually be one. Related to bug 2732; bugfix on
  1321. 0.2.0.10-alpha.
  1322. - Correct the warning displayed when a rendezvous descriptor exceeds
  1323. the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
  1324. John Brooks.
  1325. - Clients and hidden services now use HSDir-flagged relays for hidden
  1326. service descriptor downloads and uploads even if the relays have no
  1327. DirPort set and the client has disabled TunnelDirConns. This will
  1328. eventually allow us to give the HSDir flag to relays with no
  1329. DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
  1330. - Only limit the lengths of single HS descriptors, even when multiple
  1331. HS descriptors are published to an HSDir relay in a single POST
  1332. operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
  1333. o Minor bugfixes (controllers):
  1334. - Allow GETINFO fingerprint to return a fingerprint even when
  1335. we have not yet built a router descriptor. Fixes bug 3577;
  1336. bugfix on 0.2.0.1-alpha.
  1337. - Send a SUCCEEDED stream event to the controller when a reverse
  1338. resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
  1339. discovered by katmagic.
  1340. - Remove a trailing asterisk from "exit-policy/default" in the
  1341. output of the control port command "GETINFO info/names". Bugfix
  1342. on 0.1.2.5-alpha.
  1343. - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
  1344. 2917. Bugfix on 0.1.1.1-alpha.
  1345. - When we restart our relay, we might get a successful connection
  1346. from the outside before we've started our reachability tests,
  1347. triggering a warning: "ORPort found reachable, but I have no
  1348. routerinfo yet. Failing to inform controller of success." This
  1349. bug was harmless unless Tor is running under a controller
  1350. like Vidalia, in which case the controller would never get a
  1351. REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
  1352. fixes bug 1172.
  1353. - When a controller changes TrackHostExits, remove mappings for
  1354. hosts that should no longer have their exits tracked. Bugfix on
  1355. 0.1.0.1-rc.
  1356. - When a controller changes VirtualAddrNetwork, remove any mappings
  1357. for hosts that were automapped to the old network. Bugfix on
  1358. 0.1.1.19-rc.
  1359. - When a controller changes one of the AutomapHosts* options, remove
  1360. any mappings for hosts that should no longer be automapped. Bugfix
  1361. on 0.2.0.1-alpha.
  1362. - Fix an off-by-one error in calculating some controller command
  1363. argument lengths. Fortunately, this mistake is harmless since
  1364. the controller code does redundant NUL termination too. Found by
  1365. boboper. Bugfix on 0.1.1.1-alpha.
  1366. - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
  1367. would return "551 Internal error" rather than "552 Unrecognized key
  1368. ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
  1369. - Don't spam the controller with events when we have no file
  1370. descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
  1371. for log messages was already solved from bug 748.)
  1372. - Emit a GUARD DROPPED controller event for a case we missed.
  1373. - Ensure DNS requests launched by "RESOLVE" commands from the
  1374. controller respect the __LeaveStreamsUnattached setconf options. The
  1375. same goes for requests launched via DNSPort or transparent
  1376. proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
  1377. o Minor bugfixes (config options):
  1378. - Tor used to limit HttpProxyAuthenticator values to 48 characters.
  1379. Change the limit to 512 characters by removing base64 newlines.
  1380. Fixes bug 2752. Fix by Michael Yakubovich.
  1381. - Complain if PublishServerDescriptor is given multiple arguments that
  1382. include 0 or 1. This configuration will be rejected in the future.
  1383. Bugfix on 0.2.0.1-alpha; closes bug 1107.
  1384. - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
  1385. Bugfix on 0.2.0.13-alpha; closes bug 928.
  1386. o Minor bugfixes (log subsystem fixes):
  1387. - When unable to format an address as a string, report its value
  1388. as "???" rather than reusing the last formatted address. Bugfix
  1389. on 0.2.1.5-alpha.
  1390. - Be more consistent in our treatment of file system paths. "~" should
  1391. get expanded to the user's home directory in the Log config option.
  1392. Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
  1393. feature for the -f and --DataDirectory options.
  1394. o Minor bugfixes (memory management):
  1395. - Don't stack-allocate the list of supplementary GIDs when we're
  1396. about to log them. Stack-allocating NGROUPS_MAX gid_t elements
  1397. could take up to 256K, which is way too much stack. Found by
  1398. Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
  1399. - Save a couple bytes in memory allocation every time we escape
  1400. certain characters in a string. Patch from Florian Zumbiehl.
  1401. o Minor bugfixes (protocol correctness):
  1402. - When checking for 1024-bit keys, check for 1024 bits, not 128
  1403. bytes. This allows Tor to correctly discard keys of length 1017
  1404. through 1023. Bugfix on 0.0.9pre5.
  1405. - Require that introduction point keys and onion handshake keys
  1406. have a public exponent of 65537. Starts to fix bug 3207; bugfix
  1407. on 0.2.0.10-alpha.
  1408. - Handle SOCKS messages longer than 128 bytes long correctly, rather
  1409. than waiting forever for them to finish. Fixes bug 2330; bugfix
  1410. on 0.2.0.16-alpha. Found by doorss.
  1411. - Never relay a cell for a circuit we have already destroyed.
  1412. Between marking a circuit as closeable and finally closing it,
  1413. it may have been possible for a few queued cells to get relayed,
  1414. even though they would have been immediately dropped by the next
  1415. OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
  1416. - Never queue a cell for a circuit that's already been marked
  1417. for close.
  1418. - Fix a spec conformance issue: the network-status-version token
  1419. must be the first token in a v3 consensus or vote. Discovered by
  1420. "parakeep". Bugfix on 0.2.0.3-alpha.
  1421. - A networkstatus vote must contain exactly one signature. Spec
  1422. conformance issue. Bugfix on 0.2.0.3-alpha.
  1423. - When asked about a DNS record type we don't support via a
  1424. client DNSPort, reply with NOTIMPL rather than an empty
  1425. reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
  1426. - Make more fields in the controller protocol case-insensitive, since
  1427. control-spec.txt said they were.
  1428. o Minor bugfixes (log messages):
  1429. - Fix a log message that said "bits" while displaying a value in
  1430. bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
  1431. 0.2.0.1-alpha.
  1432. - Downgrade "no current certificates known for authority" message from
  1433. Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
  1434. - Correctly describe errors that occur when generating a TLS object.
  1435. Previously we would attribute them to a failure while generating a
  1436. TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
  1437. bug 1994.
  1438. - Fix an instance where a Tor directory mirror might accidentally
  1439. log the IP address of a misbehaving Tor client. Bugfix on
  1440. 0.1.0.1-rc.
  1441. - Stop logging at severity 'warn' when some other Tor client tries
  1442. to establish a circuit with us using weak DH keys. It's a protocol
  1443. violation, but that doesn't mean ordinary users need to hear about
  1444. it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
  1445. - If your relay can't keep up with the number of incoming create
  1446. cells, it would log one warning per failure into your logs. Limit
  1447. warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
  1448. o Minor bugfixes (build fixes):
  1449. - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
  1450. - When warning about missing zlib development packages during compile,
  1451. give the correct package names. Bugfix on 0.2.0.1-alpha.
  1452. - Fix warnings that newer versions of autoconf produce during
  1453. ./autogen.sh. These warnings appear to be harmless in our case,
  1454. but they were extremely verbose. Fixes bug 2020.
  1455. - Squash a compile warning on OpenBSD. Reported by Tas; fixes
  1456. bug 1848.
  1457. o Minor bugfixes (portability):
  1458. - Write several files in text mode, on OSes that distinguish text
  1459. mode from binary mode (namely, Windows). These files are:
  1460. 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
  1461. that collect those statistics; 'client_keys' and 'hostname' for
  1462. hidden services that use authentication; and (in the tor-gencert
  1463. utility) newly generated identity and signing keys. Previously,
  1464. we wouldn't specify text mode or binary mode, leading to an
  1465. assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
  1466. the DirRecordUsageByCountry option which would have triggered
  1467. the assertion failure was added), although this assertion failure
  1468. would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
  1469. - Selectively disable deprecation warnings on OS X because Lion
  1470. started deprecating the shipped copy of openssl. Fixes bug 3643.
  1471. - Use a wide type to hold sockets when built for 64-bit Windows.
  1472. Fixes bug 3270.
  1473. - Fix an issue that prevented static linking of libevent on
  1474. some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
  1475. where we introduced the "--with-static-libevent" configure option.
  1476. - Fix a bug with our locking implementation on Windows that couldn't
  1477. correctly detect when a file was already locked. Fixes bug 2504,
  1478. bugfix on 0.2.1.6-alpha.
  1479. - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
  1480. enabled.
  1481. - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
  1482. Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
  1483. "piebeer".
  1484. o Minor bugfixes (code correctness):
  1485. - Always NUL-terminate the sun_path field of a sockaddr_un before
  1486. passing it to the kernel. (Not a security issue: kernels are
  1487. smart enough to reject bad sockaddr_uns.) Found by Coverity;
  1488. CID #428. Bugfix on Tor 0.2.0.3-alpha.
  1489. - Make connection_printf_to_buf()'s behaviour sane. Its callers
  1490. expect it to emit a CRLF iff the format string ends with CRLF;
  1491. it actually emitted a CRLF iff (a) the format string ended with
  1492. CRLF or (b) the resulting string was over 1023 characters long or
  1493. (c) the format string did not end with CRLF *and* the resulting
  1494. string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
  1495. fixes part of bug 3407.
  1496. - Make send_control_event_impl()'s behaviour sane. Its callers
  1497. expect it to always emit a CRLF at the end of the string; it
  1498. might have emitted extra control characters as well. Bugfix on
  1499. 0.1.1.9-alpha; fixes another part of bug 3407.
  1500. - Make crypto_rand_int() check the value of its input correctly.
  1501. Previously, it accepted values up to UINT_MAX, but could return a
  1502. negative number if given a value above INT_MAX+1. Found by George
  1503. Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
  1504. - Fix a potential null-pointer dereference while computing a
  1505. consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
  1506. clang's analyzer.
  1507. - If we fail to compute the identity digest of a v3 legacy keypair,
  1508. warn, and don't use a buffer-full of junk instead. Bugfix on
  1509. 0.2.1.1-alpha; fixes bug 3106.
  1510. - Resolve an untriggerable issue in smartlist_string_num_isin(),
  1511. where if the function had ever in the future been used to check
  1512. for the presence of a too-large number, it would have given an
  1513. incorrect result. (Fortunately, we only used it for 16-bit
  1514. values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
  1515. - Be more careful about reporting the correct error from a failed
  1516. connect() system call. Under some circumstances, it was possible to
  1517. look at an incorrect value for errno when sending the end reason.
  1518. Bugfix on 0.1.0.1-rc.
  1519. - Correctly handle an "impossible" overflow cases in connection byte
  1520. counting, where we write or read more than 4GB on an edge connection
  1521. in a single second. Bugfix on 0.1.2.8-beta.
  1522. - Avoid a double mark-for-free warning when failing to attach a
  1523. transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
  1524. bug 2279.
  1525. - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
  1526. found by "cypherpunks". This bug was introduced before the first
  1527. Tor release, in svn commit r110.
  1528. - Fix a bug in bandwidth history state parsing that could have been
  1529. triggered if a future version of Tor ever changed the timing
  1530. granularity at which bandwidth history is measured. Bugfix on
  1531. Tor 0.1.1.11-alpha.
  1532. - Add assertions to check for overflow in arguments to
  1533. base32_encode() and base32_decode(); fix a signed-unsigned
  1534. comparison there too. These bugs are not actually reachable in Tor,
  1535. but it's good to prevent future errors too. Found by doorss.
  1536. - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
  1537. "memcpyfail".
  1538. - Set target port in get_interface_address6() correctly. Bugfix
  1539. on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
  1540. - Fix an impossible-to-actually-trigger buffer overflow in relay
  1541. descriptor generation. Bugfix on 0.1.0.15.
  1542. - Fix numerous small code-flaws found by Coverity Scan Rung 3.
  1543. o Minor bugfixes (code improvements):
  1544. - After we free an internal connection structure, overwrite it
  1545. with a different memory value than we use for overwriting a freed
  1546. internal circuit structure. Should help with debugging. Suggested
  1547. by bug 1055.
  1548. - If OpenSSL fails to make a duplicate of a private or public key, log
  1549. an error message and try to exit cleanly. May help with debugging
  1550. if bug 1209 ever remanifests.
  1551. - Some options used different conventions for uppercasing of acronyms
  1552. when comparing manpage and source. Fix those in favor of the
  1553. manpage, as it makes sense to capitalize acronyms.
  1554. - Take a first step towards making or.h smaller by splitting out
  1555. function definitions for all source files in src/or/. Leave
  1556. structures and defines in or.h for now.
  1557. - Remove a few dead assignments during router parsing. Found by
  1558. coverity.
  1559. - Don't use 1-bit wide signed bit fields. Found by coverity.
  1560. - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
  1561. None of the cases where we did this before were wrong, but by making
  1562. this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
  1563. - The memarea code now uses a sentinel value at the end of each area
  1564. to make sure nothing writes beyond the end of an area. This might
  1565. help debug some conceivable causes of bug 930.
  1566. - Always treat failure to allocate an RSA key as an unrecoverable
  1567. allocation error.
  1568. - Add some more defensive programming for architectures that can't
  1569. handle unaligned integer accesses. We don't know of any actual bugs
  1570. right now, but that's the best time to fix them. Fixes bug 1943.
  1571. o Minor bugfixes (misc):
  1572. - Fix a rare bug in rend_fn unit tests: we would fail a test when
  1573. a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
  1574. on 0.2.0.10-alpha; fixes bug 1808.
  1575. - Where available, use Libevent 2.0's periodic timers so that our
  1576. once-per-second cleanup code gets called even more closely to
  1577. once per second than it would otherwise. Fixes bug 943.
  1578. - Ignore OutboundBindAddress when connecting to localhost.
  1579. Connections to localhost need to come _from_ localhost, or else
  1580. local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
  1581. refuse to listen.
  1582. - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
  1583. too.
  1584. - If any of the v3 certs we download are unparseable, we should
  1585. actually notice the failure so we don't retry indefinitely. Bugfix
  1586. on 0.2.0.x; reported by "rotator".
  1587. - When Tor fails to parse a descriptor of any kind, dump it to disk.
  1588. Might help diagnosing bug 1051.
  1589. - Make our 'torify' script more portable; if we have only one of
  1590. 'torsocks' or 'tsocks' installed, don't complain to the user;
  1591. and explain our warning about tsocks better.
  1592. - Fix some urls in the exit notice file and make it XHTML1.1 strict
  1593. compliant. Based on a patch from Christian Kujau.
  1594. o Documentation changes:
  1595. - Modernize the doxygen configuration file slightly. Fixes bug 2707.
  1596. - Resolve all doxygen warnings except those for missing documentation.
  1597. Fixes bug 2705.
  1598. - Add doxygen documentation for more functions, fields, and types.
  1599. - Convert the HACKING file to asciidoc, and add a few new sections
  1600. to it, explaining how we use Git, how we make changelogs, and
  1601. what should go in a patch.
  1602. - Document the default socks host and port (127.0.0.1:9050) for
  1603. tor-resolve.
  1604. - Removed some unnecessary files from the source distribution. The
  1605. AUTHORS file has now been merged into the people page on the
  1606. website. The roadmaps and design doc can now be found in the
  1607. projects directory in svn.
  1608. o Deprecated and removed features (config):
  1609. - Remove the torrc.complete file. It hasn't been kept up to date
  1610. and users will have better luck checking out the manpage.
  1611. - Remove the HSAuthorityRecordStats option that version 0 hidden
  1612. service authorities could use to track statistics of overall v0
  1613. hidden service usage.
  1614. - Remove the obsolete "NoPublish" option; it has been flagged
  1615. as obsolete and has produced a warning since 0.1.1.18-rc.
  1616. - Caches no longer download and serve v2 networkstatus documents
  1617. unless FetchV2Networkstatus flag is set: these documents haven't
  1618. haven't been used by clients or relays since 0.2.0.x. Resolves
  1619. bug 3022.
  1620. o Deprecated and removed features (controller):
  1621. - The controller no longer accepts the old obsolete "addr-mappings/"
  1622. or "unregistered-servers-" GETINFO values.
  1623. - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
  1624. always on; using them is necessary for correct forward-compatible
  1625. controllers.
  1626. o Deprecated and removed features (misc):
  1627. - Hidden services no longer publish version 0 descriptors, and clients
  1628. do not request or use version 0 descriptors. However, the old hidden
  1629. service authorities still accept and serve version 0 descriptors
  1630. when contacted by older hidden services/clients.
  1631. - Remove undocumented option "-F" from tor-resolve: it hasn't done
  1632. anything since 0.2.1.16-rc.
  1633. - Remove everything related to building the expert bundle for OS X.
  1634. It has confused many users, doesn't work right on OS X 10.6,
  1635. and is hard to get rid of once installed. Resolves bug 1274.
  1636. - Remove support for .noconnect style addresses. Nobody was using
  1637. them, and they provided another avenue for detecting Tor users
  1638. via application-level web tricks.
  1639. - When we fixed bug 1038 we had to put in a restriction not to send
  1640. RELAY_EARLY cells on rend circuits. This was necessary as long
  1641. as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
  1642. active. Now remove this obsolete check. Resolves bug 2081.
  1643. - Remove workaround code to handle directory responses from servers
  1644. that had bug 539 (they would send HTTP status 503 responses _and_
  1645. send a body too). Since only server versions before
  1646. 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
  1647. keep the workaround in place.
  1648. - Remove the old 'fuzzy time' logic. It was supposed to be used for
  1649. handling calculations where we have a known amount of clock skew and
  1650. an allowed amount of unknown skew. But we only used it in three
  1651. places, and we never adjusted the known/unknown skew values. This is
  1652. still something we might want to do someday, but if we do, we'll
  1653. want to do it differently.
  1654. - Remove the "--enable-iphone" option to ./configure. According to
  1655. reports from Marco Bonetti, Tor builds fine without any special
  1656. tweaking on recent iPhone SDK versions.
  1657. Changes in version 0.2.1.30 - 2011-02-23
  1658. Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
  1659. change is a slight tweak to Tor's TLS handshake that makes relays
  1660. and bridges that run this new version reachable from Iran again.
  1661. We don't expect this tweak will win the arms race long-term, but it
  1662. buys us time until we roll out a better solution.
  1663. o Major bugfixes:
  1664. - Stop sending a CLOCK_SKEW controller status event whenever
  1665. we fetch directory information from a relay that has a wrong clock.
  1666. Instead, only inform the controller when it's a trusted authority
  1667. that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
  1668. the rest of bug 1074.
  1669. - Fix a bounds-checking error that could allow an attacker to
  1670. remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
  1671. Found by "piebeer".
  1672. - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
  1673. Tor would ignore their RelayBandwidthBurst setting,
  1674. potentially using more bandwidth than expected. Bugfix on
  1675. 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
  1676. - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
  1677. hidserv" in her torrc. The 'hidserv' argument never controlled
  1678. publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
  1679. o Minor features:
  1680. - Adjust our TLS Diffie-Hellman parameters to match those used by
  1681. Apache's mod_ssl.
  1682. - Update to the February 1 2011 Maxmind GeoLite Country database.
  1683. o Minor bugfixes:
  1684. - Check for and reject overly long directory certificates and
  1685. directory tokens before they have a chance to hit any assertions.
  1686. Bugfix on 0.2.1.28. Found by "doorss".
  1687. - Bring the logic that gathers routerinfos and assesses the
  1688. acceptability of circuits into line. This prevents a Tor OP from
  1689. getting locked in a cycle of choosing its local OR as an exit for a
  1690. path (due to a .exit request) and then rejecting the circuit because
  1691. its OR is not listed yet. It also prevents Tor clients from using an
  1692. OR running in the same instance as an exit (due to a .exit request)
  1693. if the OR does not meet the same requirements expected of an OR
  1694. running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
  1695. o Packaging changes:
  1696. - Stop shipping the Tor specs files and development proposal documents
  1697. in the tarball. They are now in a separate git repository at
  1698. git://git.torproject.org/torspec.git
  1699. - Do not include Git version tags as though they are SVN tags when
  1700. generating a tarball from inside a repository that has switched
  1701. between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
  1702. Changes in version 0.2.1.29 - 2011-01-15
  1703. Tor 0.2.1.29 continues our recent code security audit work. The main
  1704. fix resolves a remote heap overflow vulnerability that can allow remote
  1705. code execution. Other fixes address a variety of assert and crash bugs,
  1706. most of which we think are hard to exploit remotely.
  1707. o Major bugfixes (security):
  1708. - Fix a heap overflow bug where an adversary could cause heap
  1709. corruption. This bug probably allows remote code execution
  1710. attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
  1711. 0.1.2.10-rc.
  1712. - Prevent a denial-of-service attack by disallowing any
  1713. zlib-compressed data whose compression factor is implausibly
  1714. high. Fixes part of bug 2324; reported by "doorss".
  1715. - Zero out a few more keys in memory before freeing them. Fixes
  1716. bug 2384 and part of bug 2385. These key instances found by
  1717. "cypherpunks", based on Andrew Case's report about being able
  1718. to find sensitive data in Tor's memory space if you have enough
  1719. permissions. Bugfix on 0.0.2pre9.
  1720. o Major bugfixes (crashes):
  1721. - Prevent calls to Libevent from inside Libevent log handlers.
  1722. This had potential to cause a nasty set of crashes, especially
  1723. if running Libevent with debug logging enabled, and running
  1724. Tor with a controller watching for low-severity log messages.
  1725. Bugfix on 0.1.0.2-rc. Fixes bug 2190.
  1726. - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
  1727. underflow errors there too. Fixes the other part of bug 2324.
  1728. - Fix a bug where we would assert if we ever had a
  1729. cached-descriptors.new file (or another file read directly into
  1730. memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
  1731. on 0.2.1.25. Found by doorss.
  1732. - Fix some potential asserts and parsing issues with grossly
  1733. malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
  1734. Found by doorss.
  1735. o Minor bugfixes (other):
  1736. - Fix a bug with handling misformed replies to reverse DNS lookup
  1737. requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
  1738. bug reported by doorss.
  1739. - Fix compilation on mingw when a pthreads compatibility library
  1740. has been installed. (We don't want to use it, so we shouldn't
  1741. be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
  1742. - Fix a bug where we would declare that we had run out of virtual
  1743. addresses when the address space was only half-exhausted. Bugfix
  1744. on 0.1.2.1-alpha.
  1745. - Correctly handle the case where AutomapHostsOnResolve is set but
  1746. no virtual addresses are available. Fixes bug 2328; bugfix on
  1747. 0.1.2.1-alpha. Bug found by doorss.
  1748. - Correctly handle wrapping around when we run out of virtual
  1749. address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
  1750. o Minor features:
  1751. - Update to the January 1 2011 Maxmind GeoLite Country database.
  1752. - Introduce output size checks on all of our decryption functions.
  1753. o Build changes:
  1754. - Tor does not build packages correctly with Automake 1.6 and earlier;
  1755. added a check to Makefile.am to make sure that we're building with
  1756. Automake 1.7 or later.
  1757. - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
  1758. because we built it with a too-old version of automake. Thus that
  1759. release broke ./configure --enable-openbsd-malloc, which is popular
  1760. among really fast exit relays on Linux.
  1761. Changes in version 0.2.1.28 - 2010-12-17
  1762. Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
  1763. exploitable bugs. We also took this opportunity to change the IP address
  1764. for one of our directory authorities, and to update the geoip database
  1765. we ship.
  1766. o Major bugfixes:
  1767. - Fix a remotely exploitable bug that could be used to crash instances
  1768. of Tor remotely by overflowing on the heap. Remote-code execution
  1769. hasn't been confirmed, but can't be ruled out. Everyone should
  1770. upgrade. Bugfix on the 0.1.1 series and later.
  1771. o Directory authority changes:
  1772. - Change IP address and ports for gabelmoo (v3 directory authority).
  1773. o Minor features:
  1774. - Update to the December 1 2010 Maxmind GeoLite Country database.
  1775. Changes in version 0.2.1.27 - 2010-11-23
  1776. Yet another OpenSSL security patch broke its compatibility with Tor:
  1777. Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
  1778. also took this opportunity to fix several crash bugs, integrate a new
  1779. directory authority, and update the bundled GeoIP database.
  1780. o Major bugfixes:
  1781. - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
  1782. No longer set the tlsext_host_name extension on server SSL objects;
  1783. but continue to set it on client SSL objects. Our goal in setting
  1784. it was to imitate a browser, not a vhosting server. Fixes bug 2204;
  1785. bugfix on 0.2.1.1-alpha.
  1786. - Do not log messages to the controller while shrinking buffer
  1787. freelists. Doing so would sometimes make the controller connection
  1788. try to allocate a buffer chunk, which would mess up the internals
  1789. of the freelist and cause an assertion failure. Fixes bug 1125;
  1790. fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
  1791. - Learn our external IP address when we're a relay or bridge, even if
  1792. we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
  1793. where we introduced bridge relays that don't need to publish to
  1794. be useful. Fixes bug 2050.
  1795. - Do even more to reject (and not just ignore) annotations on
  1796. router descriptors received anywhere but from the cache. Previously
  1797. we would ignore such annotations at first, but cache them to disk
  1798. anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
  1799. - When you're using bridges and your network goes away and your
  1800. bridges get marked as down, recover when you attempt a new socks
  1801. connection (if the network is back), rather than waiting up to an
  1802. hour to try fetching new descriptors for your bridges. Bugfix on
  1803. 0.2.0.3-alpha; fixes bug 1981.
  1804. o Major features:
  1805. - Move to the November 2010 Maxmind GeoLite country db (rather
  1806. than the June 2009 ip-to-country GeoIP db) for our statistics that
  1807. count how many users relays are seeing from each country. Now we'll
  1808. have more accurate data, especially for many African countries.
  1809. o New directory authorities:
  1810. - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
  1811. authority.
  1812. o Minor bugfixes:
  1813. - Fix an assertion failure that could occur in directory caches or
  1814. bridge users when using a very short voting interval on a testing
  1815. network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
  1816. 0.2.0.8-alpha.
  1817. - Enforce multiplicity rules when parsing annotations. Bugfix on
  1818. 0.2.0.8-alpha. Found by piebeer.
  1819. - Allow handshaking OR connections to take a full KeepalivePeriod
  1820. seconds to handshake. Previously, we would close them after
  1821. IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
  1822. were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
  1823. for analysis help.
  1824. - When building with --enable-gcc-warnings on OpenBSD, disable
  1825. warnings in system headers. This makes --enable-gcc-warnings
  1826. pass on OpenBSD 4.8.
  1827. o Minor features:
  1828. - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
  1829. and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
  1830. stream ending reason for this case: END_STREAM_REASON_NOROUTE.
  1831. Servers can start sending this code when enough clients recognize
  1832. it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
  1833. - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
  1834. Patch from mingw-san.
  1835. o Removed files:
  1836. - Remove the old debian/ directory from the main Tor distribution.
  1837. The official Tor-for-debian git repository lives at the URL
  1838. https://git.torproject.org/debian/tor.git
  1839. - Stop shipping the old doc/website/ directory in the tarball. We
  1840. changed the website format in late 2010, and what we shipped in
  1841. 0.2.1.26 really wasn't that useful anyway.
  1842. Changes in version 0.2.1.26 - 2010-05-02
  1843. Tor 0.2.1.26 addresses the recent connection and memory overload
  1844. problems we've been seeing on relays, especially relays with their
  1845. DirPort open. If your relay has been crashing, or you turned it off
  1846. because it used too many resources, give this release a try.
  1847. This release also fixes yet another instance of broken OpenSSL libraries
  1848. that was causing some relays to drop out of the consensus.
  1849. o Major bugfixes:
  1850. - Teach relays to defend themselves from connection overload. Relays
  1851. now close idle circuits early if it looks like they were intended
  1852. for directory fetches. Relays are also more aggressive about closing
  1853. TLS connections that have no circuits on them. Such circuits are
  1854. unlikely to be re-used, and tens of thousands of them were piling
  1855. up at the fast relays, causing the relays to run out of sockets
  1856. and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
  1857. their directory fetches over TLS).
  1858. - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
  1859. that claim to be earlier than 0.9.8m, but which have in reality
  1860. backported huge swaths of 0.9.8m or 0.9.8n renegotiation
  1861. behavior. Possible fix for some cases of bug 1346.
  1862. - Directory mirrors were fetching relay descriptors only from v2
  1863. directory authorities, rather than v3 authorities like they should.
  1864. Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
  1865. to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
  1866. o Minor bugfixes:
  1867. - Finally get rid of the deprecated and now harmful notion of "clique
  1868. mode", where directory authorities maintain TLS connections to
  1869. every other relay.
  1870. o Testsuite fixes:
  1871. - In the util/threads test, no longer free the test_mutex before all
  1872. worker threads have finished. Bugfix on 0.2.1.6-alpha.
  1873. - The master thread could starve the worker threads quite badly on
  1874. certain systems, causing them to run only partially in the allowed
  1875. window. This resulted in test failures. Now the master thread sleeps
  1876. occasionally for a few microseconds while the two worker-threads
  1877. compete for the mutex. Bugfix on 0.2.0.1-alpha.
  1878. Changes in version 0.2.1.25 - 2010-03-16
  1879. Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
  1880. prevent relays from guessing their IP address correctly. It also fixes
  1881. several minor potential security bugs.
  1882. o Major bugfixes:
  1883. - Fix a regression from our patch for bug 1244 that caused relays
  1884. to guess their IP address incorrectly if they didn't set Address
  1885. in their torrc and/or their address fails to resolve. Bugfix on
  1886. 0.2.1.23; fixes bug 1269.
  1887. - When freeing a session key, zero it out completely. We only zeroed
  1888. the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
  1889. patched by ekir. Fixes bug 1254.
  1890. o Minor bugfixes:
  1891. - Fix a dereference-then-NULL-check sequence when publishing
  1892. descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
  1893. bug 1255.
  1894. - Fix another dereference-then-NULL-check sequence. Bugfix on
  1895. 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
  1896. - Make sure we treat potentially not NUL-terminated strings correctly.
  1897. Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
  1898. Changes in version 0.2.1.24 - 2010-02-21
  1899. Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
  1900. for sure!
  1901. o Minor bugfixes:
  1902. - Work correctly out-of-the-box with even more vendor-patched versions
  1903. of OpenSSL. In particular, make it so Debian and OS X don't need
  1904. customized patches to run/build.
  1905. Changes in version 0.2.1.23 - 2010-02-13
  1906. Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
  1907. again on the latest OS X, and updates the location of a directory
  1908. authority.
  1909. o Major bugfixes (performance):
  1910. - We were selecting our guards uniformly at random, and then weighting
  1911. which of our guards we'd use uniformly at random. This imbalance
  1912. meant that Tor clients were severely limited on throughput (and
  1913. probably latency too) by the first hop in their circuit. Now we
  1914. select guards weighted by currently advertised bandwidth. We also
  1915. automatically discard guards picked using the old algorithm. Fixes
  1916. bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
  1917. o Major bugfixes:
  1918. - Make Tor work again on the latest OS X: when deciding whether to
  1919. use strange flags to turn TLS renegotiation on, detect the OpenSSL
  1920. version at run-time, not compile time. We need to do this because
  1921. Apple doesn't update its dev-tools headers when it updates its
  1922. libraries in a security patch.
  1923. - Fix a potential buffer overflow in lookup_last_hid_serv_request()
  1924. that could happen on 32-bit platforms with 64-bit time_t. Also fix
  1925. a memory leak when requesting a hidden service descriptor we've
  1926. requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
  1927. by aakova.
  1928. o Minor bugfixes:
  1929. - Refactor resolve_my_address() to not use gethostbyname() anymore.
  1930. Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
  1931. o Minor features:
  1932. - Avoid a mad rush at the beginning of each month when each client
  1933. rotates half of its guards. Instead we spread the rotation out
  1934. throughout the month, but we still avoid leaving a precise timestamp
  1935. in the state file about when we first picked the guard. Improves
  1936. over the behavior introduced in 0.1.2.17.
  1937. Changes in version 0.2.1.22 - 2010-01-19
  1938. Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
  1939. authorities -- it would tell you its whole history of bridge descriptors
  1940. if you make the right directory request. This stable update also
  1941. rotates two of the seven v3 directory authority keys and locations.
  1942. o Directory authority changes:
  1943. - Rotate keys (both v3 identity and relay identity) for moria1
  1944. and gabelmoo.
  1945. o Major bugfixes:
  1946. - Stop bridge directory authorities from answering dbg-stability.txt
  1947. directory queries, which would let people fetch a list of all
  1948. bridge identities they track. Bugfix on 0.2.1.6-alpha.
  1949. Changes in version 0.2.1.21 - 2009-12-21
  1950. Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
  1951. library. If you use Tor on Linux / Unix and you're getting SSL
  1952. renegotiation errors, upgrading should help. We also recommend an
  1953. upgrade if you're an exit relay.
  1954. o Major bugfixes:
  1955. - Work around a security feature in OpenSSL 0.9.8l that prevents our
  1956. handshake from working unless we explicitly tell OpenSSL that we
  1957. are using SSL renegotiation safely. We are, of course, but OpenSSL
  1958. 0.9.8l won't work unless we say we are.
  1959. - Avoid crashing if the client is trying to upload many bytes and the
  1960. circuit gets torn down at the same time, or if the flip side
  1961. happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
  1962. o Minor bugfixes:
  1963. - Do not refuse to learn about authority certs and v2 networkstatus
  1964. documents that are older than the latest consensus. This bug might
  1965. have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
  1966. Spotted and fixed by xmux.
  1967. - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
  1968. trigger platform-specific option misparsing case found by Coverity
  1969. Scan.
  1970. - Fix a compilation warning on Fedora 12 by removing an impossible-to-
  1971. trigger assert. Fixes bug 1173.
  1972. Changes in version 0.2.1.20 - 2009-10-15
  1973. Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
  1974. services at once, prepares for more performance improvements, and
  1975. fixes a bunch of smaller bugs.
  1976. The Windows and OS X bundles also include a more recent Vidalia,
  1977. and switch from Privoxy to Polipo.
  1978. The OS X installers are now drag and drop. It's best to un-install
  1979. Tor/Vidalia and then install this new bundle, rather than upgrade. If
  1980. you want to upgrade, you'll need to update the paths for Tor and Polipo
  1981. in the Vidalia Settings window.
  1982. o Major bugfixes:
  1983. - Send circuit or stream sendme cells when our window has decreased
  1984. by 100 cells, not when it has decreased by 101 cells. Bug uncovered
  1985. by Karsten when testing the "reduce circuit window" performance
  1986. patch. Bugfix on the 54th commit on Tor -- from July 2002,
  1987. before the release of Tor 0.0.0. This is the new winner of the
  1988. oldest-bug prize.
  1989. - Fix a remotely triggerable memory leak when a consensus document
  1990. contains more than one signature from the same voter. Bugfix on
  1991. 0.2.0.3-alpha.
  1992. - Avoid segfault in rare cases when finishing an introduction circuit
  1993. as a client and finding out that we don't have an introduction key
  1994. for it. Fixes bug 1073. Reported by Aaron Swartz.
  1995. o Major features:
  1996. - Tor now reads the "circwindow" parameter out of the consensus,
  1997. and uses that value for its circuit package window rather than the
  1998. default of 1000 cells. Begins the implementation of proposal 168.
  1999. o New directory authorities:
  2000. - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
  2001. authority.
  2002. - Move moria1 and tonga to alternate IP addresses.
  2003. o Minor bugfixes:
  2004. - Fix a signed/unsigned compile warning in 0.2.1.19.
  2005. - Fix possible segmentation fault on directory authorities. Bugfix on
  2006. 0.2.1.14-rc.
  2007. - Fix an extremely rare infinite recursion bug that could occur if
  2008. we tried to log a message after shutting down the log subsystem.
  2009. Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
  2010. - Fix an obscure bug where hidden services on 64-bit big-endian
  2011. systems might mis-read the timestamp in v3 introduce cells, and
  2012. refuse to connect back to the client. Discovered by "rotor".
  2013. Bugfix on 0.2.1.6-alpha.
  2014. - We were triggering a CLOCK_SKEW controller status event whenever
  2015. we connect via the v2 connection protocol to any relay that has
  2016. a wrong clock. Instead, we should only inform the controller when
  2017. it's a trusted authority that claims our clock is wrong. Bugfix
  2018. on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
  2019. - We were telling the controller about CHECKING_REACHABILITY and
  2020. REACHABILITY_FAILED status events whenever we launch a testing
  2021. circuit or notice that one has failed. Instead, only tell the
  2022. controller when we want to inform the user of overall success or
  2023. overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
  2024. by SwissTorExit.
  2025. - Don't warn when we're using a circuit that ends with a node
  2026. excluded in ExcludeExitNodes, but the circuit is not used to access
  2027. the outside world. This should help fix bug 1090. Bugfix on
  2028. 0.2.1.6-alpha.
  2029. - Work around a small memory leak in some versions of OpenSSL that
  2030. stopped the memory used by the hostname TLS extension from being
  2031. freed.
  2032. o Minor features:
  2033. - Add a "getinfo status/accepted-server-descriptor" controller
  2034. command, which is the recommended way for controllers to learn
  2035. whether our server descriptor has been successfully received by at
  2036. least on directory authority. Un-recommend good-server-descriptor
  2037. getinfo and status events until we have a better design for them.
  2038. Changes in version 0.2.1.19 - 2009-07-28
  2039. Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
  2040. services.
  2041. o Major bugfixes:
  2042. - Make accessing hidden services on 0.2.1.x work right again.
  2043. Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
  2044. part of patch provided by "optimist".
  2045. o Minor features:
  2046. - When a relay/bridge is writing out its identity key fingerprint to
  2047. the "fingerprint" file and to its logs, write it without spaces. Now
  2048. it will look like the fingerprints in our bridges documentation,
  2049. and confuse fewer users.
  2050. o Minor bugfixes:
  2051. - Relays no longer publish a new server descriptor if they change
  2052. their MaxAdvertisedBandwidth config option but it doesn't end up
  2053. changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
  2054. fixes bug 1026. Patch from Sebastian.
  2055. - Avoid leaking memory every time we get a create cell but we have
  2056. so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
  2057. fixes bug 1034. Reported by BarkerJr.
  2058. Changes in version 0.2.1.18 - 2009-07-24
  2059. Tor 0.2.1.18 lays the foundations for performance improvements,
  2060. adds status events to help users diagnose bootstrap problems, adds
  2061. optional authentication/authorization for hidden services, fixes a
  2062. variety of potential anonymity problems, and includes a huge pile of
  2063. other features and bug fixes.
  2064. o Major features (clients):
  2065. - Start sending "bootstrap phase" status events to the controller,
  2066. so it can keep the user informed of progress fetching directory
  2067. information and establishing circuits. Also inform the controller
  2068. if we think we're stuck at a particular bootstrap phase. Implements
  2069. proposal 137.
  2070. - Clients replace entry guards that were chosen more than a few months
  2071. ago. This change should significantly improve client performance,
  2072. especially once more people upgrade, since relays that have been
  2073. a guard for a long time are currently overloaded.
  2074. - Network status consensus documents and votes now contain bandwidth
  2075. information for each relay. Clients use the bandwidth values
  2076. in the consensus, rather than the bandwidth values in each
  2077. relay descriptor. This approach opens the door to more accurate
  2078. bandwidth estimates once the directory authorities start doing
  2079. active measurements. Implements part of proposal 141.
  2080. o Major features (relays):
  2081. - Disable and refactor some debugging checks that forced a linear scan
  2082. over the whole server-side DNS cache. These accounted for over 50%
  2083. of CPU time on a relatively busy exit node's gprof profile. Also,
  2084. disable some debugging checks that appeared in exit node profile
  2085. data. Found by Jacob.
  2086. - New DirPortFrontPage option that takes an html file and publishes
  2087. it as "/" on the DirPort. Now relay operators can provide a
  2088. disclaimer without needing to set up a separate webserver. There's
  2089. a sample disclaimer in contrib/tor-exit-notice.html.
  2090. o Major features (hidden services):
  2091. - Make it possible to build hidden services that only certain clients
  2092. are allowed to connect to. This is enforced at several points,
  2093. so that unauthorized clients are unable to send INTRODUCE cells
  2094. to the service, or even (depending on the type of authentication)
  2095. to learn introduction points. This feature raises the bar for
  2096. certain kinds of active attacks against hidden services. Design
  2097. and code by Karsten Loesing. Implements proposal 121.
  2098. - Relays now store and serve v2 hidden service descriptors by default,
  2099. i.e., the new default value for HidServDirectoryV2 is 1. This is
  2100. the last step in proposal 114, which aims to make hidden service
  2101. lookups more reliable.
  2102. o Major features (path selection):
  2103. - ExitNodes and Exclude*Nodes config options now allow you to restrict
  2104. by country code ("{US}") or IP address or address pattern
  2105. ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
  2106. refinement to decide what config options should take priority if
  2107. you ask to both use a particular node and exclude it.
  2108. o Major features (misc):
  2109. - When building a consensus, do not include routers that are down.
  2110. This cuts down 30% to 40% on consensus size. Implements proposal
  2111. 138.
  2112. - New TestingTorNetwork config option to allow adjustment of
  2113. previously constant values that could slow bootstrapping. Implements
  2114. proposal 135. Patch from Karsten.
  2115. - Convert many internal address representations to optionally hold
  2116. IPv6 addresses. Generate and accept IPv6 addresses in many protocol
  2117. elements. Make resolver code handle nameservers located at IPv6
  2118. addresses.
  2119. - More work on making our TLS handshake blend in: modify the list
  2120. of ciphers advertised by OpenSSL in client mode to even more
  2121. closely resemble a common web browser. We cheat a little so that
  2122. we can advertise ciphers that the locally installed OpenSSL doesn't
  2123. know about.
  2124. - Use the TLS1 hostname extension to more closely resemble browser
  2125. behavior.
  2126. o Security fixes (anonymity/entropy):
  2127. - Never use a connection with a mismatched address to extend a
  2128. circuit, unless that connection is canonical. A canonical
  2129. connection is one whose address is authenticated by the router's
  2130. identity key, either in a NETINFO cell or in a router descriptor.
  2131. - Implement most of proposal 110: The first K cells to be sent
  2132. along a circuit are marked as special "early" cells; only K "early"
  2133. cells will be allowed. Once this code is universal, we can block
  2134. certain kinds of denial-of-service attack by requiring that EXTEND
  2135. commands must be sent using an "early" cell.
  2136. - Resume using OpenSSL's RAND_poll() for better (and more portable)
  2137. cross-platform entropy collection again. We used to use it, then
  2138. stopped using it because of a bug that could crash systems that
  2139. called RAND_poll when they had a lot of fds open. It looks like the
  2140. bug got fixed in late 2006. Our new behavior is to call RAND_poll()
  2141. at startup, and to call RAND_poll() when we reseed later only if
  2142. we have a non-buggy OpenSSL version.
  2143. - When the client is choosing entry guards, now it selects at most
  2144. one guard from a given relay family. Otherwise we could end up with
  2145. all of our entry points into the network run by the same operator.
  2146. Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
  2147. - Do not use or believe expired v3 authority certificates. Patch
  2148. from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
  2149. - Drop begin cells to a hidden service if they come from the middle
  2150. of a circuit. Patch from lark.
  2151. - When we erroneously receive two EXTEND cells for the same circuit
  2152. ID on the same connection, drop the second. Patch from lark.
  2153. - Authorities now vote for the Stable flag for any router whose
  2154. weighted MTBF is at least 5 days, regardless of the mean MTBF.
  2155. - Clients now never report any stream end reason except 'MISC'.
  2156. Implements proposal 148.
  2157. o Major bugfixes (crashes):
  2158. - Parse dates and IPv4 addresses in a locale- and libc-independent
  2159. manner, to avoid platform-dependent behavior on malformed input.
  2160. - Fix a crash that occurs on exit nodes when a nameserver request
  2161. timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
  2162. been suppressing the bug since 0.1.2.10-alpha. Partial fix for
  2163. bug 929.
  2164. - Do not assume that a stack-allocated character array will be
  2165. 64-bit aligned on platforms that demand that uint64_t access is
  2166. aligned. Possible fix for bug 604.
  2167. - Resolve a very rare crash bug that could occur when the user forced
  2168. a nameserver reconfiguration during the middle of a nameserver
  2169. probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
  2170. - Avoid a "0 divided by 0" calculation when calculating router uptime
  2171. at directory authorities. Bugfix on 0.2.0.8-alpha.
  2172. - Fix an assertion bug in parsing policy-related options; possible fix
  2173. for bug 811.
  2174. - Rate-limit too-many-sockets messages: when they happen, they happen
  2175. a lot and end up filling up the disk. Resolves bug 748.
  2176. - Fix a race condition that could cause crashes or memory corruption
  2177. when running as a server with a controller listening for log
  2178. messages.
  2179. - Avoid crashing when we have a policy specified in a DirPolicy or
  2180. SocksPolicy or ReachableAddresses option with ports set on it,
  2181. and we re-load the policy. May fix bug 996.
  2182. - Fix an assertion failure on 64-bit platforms when we allocated
  2183. memory right up to the end of a memarea, then realigned the memory
  2184. one step beyond the end. Fixes a possible cause of bug 930.
  2185. - Protect the count of open sockets with a mutex, so we can't
  2186. corrupt it when two threads are closing or opening sockets at once.
  2187. Fix for bug 939. Bugfix on 0.2.0.1-alpha.
  2188. o Major bugfixes (clients):
  2189. - Discard router descriptors as we load them if they are more than
  2190. five days old. Otherwise if Tor is off for a long time and then
  2191. starts with cached descriptors, it will try to use the onion keys
  2192. in those obsolete descriptors when building circuits. Fixes bug 887.
  2193. - When we choose to abandon a new entry guard because we think our
  2194. older ones might be better, close any circuits pending on that
  2195. new entry guard connection. This fix should make us recover much
  2196. faster when our network is down and then comes back. Bugfix on
  2197. 0.1.2.8-beta; found by lodger.
  2198. - When Tor clients restart after 1-5 days, they discard all their
  2199. cached descriptors as too old, but they still use the cached
  2200. consensus document. This approach is good for robustness, but
  2201. bad for performance: since they don't know any bandwidths, they
  2202. end up choosing at random rather than weighting their choice by
  2203. speed. Fixed by the above feature of putting bandwidths in the
  2204. consensus.
  2205. o Major bugfixes (relays):
  2206. - Relays were falling out of the networkstatus consensus for
  2207. part of a day if they changed their local config but the
  2208. authorities discarded their new descriptor as "not sufficiently
  2209. different". Now directory authorities accept a descriptor as changed
  2210. if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
  2211. patch by Sebastian.
  2212. - Ensure that two circuits can never exist on the same connection
  2213. with the same circuit ID, even if one is marked for close. This
  2214. is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
  2215. - Directory authorities were neglecting to mark relays down in their
  2216. internal histories if the relays fall off the routerlist without
  2217. ever being found unreachable. So there were relays in the histories
  2218. that haven't been seen for eight months, and are listed as being
  2219. up for eight months. This wreaked havoc on the "median wfu" and
  2220. "median mtbf" calculations, in turn making Guard and Stable flags
  2221. wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
  2222. on 0.2.0.6-alpha.
  2223. o Major bugfixes (hidden services):
  2224. - When establishing a hidden service, introduction points that
  2225. originate from cannibalized circuits were completely ignored
  2226. and not included in rendezvous service descriptors. This might
  2227. have been another reason for delay in making a hidden service
  2228. available. Bugfix from long ago (0.0.9.x?)
  2229. o Major bugfixes (memory and resource management):
  2230. - Fixed some memory leaks -- some quite frequent, some almost
  2231. impossible to trigger -- based on results from Coverity.
  2232. - Speed up parsing and cut down on memory fragmentation by using
  2233. stack-style allocations for parsing directory objects. Previously,
  2234. this accounted for over 40% of allocations from within Tor's code
  2235. on a typical directory cache.
  2236. - Use a Bloom filter rather than a digest-based set to track which
  2237. descriptors we need to keep around when we're cleaning out old
  2238. router descriptors. This speeds up the computation significantly,
  2239. and may reduce fragmentation.
  2240. o New/changed config options:
  2241. - Now NodeFamily and MyFamily config options allow spaces in
  2242. identity fingerprints, so it's easier to paste them in.
  2243. Suggested by Lucky Green.
  2244. - Allow ports 465 and 587 in the default exit policy again. We had
  2245. rejected them in 0.1.0.15, because back in 2005 they were commonly
  2246. misconfigured and ended up as spam targets. We hear they are better
  2247. locked down these days.
  2248. - Make TrackHostExit mappings expire a while after their last use, not
  2249. after their creation. Patch from Robert Hogan.
  2250. - Add an ExcludeExitNodes option so users can list a set of nodes
  2251. that should be be excluded from the exit node position, but
  2252. allowed elsewhere. Implements proposal 151.
  2253. - New --hush command-line option similar to --quiet. While --quiet
  2254. disables all logging to the console on startup, --hush limits the
  2255. output to messages of warning and error severity.
  2256. - New configure/torrc options (--enable-geoip-stats,
  2257. DirRecordUsageByCountry) to record how many IPs we've served
  2258. directory info to in each country code, how many status documents
  2259. total we've sent to each country code, and what share of the total
  2260. directory requests we should expect to see.
  2261. - Make outbound DNS packets respect the OutboundBindAddress setting.
  2262. Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
  2263. - Allow separate log levels to be configured for different logging
  2264. domains. For example, this allows one to log all notices, warnings,
  2265. or errors, plus all memory management messages of level debug or
  2266. higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
  2267. - Update to the "June 3 2009" ip-to-country file.
  2268. o Minor features (relays):
  2269. - Raise the minimum rate limiting to be a relay from 20000 bytes
  2270. to 20480 bytes (aka 20KB/s), to match our documentation. Also
  2271. update directory authorities so they always assign the Fast flag
  2272. to relays with 20KB/s of capacity. Now people running relays won't
  2273. suddenly find themselves not seeing any use, if the network gets
  2274. faster on average.
  2275. - If we're a relay and we change our IP address, be more verbose
  2276. about the reason that made us change. Should help track down
  2277. further bugs for relays on dynamic IP addresses.
  2278. - Exit servers can now answer resolve requests for ip6.arpa addresses.
  2279. - Implement most of Proposal 152: allow specialized servers to permit
  2280. single-hop circuits, and clients to use those servers to build
  2281. single-hop circuits when using a specialized controller. Patch
  2282. from Josh Albrecht. Resolves feature request 768.
  2283. - When relays do their initial bandwidth measurement, don't limit
  2284. to just our entry guards for the test circuits. Otherwise we tend
  2285. to have multiple test circuits going through a single entry guard,
  2286. which makes our bandwidth test less accurate. Fixes part of bug 654;
  2287. patch contributed by Josh Albrecht.
  2288. o Minor features (directory authorities):
  2289. - Try not to open more than one descriptor-downloading connection
  2290. to an authority at once. This should reduce load on directory
  2291. authorities. Fixes bug 366.
  2292. - Add cross-certification to newly generated certificates, so that
  2293. a signing key is enough information to look up a certificate. Start
  2294. serving certificates by <identity digest, signing key digest>
  2295. pairs. Implements proposal 157.
  2296. - When a directory authority downloads a descriptor that it then
  2297. immediately rejects, do not retry downloading it right away. Should
  2298. save some bandwidth on authorities. Fix for bug 888. Patch by
  2299. Sebastian Hahn.
  2300. - Directory authorities now serve a /tor/dbg-stability.txt URL to
  2301. help debug WFU and MTBF calculations.
  2302. - In directory authorities' approved-routers files, allow
  2303. fingerprints with or without space.
  2304. o Minor features (directory mirrors):
  2305. - When a download gets us zero good descriptors, do not notify
  2306. Tor that new directory information has arrived.
  2307. - Servers support a new URL scheme for consensus downloads that
  2308. allows the client to specify which authorities are trusted.
  2309. The server then only sends the consensus if the client will trust
  2310. it. Otherwise a 404 error is sent back. Clients use this
  2311. new scheme when the server supports it (meaning it's running
  2312. 0.2.1.1-alpha or later). Implements proposal 134.
  2313. o Minor features (bridges):
  2314. - If the bridge config line doesn't specify a port, assume 443.
  2315. This makes bridge lines a bit smaller and easier for users to
  2316. understand.
  2317. - If we're using bridges and our network goes away, be more willing
  2318. to forgive our bridges and try again when we get an application
  2319. request.
  2320. o Minor features (hidden services):
  2321. - When the client launches an introduction circuit, retry with a
  2322. new circuit after 30 seconds rather than 60 seconds.
  2323. - Launch a second client-side introduction circuit in parallel
  2324. after a delay of 15 seconds (based on work by Christian Wilms).
  2325. - Hidden services start out building five intro circuits rather
  2326. than three, and when the first three finish they publish a service
  2327. descriptor using those. Now we publish our service descriptor much
  2328. faster after restart.
  2329. - Drop the requirement to have an open dir port for storing and
  2330. serving v2 hidden service descriptors.
  2331. o Minor features (build and packaging):
  2332. - On Linux, use the prctl call to re-enable core dumps when the User
  2333. option is set.
  2334. - Try to make sure that the version of Libevent we're running with
  2335. is binary-compatible with the one we built with. May address bug
  2336. 897 and others.
  2337. - Add a new --enable-local-appdata configuration switch to change
  2338. the default location of the datadir on win32 from APPDATA to
  2339. LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
  2340. entirely. Patch from coderman.
  2341. - Build correctly against versions of OpenSSL 0.9.8 or later that
  2342. are built without support for deprecated functions.
  2343. - On platforms with a maximum syslog string length, truncate syslog
  2344. messages to that length ourselves, rather than relying on the
  2345. system to do it for us.
  2346. - Automatically detect MacOSX versions earlier than 10.4.0, and
  2347. disable kqueue from inside Tor when running with these versions.
  2348. We previously did this from the startup script, but that was no
  2349. help to people who didn't use the startup script. Resolves bug 863.
  2350. - Build correctly when configured to build outside the main source
  2351. path. Patch from Michael Gold.
  2352. - Disable GCC's strict alias optimization by default, to avoid the
  2353. likelihood of its introducing subtle bugs whenever our code violates
  2354. the letter of C99's alias rules.
  2355. - Change the contrib/tor.logrotate script so it makes the new
  2356. logs as "_tor:_tor" rather than the default, which is generally
  2357. "root:wheel". Fixes bug 676, reported by Serge Koksharov.
  2358. - Change our header file guard macros to be less likely to conflict
  2359. with system headers. Adam Langley noticed that we were conflicting
  2360. with log.h on Android.
  2361. - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
  2362. and stop using a warning that had become unfixably verbose under
  2363. GCC 4.3.
  2364. - Use a lockfile to make sure that two Tor processes are not
  2365. simultaneously running with the same datadir.
  2366. - Allow OpenSSL to use dynamic locks if it wants.
  2367. - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
  2368. o Minor features (controllers):
  2369. - When generating circuit events with verbose nicknames for
  2370. controllers, try harder to look up nicknames for routers on a
  2371. circuit. (Previously, we would look in the router descriptors we had
  2372. for nicknames, but not in the consensus.) Partial fix for bug 941.
  2373. - New controller event NEWCONSENSUS that lists the networkstatus
  2374. lines for every recommended relay. Now controllers like Torflow
  2375. can keep up-to-date on which relays they should be using.
  2376. - New controller event "clients_seen" to report a geoip-based summary
  2377. of which countries we've seen clients from recently. Now controllers
  2378. like Vidalia can show bridge operators that they're actually making
  2379. a difference.
  2380. - Add a 'getinfo status/clients-seen' controller command, in case
  2381. controllers want to hear clients_seen events but connect late.
  2382. - New CONSENSUS_ARRIVED event to note when a new consensus has
  2383. been fetched and validated.
  2384. - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
  2385. controllers to prevent SIGHUP from reloading the configuration.
  2386. Fixes bug 856.
  2387. - Return circuit purposes in response to GETINFO circuit-status.
  2388. Fixes bug 858.
  2389. - Serve the latest v3 networkstatus consensus via the control
  2390. port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
  2391. - Add a "GETINFO /status/bootstrap-phase" controller option, so the
  2392. controller can query our current bootstrap state in case it attaches
  2393. partway through and wants to catch up.
  2394. - Provide circuit purposes along with circuit events to the controller.
  2395. o Minor features (tools):
  2396. - Do not have tor-resolve automatically refuse all .onion addresses;
  2397. if AutomapHostsOnResolve is set in your torrc, this will work fine.
  2398. - Add a -p option to tor-resolve for specifying the SOCKS port: some
  2399. people find host:port too confusing.
  2400. - Print the SOCKS5 error message string as well as the error code
  2401. when a tor-resolve request fails. Patch from Jacob.
  2402. o Minor bugfixes (memory and resource management):
  2403. - Clients no longer cache certificates for authorities they do not
  2404. recognize. Bugfix on 0.2.0.9-alpha.
  2405. - Do not use C's stdio library for writing to log files. This will
  2406. improve logging performance by a minute amount, and will stop
  2407. leaking fds when our disk is full. Fixes bug 861.
  2408. - Stop erroneous use of O_APPEND in cases where we did not in fact
  2409. want to re-seek to the end of a file before every last write().
  2410. - Fix a small alignment and memory-wasting bug on buffer chunks.
  2411. Spotted by rovv.
  2412. - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
  2413. to avoid unused RAM in buffer chunks and memory pools.
  2414. - Reduce the default smartlist size from 32 to 16; it turns out that
  2415. most smartlists hold around 8-12 elements tops.
  2416. - Make dumpstats() log the fullness and size of openssl-internal
  2417. buffers.
  2418. - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
  2419. patch to their OpenSSL, turn it on to save memory on servers. This
  2420. patch will (with any luck) get included in a mainline distribution
  2421. before too long.
  2422. - Fix a memory leak when v3 directory authorities load their keys
  2423. and cert from disk. Bugfix on 0.2.0.1-alpha.
  2424. - Stop using malloc_usable_size() to use more area than we had
  2425. actually allocated: it was safe, but made valgrind really unhappy.
  2426. - Make the assert_circuit_ok() function work correctly on circuits that
  2427. have already been marked for close.
  2428. - Fix uninitialized size field for memory area allocation: may improve
  2429. memory performance during directory parsing.
  2430. o Minor bugfixes (clients):
  2431. - Stop reloading the router list from disk for no reason when we
  2432. run out of reachable directory mirrors. Once upon a time reloading
  2433. it would set the 'is_running' flag back to 1 for them. It hasn't
  2434. done that for a long time.
  2435. - When we had picked an exit node for a connection, but marked it as
  2436. "optional", and it turned out we had no onion key for the exit,
  2437. stop wanting that exit and try again. This situation may not
  2438. be possible now, but will probably become feasible with proposal
  2439. 158. Spotted by rovv. Fixes another case of bug 752.
  2440. - Fix a bug in address parsing that was preventing bridges or hidden
  2441. service targets from being at IPv6 addresses.
  2442. - Do not remove routers as too old if we do not have any consensus
  2443. document. Bugfix on 0.2.0.7-alpha.
  2444. - When an exit relay resolves a stream address to a local IP address,
  2445. do not just keep retrying that same exit relay over and
  2446. over. Instead, just close the stream. Addresses bug 872. Bugfix
  2447. on 0.2.0.32. Patch from rovv.
  2448. - Made Tor a little less aggressive about deleting expired
  2449. certificates. Partial fix for bug 854.
  2450. - Treat duplicate certificate fetches as failures, so that we do
  2451. not try to re-fetch an expired certificate over and over and over.
  2452. - Do not say we're fetching a certificate when we'll in fact skip it
  2453. because of a pending download.
  2454. - If we have correct permissions on $datadir, we complain to stdout
  2455. and fail to start. But dangerous permissions on
  2456. $datadir/cached-status/ would cause us to open a log and complain
  2457. there. Now complain to stdout and fail to start in both cases. Fixes
  2458. bug 820, reported by seeess.
  2459. o Minor bugfixes (bridges):
  2460. - When we made bridge authorities stop serving bridge descriptors over
  2461. unencrypted links, we also broke DirPort reachability testing for
  2462. bridges. So bridges with a non-zero DirPort were printing spurious
  2463. warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
  2464. - Don't allow a bridge to publish its router descriptor to a
  2465. non-bridge directory authority. Fixes part of bug 932.
  2466. - When we change to or from being a bridge, reset our counts of
  2467. client usage by country. Fixes bug 932.
  2468. o Minor bugfixes (relays):
  2469. - Log correct error messages for DNS-related network errors on
  2470. Windows.
  2471. - Actually return -1 in the error case for read_bandwidth_usage().
  2472. Harmless bug, since we currently don't care about the return value
  2473. anywhere. Bugfix on 0.2.0.9-alpha.
  2474. - Provide a more useful log message if bug 977 (related to buffer
  2475. freelists) ever reappears, and do not crash right away.
  2476. - We were already rejecting relay begin cells with destination port
  2477. of 0. Now also reject extend cells with destination port or address
  2478. of 0. Suggested by lark.
  2479. - When we can't transmit a DNS request due to a network error, retry
  2480. it after a while, and eventually transmit a failing response to
  2481. the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
  2482. - Solve a bug that kept hardware crypto acceleration from getting
  2483. enabled when accounting was turned on. Fixes bug 907. Bugfix on
  2484. 0.0.9pre6.
  2485. - When a canonical connection appears later in our internal list
  2486. than a noncanonical one for a given OR ID, always use the
  2487. canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
  2488. Spotted by rovv.
  2489. - Avoid some nasty corner cases in the logic for marking connections
  2490. as too old or obsolete or noncanonical for circuits. Partial
  2491. bugfix on bug 891.
  2492. - Fix another interesting corner-case of bug 891 spotted by rovv:
  2493. Previously, if two hosts had different amounts of clock drift, and
  2494. one of them created a new connection with just the wrong timing,
  2495. the other might decide to deprecate the new connection erroneously.
  2496. Bugfix on 0.1.1.13-alpha.
  2497. - If one win32 nameserver fails to get added, continue adding the
  2498. rest, and don't automatically fail.
  2499. - Fix a bug where an unreachable relay would establish enough
  2500. reachability testing circuits to do a bandwidth test -- if
  2501. we already have a connection to the middle hop of the testing
  2502. circuit, then it could establish the last hop by using the existing
  2503. connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
  2504. circuits no longer use entry guards in 0.2.1.3-alpha.
  2505. o Minor bugfixes (directory authorities):
  2506. - Limit uploaded directory documents to be 16M rather than 500K.
  2507. The directory authorities were refusing v3 consensus votes from
  2508. other authorities, since the votes are now 504K. Fixes bug 959;
  2509. bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
  2510. - Directory authorities should never send a 503 "busy" response to
  2511. requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
  2512. bug 959.
  2513. - Fix code so authorities _actually_ send back X-Descriptor-Not-New
  2514. headers. Bugfix on 0.2.0.10-alpha.
  2515. o Minor bugfixes (hidden services):
  2516. - When we can't find an intro key for a v2 hidden service descriptor,
  2517. fall back to the v0 hidden service descriptor and log a bug message.
  2518. Workaround for bug 1024.
  2519. - In very rare situations new hidden service descriptors were
  2520. published earlier than 30 seconds after the last change to the
  2521. service. (We currently think that a hidden service descriptor
  2522. that's been stable for 30 seconds is worth publishing.)
  2523. - If a hidden service sends us an END cell, do not consider
  2524. retrying the connection; just close it. Patch from rovv.
  2525. - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
  2526. service directories if they have no advertised dir port. Bugfix
  2527. on 0.2.0.10-alpha.
  2528. o Minor bugfixes (tools):
  2529. - In the torify(1) manpage, mention that tsocks will leak your
  2530. DNS requests.
  2531. o Minor bugfixes (controllers):
  2532. - If the controller claimed responsibility for a stream, but that
  2533. stream never finished making its connection, it would live
  2534. forever in circuit_wait state. Now we close it after SocksTimeout
  2535. seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
  2536. - Make DNS resolved controller events into "CLOSED", not
  2537. "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
  2538. bug 807.
  2539. - The control port would close the connection before flushing long
  2540. replies, such as the network consensus, if a QUIT command was issued
  2541. before the reply had completed. Now, the control port flushes all
  2542. pending replies before closing the connection. Also fix a spurious
  2543. warning when a QUIT command is issued after a malformed or rejected
  2544. AUTHENTICATE command, but before the connection was closed. Patch
  2545. by Marcus Griep. Fixes bugs 1015 and 1016.
  2546. - Fix a bug that made stream bandwidth get misreported to the
  2547. controller.
  2548. o Deprecated and removed features:
  2549. - The old "tor --version --version" command, which would print out
  2550. the subversion "Id" of most of the source files, is now removed. It
  2551. turned out to be less useful than we'd expected, and harder to
  2552. maintain.
  2553. - RedirectExits has been removed. It was deprecated since
  2554. 0.2.0.3-alpha.
  2555. - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
  2556. has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
  2557. - Cell pools are now always enabled; --disable-cell-pools is ignored.
  2558. - Directory mirrors no longer fetch the v1 directory or
  2559. running-routers files. They are obsolete, and nobody asks for them
  2560. anymore. This is the first step to making v1 authorities obsolete.
  2561. - Take out the TestVia config option, since it was a workaround for
  2562. a bug that was fixed in Tor 0.1.1.21.
  2563. - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
  2564. HiddenServiceExcludeNodes as obsolete: they never worked properly,
  2565. and nobody seems to be using them. Fixes bug 754. Bugfix on
  2566. 0.1.0.1-rc. Patch from Christian Wilms.
  2567. - Remove all backward-compatibility code for relays running
  2568. versions of Tor so old that they no longer work at all on the
  2569. Tor network.
  2570. o Code simplifications and refactoring:
  2571. - Tool-assisted documentation cleanup. Nearly every function or
  2572. static variable in Tor should have its own documentation now.
  2573. - Rename the confusing or_is_obsolete field to the more appropriate
  2574. is_bad_for_new_circs, and move it to or_connection_t where it
  2575. belongs.
  2576. - Move edge-only flags from connection_t to edge_connection_t: not
  2577. only is this better coding, but on machines of plausible alignment,
  2578. it should save 4-8 bytes per connection_t. "Every little bit helps."
  2579. - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
  2580. for consistency; keep old option working for backward compatibility.
  2581. - Simplify the code for finding connections to use for a circuit.
  2582. - Revise the connection_new functions so that a more typesafe variant
  2583. exists. This will work better with Coverity, and let us find any
  2584. actual mistakes we're making here.
  2585. - Refactor unit testing logic so that dmalloc can be used sensibly
  2586. with unit tests to check for memory leaks.
  2587. - Move all hidden-service related fields from connection and circuit
  2588. structure to substructures: this way they won't eat so much memory.
  2589. - Squeeze 2-5% out of client performance (according to oprofile) by
  2590. improving the implementation of some policy-manipulation functions.
  2591. - Change the implementation of ExcludeNodes and ExcludeExitNodes to
  2592. be more efficient. Formerly it was quadratic in the number of
  2593. servers; now it should be linear. Fixes bug 509.
  2594. - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
  2595. and n_conn_id_digest fields into a separate structure that's
  2596. only needed when the circuit has not yet attached to an n_conn.
  2597. - Optimize out calls to time(NULL) that occur for every IO operation,
  2598. or for every cell. On systems like Windows where time() is a
  2599. slow syscall, this fix will be slightly helpful.
  2600. Changes in version 0.2.0.35 - 2009-06-24
  2601. o Security fix:
  2602. - Avoid crashing in the presence of certain malformed descriptors.
  2603. Found by lark, and by automated fuzzing.
  2604. - Fix an edge case where a malicious exit relay could convince a
  2605. controller that the client's DNS question resolves to an internal IP
  2606. address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
  2607. o Major bugfixes:
  2608. - Finally fix the bug where dynamic-IP relays disappear when their
  2609. IP address changes: directory mirrors were mistakenly telling
  2610. them their old address if they asked via begin_dir, so they
  2611. never got an accurate answer about their new address, so they
  2612. just vanished after a day. For belt-and-suspenders, relays that
  2613. don't set Address in their config now avoid using begin_dir for
  2614. all direct connections. Should fix bugs 827, 883, and 900.
  2615. - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
  2616. that would occur on some exit nodes when DNS failures and timeouts
  2617. occurred in certain patterns. Fix for bug 957.
  2618. o Minor bugfixes:
  2619. - When starting with a cache over a few days old, do not leak
  2620. memory for the obsolete router descriptors in it. Bugfix on
  2621. 0.2.0.33; fixes bug 672.
  2622. - Hidden service clients didn't use a cached service descriptor that
  2623. was older than 15 minutes, but wouldn't fetch a new one either,
  2624. because there was already one in the cache. Now, fetch a v2
  2625. descriptor unless the same descriptor was added to the cache within
  2626. the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
  2627. Changes in version 0.2.0.34 - 2009-02-08
  2628. Tor 0.2.0.34 features several more security-related fixes. You should
  2629. upgrade, especially if you run an exit relay (remote crash) or a
  2630. directory authority (remote infinite loop), or you're on an older
  2631. (pre-XP) or not-recently-patched Windows (remote exploit).
  2632. This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
  2633. have many known flaws, and nobody should be using them. You should
  2634. upgrade. If you're using a Linux or BSD and its packages are obsolete,
  2635. stop using those packages and upgrade anyway.
  2636. o Security fixes:
  2637. - Fix an infinite-loop bug on handling corrupt votes under certain
  2638. circumstances. Bugfix on 0.2.0.8-alpha.
  2639. - Fix a temporary DoS vulnerability that could be performed by
  2640. a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
  2641. - Avoid a potential crash on exit nodes when processing malformed
  2642. input. Remote DoS opportunity. Bugfix on 0.2.0.33.
  2643. - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
  2644. Spec conformance issue. Bugfix on Tor 0.0.2pre27.
  2645. o Minor bugfixes:
  2646. - Fix compilation on systems where time_t is a 64-bit integer.
  2647. Patch from Matthias Drochner.
  2648. - Don't consider expiring already-closed client connections. Fixes
  2649. bug 893. Bugfix on 0.0.2pre20.
  2650. Changes in version 0.2.0.33 - 2009-01-21
  2651. Tor 0.2.0.33 fixes a variety of bugs that were making relays less
  2652. useful to users. It also finally fixes a bug where a relay or client
  2653. that's been off for many days would take a long time to bootstrap.
  2654. This update also fixes an important security-related bug reported by
  2655. Ilja van Sprundel. You should upgrade. (We'll send out more details
  2656. about the bug once people have had some time to upgrade.)
  2657. o Security fixes:
  2658. - Fix a heap-corruption bug that may be remotely triggerable on
  2659. some platforms. Reported by Ilja van Sprundel.
  2660. o Major bugfixes:
  2661. - When a stream at an exit relay is in state "resolving" or
  2662. "connecting" and it receives an "end" relay cell, the exit relay
  2663. would silently ignore the end cell and not close the stream. If
  2664. the client never closes the circuit, then the exit relay never
  2665. closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
  2666. reported by "wood".
  2667. - When sending CREATED cells back for a given circuit, use a 64-bit
  2668. connection ID to find the right connection, rather than an addr:port
  2669. combination. Now that we can have multiple OR connections between
  2670. the same ORs, it is no longer possible to use addr:port to uniquely
  2671. identify a connection.
  2672. - Bridge relays that had DirPort set to 0 would stop fetching
  2673. descriptors shortly after startup, and then briefly resume
  2674. after a new bandwidth test and/or after publishing a new bridge
  2675. descriptor. Bridge users that try to bootstrap from them would
  2676. get a recent networkstatus but would get descriptors from up to
  2677. 18 hours earlier, meaning most of the descriptors were obsolete
  2678. already. Reported by Tas; bugfix on 0.2.0.13-alpha.
  2679. - Prevent bridge relays from serving their 'extrainfo' document
  2680. to anybody who asks, now that extrainfo docs include potentially
  2681. sensitive aggregated client geoip summaries. Bugfix on
  2682. 0.2.0.13-alpha.
  2683. - If the cached networkstatus consensus is more than five days old,
  2684. discard it rather than trying to use it. In theory it could be
  2685. useful because it lists alternate directory mirrors, but in practice
  2686. it just means we spend many minutes trying directory mirrors that
  2687. are long gone from the network. Also discard router descriptors as
  2688. we load them if they are more than five days old, since the onion
  2689. key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
  2690. o Minor bugfixes:
  2691. - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
  2692. could make gcc generate non-functional binary search code. Bugfix
  2693. on 0.2.0.10-alpha.
  2694. - Build correctly on platforms without socklen_t.
  2695. - Compile without warnings on solaris.
  2696. - Avoid potential crash on internal error during signature collection.
  2697. Fixes bug 864. Patch from rovv.
  2698. - Correct handling of possible malformed authority signing key
  2699. certificates with internal signature types. Fixes bug 880.
  2700. Bugfix on 0.2.0.3-alpha.
  2701. - Fix a hard-to-trigger resource leak when logging credential status.
  2702. CID 349.
  2703. - When we can't initialize DNS because the network is down, do not
  2704. automatically stop Tor from starting. Instead, we retry failed
  2705. dns_init() every 10 minutes, and change the exit policy to reject
  2706. *:* until one succeeds. Fixes bug 691.
  2707. - Use 64 bits instead of 32 bits for connection identifiers used with
  2708. the controller protocol, to greatly reduce risk of identifier reuse.
  2709. - When we're choosing an exit node for a circuit, and we have
  2710. no pending streams, choose a good general exit rather than one that
  2711. supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
  2712. - Fix another case of assuming, when a specific exit is requested,
  2713. that we know more than the user about what hosts it allows.
  2714. Fixes one case of bug 752. Patch from rovv.
  2715. - Clip the MaxCircuitDirtiness config option to a minimum of 10
  2716. seconds. Warn the user if lower values are given in the
  2717. configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
  2718. - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
  2719. user if lower values are given in the configuration. Bugfix on
  2720. 0.1.1.17-rc. Patch by Sebastian.
  2721. - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
  2722. the cache because we already had a v0 descriptor with the same ID.
  2723. Bugfix on 0.2.0.18-alpha.
  2724. - Fix a race condition when freeing keys shared between main thread
  2725. and CPU workers that could result in a memory leak. Bugfix on
  2726. 0.1.0.1-rc. Fixes bug 889.
  2727. - Send a valid END cell back when a client tries to connect to a
  2728. nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
  2729. 840. Patch from rovv.
  2730. - Check which hops rendezvous stream cells are associated with to
  2731. prevent possible guess-the-streamid injection attacks from
  2732. intermediate hops. Fixes another case of bug 446. Based on patch
  2733. from rovv.
  2734. - If a broken client asks a non-exit router to connect somewhere,
  2735. do not even do the DNS lookup before rejecting the connection.
  2736. Fixes another case of bug 619. Patch from rovv.
  2737. - When a relay gets a create cell it can't decrypt (e.g. because it's
  2738. using the wrong onion key), we were dropping it and letting the
  2739. client time out. Now actually answer with a destroy cell. Fixes
  2740. bug 904. Bugfix on 0.0.2pre8.
  2741. o Minor bugfixes (hidden services):
  2742. - Do not throw away existing introduction points on SIGHUP. Bugfix on
  2743. 0.0.6pre1. Patch by Karsten. Fixes bug 874.
  2744. o Minor features:
  2745. - Report the case where all signatures in a detached set are rejected
  2746. differently than the case where there is an error handling the
  2747. detached set.
  2748. - When we realize that another process has modified our cached
  2749. descriptors, print out a more useful error message rather than
  2750. triggering an assertion. Fixes bug 885. Patch from Karsten.
  2751. - Implement the 0x20 hack to better resist DNS poisoning: set the
  2752. case on outgoing DNS requests randomly, and reject responses that do
  2753. not match the case correctly. This logic can be disabled with the
  2754. ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
  2755. of servers that do not reliably preserve case in replies. See
  2756. "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
  2757. for more info.
  2758. - Check DNS replies for more matching fields to better resist DNS
  2759. poisoning.
  2760. - Never use OpenSSL compression: it wastes RAM and CPU trying to
  2761. compress cells, which are basically all encrypted, compressed, or
  2762. both.
  2763. Changes in version 0.2.0.32 - 2008-11-20
  2764. Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
  2765. packages (and maybe other packages) noticed by Theo de Raadt, fixes
  2766. a smaller security flaw that might allow an attacker to access local
  2767. services, further improves hidden service performance, and fixes a
  2768. variety of other issues.
  2769. o Security fixes:
  2770. - The "User" and "Group" config options did not clear the
  2771. supplementary group entries for the Tor process. The "User" option
  2772. is now more robust, and we now set the groups to the specified
  2773. user's primary group. The "Group" option is now ignored. For more
  2774. detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
  2775. in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
  2776. and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
  2777. - The "ClientDNSRejectInternalAddresses" config option wasn't being
  2778. consistently obeyed: if an exit relay refuses a stream because its
  2779. exit policy doesn't allow it, we would remember what IP address
  2780. the relay said the destination address resolves to, even if it's
  2781. an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
  2782. o Major bugfixes:
  2783. - Fix a DOS opportunity during the voting signature collection process
  2784. at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
  2785. o Major bugfixes (hidden services):
  2786. - When fetching v0 and v2 rendezvous service descriptors in parallel,
  2787. we were failing the whole hidden service request when the v0
  2788. descriptor fetch fails, even if the v2 fetch is still pending and
  2789. might succeed. Similarly, if the last v2 fetch fails, we were
  2790. failing the whole hidden service request even if a v0 fetch is
  2791. still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
  2792. - When extending a circuit to a hidden service directory to upload a
  2793. rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
  2794. requests failed, because the router descriptor has not been
  2795. downloaded yet. In these cases, do not attempt to upload the
  2796. rendezvous descriptor, but wait until the router descriptor is
  2797. downloaded and retry. Likewise, do not attempt to fetch a rendezvous
  2798. descriptor from a hidden service directory for which the router
  2799. descriptor has not yet been downloaded. Fixes bug 767. Bugfix
  2800. on 0.2.0.10-alpha.
  2801. o Minor bugfixes:
  2802. - Fix several infrequent memory leaks spotted by Coverity.
  2803. - When testing for libevent functions, set the LDFLAGS variable
  2804. correctly. Found by Riastradh.
  2805. - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
  2806. bootstrapping with tunneled directory connections. Bugfix on
  2807. 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
  2808. - When asked to connect to A.B.exit:80, if we don't know the IP for A
  2809. and we know that server B rejects most-but-not all connections to
  2810. port 80, we would previously reject the connection. Now, we assume
  2811. the user knows what they were asking for. Fixes bug 752. Bugfix
  2812. on 0.0.9rc5. Diagnosed by BarkerJr.
  2813. - If we overrun our per-second write limits a little, count this as
  2814. having used up our write allocation for the second, and choke
  2815. outgoing directory writes. Previously, we had only counted this when
  2816. we had met our limits precisely. Fixes bug 824. Patch from by rovv.
  2817. Bugfix on 0.2.0.x (??).
  2818. - Remove the old v2 directory authority 'lefkada' from the default
  2819. list. It has been gone for many months.
  2820. - Stop doing unaligned memory access that generated bus errors on
  2821. sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
  2822. - Make USR2 log-level switch take effect immediately. Bugfix on
  2823. 0.1.2.8-beta.
  2824. o Minor bugfixes (controller):
  2825. - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
  2826. 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
  2827. Changes in version 0.2.0.31 - 2008-09-03
  2828. Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
  2829. a big bug we're seeing where in rare cases traffic from one Tor stream
  2830. gets mixed into another stream, and fixes a variety of smaller issues.
  2831. o Major bugfixes:
  2832. - Make sure that two circuits can never exist on the same connection
  2833. with the same circuit ID, even if one is marked for close. This
  2834. is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
  2835. - Relays now reject risky extend cells: if the extend cell includes
  2836. a digest of all zeroes, or asks to extend back to the relay that
  2837. sent the extend cell, tear down the circuit. Ideas suggested
  2838. by rovv.
  2839. - If not enough of our entry guards are available so we add a new
  2840. one, we might use the new one even if it overlapped with the
  2841. current circuit's exit relay (or its family). Anonymity bugfix
  2842. pointed out by rovv.
  2843. o Minor bugfixes:
  2844. - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
  2845. 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
  2846. - Correctly detect the presence of the linux/netfilter_ipv4.h header
  2847. when building against recent kernels. Bugfix on 0.1.2.1-alpha.
  2848. - Pick size of default geoip filename string correctly on windows.
  2849. Fixes bug 806. Bugfix on 0.2.0.30.
  2850. - Make the autoconf script accept the obsolete --with-ssl-dir
  2851. option as an alias for the actually-working --with-openssl-dir
  2852. option. Fix the help documentation to recommend --with-openssl-dir.
  2853. Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
  2854. - When using the TransPort option on OpenBSD, and using the User
  2855. option to change UID and drop privileges, make sure to open
  2856. /dev/pf before dropping privileges. Fixes bug 782. Patch from
  2857. Christopher Davis. Bugfix on 0.1.2.1-alpha.
  2858. - Try to attach connections immediately upon receiving a RENDEZVOUS2
  2859. or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
  2860. on the client side when connecting to a hidden service. Bugfix
  2861. on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
  2862. - When closing an application-side connection because its circuit is
  2863. getting torn down, generate the stream event correctly. Bugfix on
  2864. 0.1.2.x. Anonymous patch.
  2865. Changes in version 0.2.0.30 - 2008-07-15
  2866. This new stable release switches to a more efficient directory
  2867. distribution design, adds features to make connections to the Tor
  2868. network harder to block, allows Tor to act as a DNS proxy, adds separate
  2869. rate limiting for relayed traffic to make it easier for clients to
  2870. become relays, fixes a variety of potential anonymity problems, and
  2871. includes the usual huge pile of other features and bug fixes.
  2872. o New v3 directory design:
  2873. - Tor now uses a new way to learn about and distribute information
  2874. about the network: the directory authorities vote on a common
  2875. network status document rather than each publishing their own
  2876. opinion. Now clients and caches download only one networkstatus
  2877. document to bootstrap, rather than downloading one for each
  2878. authority. Clients only download router descriptors listed in
  2879. the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
  2880. for details.
  2881. - Set up moria1, tor26, and dizum as v3 directory authorities
  2882. in addition to being v2 authorities. Also add three new ones:
  2883. ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
  2884. dannenberg (run by CCC).
  2885. - Switch to multi-level keys for directory authorities: now their
  2886. long-term identity key can be kept offline, and they periodically
  2887. generate a new signing key. Clients fetch the "key certificates"
  2888. to keep up to date on the right keys. Add a standalone tool
  2889. "tor-gencert" to generate key certificates. Implements proposal 103.
  2890. - Add a new V3AuthUseLegacyKey config option to make it easier for
  2891. v3 authorities to change their identity keys if another bug like
  2892. Debian's OpenSSL RNG flaw appears.
  2893. - Authorities and caches fetch the v2 networkstatus documents
  2894. less often, now that v3 is recommended.
  2895. o Make Tor connections stand out less on the wire:
  2896. - Use an improved TLS handshake designed by Steven Murdoch in proposal
  2897. 124, as revised in proposal 130. The new handshake is meant to
  2898. be harder for censors to fingerprint, and it adds the ability
  2899. to detect certain kinds of man-in-the-middle traffic analysis
  2900. attacks. The new handshake format includes version negotiation for
  2901. OR connections as described in proposal 105, which will allow us
  2902. to improve Tor's link protocol more safely in the future.
  2903. - Enable encrypted directory connections by default for non-relays,
  2904. so censor tools that block Tor directory connections based on their
  2905. plaintext patterns will no longer work. This means Tor works in
  2906. certain censored countries by default again.
  2907. - Stop including recognizeable strings in the commonname part of
  2908. Tor's x509 certificates.
  2909. o Implement bridge relays:
  2910. - Bridge relays (or "bridges" for short) are Tor relays that aren't
  2911. listed in the main Tor directory. Since there is no complete public
  2912. list of them, even an ISP that is filtering connections to all the
  2913. known Tor relays probably won't be able to block all the bridges.
  2914. See doc/design-paper/blocking.pdf and proposal 125 for details.
  2915. - New config option BridgeRelay that specifies you want to be a
  2916. bridge relay rather than a normal relay. When BridgeRelay is set
  2917. to 1, then a) you cache dir info even if your DirPort ins't on,
  2918. and b) the default for PublishServerDescriptor is now "bridge"
  2919. rather than "v2,v3".
  2920. - New config option "UseBridges 1" for clients that want to use bridge
  2921. relays instead of ordinary entry guards. Clients then specify
  2922. bridge relays by adding "Bridge" lines to their config file. Users
  2923. can learn about a bridge relay either manually through word of
  2924. mouth, or by one of our rate-limited mechanisms for giving out
  2925. bridge addresses without letting an attacker easily enumerate them
  2926. all. See https://www.torproject.org/bridges for details.
  2927. - Bridge relays behave like clients with respect to time intervals
  2928. for downloading new v3 consensus documents -- otherwise they
  2929. stand out. Bridge users now wait until the end of the interval,
  2930. so their bridge relay will be sure to have a new consensus document.
  2931. o Implement bridge directory authorities:
  2932. - Bridge authorities are like normal directory authorities, except
  2933. they don't serve a list of known bridges. Therefore users that know
  2934. a bridge's fingerprint can fetch a relay descriptor for that bridge,
  2935. including fetching updates e.g. if the bridge changes IP address,
  2936. yet an attacker can't just fetch a list of all the bridges.
  2937. - Set up Tonga as the default bridge directory authority.
  2938. - Bridge authorities refuse to serve bridge descriptors or other
  2939. bridge information over unencrypted connections (that is, when
  2940. responding to direct DirPort requests rather than begin_dir cells.)
  2941. - Bridge directory authorities do reachability testing on the
  2942. bridges they know. They provide router status summaries to the
  2943. controller via "getinfo ns/purpose/bridge", and also dump summaries
  2944. to a file periodically, so we can keep internal stats about which
  2945. bridges are functioning.
  2946. - If bridge users set the UpdateBridgesFromAuthority config option,
  2947. but the digest they ask for is a 404 on the bridge authority,
  2948. they fall back to contacting the bridge directly.
  2949. - Bridges always use begin_dir to publish their server descriptor to
  2950. the bridge authority using an anonymous encrypted tunnel.
  2951. - Early work on a "bridge community" design: if bridge authorities set
  2952. the BridgePassword config option, they will serve a snapshot of
  2953. known bridge routerstatuses from their DirPort to anybody who
  2954. knows that password. Unset by default.
  2955. - Tor now includes an IP-to-country GeoIP file, so bridge relays can
  2956. report sanitized aggregated summaries in their extra-info documents
  2957. privately to the bridge authority, listing which countries are
  2958. able to reach them. We hope this mechanism will let us learn when
  2959. certain countries start trying to block bridges.
  2960. - Bridge authorities write bridge descriptors to disk, so they can
  2961. reload them after a reboot. They can also export the descriptors
  2962. to other programs, so we can distribute them to blocked users via
  2963. the BridgeDB interface, e.g. via https://bridges.torproject.org/
  2964. and bridges@torproject.org.
  2965. o Tor can be a DNS proxy:
  2966. - The new client-side DNS proxy feature replaces the need for
  2967. dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
  2968. for DNS requests on port 9999, use the Tor network to resolve them
  2969. anonymously, and send the reply back like a regular DNS server.
  2970. The code still only implements a subset of DNS.
  2971. - Add a new AutomapHostsOnResolve option: when it is enabled, any
  2972. resolve request for hosts matching a given pattern causes Tor to
  2973. generate an internal virtual address mapping for that host. This
  2974. allows DNSPort to work sensibly with hidden service users. By
  2975. default, .exit and .onion addresses are remapped; the list of
  2976. patterns can be reconfigured with AutomapHostsSuffixes.
  2977. - Add an "-F" option to tor-resolve to force a resolve for a .onion
  2978. address. Thanks to the AutomapHostsOnResolve option, this is no
  2979. longer a completely silly thing to do.
  2980. o Major features (relay usability):
  2981. - New config options RelayBandwidthRate and RelayBandwidthBurst:
  2982. a separate set of token buckets for relayed traffic. Right now
  2983. relayed traffic is defined as answers to directory requests, and
  2984. OR connections that don't have any local circuits on them. See
  2985. proposal 111 for details.
  2986. - Create listener connections before we setuid to the configured
  2987. User and Group. Now non-Windows users can choose port values
  2988. under 1024, start Tor as root, and have Tor bind those ports
  2989. before it changes to another UID. (Windows users could already
  2990. pick these ports.)
  2991. - Added a new ConstrainedSockets config option to set SO_SNDBUF and
  2992. SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
  2993. on "vserver" accounts. Patch from coderman.
  2994. o Major features (directory authorities):
  2995. - Directory authorities track weighted fractional uptime and weighted
  2996. mean-time-between failures for relays. WFU is suitable for deciding
  2997. whether a node is "usually up", while MTBF is suitable for deciding
  2998. whether a node is "likely to stay up." We need both, because
  2999. "usually up" is a good requirement for guards, while "likely to
  3000. stay up" is a good requirement for long-lived connections.
  3001. - Directory authorities use a new formula for selecting which relays
  3002. to advertise as Guards: they must be in the top 7/8 in terms of
  3003. how long we have known about them, and above the median of those
  3004. nodes in terms of weighted fractional uptime.
  3005. - Directory authorities use a new formula for selecting which relays
  3006. to advertise as Stable: when we have 4 or more days of data, use
  3007. median measured MTBF rather than median declared uptime. Implements
  3008. proposal 108.
  3009. - Directory authorities accept and serve "extra info" documents for
  3010. routers. Routers now publish their bandwidth-history lines in the
  3011. extra-info docs rather than the main descriptor. This step saves
  3012. 60% (!) on compressed router descriptor downloads. Servers upload
  3013. extra-info docs to any authority that accepts them; directory
  3014. authorities now allow multiple router descriptors and/or extra
  3015. info documents to be uploaded in a single go. Authorities, and
  3016. caches that have been configured to download extra-info documents,
  3017. download them as needed. Implements proposal 104.
  3018. - Authorities now list relays who have the same nickname as
  3019. a different named relay, but list them with a new flag:
  3020. "Unnamed". Now we can make use of relays that happen to pick the
  3021. same nickname as a server that registered two years ago and then
  3022. disappeared. Implements proposal 122.
  3023. - Store routers in a file called cached-descriptors instead of in
  3024. cached-routers. Initialize cached-descriptors from cached-routers
  3025. if the old format is around. The new format allows us to store
  3026. annotations along with descriptors, to record the time we received
  3027. each descriptor, its source, and its purpose: currently one of
  3028. general, controller, or bridge.
  3029. o Major features (other):
  3030. - New config options WarnPlaintextPorts and RejectPlaintextPorts so
  3031. Tor can warn and/or refuse connections to ports commonly used with
  3032. vulnerable-plaintext protocols. Currently we warn on ports 23,
  3033. 109, 110, and 143, but we don't reject any. Based on proposal 129
  3034. by Kevin Bauer and Damon McCoy.
  3035. - Integrate Karsten Loesing's Google Summer of Code project to publish
  3036. hidden service descriptors on a set of redundant relays that are a
  3037. function of the hidden service address. Now we don't have to rely
  3038. on three central hidden service authorities for publishing and
  3039. fetching every hidden service descriptor. Implements proposal 114.
  3040. - Allow tunnelled directory connections to ask for an encrypted
  3041. "begin_dir" connection or an anonymized "uses a full Tor circuit"
  3042. connection independently. Now we can make anonymized begin_dir
  3043. connections for (e.g.) more secure hidden service posting and
  3044. fetching.
  3045. o Major bugfixes (crashes and assert failures):
  3046. - Stop imposing an arbitrary maximum on the number of file descriptors
  3047. used for busy servers. Bug reported by Olaf Selke; patch from
  3048. Sebastian Hahn.
  3049. - Avoid possible failures when generating a directory with routers
  3050. with over-long versions strings, or too many flags set.
  3051. - Fix a rare assert error when we're closing one of our threads:
  3052. use a mutex to protect the list of logs, so we never write to the
  3053. list as it's being freed. Fixes the very rare bug 575, which is
  3054. kind of the revenge of bug 222.
  3055. - Avoid segfault in the case where a badly behaved v2 versioning
  3056. directory sends a signed networkstatus with missing client-versions.
  3057. - When we hit an EOF on a log (probably because we're shutting down),
  3058. don't try to remove the log from the list: just mark it as
  3059. unusable. (Bulletproofs against bug 222.)
  3060. o Major bugfixes (code security fixes):
  3061. - Detect size overflow in zlib code. Reported by Justin Ferguson and
  3062. Dan Kaminsky.
  3063. - Rewrite directory tokenization code to never run off the end of
  3064. a string. Fixes bug 455. Patch from croup.
  3065. - Be more paranoid about overwriting sensitive memory on free(),
  3066. as a defensive programming tactic to ensure forward secrecy.
  3067. o Major bugfixes (anonymity fixes):
  3068. - Reject requests for reverse-dns lookup of names that are in
  3069. a private address space. Patch from lodger.
  3070. - Never report that we've used more bandwidth than we're willing to
  3071. relay: it leaks how much non-relay traffic we're using. Resolves
  3072. bug 516.
  3073. - As a client, do not believe any server that tells us that an
  3074. address maps to an internal address space.
  3075. - Warn about unsafe ControlPort configurations.
  3076. - Directory authorities now call routers Fast if their bandwidth is
  3077. at least 100KB/s, and consider their bandwidth adequate to be a
  3078. Guard if it is at least 250KB/s, no matter the medians. This fix
  3079. complements proposal 107.
  3080. - Directory authorities now never mark more than 2 servers per IP as
  3081. Valid and Running (or 5 on addresses shared by authorities).
  3082. Implements proposal 109, by Kevin Bauer and Damon McCoy.
  3083. - If we're a relay, avoid picking ourselves as an introduction point,
  3084. a rendezvous point, or as the final hop for internal circuits. Bug
  3085. reported by taranis and lodger.
  3086. - Exit relays that are used as a client can now reach themselves
  3087. using the .exit notation, rather than just launching an infinite
  3088. pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
  3089. - Fix a bug where, when we were choosing the 'end stream reason' to
  3090. put in our relay end cell that we send to the exit relay, Tor
  3091. clients on Windows were sometimes sending the wrong 'reason'. The
  3092. anonymity problem is that exit relays may be able to guess whether
  3093. the client is running Windows, thus helping partition the anonymity
  3094. set. Down the road we should stop sending reasons to exit relays,
  3095. or otherwise prevent future versions of this bug.
  3096. - Only update guard status (usable / not usable) once we have
  3097. enough directory information. This was causing us to discard all our
  3098. guards on startup if we hadn't been running for a few weeks. Fixes
  3099. bug 448.
  3100. - When our directory information has been expired for a while, stop
  3101. being willing to build circuits using it. Fixes bug 401.
  3102. o Major bugfixes (peace of mind for relay operators)
  3103. - Non-exit relays no longer answer "resolve" relay cells, so they
  3104. can't be induced to do arbitrary DNS requests. (Tor clients already
  3105. avoid using non-exit relays for resolve cells, but now servers
  3106. enforce this too.) Fixes bug 619. Patch from lodger.
  3107. - When we setconf ClientOnly to 1, close any current OR and Dir
  3108. listeners. Reported by mwenge.
  3109. o Major bugfixes (other):
  3110. - If we only ever used Tor for hidden service lookups or posts, we
  3111. would stop building circuits and start refusing connections after
  3112. 24 hours, since we falsely believed that Tor was dormant. Reported
  3113. by nwf.
  3114. - Add a new __HashedControlSessionPassword option for controllers
  3115. to use for one-off session password hashes that shouldn't get
  3116. saved to disk by SAVECONF --- Vidalia users were accumulating a
  3117. pile of HashedControlPassword lines in their torrc files, one for
  3118. each time they had restarted Tor and then clicked Save. Make Tor
  3119. automatically convert "HashedControlPassword" to this new option but
  3120. only when it's given on the command line. Partial fix for bug 586.
  3121. - Patch from "Andrew S. Lists" to catch when we contact a directory
  3122. mirror at IP address X and he says we look like we're coming from
  3123. IP address X. Otherwise this would screw up our address detection.
  3124. - Reject uploaded descriptors and extrainfo documents if they're
  3125. huge. Otherwise we'll cache them all over the network and it'll
  3126. clog everything up. Suggested by Aljosha Judmayer.
  3127. - When a hidden service was trying to establish an introduction point,
  3128. and Tor *did* manage to reuse one of the preemptively built
  3129. circuits, it didn't correctly remember which one it used,
  3130. so it asked for another one soon after, until there were no
  3131. more preemptive circuits, at which point it launched one from
  3132. scratch. Bugfix on 0.0.9.x.
  3133. o Rate limiting and load balancing improvements:
  3134. - When we add data to a write buffer in response to the data on that
  3135. write buffer getting low because of a flush, do not consider the
  3136. newly added data as a candidate for immediate flushing, but rather
  3137. make it wait until the next round of writing. Otherwise, we flush
  3138. and refill recursively, and a single greedy TLS connection can
  3139. eat all of our bandwidth.
  3140. - When counting the number of bytes written on a TLS connection,
  3141. look at the BIO actually used for writing to the network, not
  3142. at the BIO used (sometimes) to buffer data for the network.
  3143. Looking at different BIOs could result in write counts on the
  3144. order of ULONG_MAX. Fixes bug 614.
  3145. - If we change our MaxAdvertisedBandwidth and then reload torrc,
  3146. Tor won't realize it should publish a new relay descriptor. Fixes
  3147. bug 688, reported by mfr.
  3148. - Avoid using too little bandwidth when our clock skips a few seconds.
  3149. - Choose which bridge to use proportional to its advertised bandwidth,
  3150. rather than uniformly at random. This should speed up Tor for
  3151. bridge users. Also do this for people who set StrictEntryNodes.
  3152. o Bootstrapping faster and building circuits more intelligently:
  3153. - Fix bug 660 that was preventing us from knowing that we should
  3154. preemptively build circuits to handle expected directory requests.
  3155. - When we're checking if we have enough dir info for each relay
  3156. to begin establishing circuits, make sure that we actually have
  3157. the descriptor listed in the consensus, not just any descriptor.
  3158. - Correctly notify one-hop connections when a circuit build has
  3159. failed. Possible fix for bug 669. Found by lodger.
  3160. - Clients now hold circuitless TLS connections open for 1.5 times
  3161. MaxCircuitDirtiness (15 minutes), since it is likely that they'll
  3162. rebuild a new circuit over them within that timeframe. Previously,
  3163. they held them open only for KeepalivePeriod (5 minutes).
  3164. o Performance improvements (memory):
  3165. - Add OpenBSD malloc code from "phk" as an optional malloc
  3166. replacement on Linux: some glibc libraries do very poorly with
  3167. Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
  3168. ./configure to get the replacement malloc code.
  3169. - Switch our old ring buffer implementation for one more like that
  3170. used by free Unix kernels. The wasted space in a buffer with 1mb
  3171. of data will now be more like 8k than 1mb. The new implementation
  3172. also avoids realloc();realloc(); patterns that can contribute to
  3173. memory fragmentation.
  3174. - Change the way that Tor buffers data that it is waiting to write.
  3175. Instead of queueing data cells in an enormous ring buffer for each
  3176. client->OR or OR->OR connection, we now queue cells on a separate
  3177. queue for each circuit. This lets us use less slack memory, and
  3178. will eventually let us be smarter about prioritizing different kinds
  3179. of traffic.
  3180. - Reference-count and share copies of address policy entries; only 5%
  3181. of them were actually distinct.
  3182. - Tune parameters for cell pool allocation to minimize amount of
  3183. RAM overhead used.
  3184. - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
  3185. for every single inactive connection_t. Free items from the
  3186. 4k/16k-buffer free lists when they haven't been used for a while.
  3187. - Make memory debugging information describe more about history
  3188. of cell allocation, so we can help reduce our memory use.
  3189. - Be even more aggressive about releasing RAM from small
  3190. empty buffers. Thanks to our free-list code, this shouldn't be too
  3191. performance-intensive.
  3192. - Log malloc statistics from mallinfo() on platforms where it exists.
  3193. - Use memory pools to allocate cells with better speed and memory
  3194. efficiency, especially on platforms where malloc() is inefficient.
  3195. - Add a --with-tcmalloc option to the configure script to link
  3196. against tcmalloc (if present). Does not yet search for non-system
  3197. include paths.
  3198. o Performance improvements (socket management):
  3199. - Count the number of open sockets separately from the number of
  3200. active connection_t objects. This will let us avoid underusing
  3201. our allocated connection limit.
  3202. - We no longer use socket pairs to link an edge connection to an
  3203. anonymous directory connection or a DirPort test connection.
  3204. Instead, we track the link internally and transfer the data
  3205. in-process. This saves two sockets per "linked" connection (at the
  3206. client and at the server), and avoids the nasty Windows socketpair()
  3207. workaround.
  3208. - We were leaking a file descriptor if Tor started with a zero-length
  3209. cached-descriptors file. Patch by "freddy77".
  3210. o Performance improvements (CPU use):
  3211. - Never walk through the list of logs if we know that no log target
  3212. is interested in a given message.
  3213. - Call routerlist_remove_old_routers() much less often. This should
  3214. speed startup, especially on directory caches.
  3215. - Base64 decoding was actually showing up on our profile when parsing
  3216. the initial descriptor file; switch to an in-process all-at-once
  3217. implementation that's about 3.5x times faster than calling out to
  3218. OpenSSL.
  3219. - Use a slightly simpler string hashing algorithm (copying Python's
  3220. instead of Java's) and optimize our digest hashing algorithm to take
  3221. advantage of 64-bit platforms and to remove some possibly-costly
  3222. voodoo.
  3223. - When implementing AES counter mode, update only the portions of the
  3224. counter buffer that need to change, and don't keep separate
  3225. network-order and host-order counters on big-endian hosts (where
  3226. they are the same).
  3227. - Add an in-place version of aes_crypt() so that we can avoid doing a
  3228. needless memcpy() call on each cell payload.
  3229. - Use Critical Sections rather than Mutexes for synchronizing threads
  3230. on win32; Mutexes are heavier-weight, and designed for synchronizing
  3231. between processes.
  3232. o Performance improvements (bandwidth use):
  3233. - Don't try to launch new descriptor downloads quite so often when we
  3234. already have enough directory information to build circuits.
  3235. - Version 1 directories are no longer generated in full. Instead,
  3236. authorities generate and serve "stub" v1 directories that list
  3237. no servers. This will stop Tor versions 0.1.0.x and earlier from
  3238. working, but (for security reasons) nobody should be running those
  3239. versions anyway.
  3240. - Avoid going directly to the directory authorities even if you're a
  3241. relay, if you haven't found yourself reachable yet or if you've
  3242. decided not to advertise your dirport yet. Addresses bug 556.
  3243. - If we've gone 12 hours since our last bandwidth check, and we
  3244. estimate we have less than 50KB bandwidth capacity but we could
  3245. handle more, do another bandwidth test.
  3246. - Support "If-Modified-Since" when answering HTTP requests for
  3247. directories, running-routers documents, and v2 and v3 networkstatus
  3248. documents. (There's no need to support it for router descriptors,
  3249. since those are downloaded by descriptor digest.)
  3250. - Stop fetching directory info so aggressively if your DirPort is
  3251. on but your ORPort is off; stop fetching v2 dir info entirely.
  3252. You can override these choices with the new FetchDirInfoEarly
  3253. config option.
  3254. o Changed config option behavior (features):
  3255. - Configuration files now accept C-style strings as values. This
  3256. helps encode characters not allowed in the current configuration
  3257. file format, such as newline or #. Addresses bug 557.
  3258. - Add hidden services and DNSPorts to the list of things that make
  3259. Tor accept that it has running ports. Change starting Tor with no
  3260. ports from a fatal error to a warning; we might change it back if
  3261. this turns out to confuse anybody. Fixes bug 579.
  3262. - Make PublishServerDescriptor default to 1, so the default doesn't
  3263. have to change as we invent new directory protocol versions.
  3264. - Allow people to say PreferTunnelledDirConns rather than
  3265. PreferTunneledDirConns, for those alternate-spellers out there.
  3266. - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
  3267. accommodate the growing number of servers that use the default
  3268. and are reaching it.
  3269. - Make it possible to enable HashedControlPassword and
  3270. CookieAuthentication at the same time.
  3271. - When a TrackHostExits-chosen exit fails too many times in a row,
  3272. stop using it. Fixes bug 437.
  3273. o Changed config option behavior (bugfixes):
  3274. - Do not read the configuration file when we've only been told to
  3275. generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
  3276. based on patch from Sebastian Hahn.
  3277. - Actually validate the options passed to AuthDirReject,
  3278. AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
  3279. - Make "ClientOnly 1" config option disable directory ports too.
  3280. - Don't stop fetching descriptors when FetchUselessDescriptors is
  3281. set, even if we stop asking for circuits. Bug reported by tup
  3282. and ioerror.
  3283. - Servers used to decline to publish their DirPort if their
  3284. BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
  3285. they look only at BandwidthRate and RelayBandwidthRate.
  3286. - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
  3287. minus 1 byte: the actual maximum declared bandwidth.
  3288. - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
  3289. - Make the NodeFamilies config option work. (Reported by
  3290. lodger -- it has never actually worked, even though we added it
  3291. in Oct 2004.)
  3292. - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
  3293. now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
  3294. o New config options:
  3295. - New configuration options AuthDirMaxServersPerAddr and
  3296. AuthDirMaxServersperAuthAddr to override default maximum number
  3297. of servers allowed on a single IP address. This is important for
  3298. running a test network on a single host.
  3299. - Three new config options (AlternateDirAuthority,
  3300. AlternateBridgeAuthority, and AlternateHSAuthority) that let the
  3301. user selectively replace the default directory authorities by type,
  3302. rather than the all-or-nothing replacement that DirServer offers.
  3303. - New config options AuthDirBadDir and AuthDirListBadDirs for
  3304. authorities to mark certain relays as "bad directories" in the
  3305. networkstatus documents. Also supports the "!baddir" directive in
  3306. the approved-routers file.
  3307. - New config option V2AuthoritativeDirectory that all v2 directory
  3308. authorities must set. This lets v3 authorities choose not to serve
  3309. v2 directory information.
  3310. o Minor features (other):
  3311. - When we're not serving v2 directory information, there is no reason
  3312. to actually keep any around. Remove the obsolete files and directory
  3313. on startup if they are very old and we aren't going to serve them.
  3314. - When we negotiate a v2 link-layer connection (not yet implemented),
  3315. accept RELAY_EARLY cells and turn them into RELAY cells if we've
  3316. negotiated a v1 connection for their next step. Initial steps for
  3317. proposal 110.
  3318. - When we have no consensus, check FallbackNetworkstatusFile (defaults
  3319. to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
  3320. we can start out knowing some directory caches. We don't ship with
  3321. a fallback consensus by default though, because it was making
  3322. bootstrapping take too long while we tried many down relays.
  3323. - Authorities send back an X-Descriptor-Not-New header in response to
  3324. an accepted-but-discarded descriptor upload. Partially implements
  3325. fix for bug 535.
  3326. - If we find a cached-routers file that's been sitting around for more
  3327. than 28 days unmodified, then most likely it's a leftover from
  3328. when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
  3329. routers anyway.
  3330. - When we (as a cache) download a descriptor because it was listed
  3331. in a consensus, remember when the consensus was supposed to expire,
  3332. and don't expire the descriptor until then.
  3333. - Optionally (if built with -DEXPORTMALLINFO) export the output
  3334. of mallinfo via http, as tor/mallinfo.txt. Only accessible
  3335. from localhost.
  3336. - Tag every guard node in our state file with the version that
  3337. we believe added it, or with our own version if we add it. This way,
  3338. if a user temporarily runs an old version of Tor and then switches
  3339. back to a new one, she doesn't automatically lose her guards.
  3340. - When somebody requests a list of statuses or servers, and we have
  3341. none of those, return a 404 rather than an empty 200.
  3342. - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
  3343. from croup.)
  3344. - Add an HSAuthorityRecordStats option that hidden service authorities
  3345. can use to track statistics of overall hidden service usage without
  3346. logging information that would be as useful to an attacker.
  3347. - Allow multiple HiddenServicePort directives with the same virtual
  3348. port; when they occur, the user is sent round-robin to one
  3349. of the target ports chosen at random. Partially fixes bug 393 by
  3350. adding limited ad-hoc round-robining.
  3351. - Revamp file-writing logic so we don't need to have the entire
  3352. contents of a file in memory at once before we write to disk. Tor,
  3353. meet stdio.
  3354. o Minor bugfixes (other):
  3355. - Alter the code that tries to recover from unhandled write
  3356. errors, to not try to flush onto a socket that's given us
  3357. unhandled errors.
  3358. - Directory mirrors no longer include a guess at the client's IP
  3359. address if the connection appears to be coming from the same /24
  3360. network; it was producing too many wrong guesses.
  3361. - If we're trying to flush the last bytes on a connection (for
  3362. example, when answering a directory request), reset the
  3363. time-to-give-up timeout every time we manage to write something
  3364. on the socket.
  3365. - Reject router descriptors with out-of-range bandwidthcapacity or
  3366. bandwidthburst values.
  3367. - If we can't expand our list of entry guards (e.g. because we're
  3368. using bridges or we have StrictEntryNodes set), don't mark relays
  3369. down when they fail a directory request. Otherwise we're too quick
  3370. to mark all our entry points down.
  3371. - Authorities no longer send back "400 you're unreachable please fix
  3372. it" errors to Tor servers that aren't online all the time. We're
  3373. supposed to tolerate these servers now.
  3374. - Let directory authorities startup even when they can't generate
  3375. a descriptor immediately, e.g. because they don't know their
  3376. address.
  3377. - Correctly enforce that elements of directory objects do not appear
  3378. more often than they are allowed to appear.
  3379. - Stop allowing hibernating servers to be "stable" or "fast".
  3380. - On Windows, we were preventing other processes from reading
  3381. cached-routers while Tor was running. (Reported by janbar)
  3382. - Check return values from pthread_mutex functions.
  3383. - When opening /dev/null in finish_daemonize(), do not pass the
  3384. O_CREAT flag. Fortify was complaining, and correctly so. Fixes
  3385. bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
  3386. o Controller features:
  3387. - The GETCONF command now escapes and quotes configuration values
  3388. that don't otherwise fit into the torrc file.
  3389. - The SETCONF command now handles quoted values correctly.
  3390. - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
  3391. ask about source, timestamp of arrival, purpose, etc. We need
  3392. something like this to help Vidalia not do GeoIP lookups on bridge
  3393. addresses.
  3394. - Allow multiple HashedControlPassword config lines, to support
  3395. multiple controller passwords.
  3396. - Accept LF instead of CRLF on controller, since some software has a
  3397. hard time generating real Internet newlines.
  3398. - Add GETINFO values for the server status events
  3399. "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
  3400. Robert Hogan.
  3401. - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
  3402. GETINFO for Torstat to use until it can switch to using extrainfos.
  3403. - New config option CookieAuthFile to choose a new location for the
  3404. cookie authentication file, and config option
  3405. CookieAuthFileGroupReadable to make it group-readable.
  3406. - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
  3407. match requests to applications. Patch from Robert Hogan.
  3408. - Add a RESOLVE command to launch hostname lookups. Original patch
  3409. from Robert Hogan.
  3410. - Add GETINFO status/enough-dir-info to let controllers tell whether
  3411. Tor has downloaded sufficient directory information. Patch from Tup.
  3412. - You can now use the ControlSocket option to tell Tor to listen for
  3413. controller connections on Unix domain sockets on systems that
  3414. support them. Patch from Peter Palfrader.
  3415. - New "GETINFO address-mappings/*" command to get address mappings
  3416. with expiry information. "addr-mappings/*" is now deprecated.
  3417. Patch from Tup.
  3418. - Add a new config option __DisablePredictedCircuits designed for
  3419. use by the controller, when we don't want Tor to build any circuits
  3420. preemptively.
  3421. - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
  3422. so we can exit from the middle of the circuit.
  3423. - Implement "getinfo status/circuit-established".
  3424. - Implement "getinfo status/version/..." so a controller can tell
  3425. whether the current version is recommended, and whether any versions
  3426. are good, and how many authorities agree. Patch from "shibz".
  3427. - Controllers should now specify cache=no or cache=yes when using
  3428. the +POSTDESCRIPTOR command.
  3429. - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
  3430. Robert Hogan. Fixes the first part of bug 681.
  3431. - When reporting clock skew, and we know that the clock is _at least
  3432. as skewed_ as some value, but we don't know the actual value,
  3433. report the value as a "minimum skew."
  3434. o Controller bugfixes:
  3435. - Generate "STATUS_SERVER" events rather than misspelled
  3436. "STATUS_SEVER" events. Caught by mwenge.
  3437. - Reject controller commands over 1MB in length, so rogue
  3438. processes can't run us out of memory.
  3439. - Change the behavior of "getinfo status/good-server-descriptor"
  3440. so it doesn't return failure when any authority disappears.
  3441. - Send NAMESERVER_STATUS messages for a single failed nameserver
  3442. correctly.
  3443. - When the DANGEROUS_VERSION controller status event told us we're
  3444. running an obsolete version, it used the string "OLD" to describe
  3445. it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
  3446. "OBSOLETE" in both cases.
  3447. - Respond to INT and TERM SIGNAL commands before we execute the
  3448. signal, in case the signal shuts us down. We had a patch in
  3449. 0.1.2.1-alpha that tried to do this by queueing the response on
  3450. the connection's buffer before shutting down, but that really
  3451. isn't the same thing at all. Bug located by Matt Edman.
  3452. - Provide DNS expiry times in GMT, not in local time. For backward
  3453. compatibility, ADDRMAP events only provide GMT expiry in an extended
  3454. field. "GETINFO address-mappings" always does the right thing.
  3455. - Use CRLF line endings properly in NS events.
  3456. - Make 'getinfo fingerprint' return a 551 error if we're not a
  3457. server, so we match what the control spec claims we do. Reported
  3458. by daejees.
  3459. - Fix a typo in an error message when extendcircuit fails that
  3460. caused us to not follow the \r\n-based delimiter protocol. Reported
  3461. by daejees.
  3462. - When tunneling an encrypted directory connection, and its first
  3463. circuit fails, do not leave it unattached and ask the controller
  3464. to deal. Fixes the second part of bug 681.
  3465. - Treat some 403 responses from directory servers as INFO rather than
  3466. WARN-severity events.
  3467. o Portability / building / compiling:
  3468. - When building with --enable-gcc-warnings, check for whether Apple's
  3469. warning "-Wshorten-64-to-32" is available.
  3470. - Support compilation to target iPhone; patch from cjacker huang.
  3471. To build for iPhone, pass the --enable-iphone option to configure.
  3472. - Port Tor to build and run correctly on Windows CE systems, using
  3473. the wcecompat library. Contributed by Valerio Lupi.
  3474. - Detect non-ASCII platforms (if any still exist) and refuse to
  3475. build there: some of our code assumes that 'A' is 65 and so on.
  3476. - Clear up some MIPSPro compiler warnings.
  3477. - Make autoconf search for libevent, openssl, and zlib consistently.
  3478. - Update deprecated macros in configure.in.
  3479. - When warning about missing headers, tell the user to let us
  3480. know if the compile succeeds anyway, so we can downgrade the
  3481. warning.
  3482. - Include the current subversion revision as part of the version
  3483. string: either fetch it directly if we're in an SVN checkout, do
  3484. some magic to guess it if we're in an SVK checkout, or use
  3485. the last-detected version if we're building from a .tar.gz.
  3486. Use this version consistently in log messages.
  3487. - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
  3488. - Read resolv.conf files correctly on platforms where read() returns
  3489. partial results on small file reads.
  3490. - Build without verbose warnings even on gcc 4.2 and 4.3.
  3491. - On Windows, correctly detect errors when listing the contents of
  3492. a directory. Fix from lodger.
  3493. - Run 'make test' as part of 'make dist', so we stop releasing so
  3494. many development snapshots that fail their unit tests.
  3495. - Add support to detect Libevent versions in the 1.4.x series
  3496. on mingw.
  3497. - Add command-line arguments to unit-test executable so that we can
  3498. invoke any chosen test from the command line rather than having
  3499. to run the whole test suite at once; and so that we can turn on
  3500. logging for the unit tests.
  3501. - Do not automatically run configure from autogen.sh. This
  3502. non-standard behavior tended to annoy people who have built other
  3503. programs.
  3504. - Fix a macro/CPP interaction that was confusing some compilers:
  3505. some GCCs don't like #if/#endif pairs inside macro arguments.
  3506. Fixes bug 707.
  3507. - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
  3508. Fixes bug 704; fix from Steven Murdoch.
  3509. - Correctly detect transparent proxy support on Linux hosts that
  3510. require in.h to be included before netfilter_ipv4.h. Patch
  3511. from coderman.
  3512. o Logging improvements:
  3513. - When we haven't had any application requests lately, don't bother
  3514. logging that we have expired a bunch of descriptors.
  3515. - When attempting to open a logfile fails, tell us why.
  3516. - Only log guard node status when guard node status has changed.
  3517. - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
  3518. make "INFO" 75% less verbose.
  3519. - When SafeLogging is disabled, log addresses along with all TLS
  3520. errors.
  3521. - Report TLS "zero return" case as a "clean close" and "IO error"
  3522. as a "close". Stop calling closes "unexpected closes": existing
  3523. Tors don't use SSL_close(), so having a connection close without
  3524. the TLS shutdown handshake is hardly unexpected.
  3525. - When we receive a consensus from the future, warn about skew.
  3526. - Make "not enough dir info yet" warnings describe *why* Tor feels
  3527. it doesn't have enough directory info yet.
  3528. - On the USR1 signal, when dmalloc is in use, log the top 10 memory
  3529. consumers. (We already do this on HUP.)
  3530. - Give more descriptive well-formedness errors for out-of-range
  3531. hidden service descriptor/protocol versions.
  3532. - Stop recommending that every server operator send mail to tor-ops.
  3533. Resolves bug 597. Bugfix on 0.1.2.x.
  3534. - Improve skew reporting: try to give the user a better log message
  3535. about how skewed they are, and how much this matters.
  3536. - New --quiet command-line option to suppress the default console log.
  3537. Good in combination with --hash-password.
  3538. - Don't complain that "your server has not managed to confirm that its
  3539. ports are reachable" if we haven't been able to build any circuits
  3540. yet.
  3541. - Detect the reason for failing to mmap a descriptor file we just
  3542. wrote, and give a more useful log message. Fixes bug 533.
  3543. - Always prepend "Bug: " to any log message about a bug.
  3544. - When dumping memory usage, list bytes used in buffer memory
  3545. free-lists.
  3546. - When running with dmalloc, dump more stats on hup and on exit.
  3547. - Put a platform string (e.g. "Linux i686") in the startup log
  3548. message, so when people paste just their logs, we know if it's
  3549. OpenBSD or Windows or what.
  3550. - When logging memory usage, break down memory used in buffers by
  3551. buffer type.
  3552. - When we are reporting the DirServer line we just parsed, we were
  3553. logging the second stanza of the key fingerprint, not the first.
  3554. - Even though Windows is equally happy with / and \ as path separators,
  3555. try to use \ consistently on Windows and / consistently on Unix: it
  3556. makes the log messages nicer.
  3557. - On OSX, stop warning the user that kqueue support in libevent is
  3558. "experimental", since it seems to have worked fine for ages.
  3559. o Contributed scripts and tools:
  3560. - Update linux-tor-prio.sh script to allow QoS based on the uid of
  3561. the Tor process. Patch from Marco Bonetti with tweaks from Mike
  3562. Perry.
  3563. - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
  3564. Unix users an easy way to script their Tor process (e.g. by
  3565. adjusting bandwidth based on the time of the day).
  3566. - In the exitlist script, only consider the most recently published
  3567. server descriptor for each server. Also, when the user requests
  3568. a list of servers that _reject_ connections to a given address,
  3569. explicitly exclude the IPs that also have servers that accept
  3570. connections to that address. Resolves bug 405.
  3571. - Include a new contrib/tor-exit-notice.html file that exit relay
  3572. operators can put on their website to help reduce abuse queries.
  3573. o Newly deprecated features:
  3574. - The status/version/num-versioning and status/version/num-concurring
  3575. GETINFO controller options are no longer useful in the v3 directory
  3576. protocol: treat them as deprecated, and warn when they're used.
  3577. - The RedirectExits config option is now deprecated.
  3578. o Removed features:
  3579. - Drop the old code to choke directory connections when the
  3580. corresponding OR connections got full: thanks to the cell queue
  3581. feature, OR conns don't get full any more.
  3582. - Remove the old "dns worker" server DNS code: it hasn't been default
  3583. since 0.1.2.2-alpha, and all the servers are using the new
  3584. eventdns code.
  3585. - Remove the code to generate the oldest (v1) directory format.
  3586. - Remove support for the old bw_accounting file: we've been storing
  3587. bandwidth accounting information in the state file since
  3588. 0.1.2.5-alpha. This may result in bandwidth accounting errors
  3589. if you try to upgrade from 0.1.1.x or earlier, or if you try to
  3590. downgrade to 0.1.1.x or earlier.
  3591. - Drop support for OpenSSL version 0.9.6. Just about nobody was using
  3592. it, it had no AES, and it hasn't seen any security patches since
  3593. 2004.
  3594. - Stop overloading the circuit_t.onionskin field for both "onionskin
  3595. from a CREATE cell that we are waiting for a cpuworker to be
  3596. assigned" and "onionskin from an EXTEND cell that we are going to
  3597. send to an OR as soon as we are connected". Might help with bug 600.
  3598. - Remove the tor_strpartition() function: its logic was confused,
  3599. and it was only used for one thing that could be implemented far
  3600. more easily.
  3601. - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
  3602. and TorControl.py, as they use the old v0 controller protocol,
  3603. and are obsoleted by TorFlow anyway.
  3604. - Drop support for v1 rendezvous descriptors, since we never used
  3605. them anyway, and the code has probably rotted by now. Based on
  3606. patch from Karsten Loesing.
  3607. - Stop allowing address masks that do not correspond to bit prefixes.
  3608. We have warned about these for a really long time; now it's time
  3609. to reject them. (Patch from croup.)
  3610. - Remove an optimization in the AES counter-mode code that assumed
  3611. that the counter never exceeded 2^68. When the counter can be set
  3612. arbitrarily as an IV (as it is by Karsten's new hidden services
  3613. code), this assumption no longer holds.
  3614. - Disable the SETROUTERPURPOSE controller command: it is now
  3615. obsolete.
  3616. Changes in version 0.1.2.19 - 2008-01-17
  3617. Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
  3618. exit policy a little bit more conservative so it's safer to run an
  3619. exit relay on a home system, and fixes a variety of smaller issues.
  3620. o Security fixes:
  3621. - Exit policies now reject connections that are addressed to a
  3622. relay's public (external) IP address too, unless
  3623. ExitPolicyRejectPrivate is turned off. We do this because too
  3624. many relays are running nearby to services that trust them based
  3625. on network address.
  3626. o Major bugfixes:
  3627. - When the clock jumps forward a lot, do not allow the bandwidth
  3628. buckets to become negative. Fixes bug 544.
  3629. - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
  3630. on every successful resolve. Reported by Mike Perry.
  3631. - Purge old entries from the "rephist" database and the hidden
  3632. service descriptor database even when DirPort is zero.
  3633. - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
  3634. requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
  3635. crashing or mis-answering these requests.
  3636. - When we decide to send a 503 response to a request for servers, do
  3637. not then also send the server descriptors: this defeats the whole
  3638. purpose. Fixes bug 539.
  3639. o Minor bugfixes:
  3640. - Changing the ExitPolicyRejectPrivate setting should cause us to
  3641. rebuild our server descriptor.
  3642. - Fix handling of hex nicknames when answering controller requests for
  3643. networkstatus by name, or when deciding whether to warn about
  3644. unknown routers in a config option. (Patch from mwenge.)
  3645. - Fix a couple of hard-to-trigger autoconf problems that could result
  3646. in really weird results on platforms whose sys/types.h files define
  3647. nonstandard integer types.
  3648. - Don't try to create the datadir when running --verify-config or
  3649. --hash-password. Resolves bug 540.
  3650. - If we were having problems getting a particular descriptor from the
  3651. directory caches, and then we learned about a new descriptor for
  3652. that router, we weren't resetting our failure count. Reported
  3653. by lodger.
  3654. - Although we fixed bug 539 (where servers would send HTTP status 503
  3655. responses _and_ send a body too), there are still servers out there
  3656. that haven't upgraded. Therefore, make clients parse such bodies
  3657. when they receive them.
  3658. - Run correctly on systems where rlim_t is larger than unsigned long.
  3659. This includes some 64-bit systems.
  3660. - Run correctly on platforms (like some versions of OS X 10.5) where
  3661. the real limit for number of open files is OPEN_FILES, not rlim_max
  3662. from getrlimit(RLIMIT_NOFILES).
  3663. - Avoid a spurious free on base64 failure.
  3664. - Avoid segfaults on certain complex invocations of
  3665. router_get_by_hexdigest().
  3666. - Fix rare bug on REDIRECTSTREAM control command when called with no
  3667. port set: it could erroneously report an error when none had
  3668. happened.
  3669. Changes in version 0.1.2.18 - 2007-10-28
  3670. Tor 0.1.2.18 fixes many problems including crash bugs, problems with
  3671. hidden service introduction that were causing huge delays, and a big
  3672. bug that was causing some servers to disappear from the network status
  3673. lists for a few hours each day.
  3674. o Major bugfixes (crashes):
  3675. - If a connection is shut down abruptly because of something that
  3676. happened inside connection_flushed_some(), do not call
  3677. connection_finished_flushing(). Should fix bug 451:
  3678. "connection_stop_writing: Assertion conn->write_event failed"
  3679. Bugfix on 0.1.2.7-alpha.
  3680. - Fix possible segfaults in functions called from
  3681. rend_process_relay_cell().
  3682. o Major bugfixes (hidden services):
  3683. - Hidden services were choosing introduction points uniquely by
  3684. hexdigest, but when constructing the hidden service descriptor
  3685. they merely wrote the (potentially ambiguous) nickname.
  3686. - Clients now use the v2 intro format for hidden service
  3687. connections: they specify their chosen rendezvous point by identity
  3688. digest rather than by (potentially ambiguous) nickname. These
  3689. changes could speed up hidden service connections dramatically.
  3690. o Major bugfixes (other):
  3691. - Stop publishing a new server descriptor just because we get a
  3692. HUP signal. This led (in a roundabout way) to some servers getting
  3693. dropped from the networkstatus lists for a few hours each day.
  3694. - When looking for a circuit to cannibalize, consider family as well
  3695. as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
  3696. circuit cannibalization).
  3697. - When a router wasn't listed in a new networkstatus, we were leaving
  3698. the flags for that router alone -- meaning it remained Named,
  3699. Running, etc -- even though absence from the networkstatus means
  3700. that it shouldn't be considered to exist at all anymore. Now we
  3701. clear all the flags for routers that fall out of the networkstatus
  3702. consensus. Fixes bug 529.
  3703. o Minor bugfixes:
  3704. - Don't try to access (or alter) the state file when running
  3705. --list-fingerprint or --verify-config or --hash-password. Resolves
  3706. bug 499.
  3707. - When generating information telling us how to extend to a given
  3708. router, do not try to include the nickname if it is
  3709. absent. Resolves bug 467.
  3710. - Fix a user-triggerable segfault in expand_filename(). (There isn't
  3711. a way to trigger this remotely.)
  3712. - When sending a status event to the controller telling it that an
  3713. OR address is reachable, set the port correctly. (Previously we
  3714. were reporting the dir port.)
  3715. - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
  3716. command. Bugfix on 0.1.2.17.
  3717. - When loading bandwidth history, do not believe any information in
  3718. the future. Fixes bug 434.
  3719. - When loading entry guard information, do not believe any information
  3720. in the future.
  3721. - When we have our clock set far in the future and generate an
  3722. onion key, then re-set our clock to be correct, we should not stop
  3723. the onion key from getting rotated.
  3724. - On some platforms, accept() can return a broken address. Detect
  3725. this more quietly, and deal accordingly. Fixes bug 483.
  3726. - It's not actually an error to find a non-pending entry in the DNS
  3727. cache when canceling a pending resolve. Don't log unless stuff
  3728. is fishy. Resolves bug 463.
  3729. - Don't reset trusted dir server list when we set a configuration
  3730. option. Patch from Robert Hogan.
  3731. Changes in version 0.1.2.17 - 2007-08-30
  3732. Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
  3733. X bundles. Vidalia 0.0.14 makes authentication required for the
  3734. ControlPort in the default configuration, which addresses important
  3735. security risks. Everybody who uses Vidalia (or another controller)
  3736. should upgrade.
  3737. In addition, this Tor update fixes major load balancing problems with
  3738. path selection, which should speed things up a lot once many people
  3739. have upgraded.
  3740. o Major bugfixes (security):
  3741. - We removed support for the old (v0) control protocol. It has been
  3742. deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
  3743. become more of a headache than it's worth.
  3744. o Major bugfixes (load balancing):
  3745. - When choosing nodes for non-guard positions, weight guards
  3746. proportionally less, since they already have enough load. Patch
  3747. from Mike Perry.
  3748. - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
  3749. will allow fast Tor servers to get more attention.
  3750. - When we're upgrading from an old Tor version, forget our current
  3751. guards and pick new ones according to the new weightings. These
  3752. three load balancing patches could raise effective network capacity
  3753. by a factor of four. Thanks to Mike Perry for measurements.
  3754. o Major bugfixes (stream expiration):
  3755. - Expire not-yet-successful application streams in all cases if
  3756. they've been around longer than SocksTimeout. Right now there are
  3757. some cases where the stream will live forever, demanding a new
  3758. circuit every 15 seconds. Fixes bug 454; reported by lodger.
  3759. o Minor features (controller):
  3760. - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
  3761. is valid before any authentication has been received. It tells
  3762. a controller what kind of authentication is expected, and what
  3763. protocol is spoken. Implements proposal 119.
  3764. o Minor bugfixes (performance):
  3765. - Save on most routerlist_assert_ok() calls in routerlist.c, thus
  3766. greatly speeding up loading cached-routers from disk on startup.
  3767. - Disable sentinel-based debugging for buffer code: we squashed all
  3768. the bugs that this was supposed to detect a long time ago, and now
  3769. its only effect is to change our buffer sizes from nice powers of
  3770. two (which platform mallocs tend to like) to values slightly over
  3771. powers of two (which make some platform mallocs sad).
  3772. o Minor bugfixes (misc):
  3773. - If exit bandwidth ever exceeds one third of total bandwidth, then
  3774. use the correct formula to weight exit nodes when choosing paths.
  3775. Based on patch from Mike Perry.
  3776. - Choose perfectly fairly among routers when choosing by bandwidth and
  3777. weighting by fraction of bandwidth provided by exits. Previously, we
  3778. would choose with only approximate fairness, and correct ourselves
  3779. if we ran off the end of the list.
  3780. - If we require CookieAuthentication but we fail to write the
  3781. cookie file, we would warn but not exit, and end up in a state
  3782. where no controller could authenticate. Now we exit.
  3783. - If we require CookieAuthentication, stop generating a new cookie
  3784. every time we change any piece of our config.
  3785. - Refuse to start with certain directory authority keys, and
  3786. encourage people using them to stop.
  3787. - Terminate multi-line control events properly. Original patch
  3788. from tup.
  3789. - Fix a minor memory leak when we fail to find enough suitable
  3790. servers to choose a circuit.
  3791. - Stop leaking part of the descriptor when we run into a particularly
  3792. unparseable piece of it.
  3793. Changes in version 0.1.2.16 - 2007-08-01
  3794. Tor 0.1.2.16 fixes a critical security vulnerability that allows a
  3795. remote attacker in certain situations to rewrite the user's torrc
  3796. configuration file. This can completely compromise anonymity of users
  3797. in most configurations, including those running the Vidalia bundles,
  3798. TorK, etc. Or worse.
  3799. o Major security fixes:
  3800. - Close immediately after missing authentication on control port;
  3801. do not allow multiple authentication attempts.
  3802. Changes in version 0.1.2.15 - 2007-07-17
  3803. Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
  3804. problems, fixes compilation on BSD, and fixes a variety of other
  3805. bugs. Everybody should upgrade.
  3806. o Major bugfixes (compilation):
  3807. - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
  3808. o Major bugfixes (crashes):
  3809. - Try even harder not to dereference the first character after
  3810. an mmap(). Reported by lodger.
  3811. - Fix a crash bug in directory authorities when we re-number the
  3812. routerlist while inserting a new router.
  3813. - When the cached-routers file is an even multiple of the page size,
  3814. don't run off the end and crash. (Fixes bug 455; based on idea
  3815. from croup.)
  3816. - Fix eventdns.c behavior on Solaris: It is critical to include
  3817. orconfig.h _before_ sys/types.h, so that we can get the expected
  3818. definition of _FILE_OFFSET_BITS.
  3819. o Major bugfixes (security):
  3820. - Fix a possible buffer overrun when using BSD natd support. Bug
  3821. found by croup.
  3822. - When sending destroy cells from a circuit's origin, don't include
  3823. the reason for tearing down the circuit. The spec says we didn't,
  3824. and now we actually don't. Reported by lodger.
  3825. - Keep streamids from different exits on a circuit separate. This
  3826. bug may have allowed other routers on a given circuit to inject
  3827. cells into streams. Reported by lodger; fixes bug 446.
  3828. - If there's a never-before-connected-to guard node in our list,
  3829. never choose any guards past it. This way we don't expand our
  3830. guard list unless we need to.
  3831. o Minor bugfixes (guard nodes):
  3832. - Weight guard selection by bandwidth, so that low-bandwidth nodes
  3833. don't get overused as guards.
  3834. o Minor bugfixes (directory):
  3835. - Correctly count the number of authorities that recommend each
  3836. version. Previously, we were under-counting by 1.
  3837. - Fix a potential crash bug when we load many server descriptors at
  3838. once and some of them make others of them obsolete. Fixes bug 458.
  3839. o Minor bugfixes (hidden services):
  3840. - Stop tearing down the whole circuit when the user asks for a
  3841. connection to a port that the hidden service didn't configure.
  3842. Resolves bug 444.
  3843. o Minor bugfixes (misc):
  3844. - On Windows, we were preventing other processes from reading
  3845. cached-routers while Tor was running. Reported by janbar.
  3846. - Fix a possible (but very unlikely) bug in picking routers by
  3847. bandwidth. Add a log message to confirm that it is in fact
  3848. unlikely. Patch from lodger.
  3849. - Backport a couple of memory leak fixes.
  3850. - Backport miscellaneous cosmetic bugfixes.
  3851. Changes in version 0.1.2.14 - 2007-05-25
  3852. Tor 0.1.2.14 changes the addresses of two directory authorities (this
  3853. change especially affects those who serve or use hidden services),
  3854. and fixes several other crash- and security-related bugs.
  3855. o Directory authority changes:
  3856. - Two directory authorities (moria1 and moria2) just moved to new
  3857. IP addresses. This change will particularly affect those who serve
  3858. or use hidden services.
  3859. o Major bugfixes (crashes):
  3860. - If a directory server runs out of space in the connection table
  3861. as it's processing a begin_dir request, it will free the exit stream
  3862. but leave it attached to the circuit, leading to unpredictable
  3863. behavior. (Reported by seeess, fixes bug 425.)
  3864. - Fix a bug in dirserv_remove_invalid() that would cause authorities
  3865. to corrupt memory under some really unlikely scenarios.
  3866. - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
  3867. - Avoid segfaults when reading from mmaped descriptor file. (Reported
  3868. by lodger.)
  3869. o Major bugfixes (security):
  3870. - When choosing an entry guard for a circuit, avoid using guards
  3871. that are in the same family as the chosen exit -- not just guards
  3872. that are exactly the chosen exit. (Reported by lodger.)
  3873. o Major bugfixes (resource management):
  3874. - If a directory authority is down, skip it when deciding where to get
  3875. networkstatus objects or descriptors. Otherwise we keep asking
  3876. every 10 seconds forever. Fixes bug 384.
  3877. - Count it as a failure if we fetch a valid network-status but we
  3878. don't want to keep it. Otherwise we'll keep fetching it and keep
  3879. not wanting to keep it. Fixes part of bug 422.
  3880. - If all of our dirservers have given us bad or no networkstatuses
  3881. lately, then stop hammering them once per minute even when we
  3882. think they're failed. Fixes another part of bug 422.
  3883. o Minor bugfixes:
  3884. - Actually set the purpose correctly for descriptors inserted with
  3885. purpose=controller.
  3886. - When we have k non-v2 authorities in our DirServer config,
  3887. we ignored the last k authorities in the list when updating our
  3888. network-statuses.
  3889. - Correctly back-off from requesting router descriptors that we are
  3890. having a hard time downloading.
  3891. - Read resolv.conf files correctly on platforms where read() returns
  3892. partial results on small file reads.
  3893. - Don't rebuild the entire router store every time we get 32K of
  3894. routers: rebuild it when the journal gets very large, or when
  3895. the gaps in the store get very large.
  3896. o Minor features:
  3897. - When routers publish SVN revisions in their router descriptors,
  3898. authorities now include those versions correctly in networkstatus
  3899. documents.
  3900. - Warn when using a version of libevent before 1.3b to run a server on
  3901. OSX or BSD: these versions interact badly with userspace threads.
  3902. Changes in version 0.1.2.13 - 2007-04-24
  3903. This release features some major anonymity fixes, such as safer path
  3904. selection; better client performance; faster bootstrapping, better
  3905. address detection, and better DNS support for servers; write limiting as
  3906. well as read limiting to make servers easier to run; and a huge pile of
  3907. other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
  3908. Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
  3909. of the Freenode IRC network, remembering his patience and vision for
  3910. free speech on the Internet.
  3911. o Major features, client performance:
  3912. - Weight directory requests by advertised bandwidth. Now we can
  3913. let servers enable write limiting but still allow most clients to
  3914. succeed at their directory requests. (We still ignore weights when
  3915. choosing a directory authority; I hope this is a feature.)
  3916. - Stop overloading exit nodes -- avoid choosing them for entry or
  3917. middle hops when the total bandwidth available from non-exit nodes
  3918. is much higher than the total bandwidth available from exit nodes.
  3919. - Rather than waiting a fixed amount of time between retrying
  3920. application connections, we wait only 10 seconds for the first,
  3921. 10 seconds for the second, and 15 seconds for each retry after
  3922. that. Hopefully this will improve the expected user experience.
  3923. - Sometimes we didn't bother sending a RELAY_END cell when an attempt
  3924. to open a stream fails; now we do in more cases. This should
  3925. make clients able to find a good exit faster in some cases, since
  3926. unhandleable requests will now get an error rather than timing out.
  3927. o Major features, client functionality:
  3928. - Implement BEGIN_DIR cells, so we can connect to a directory
  3929. server via TLS to do encrypted directory requests rather than
  3930. plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
  3931. config options if you like. For now, this feature only works if
  3932. you already have a descriptor for the destination dirserver.
  3933. - Add support for transparent application connections: this basically
  3934. bundles the functionality of trans-proxy-tor into the Tor
  3935. mainline. Now hosts with compliant pf/netfilter implementations
  3936. can redirect TCP connections straight to Tor without diverting
  3937. through SOCKS. (Based on patch from tup.)
  3938. - Add support for using natd; this allows FreeBSDs earlier than
  3939. 5.1.2 to have ipfw send connections through Tor without using
  3940. SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
  3941. o Major features, servers:
  3942. - Setting up a dyndns name for your server is now optional: servers
  3943. with no hostname or IP address will learn their IP address by
  3944. asking the directory authorities. This code only kicks in when you
  3945. would normally have exited with a "no address" error. Nothing's
  3946. authenticated, so use with care.
  3947. - Directory servers now spool server descriptors, v1 directories,
  3948. and v2 networkstatus objects to buffers as needed rather than en
  3949. masse. They also mmap the cached-routers files. These steps save
  3950. lots of memory.
  3951. - Stop requiring clients to have well-formed certificates, and stop
  3952. checking nicknames in certificates. (Clients have certificates so
  3953. that they can look like Tor servers, but in the future we might want
  3954. to allow them to look like regular TLS clients instead. Nicknames
  3955. in certificates serve no purpose other than making our protocol
  3956. easier to recognize on the wire.) Implements proposal 106.
  3957. o Improvements on DNS support:
  3958. - Add "eventdns" asynchronous dns library originally based on code
  3959. from Adam Langley. Now we can discard the old rickety dnsworker
  3960. concept, and support a wider variety of DNS functions. Allows
  3961. multithreaded builds on NetBSD and OpenBSD again.
  3962. - Add server-side support for "reverse" DNS lookups (using PTR
  3963. records so clients can determine the canonical hostname for a given
  3964. IPv4 address). Only supported by servers using eventdns; servers
  3965. now announce in their descriptors if they don't support eventdns.
  3966. - Workaround for name servers (like Earthlink's) that hijack failing
  3967. DNS requests and replace the no-such-server answer with a "helpful"
  3968. redirect to an advertising-driven search portal. Also work around
  3969. DNS hijackers who "helpfully" decline to hijack known-invalid
  3970. RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
  3971. lets you turn it off.
  3972. - Servers now check for the case when common DNS requests are going to
  3973. wildcarded addresses (i.e. all getting the same answer), and change
  3974. their exit policy to reject *:* if it's happening.
  3975. - When asked to resolve a hostname, don't use non-exit servers unless
  3976. requested to do so. This allows servers with broken DNS to be
  3977. useful to the network.
  3978. - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
  3979. useless IPv6 DNS resolves.
  3980. - Specify and implement client-side SOCKS5 interface for reverse DNS
  3981. lookups (see doc/socks-extensions.txt). Also cache them.
  3982. - When we change nameservers or IP addresses, reset and re-launch
  3983. our tests for DNS hijacking.
  3984. o Improvements on reachability testing:
  3985. - Servers send out a burst of long-range padding cells once they've
  3986. established that they're reachable. Spread them over 4 circuits,
  3987. so hopefully a few will be fast. This exercises bandwidth and
  3988. bootstraps them into the directory more quickly.
  3989. - When we find our DirPort to be reachable, publish a new descriptor
  3990. so we'll tell the world (reported by pnx).
  3991. - Directory authorities now only decide that routers are reachable
  3992. if their identity keys are as expected.
  3993. - Do DirPort reachability tests less often, since a single test
  3994. chews through many circuits before giving up.
  3995. - Avoid some false positives during reachability testing: don't try
  3996. to test via a server that's on the same /24 network as us.
  3997. - Start publishing one minute or so after we find our ORPort
  3998. to be reachable. This will help reduce the number of descriptors
  3999. we have for ourselves floating around, since it's quite likely
  4000. other things (e.g. DirPort) will change during that minute too.
  4001. - Routers no longer try to rebuild long-term connections to directory
  4002. authorities, and directory authorities no longer try to rebuild
  4003. long-term connections to all servers. We still don't hang up
  4004. connections in these two cases though -- we need to look at it
  4005. more carefully to avoid flapping, and we likely need to wait til
  4006. 0.1.1.x is obsolete.
  4007. o Improvements on rate limiting:
  4008. - Enable write limiting as well as read limiting. Now we sacrifice
  4009. capacity if we're pushing out lots of directory traffic, rather
  4010. than overrunning the user's intended bandwidth limits.
  4011. - Include TLS overhead when counting bandwidth usage; previously, we
  4012. would count only the bytes sent over TLS, but not the bytes used
  4013. to send them.
  4014. - Servers decline directory requests much more aggressively when
  4015. they're low on bandwidth. Otherwise they end up queueing more and
  4016. more directory responses, which can't be good for latency.
  4017. - But never refuse directory requests from local addresses.
  4018. - Be willing to read or write on local connections (e.g. controller
  4019. connections) even when the global rate limiting buckets are empty.
  4020. - Flush local controller connection buffers periodically as we're
  4021. writing to them, so we avoid queueing 4+ megabytes of data before
  4022. trying to flush.
  4023. - Revise and clean up the torrc.sample that we ship with; add
  4024. a section for BandwidthRate and BandwidthBurst.
  4025. o Major features, NT services:
  4026. - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
  4027. command-line flag so that admins can override the default by saying
  4028. "tor --service install --user "SomeUser"". This will not affect
  4029. existing installed services. Also, warn the user that the service
  4030. will look for its configuration file in the service user's
  4031. %appdata% directory. (We can't do the "hardwire the user's appdata
  4032. directory" trick any more, since we may not have read access to that
  4033. directory.)
  4034. - Support running the Tor service with a torrc not in the same
  4035. directory as tor.exe and default to using the torrc located in
  4036. the %appdata%\Tor\ of the user who installed the service. Patch
  4037. from Matt Edman.
  4038. - Add an --ignore-missing-torrc command-line option so that we can
  4039. get the "use sensible defaults if the configuration file doesn't
  4040. exist" behavior even when specifying a torrc location on the
  4041. command line.
  4042. - When stopping an NT service, wait up to 10 sec for it to actually
  4043. stop. (Patch from Matt Edman; resolves bug 295.)
  4044. o Directory authority improvements:
  4045. - Stop letting hibernating or obsolete servers affect uptime and
  4046. bandwidth cutoffs.
  4047. - Stop listing hibernating servers in the v1 directory.
  4048. - Authorities no longer recommend exits as guards if this would shift
  4049. too much load to the exit nodes.
  4050. - Authorities now specify server versions in networkstatus. This adds
  4051. about 2% to the size of compressed networkstatus docs, and allows
  4052. clients to tell which servers support BEGIN_DIR and which don't.
  4053. The implementation is forward-compatible with a proposed future
  4054. protocol version scheme not tied to Tor versions.
  4055. - DirServer configuration lines now have an orport= option so
  4056. clients can open encrypted tunnels to the authorities without
  4057. having downloaded their descriptors yet. Enabled for moria1,
  4058. moria2, tor26, and lefkada now in the default configuration.
  4059. - Add a BadDirectory flag to network status docs so that authorities
  4060. can (eventually) tell clients about caches they believe to be
  4061. broken. Not used yet.
  4062. - Allow authorities to list nodes as bad exits in their
  4063. approved-routers file by fingerprint or by address. If most
  4064. authorities set a BadExit flag for a server, clients don't think
  4065. of it as a general-purpose exit. Clients only consider authorities
  4066. that advertise themselves as listing bad exits.
  4067. - Patch from Steve Hildrey: Generate network status correctly on
  4068. non-versioning dirservers.
  4069. - Have directory authorities allow larger amounts of drift in uptime
  4070. without replacing the server descriptor: previously, a server that
  4071. restarted every 30 minutes could have 48 "interesting" descriptors
  4072. per day.
  4073. - Reserve the nickname "Unnamed" for routers that can't pick
  4074. a hostname: any router can call itself Unnamed; directory
  4075. authorities will never allocate Unnamed to any particular router;
  4076. clients won't believe that any router is the canonical Unnamed.
  4077. o Directory mirrors and clients:
  4078. - Discard any v1 directory info that's over 1 month old (for
  4079. directories) or over 1 week old (for running-routers lists).
  4080. - Clients track responses with status 503 from dirservers. After a
  4081. dirserver has given us a 503, we try not to use it until an hour has
  4082. gone by, or until we have no dirservers that haven't given us a 503.
  4083. - When we get a 503 from a directory, and we're not a server, we no
  4084. longer count the failure against the total number of failures
  4085. allowed for the object we're trying to download.
  4086. - Prepare for servers to publish descriptors less often: never
  4087. discard a descriptor simply for being too old until either it is
  4088. recommended by no authorities, or until we get a better one for
  4089. the same router. Make caches consider retaining old recommended
  4090. routers for even longer.
  4091. - Directory servers now provide 'Pragma: no-cache' and 'Expires'
  4092. headers for content, so that we can work better in the presence of
  4093. caching HTTP proxies.
  4094. - Stop fetching descriptors if you're not a dir mirror and you
  4095. haven't tried to establish any circuits lately. (This currently
  4096. causes some dangerous behavior, because when you start up again
  4097. you'll use your ancient server descriptors.)
  4098. o Major fixes, crashes:
  4099. - Stop crashing when the controller asks us to resetconf more than
  4100. one config option at once. (Vidalia 0.0.11 does this.)
  4101. - Fix a longstanding obscure crash bug that could occur when we run
  4102. out of DNS worker processes, if we're not using eventdns. (Resolves
  4103. bug 390.)
  4104. - Fix an assert that could trigger if a controller quickly set then
  4105. cleared EntryNodes. (Bug found by Udo van den Heuvel.)
  4106. - Avoid crash when telling controller about stream-status and a
  4107. stream is detached.
  4108. - Avoid sending junk to controllers or segfaulting when a controller
  4109. uses EVENT_NEW_DESC with verbose nicknames.
  4110. - Stop triggering asserts if the controller tries to extend hidden
  4111. service circuits (reported by mwenge).
  4112. - If we start a server with ClientOnly 1, then set ClientOnly to 0
  4113. and hup, stop triggering an assert based on an empty onion_key.
  4114. - Mask out all signals in sub-threads; only the libevent signal
  4115. handler should be processing them. This should prevent some crashes
  4116. on some machines using pthreads. (Patch from coderman.)
  4117. - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
  4118. o Major fixes, anonymity/security:
  4119. - Automatically avoid picking more than one node from the same
  4120. /16 network when constructing a circuit. Add an
  4121. "EnforceDistinctSubnets" option to let people disable it if they
  4122. want to operate private test networks on a single subnet.
  4123. - When generating bandwidth history, round down to the nearest
  4124. 1k. When storing accounting data, round up to the nearest 1k.
  4125. - When we're running as a server, remember when we last rotated onion
  4126. keys, so that we will rotate keys once they're a week old even if
  4127. we never stay up for a week ourselves.
  4128. - If a client asked for a server by name, and there's a named server
  4129. in our network-status but we don't have its descriptor yet, we
  4130. could return an unnamed server instead.
  4131. - Reject (most) attempts to use Tor circuits with length one. (If
  4132. many people start using Tor as a one-hop proxy, exit nodes become
  4133. a more attractive target for compromise.)
  4134. - Just because your DirPort is open doesn't mean people should be
  4135. able to remotely teach you about hidden service descriptors. Now
  4136. only accept rendezvous posts if you've got HSAuthoritativeDir set.
  4137. - Fix a potential race condition in the rpm installer. Found by
  4138. Stefan Nordhausen.
  4139. - Do not log IPs with TLS failures for incoming TLS
  4140. connections. (Fixes bug 382.)
  4141. o Major fixes, other:
  4142. - If our system clock jumps back in time, don't publish a negative
  4143. uptime in the descriptor.
  4144. - When we start during an accounting interval before it's time to wake
  4145. up, remember to wake up at the correct time. (May fix bug 342.)
  4146. - Previously, we would cache up to 16 old networkstatus documents
  4147. indefinitely, if they came from nontrusted authorities. Now we
  4148. discard them if they are more than 10 days old.
  4149. - When we have a state file we cannot parse, tell the user and
  4150. move it aside. Now we avoid situations where the user starts
  4151. Tor in 1904, Tor writes a state file with that timestamp in it,
  4152. the user fixes her clock, and Tor refuses to start.
  4153. - Publish a new descriptor after we hup/reload. This is important
  4154. if our config has changed such that we'll want to start advertising
  4155. our DirPort now, etc.
  4156. - If we are using an exit enclave and we can't connect, e.g. because
  4157. its webserver is misconfigured to not listen on localhost, then
  4158. back off and try connecting from somewhere else before we fail.
  4159. o New config options or behaviors:
  4160. - When EntryNodes are configured, rebuild the guard list to contain,
  4161. in order: the EntryNodes that were guards before; the rest of the
  4162. EntryNodes; the nodes that were guards before.
  4163. - Do not warn when individual nodes in the configuration's EntryNodes,
  4164. ExitNodes, etc are down: warn only when all possible nodes
  4165. are down. (Fixes bug 348.)
  4166. - Put a lower-bound on MaxAdvertisedBandwidth.
  4167. - Start using the state file to store bandwidth accounting data:
  4168. the bw_accounting file is now obsolete. We'll keep generating it
  4169. for a while for people who are still using 0.1.2.4-alpha.
  4170. - Try to batch changes to the state file so that we do as few
  4171. disk writes as possible while still storing important things in
  4172. a timely fashion.
  4173. - The state file and the bw_accounting file get saved less often when
  4174. the AvoidDiskWrites config option is set.
  4175. - Make PIDFile work on Windows.
  4176. - Add internal descriptions for a bunch of configuration options:
  4177. accessible via controller interface and in comments in saved
  4178. options files.
  4179. - Reject *:563 (NNTPS) in the default exit policy. We already reject
  4180. NNTP by default, so this seems like a sensible addition.
  4181. - Clients now reject hostnames with invalid characters. This should
  4182. avoid some inadvertent info leaks. Add an option
  4183. AllowNonRFC953Hostnames to disable this behavior, in case somebody
  4184. is running a private network with hosts called @, !, and #.
  4185. - Check for addresses with invalid characters at the exit as well,
  4186. and warn less verbosely when they fail. You can override this by
  4187. setting ServerDNSAllowNonRFC953Addresses to 1.
  4188. - Remove some options that have been deprecated since at least
  4189. 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
  4190. SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
  4191. to set log options. Mark PathlenCoinWeight as obsolete.
  4192. - Stop accepting certain malformed ports in configured exit policies.
  4193. - When the user uses bad syntax in the Log config line, stop
  4194. suggesting other bad syntax as a replacement.
  4195. - Add new config option "ResolvConf" to let the server operator
  4196. choose an alternate resolve.conf file when using eventdns.
  4197. - If one of our entry guards is on the ExcludeNodes list, or the
  4198. directory authorities don't think it's a good guard, treat it as
  4199. if it were unlisted: stop using it as a guard, and throw it off
  4200. the guards list if it stays that way for a long time.
  4201. - Allow directory authorities to be marked separately as authorities
  4202. for the v1 directory protocol, the v2 directory protocol, and
  4203. as hidden service directories, to make it easier to retire old
  4204. authorities. V1 authorities should set "HSAuthoritativeDir 1"
  4205. to continue being hidden service authorities too.
  4206. - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
  4207. - Make TrackExitHosts case-insensitive, and fix the behavior of
  4208. ".suffix" TrackExitHosts items to avoid matching in the middle of
  4209. an address.
  4210. - New DirPort behavior: if you have your dirport set, you download
  4211. descriptors aggressively like a directory mirror, whether or not
  4212. your ORPort is set.
  4213. o Docs:
  4214. - Create a new file ReleaseNotes which was the old ChangeLog. The
  4215. new ChangeLog file now includes the notes for all development
  4216. versions too.
  4217. - Add a new address-spec.txt document to describe our special-case
  4218. addresses: .exit, .onion, and .noconnnect.
  4219. - Fork the v1 directory protocol into its own spec document,
  4220. and mark dir-spec.txt as the currently correct (v2) spec.
  4221. o Packaging, porting, and contrib
  4222. - "tor --verify-config" now exits with -1(255) or 0 depending on
  4223. whether the config options are bad or good.
  4224. - The Debian package now uses --verify-config when (re)starting,
  4225. to distinguish configuration errors from other errors.
  4226. - Adapt a patch from goodell to let the contrib/exitlist script
  4227. take arguments rather than require direct editing.
  4228. - Prevent the contrib/exitlist script from printing the same
  4229. result more than once.
  4230. - Add support to tor-resolve tool for reverse lookups and SOCKS5.
  4231. - In the hidden service example in torrc.sample, stop recommending
  4232. esoteric and discouraged hidden service options.
  4233. - Patch from Michael Mohr to contrib/cross.sh, so it checks more
  4234. values before failing, and always enables eventdns.
  4235. - Try to detect Windows correctly when cross-compiling.
  4236. - Libevent-1.2 exports, but does not define in its headers, strlcpy.
  4237. Try to fix this in configure.in by checking for most functions
  4238. before we check for libevent.
  4239. - Update RPMs to require libevent 1.2.
  4240. - Experimentally re-enable kqueue on OSX when using libevent 1.1b
  4241. or later. Log when we are doing this, so we can diagnose it when
  4242. it fails. (Also, recommend libevent 1.1b for kqueue and
  4243. win32 methods; deprecate libevent 1.0b harder; make libevent
  4244. recommendation system saner.)
  4245. - Build with recent (1.3+) libevents on platforms that do not
  4246. define the nonstandard types "u_int8_t" and friends.
  4247. - Remove architecture from OS X builds. The official builds are
  4248. now universal binaries.
  4249. - Run correctly on OS X platforms with case-sensitive filesystems.
  4250. - Correctly set maximum connection limit on Cygwin. (This time
  4251. for sure!)
  4252. - Start compiling on MinGW on Windows (patches from Mike Chiussi
  4253. and many others).
  4254. - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
  4255. - Finally fix the openssl warnings from newer gccs that believe that
  4256. ignoring a return value is okay, but casting a return value and
  4257. then ignoring it is a sign of madness.
  4258. - On architectures where sizeof(int)>4, still clamp declarable
  4259. bandwidth to INT32_MAX.
  4260. o Minor features, controller:
  4261. - Warn the user when an application uses the obsolete binary v0
  4262. control protocol. We're planning to remove support for it during
  4263. the next development series, so it's good to give people some
  4264. advance warning.
  4265. - Add STREAM_BW events to report per-entry-stream bandwidth
  4266. use. (Patch from Robert Hogan.)
  4267. - Rate-limit SIGNEWNYM signals in response to controllers that
  4268. impolitely generate them for every single stream. (Patch from
  4269. mwenge; closes bug 394.)
  4270. - Add a REMAP status to stream events to note that a stream's
  4271. address has changed because of a cached address or a MapAddress
  4272. directive.
  4273. - Make REMAP stream events have a SOURCE (cache or exit), and
  4274. make them generated in every case where we get a successful
  4275. connected or resolved cell.
  4276. - Track reasons for OR connection failure; make these reasons
  4277. available via the controller interface. (Patch from Mike Perry.)
  4278. - Add a SOCKS_BAD_HOSTNAME client status event so controllers
  4279. can learn when clients are sending malformed hostnames to Tor.
  4280. - Specify and implement some of the controller status events.
  4281. - Have GETINFO dir/status/* work on hosts with DirPort disabled.
  4282. - Reimplement GETINFO so that info/names stays in sync with the
  4283. actual keys.
  4284. - Implement "GETINFO fingerprint".
  4285. - Implement "SETEVENTS GUARD" so controllers can get updates on
  4286. entry guard status as it changes.
  4287. - Make all connections to addresses of the form ".noconnect"
  4288. immediately get closed. This lets application/controller combos
  4289. successfully test whether they're talking to the same Tor by
  4290. watching for STREAM events.
  4291. - Add a REASON field to CIRC events; for backward compatibility, this
  4292. field is sent only to controllers that have enabled the extended
  4293. event format. Also, add additional reason codes to explain why
  4294. a given circuit has been destroyed or truncated. (Patches from
  4295. Mike Perry)
  4296. - Add a REMOTE_REASON field to extended CIRC events to tell the
  4297. controller why a remote OR told us to close a circuit.
  4298. - Stream events also now have REASON and REMOTE_REASON fields,
  4299. working much like those for circuit events.
  4300. - There's now a GETINFO ns/... field so that controllers can ask Tor
  4301. about the current status of a router.
  4302. - A new event type "NS" to inform a controller when our opinion of
  4303. a router's status has changed.
  4304. - Add a GETINFO events/names and GETINFO features/names so controllers
  4305. can tell which events and features are supported.
  4306. - A new CLEARDNSCACHE signal to allow controllers to clear the
  4307. client-side DNS cache without expiring circuits.
  4308. - Fix CIRC controller events so that controllers can learn the
  4309. identity digests of non-Named servers used in circuit paths.
  4310. - Let controllers ask for more useful identifiers for servers. Instead
  4311. of learning identity digests for un-Named servers and nicknames
  4312. for Named servers, the new identifiers include digest, nickname,
  4313. and indication of Named status. Off by default; see control-spec.txt
  4314. for more information.
  4315. - Add a "getinfo address" controller command so it can display Tor's
  4316. best guess to the user.
  4317. - New controller event to alert the controller when our server
  4318. descriptor has changed.
  4319. - Give more meaningful errors on controller authentication failure.
  4320. - Export the default exit policy via the control port, so controllers
  4321. don't need to guess what it is / will be later.
  4322. o Minor bugfixes, controller:
  4323. - When creating a circuit via the controller, send a 'launched'
  4324. event when we're done, so we follow the spec better.
  4325. - Correct the control spec to match how the code actually responds
  4326. to 'getinfo addr-mappings/*'. Reported by daejees.
  4327. - The control spec described a GUARDS event, but the code
  4328. implemented a GUARD event. Standardize on GUARD, but let people
  4329. ask for GUARDS too. Reported by daejees.
  4330. - Give the controller END_STREAM_REASON_DESTROY events _before_ we
  4331. clear the corresponding on_circuit variable, and remember later
  4332. that we don't need to send a redundant CLOSED event. (Resolves part
  4333. 3 of bug 367.)
  4334. - Report events where a resolve succeeded or where we got a socks
  4335. protocol error correctly, rather than calling both of them
  4336. "INTERNAL".
  4337. - Change reported stream target addresses to IP consistently when
  4338. we finally get the IP from an exit node.
  4339. - Send log messages to the controller even if they happen to be very
  4340. long.
  4341. - Flush ERR-level controller status events just like we currently
  4342. flush ERR-level log events, so that a Tor shutdown doesn't prevent
  4343. the controller from learning about current events.
  4344. - Report the circuit number correctly in STREAM CLOSED events. Bug
  4345. reported by Mike Perry.
  4346. - Do not report bizarre values for results of accounting GETINFOs
  4347. when the last second's write or read exceeds the allotted bandwidth.
  4348. - Report "unrecognized key" rather than an empty string when the
  4349. controller tries to fetch a networkstatus that doesn't exist.
  4350. - When the controller does a "GETINFO network-status", tell it
  4351. about even those routers whose descriptors are very old, and use
  4352. long nicknames where appropriate.
  4353. - Fix handling of verbose nicknames with ORCONN controller events:
  4354. make them show up exactly when requested, rather than exactly when
  4355. not requested.
  4356. - Controller signals now work on non-Unix platforms that don't define
  4357. SIGUSR1 and SIGUSR2 the way we expect.
  4358. - Respond to SIGNAL command before we execute the signal, in case
  4359. the signal shuts us down. Suggested by Karsten Loesing.
  4360. - Handle reporting OR_CONN_EVENT_NEW events to the controller.
  4361. o Minor features, code performance:
  4362. - Major performance improvement on inserting descriptors: change
  4363. algorithm from O(n^2) to O(n).
  4364. - Do not rotate onion key immediately after setting it for the first
  4365. time.
  4366. - Call router_have_min_dir_info half as often. (This is showing up in
  4367. some profiles, but not others.)
  4368. - When using GCC, make log_debug never get called at all, and its
  4369. arguments never get evaluated, when no debug logs are configured.
  4370. (This is showing up in some profiles, but not others.)
  4371. - Statistics dumped by -USR2 now include a breakdown of public key
  4372. operations, for profiling.
  4373. - Make the common memory allocation path faster on machines where
  4374. malloc(0) returns a pointer.
  4375. - Split circuit_t into origin_circuit_t and or_circuit_t, and
  4376. split connection_t into edge, or, dir, control, and base structs.
  4377. These will save quite a bit of memory on busy servers, and they'll
  4378. also help us track down bugs in the code and bugs in the spec.
  4379. - Use OpenSSL's AES implementation on platforms where it's faster.
  4380. This could save us as much as 10% CPU usage.
  4381. o Minor features, descriptors and descriptor handling:
  4382. - Avoid duplicate entries on MyFamily line in server descriptor.
  4383. - When Tor receives a router descriptor that it asked for, but
  4384. no longer wants (because it has received fresh networkstatuses
  4385. in the meantime), do not warn the user. Cache the descriptor if
  4386. we're a cache; drop it if we aren't.
  4387. - Servers no longer ever list themselves in their "family" line,
  4388. even if configured to do so. This makes it easier to configure
  4389. family lists conveniently.
  4390. o Minor fixes, confusing/misleading log messages:
  4391. - Display correct results when reporting which versions are
  4392. recommended, and how recommended they are. (Resolves bug 383.)
  4393. - Inform the server operator when we decide not to advertise a
  4394. DirPort due to AccountingMax enabled or a low BandwidthRate.
  4395. - Only include function names in log messages for info/debug messages.
  4396. For notice/warn/err, the content of the message should be clear on
  4397. its own, and printing the function name only confuses users.
  4398. - Remove even more protocol-related warnings from Tor server logs,
  4399. such as bad TLS handshakes and malformed begin cells.
  4400. - Fix bug 314: Tor clients issued "unsafe socks" warnings even
  4401. when the IP address is mapped through MapAddress to a hostname.
  4402. - Fix misleading log messages: an entry guard that is "unlisted",
  4403. as well as not known to be "down" (because we've never heard
  4404. of it), is not therefore "up".
  4405. o Minor fixes, old/obsolete behavior:
  4406. - Start assuming we can use a create_fast cell if we don't know
  4407. what version a router is running.
  4408. - We no longer look for identity and onion keys in "identity.key" and
  4409. "onion.key" -- these were replaced by secret_id_key and
  4410. secret_onion_key in 0.0.8pre1.
  4411. - We no longer require unrecognized directory entries to be
  4412. preceded by "opt".
  4413. - Drop compatibility with obsolete Tors that permit create cells
  4414. to have the wrong circ_id_type.
  4415. - Remove code to special-case "-cvs" ending, since it has not
  4416. actually mattered since 0.0.9.
  4417. - Don't re-write the fingerprint file every restart, unless it has
  4418. changed.
  4419. o Minor fixes, misc client-side behavior:
  4420. - Always remove expired routers and networkstatus docs before checking
  4421. whether we have enough information to build circuits. (Fixes
  4422. bug 373.)
  4423. - When computing clock skew from directory HTTP headers, consider what
  4424. time it was when we finished asking for the directory, not what
  4425. time it is now.
  4426. - Make our socks5 handling more robust to broken socks clients:
  4427. throw out everything waiting on the buffer in between socks
  4428. handshake phases, since they can't possibly (so the theory
  4429. goes) have predicted what we plan to respond to them.
  4430. - Expire socks connections if they spend too long waiting for the
  4431. handshake to finish. Previously we would let them sit around for
  4432. days, if the connecting application didn't close them either.
  4433. - And if the socks handshake hasn't started, don't send a
  4434. "DNS resolve socks failed" handshake reply; just close it.
  4435. - If the user asks to use invalid exit nodes, be willing to use
  4436. unstable ones.
  4437. - Track unreachable entry guards correctly: don't conflate
  4438. 'unreachable by us right now' with 'listed as down by the directory
  4439. authorities'. With the old code, if a guard was unreachable by us
  4440. but listed as running, it would clog our guard list forever.
  4441. - Behave correctly in case we ever have a network with more than
  4442. 2GB/s total advertised capacity.
  4443. - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
  4444. - Fix a memory leak when we ask for "all" networkstatuses and we
  4445. get one we don't recognize.
  4446. Changes in version 0.1.1.26 - 2006-12-14
  4447. o Security bugfixes:
  4448. - Stop sending the HttpProxyAuthenticator string to directory
  4449. servers when directory connections are tunnelled through Tor.
  4450. - Clients no longer store bandwidth history in the state file.
  4451. - Do not log introduction points for hidden services if SafeLogging
  4452. is set.
  4453. o Minor bugfixes:
  4454. - Fix an assert failure when a directory authority sets
  4455. AuthDirRejectUnlisted and then receives a descriptor from an
  4456. unlisted router (reported by seeess).
  4457. Changes in version 0.1.1.25 - 2006-11-04
  4458. o Major bugfixes:
  4459. - When a client asks us to resolve (rather than connect to)
  4460. an address, and we have a cached answer, give them the cached
  4461. answer. Previously, we would give them no answer at all.
  4462. - We were building exactly the wrong circuits when we predict
  4463. hidden service requirements, meaning Tor would have to build all
  4464. its circuits on demand.
  4465. - If none of our live entry guards have a high uptime, but we
  4466. require a guard with a high uptime, try adding a new guard before
  4467. we give up on the requirement. This patch should make long-lived
  4468. connections more stable on average.
  4469. - When testing reachability of our DirPort, don't launch new
  4470. tests when there's already one in progress -- unreachable
  4471. servers were stacking up dozens of testing streams.
  4472. o Security bugfixes:
  4473. - When the user sends a NEWNYM signal, clear the client-side DNS
  4474. cache too. Otherwise we continue to act on previous information.
  4475. o Minor bugfixes:
  4476. - Avoid a memory corruption bug when creating a hash table for
  4477. the first time.
  4478. - Avoid possibility of controller-triggered crash when misusing
  4479. certain commands from a v0 controller on platforms that do not
  4480. handle printf("%s",NULL) gracefully.
  4481. - Avoid infinite loop on unexpected controller input.
  4482. - Don't log spurious warnings when we see a circuit close reason we
  4483. don't recognize; it's probably just from a newer version of Tor.
  4484. - Add Vidalia to the OS X uninstaller script, so when we uninstall
  4485. Tor/Privoxy we also uninstall Vidalia.
  4486. Changes in version 0.1.1.24 - 2006-09-29
  4487. o Major bugfixes:
  4488. - Allow really slow clients to not hang up five minutes into their
  4489. directory downloads (suggested by Adam J. Richter).
  4490. - Fix major performance regression from 0.1.0.x: instead of checking
  4491. whether we have enough directory information every time we want to
  4492. do something, only check when the directory information has changed.
  4493. This should improve client CPU usage by 25-50%.
  4494. - Don't crash if, after a server has been running for a while,
  4495. it can't resolve its hostname.
  4496. - When a client asks us to resolve (not connect to) an address,
  4497. and we have a cached answer, give them the cached answer.
  4498. Previously, we would give them no answer at all.
  4499. o Minor bugfixes:
  4500. - Allow Tor to start when RunAsDaemon is set but no logs are set.
  4501. - Don't crash when the controller receives a third argument to an
  4502. "extendcircuit" request.
  4503. - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
  4504. response; fix error code when "getinfo dir/status/" fails.
  4505. - Fix configure.in to not produce broken configure files with
  4506. more recent versions of autoconf. Thanks to Clint for his auto*
  4507. voodoo.
  4508. - Fix security bug on NetBSD that could allow someone to force
  4509. uninitialized RAM to be sent to a server's DNS resolver. This
  4510. only affects NetBSD and other platforms that do not bounds-check
  4511. tolower().
  4512. - Warn user when using libevent 1.1a or earlier with win32 or kqueue
  4513. methods: these are known to be buggy.
  4514. - If we're a directory mirror and we ask for "all" network status
  4515. documents, we would discard status documents from authorities
  4516. we don't recognize.
  4517. Changes in version 0.1.1.23 - 2006-07-30
  4518. o Major bugfixes:
  4519. - Fast Tor servers, especially exit nodes, were triggering asserts
  4520. due to a bug in handling the list of pending DNS resolves. Some
  4521. bugs still remain here; we're hunting them.
  4522. - Entry guards could crash clients by sending unexpected input.
  4523. - More fixes on reachability testing: if you find yourself reachable,
  4524. then don't ever make any client requests (so you stop predicting
  4525. circuits), then hup or have your clock jump, then later your IP
  4526. changes, you won't think circuits are working, so you won't try to
  4527. test reachability, so you won't publish.
  4528. o Minor bugfixes:
  4529. - Avoid a crash if the controller does a resetconf firewallports
  4530. and then a setconf fascistfirewall=1.
  4531. - Avoid an integer underflow when the dir authority decides whether
  4532. a router is stable: we might wrongly label it stable, and compute
  4533. a slightly wrong median stability, when a descriptor is published
  4534. later than now.
  4535. - Fix a place where we might trigger an assert if we can't build our
  4536. own server descriptor yet.
  4537. Changes in version 0.1.1.22 - 2006-07-05
  4538. o Major bugfixes:
  4539. - Fix a big bug that was causing servers to not find themselves
  4540. reachable if they changed IP addresses. Since only 0.1.1.22+
  4541. servers can do reachability testing correctly, now we automatically
  4542. make sure to test via one of these.
  4543. - Fix to allow clients and mirrors to learn directory info from
  4544. descriptor downloads that get cut off partway through.
  4545. - Directory authorities had a bug in deciding if a newly published
  4546. descriptor was novel enough to make everybody want a copy -- a few
  4547. servers seem to be publishing new descriptors many times a minute.
  4548. o Minor bugfixes:
  4549. - Fix a rare bug that was causing some servers to complain about
  4550. "closing wedged cpuworkers" and skip some circuit create requests.
  4551. - Make the Exit flag in directory status documents actually work.
  4552. Changes in version 0.1.1.21 - 2006-06-10
  4553. o Crash and assert fixes from 0.1.1.20:
  4554. - Fix a rare crash on Tor servers that have enabled hibernation.
  4555. - Fix a seg fault on startup for Tor networks that use only one
  4556. directory authority.
  4557. - Fix an assert from a race condition that occurs on Tor servers
  4558. while exiting, where various threads are trying to log that they're
  4559. exiting, and delete the logs, at the same time.
  4560. - Make our unit tests pass again on certain obscure platforms.
  4561. o Other fixes:
  4562. - Add support for building SUSE RPM packages.
  4563. - Speed up initial bootstrapping for clients: if we are making our
  4564. first ever connection to any entry guard, then don't mark it down
  4565. right after that.
  4566. - When only one Tor server in the network is labelled as a guard,
  4567. and we've already picked him, we would cycle endlessly picking him
  4568. again, being unhappy about it, etc. Now we specifically exclude
  4569. current guards when picking a new guard.
  4570. - Servers send create cells more reliably after the TLS connection
  4571. is established: we were sometimes forgetting to send half of them
  4572. when we had more than one pending.
  4573. - If we get a create cell that asks us to extend somewhere, but the
  4574. Tor server there doesn't match the expected digest, we now send
  4575. a destroy cell back, rather than silently doing nothing.
  4576. - Make options->RedirectExit work again.
  4577. - Make cookie authentication for the controller work again.
  4578. - Stop being picky about unusual characters in the arguments to
  4579. mapaddress. It's none of our business.
  4580. - Add a new config option "TestVia" that lets you specify preferred
  4581. middle hops to use for test circuits. Perhaps this will let me
  4582. debug the reachability problems better.
  4583. o Log / documentation fixes:
  4584. - If we're a server and some peer has a broken TLS certificate, don't
  4585. log about it unless ProtocolWarnings is set, i.e., we want to hear
  4586. about protocol violations by others.
  4587. - Fix spelling of VirtualAddrNetwork in man page.
  4588. - Add a better explanation at the top of the autogenerated torrc file
  4589. about what happened to our old torrc.
  4590. Changes in version 0.1.1.20 - 2006-05-23
  4591. o Crash and assert fixes from 0.1.0.17:
  4592. - Fix assert bug in close_logs() on exit: when we close and delete
  4593. logs, remove them all from the global "logfiles" list.
  4594. - Fix an assert error when we're out of space in the connection_list
  4595. and we try to post a hidden service descriptor (reported by Peter
  4596. Palfrader).
  4597. - Fix a rare assert error when we've tried all intro points for
  4598. a hidden service and we try fetching the service descriptor again:
  4599. "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
  4600. - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
  4601. out and refuse the setconf if it would fail.
  4602. - If you specify a relative torrc path and you set RunAsDaemon in
  4603. your torrc, then it chdir()'s to the new directory. If you then
  4604. HUP, it tries to load the new torrc location, fails, and exits.
  4605. The fix: no longer allow a relative path to torrc when using -f.
  4606. - Check for integer overflows in more places, when adding elements
  4607. to smartlists. This could possibly prevent a buffer overflow
  4608. on malicious huge inputs.
  4609. o Security fixes, major:
  4610. - When we're printing strings from the network, don't try to print
  4611. non-printable characters. Now we're safer against shell escape
  4612. sequence exploits, and also against attacks to fool users into
  4613. misreading their logs.
  4614. - Implement entry guards: automatically choose a handful of entry
  4615. nodes and stick with them for all circuits. Only pick new guards
  4616. when the ones you have are unsuitable, and if the old guards
  4617. become suitable again, switch back. This will increase security
  4618. dramatically against certain end-point attacks. The EntryNodes
  4619. config option now provides some hints about which entry guards you
  4620. want to use most; and StrictEntryNodes means to only use those.
  4621. Fixes CVE-2006-0414.
  4622. - Implement exit enclaves: if we know an IP address for the
  4623. destination, and there's a running Tor server at that address
  4624. which allows exit to the destination, then extend the circuit to
  4625. that exit first. This provides end-to-end encryption and end-to-end
  4626. authentication. Also, if the user wants a .exit address or enclave,
  4627. use 4 hops rather than 3, and cannibalize a general circ for it
  4628. if you can.
  4629. - Obey our firewall options more faithfully:
  4630. . If we can't get to a dirserver directly, try going via Tor.
  4631. . Don't ever try to connect (as a client) to a place our
  4632. firewall options forbid.
  4633. . If we specify a proxy and also firewall options, obey the
  4634. firewall options even when we're using the proxy: some proxies
  4635. can only proxy to certain destinations.
  4636. - Make clients regenerate their keys when their IP address changes.
  4637. - For the OS X package's modified privoxy config file, comment
  4638. out the "logfile" line so we don't log everything passed
  4639. through privoxy.
  4640. - Our TLS handshakes were generating a single public/private
  4641. keypair for the TLS context, rather than making a new one for
  4642. each new connection. Oops. (But we were still rotating them
  4643. periodically, so it's not so bad.)
  4644. - When we were cannibalizing a circuit with a particular exit
  4645. node in mind, we weren't checking to see if that exit node was
  4646. already present earlier in the circuit. Now we are.
  4647. - Require server descriptors to list IPv4 addresses -- hostnames
  4648. are no longer allowed. This also fixes potential vulnerabilities
  4649. to servers providing hostnames as their address and then
  4650. preferentially resolving them so they can partition users.
  4651. - Our logic to decide if the OR we connected to was the right guy
  4652. was brittle and maybe open to a mitm for invalid routers.
  4653. o Security fixes, minor:
  4654. - Adjust tor-spec.txt to parameterize cell and key lengths. Now
  4655. Ian Goldberg can prove things about our handshake protocol more
  4656. easily.
  4657. - Make directory authorities generate a separate "guard" flag to
  4658. mean "would make a good entry guard". Clients now honor the
  4659. is_guard flag rather than looking at is_fast or is_stable.
  4660. - Try to list MyFamily elements by key, not by nickname, and warn
  4661. if we've not heard of a server.
  4662. - Start using RAND_bytes rather than RAND_pseudo_bytes from
  4663. OpenSSL. Also, reseed our entropy every hour, not just at
  4664. startup. And add entropy in 512-bit chunks, not 160-bit chunks.
  4665. - Refuse server descriptors where the fingerprint line doesn't match
  4666. the included identity key. Tor doesn't care, but other apps (and
  4667. humans) might actually be trusting the fingerprint line.
  4668. - We used to kill the circuit when we receive a relay command we
  4669. don't recognize. Now we just drop that cell.
  4670. - Fix a bug found by Lasse Overlier: when we were making internal
  4671. circuits (intended to be cannibalized later for rendezvous and
  4672. introduction circuits), we were picking them so that they had
  4673. useful exit nodes. There was no need for this, and it actually
  4674. aids some statistical attacks.
  4675. - Start treating internal circuits and exit circuits separately.
  4676. It's important to keep them separate because internal circuits
  4677. have their last hops picked like middle hops, rather than like
  4678. exit hops. So exiting on them will break the user's expectations.
  4679. - Fix a possible way to DoS dirservers.
  4680. - When the client asked for a rendezvous port that the hidden
  4681. service didn't want to provide, we were sending an IP address
  4682. back along with the end cell. Fortunately, it was zero. But stop
  4683. that anyway.
  4684. o Packaging improvements:
  4685. - Implement --with-libevent-dir option to ./configure. Improve
  4686. search techniques to find libevent, and use those for openssl too.
  4687. - Fix a couple of bugs in OpenSSL detection. Deal better when
  4688. there are multiple SSLs installed with different versions.
  4689. - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
  4690. - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
  4691. "-Wall -g -O2".
  4692. - Make unit tests (and other invocations that aren't the real Tor)
  4693. run without launching listeners, creating subdirectories, and so on.
  4694. - The OS X installer was adding a symlink for tor_resolve but
  4695. the binary was called tor-resolve (reported by Thomas Hardly).
  4696. - Now we can target arch and OS in rpm builds (contributed by
  4697. Phobos). Also make the resulting dist-rpm filename match the
  4698. target arch.
  4699. - Apply Matt Ghali's --with-syslog-facility patch to ./configure
  4700. if you log to syslog and want something other than LOG_DAEMON.
  4701. - Fix the torify (tsocks) config file to not use Tor for localhost
  4702. connections.
  4703. - Start shipping socks-extensions.txt, tor-doc-unix.html,
  4704. tor-doc-server.html, and stylesheet.css in the tarball.
  4705. - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
  4706. They are useless now.
  4707. - Add Peter Palfrader's contributed check-tor script. It lets you
  4708. easily check whether a given server (referenced by nickname)
  4709. is reachable by you.
  4710. - Add BSD-style contributed startup script "rc.subr" from Peter
  4711. Thoenen.
  4712. o Directory improvements -- new directory protocol:
  4713. - See tor/doc/dir-spec.txt for all the juicy details. Key points:
  4714. - Authorities and caches publish individual descriptors (by
  4715. digest, by fingerprint, by "all", and by "tell me yours").
  4716. - Clients don't download or use the old directory anymore. Now they
  4717. download network-statuses from the directory authorities, and
  4718. fetch individual server descriptors as needed from mirrors.
  4719. - Clients don't download descriptors of non-running servers.
  4720. - Download descriptors by digest, not by fingerprint. Caches try to
  4721. download all listed digests from authorities; clients try to
  4722. download "best" digests from caches. This avoids partitioning
  4723. and isolating attacks better.
  4724. - Only upload a new server descriptor when options change, 18
  4725. hours have passed, uptime is reset, or bandwidth changes a lot.
  4726. - Directory authorities silently throw away new descriptors that
  4727. haven't changed much if the timestamps are similar. We do this to
  4728. tolerate older Tor servers that upload a new descriptor every 15
  4729. minutes. (It seemed like a good idea at the time.)
  4730. - Clients choose directory servers from the network status lists,
  4731. not from their internal list of router descriptors. Now they can
  4732. go to caches directly rather than needing to go to authorities
  4733. to bootstrap the first set of descriptors.
  4734. - When picking a random directory, prefer non-authorities if any
  4735. are known.
  4736. - Add a new flag to network-status indicating whether the server
  4737. can answer v2 directory requests too.
  4738. - Directory mirrors now cache up to 16 unrecognized network-status
  4739. docs, so new directory authorities will be cached too.
  4740. - Stop parsing, storing, or using running-routers output (but
  4741. mirrors still cache and serve it).
  4742. - Clients consider a threshold of "versioning" directory authorities
  4743. before deciding whether to warn the user that he's obsolete.
  4744. - Authorities publish separate sorted lists of recommended versions
  4745. for clients and for servers.
  4746. - Change DirServers config line to note which dirs are v1 authorities.
  4747. - Put nicknames on the DirServer line, so we can refer to them
  4748. without requiring all our users to memorize their IP addresses.
  4749. - Remove option when getting directory cache to see whether they
  4750. support running-routers; they all do now. Replace it with one
  4751. to see whether caches support v2 stuff.
  4752. - Stop listing down or invalid nodes in the v1 directory. This
  4753. reduces its bulk by about 1/3, and reduces load on mirrors.
  4754. - Mirrors no longer cache the v1 directory as often.
  4755. - If we as a directory mirror don't know of any v1 directory
  4756. authorities, then don't try to cache any v1 directories.
  4757. o Other directory improvements:
  4758. - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
  4759. fifth authoritative directory servers.
  4760. - Directory authorities no longer require an open connection from
  4761. a server to consider him "reachable". We need this change because
  4762. when we add new directory authorities, old servers won't know not
  4763. to hang up on them.
  4764. - Dir authorities now do their own external reachability testing
  4765. of each server, and only list as running the ones they found to
  4766. be reachable. We also send back warnings to the server's logs if
  4767. it uploads a descriptor that we already believe is unreachable.
  4768. - Spread the directory authorities' reachability testing over the
  4769. entire testing interval, so we don't try to do 500 TLS's at once
  4770. every 20 minutes.
  4771. - Make the "stable" router flag in network-status be the median of
  4772. the uptimes of running valid servers, and make clients pay
  4773. attention to the network-status flags. Thus the cutoff adapts
  4774. to the stability of the network as a whole, making IRC, IM, etc
  4775. connections more reliable.
  4776. - Make the v2 dir's "Fast" flag based on relative capacity, just
  4777. like "Stable" is based on median uptime. Name everything in the
  4778. top 7/8 Fast, and only the top 1/2 gets to be a Guard.
  4779. - Retry directory requests if we fail to get an answer we like
  4780. from a given dirserver (we were retrying before, but only if
  4781. we fail to connect).
  4782. - Return a robots.txt on our dirport to discourage google indexing.
  4783. o Controller protocol improvements:
  4784. - Revised controller protocol (version 1) that uses ascii rather
  4785. than binary: tor/doc/control-spec.txt. Add supporting libraries
  4786. in python and java and c# so you can use the controller from your
  4787. applications without caring how our protocol works.
  4788. - Allow the DEBUG controller event to work again. Mark certain log
  4789. entries as "don't tell this to controllers", so we avoid cycles.
  4790. - New controller function "getinfo accounting", to ask how
  4791. many bytes we've used in this time period.
  4792. - Add a "resetconf" command so you can set config options like
  4793. AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
  4794. a config option in the torrc with no value, then it clears it
  4795. entirely (rather than setting it to its default).
  4796. - Add a "getinfo config-file" to tell us where torrc is. Also
  4797. expose guard nodes, config options/names.
  4798. - Add a "quit" command (when when using the controller manually).
  4799. - Add a new signal "newnym" to "change pseudonyms" -- that is, to
  4800. stop using any currently-dirty circuits for new streams, so we
  4801. don't link new actions to old actions. This also occurs on HUP
  4802. or "signal reload".
  4803. - If we would close a stream early (e.g. it asks for a .exit that
  4804. we know would refuse it) but the LeaveStreamsUnattached config
  4805. option is set by the controller, then don't close it.
  4806. - Add a new controller event type "authdir_newdescs" that allows
  4807. controllers to get all server descriptors that were uploaded to
  4808. a router in its role as directory authority.
  4809. - New controller option "getinfo desc/all-recent" to fetch the
  4810. latest server descriptor for every router that Tor knows about.
  4811. - Fix the controller's "attachstream 0" command to treat conn like
  4812. it just connected, doing address remapping, handling .exit and
  4813. .onion idioms, and so on. Now we're more uniform in making sure
  4814. that the controller hears about new and closing connections.
  4815. - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
  4816. the controller. Also, rotate dns and cpu workers if the controller
  4817. changes options that will affect them; and initialize the dns
  4818. worker cache tree whether or not we start out as a server.
  4819. - Add a new circuit purpose 'controller' to let the controller ask
  4820. for a circuit that Tor won't try to use. Extend the "extendcircuit"
  4821. controller command to let you specify the purpose if you're starting
  4822. a new circuit. Add a new "setcircuitpurpose" controller command to
  4823. let you change a circuit's purpose after it's been created.
  4824. - Let the controller ask for "getinfo dir/server/foo" so it can ask
  4825. directly rather than connecting to the dir port. "getinfo
  4826. dir/status/foo" also works, but currently only if your DirPort
  4827. is enabled.
  4828. - Let the controller tell us about certain router descriptors
  4829. that it doesn't want Tor to use in circuits. Implement
  4830. "setrouterpurpose" and modify "+postdescriptor" to do this.
  4831. - If the controller's *setconf commands fail, collect an error
  4832. message in a string and hand it back to the controller -- don't
  4833. just tell them to go read their logs.
  4834. o Scalability, resource management, and performance:
  4835. - Fix a major load balance bug: we were round-robin reading in 16 KB
  4836. chunks, and servers with bandwidthrate of 20 KB, while downloading
  4837. a 600 KB directory, would starve their other connections. Now we
  4838. try to be a bit more fair.
  4839. - Be more conservative about whether to advertise our DirPort.
  4840. The main change is to not advertise if we're running at capacity
  4841. and either a) we could hibernate ever or b) our capacity is low
  4842. and we're using a default DirPort.
  4843. - We weren't cannibalizing circuits correctly for
  4844. CIRCUIT_PURPOSE_C_ESTABLISH_REND and
  4845. CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
  4846. build those from scratch. This should make hidden services faster.
  4847. - Predict required circuits better, with an eye toward making hidden
  4848. services faster on the service end.
  4849. - Compress exit policies even more: look for duplicate lines and
  4850. remove them.
  4851. - Generate 18.0.0.0/8 address policy format in descs when we can;
  4852. warn when the mask is not reducible to a bit-prefix.
  4853. - There used to be two ways to specify your listening ports in a
  4854. server descriptor: on the "router" line and with a separate "ports"
  4855. line. Remove support for the "ports" line.
  4856. - Reduce memory requirements in our structs by changing the order
  4857. of fields. Replace balanced trees with hash tables. Inline
  4858. bottleneck smartlist functions. Add a "Map from digest to void*"
  4859. abstraction so we can do less hex encoding/decoding, and use it
  4860. in router_get_by_digest(). Many other CPU and memory improvements.
  4861. - Allow tor_gzip_uncompress to extract as much as possible from
  4862. truncated compressed data. Try to extract as many
  4863. descriptors as possible from truncated http responses (when
  4864. purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
  4865. - Make circ->onionskin a pointer, not a static array. moria2 was using
  4866. 125000 circuit_t's after it had been up for a few weeks, which
  4867. translates to 20+ megs of wasted space.
  4868. - The private half of our EDH handshake keys are now chosen out
  4869. of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
  4870. - Stop doing the complex voodoo overkill checking for insecure
  4871. Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
  4872. - Do round-robin writes for TLS of at most 16 kB per write. This
  4873. might be more fair on loaded Tor servers.
  4874. - Do not use unaligned memory access on alpha, mips, or mipsel.
  4875. It *works*, but is very slow, so we treat them as if it doesn't.
  4876. o Other bugfixes and improvements:
  4877. - Start storing useful information to $DATADIR/state, so we can
  4878. remember things across invocations of Tor. Retain unrecognized
  4879. lines so we can be forward-compatible, and write a TorVersion line
  4880. so we can be backward-compatible.
  4881. - If ORPort is set, Address is not explicitly set, and our hostname
  4882. resolves to a private IP address, try to use an interface address
  4883. if it has a public address. Now Windows machines that think of
  4884. themselves as localhost can guess their address.
  4885. - Regenerate our local descriptor if it's dirty and we try to use
  4886. it locally (e.g. if it changes during reachability detection).
  4887. This was causing some Tor servers to keep publishing the same
  4888. initial descriptor forever.
  4889. - Tor servers with dynamic IP addresses were needing to wait 18
  4890. hours before they could start doing reachability testing using
  4891. the new IP address and ports. This is because they were using
  4892. the internal descriptor to learn what to test, yet they were only
  4893. rebuilding the descriptor once they decided they were reachable.
  4894. - It turns out we couldn't bootstrap a network since we added
  4895. reachability detection in 0.1.0.1-rc. Good thing the Tor network
  4896. has never gone down. Add an AssumeReachable config option to let
  4897. servers and authorities bootstrap. When we're trying to build a
  4898. high-uptime or high-bandwidth circuit but there aren't enough
  4899. suitable servers, try being less picky rather than simply failing.
  4900. - Newly bootstrapped Tor networks couldn't establish hidden service
  4901. circuits until they had nodes with high uptime. Be more tolerant.
  4902. - Really busy servers were keeping enough circuits open on stable
  4903. connections that they were wrapping around the circuit_id
  4904. space. (It's only two bytes.) This exposed a bug where we would
  4905. feel free to reuse a circuit_id even if it still exists but has
  4906. been marked for close. Try to fix this bug. Some bug remains.
  4907. - When we fail to bind or listen on an incoming or outgoing
  4908. socket, we now close it before refusing, rather than just
  4909. leaking it. (Thanks to Peter Palfrader for finding.)
  4910. - Fix a file descriptor leak in start_daemon().
  4911. - On Windows, you can't always reopen a port right after you've
  4912. closed it. So change retry_listeners() to only close and re-open
  4913. ports that have changed.
  4914. - Workaround a problem with some http proxies that refuse GET
  4915. requests that specify "Content-Length: 0". Reported by Adrian.
  4916. - Recover better from TCP connections to Tor servers that are
  4917. broken but don't tell you (it happens!); and rotate TLS
  4918. connections once a week.
  4919. - Fix a scary-looking but apparently harmless bug where circuits
  4920. would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
  4921. servers, and never switch to state CIRCUIT_STATE_OPEN.
  4922. - Check for even more Windows version flags when writing the platform
  4923. string in server descriptors, and note any we don't recognize.
  4924. - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
  4925. get a better idea of why their circuits failed. Not used yet.
  4926. - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
  4927. We don't use them yet, but maybe one day our DNS resolver will be
  4928. able to discover them.
  4929. - Let people type "tor --install" as well as "tor -install" when they
  4930. want to make it an NT service.
  4931. - Looks like we were never delivering deflated (i.e. compressed)
  4932. running-routers lists, even when asked. Oops.
  4933. - We were leaking some memory every time the client changed IPs.
  4934. - Clean up more of the OpenSSL memory when exiting, so we can detect
  4935. memory leaks better.
  4936. - Never call free() on tor_malloc()d memory. This will help us
  4937. use dmalloc to detect memory leaks.
  4938. - Some Tor servers process billions of cells per day. These
  4939. statistics are now uint64_t's.
  4940. - Check [X-]Forwarded-For headers in HTTP requests when generating
  4941. log messages. This lets people run dirservers (and caches) behind
  4942. Apache but still know which IP addresses are causing warnings.
  4943. - Fix minor integer overflow in calculating when we expect to use up
  4944. our bandwidth allocation before hibernating.
  4945. - Lower the minimum required number of file descriptors to 1000,
  4946. so we can have some overhead for Valgrind on Linux, where the
  4947. default ulimit -n is 1024.
  4948. - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
  4949. and its existence is confusing some users.
  4950. o Config option fixes:
  4951. - Add a new config option ExitPolicyRejectPrivate which defaults
  4952. to on. Now all exit policies will begin with rejecting private
  4953. addresses, unless the server operator explicitly turns it off.
  4954. - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
  4955. - Add new ReachableORAddresses and ReachableDirAddresses options
  4956. that understand address policies. FascistFirewall is now a synonym
  4957. for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
  4958. - Start calling it FooListenAddress rather than FooBindAddress,
  4959. since few of our users know what it means to bind an address
  4960. or port.
  4961. - If the user gave Tor an odd number of command-line arguments,
  4962. we were silently ignoring the last one. Now we complain and fail.
  4963. This wins the oldest-bug prize -- this bug has been present since
  4964. November 2002, as released in Tor 0.0.0.
  4965. - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
  4966. torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
  4967. it would silently ignore the 6668.
  4968. - If we get a linelist or linelist_s config option from the torrc,
  4969. e.g. ExitPolicy, and it has no value, warn and skip rather than
  4970. silently resetting it to its default.
  4971. - Setconf was appending items to linelists, not clearing them.
  4972. - Add MyFamily to torrc.sample in the server section, so operators
  4973. will be more likely to learn that it exists.
  4974. - Make ContactInfo mandatory for authoritative directory servers.
  4975. - MaxConn has been obsolete for a while now. Document the ConnLimit
  4976. config option, which is a *minimum* number of file descriptors
  4977. that must be available else Tor refuses to start.
  4978. - Get rid of IgnoreVersion undocumented config option, and make us
  4979. only warn, never exit, when we're running an obsolete version.
  4980. - Make MonthlyAccountingStart config option truly obsolete now.
  4981. - Correct the man page entry on TrackHostExitsExpire.
  4982. - Let directory authorities start even if they don't specify an
  4983. Address config option.
  4984. - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
  4985. reflect the updated flags in our v2 dir protocol.
  4986. o Config option features:
  4987. - Add a new config option FastFirstHopPK (on by default) so clients
  4988. do a trivial crypto handshake for their first hop, since TLS has
  4989. already taken care of confidentiality and authentication.
  4990. - Let the user set ControlListenAddress in the torrc. This can be
  4991. dangerous, but there are some cases (like a secured LAN) where it
  4992. makes sense.
  4993. - New config options to help controllers: FetchServerDescriptors
  4994. and FetchHidServDescriptors for whether to fetch server
  4995. info and hidserv info or let the controller do it, and
  4996. PublishServerDescriptor and PublishHidServDescriptors.
  4997. - Also let the controller set the __AllDirActionsPrivate config
  4998. option if you want all directory fetches/publishes to happen via
  4999. Tor (it assumes your controller bootstraps your circuits).
  5000. - Add "HardwareAccel" config option: support for crypto hardware
  5001. accelerators via OpenSSL. Off by default, until we find somebody
  5002. smart who can test it for us. (It appears to produce seg faults
  5003. in at least some cases.)
  5004. - New config option "AuthDirRejectUnlisted" for directory authorities
  5005. as a panic button: if we get flooded with unusable servers we can
  5006. revert to only listing servers in the approved-routers file.
  5007. - Directory authorities can now reject/invalidate by key and IP,
  5008. with the config options "AuthDirInvalid" and "AuthDirReject", or
  5009. by marking a fingerprint as "!reject" or "!invalid" (as its
  5010. nickname) in the approved-routers file. This is useful since
  5011. currently we automatically list servers as running and usable
  5012. even if we know they're jerks.
  5013. - Add a new config option TestSocks so people can see whether their
  5014. applications are using socks4, socks4a, socks5-with-ip, or
  5015. socks5-with-fqdn. This way they don't have to keep mucking
  5016. with tcpdump and wondering if something got cached somewhere.
  5017. - Add "private:*" as an alias in configuration for policies. Now
  5018. you can simplify your exit policy rather than needing to list
  5019. every single internal or nonroutable network space.
  5020. - Accept "private:*" in routerdesc exit policies; not generated yet
  5021. because older Tors do not understand it.
  5022. - Add configuration option "V1AuthoritativeDirectory 1" which
  5023. moria1, moria2, and tor26 have set.
  5024. - Implement an option, VirtualAddrMask, to set which addresses
  5025. get handed out in response to mapaddress requests. This works
  5026. around a bug in tsocks where 127.0.0.0/8 is never socksified.
  5027. - Add a new config option FetchUselessDescriptors, off by default,
  5028. for when you plan to run "exitlist" on your client and you want
  5029. to know about even the non-running descriptors.
  5030. - SocksTimeout: How long do we let a socks connection wait
  5031. unattached before we fail it?
  5032. - CircuitBuildTimeout: Cull non-open circuits that were born
  5033. at least this many seconds ago.
  5034. - CircuitIdleTimeout: Cull open clean circuits that were born
  5035. at least this many seconds ago.
  5036. - New config option SafeSocks to reject all application connections
  5037. using unsafe socks protocols. Defaults to off.
  5038. o Improved and clearer log messages:
  5039. - Reduce clutter in server logs. We're going to try to make
  5040. them actually usable now. New config option ProtocolWarnings that
  5041. lets you hear about how _other Tors_ are breaking the protocol. Off
  5042. by default.
  5043. - Divide log messages into logging domains. Once we put some sort
  5044. of interface on this, it will let people looking at more verbose
  5045. log levels specify the topics they want to hear more about.
  5046. - Log server fingerprint on startup, so new server operators don't
  5047. have to go hunting around their filesystem for it.
  5048. - Provide dire warnings to any users who set DirServer manually;
  5049. move it out of torrc.sample and into torrc.complete.
  5050. - Make the log message less scary when all the dirservers are
  5051. temporarily unreachable.
  5052. - When tor_socketpair() fails in Windows, give a reasonable
  5053. Windows-style errno back.
  5054. - Improve tor_gettimeofday() granularity on windows.
  5055. - We were printing the number of idle dns workers incorrectly when
  5056. culling them.
  5057. - Handle duplicate lines in approved-routers files without warning.
  5058. - We were whining about using socks4 or socks5-with-local-lookup
  5059. even when it's an IP address in the "virtual" range we designed
  5060. exactly for this case.
  5061. - Check for named servers when looking them up by nickname;
  5062. warn when we're calling a non-named server by its nickname;
  5063. don't warn twice about the same name.
  5064. - Downgrade the dirserver log messages when whining about
  5065. unreachability.
  5066. - Correct "your server is reachable" log entries to indicate that
  5067. it was self-testing that told us so.
  5068. - If we're trying to be a Tor server and running Windows 95/98/ME
  5069. as a server, explain that we'll likely crash.
  5070. - Provide a more useful warn message when our onion queue gets full:
  5071. the CPU is too slow or the exit policy is too liberal.
  5072. - Don't warn when we receive a 503 from a dirserver/cache -- this
  5073. will pave the way for them being able to refuse if they're busy.
  5074. - When we fail to bind a listener, try to provide a more useful
  5075. log message: e.g., "Is Tor already running?"
  5076. - Only start testing reachability once we've established a
  5077. circuit. This will make startup on dir authorities less noisy.
  5078. - Don't try to upload hidden service descriptors until we have
  5079. established a circuit.
  5080. - Tor didn't warn when it failed to open a log file.
  5081. - Warn when listening on a public address for socks. We suspect a
  5082. lot of people are setting themselves up as open socks proxies,
  5083. and they have no idea that jerks on the Internet are using them,
  5084. since they simply proxy the traffic into the Tor network.
  5085. - Give a useful message when people run Tor as the wrong user,
  5086. rather than telling them to start chowning random directories.
  5087. - Fix a harmless bug that was causing Tor servers to log
  5088. "Got an end because of misc error, but we're not an AP. Closing."
  5089. - Fix wrong log message when you add a "HiddenServiceNodes" config
  5090. line without any HiddenServiceDir line (reported by Chris Thomas).
  5091. - Directory authorities now stop whining so loudly about bad
  5092. descriptors that they fetch from other dirservers. So when there's
  5093. a log complaint, it's for sure from a freshly uploaded descriptor.
  5094. - When logging via syslog, include the pid whenever we provide
  5095. a log entry. Suggested by Todd Fries.
  5096. - When we're shutting down and we do something like try to post a
  5097. server descriptor or rendezvous descriptor, don't complain that
  5098. we seem to be unreachable. Of course we are, we're shutting down.
  5099. - Change log line for unreachability to explicitly suggest /etc/hosts
  5100. as the culprit. Also make it clearer what IP address and ports we're
  5101. testing for reachability.
  5102. - Put quotes around user-supplied strings when logging so users are
  5103. more likely to realize if they add bad characters (like quotes)
  5104. to the torrc.
  5105. - NT service patch from Matt Edman to improve error messages on Win32.
  5106. Changes in version 0.1.0.17 - 2006-02-17
  5107. o Crash bugfixes on 0.1.0.x:
  5108. - When servers with a non-zero DirPort came out of hibernation,
  5109. sometimes they would trigger an assert.
  5110. o Other important bugfixes:
  5111. - On platforms that don't have getrlimit (like Windows), we were
  5112. artificially constraining ourselves to a max of 1024
  5113. connections. Now just assume that we can handle as many as 15000
  5114. connections. Hopefully this won't cause other problems.
  5115. o Backported features:
  5116. - When we're a server, a client asks for an old-style directory,
  5117. and our write bucket is empty, don't give it to him. This way
  5118. small servers can continue to serve the directory *sometimes*,
  5119. without getting overloaded.
  5120. - Whenever you get a 503 in response to a directory fetch, try
  5121. once more. This will become important once servers start sending
  5122. 503's whenever they feel busy.
  5123. - Fetch a new directory every 120 minutes, not every 40 minutes.
  5124. Now that we have hundreds of thousands of users running the old
  5125. directory algorithm, it's starting to hurt a lot.
  5126. - Bump up the period for forcing a hidden service descriptor upload
  5127. from 20 minutes to 1 hour.
  5128. Changes in version 0.1.0.16 - 2006-01-02
  5129. o Crash bugfixes on 0.1.0.x:
  5130. - On Windows, build with a libevent patch from "I-M Weasel" to avoid
  5131. corrupting the heap, losing FDs, or crashing when we need to resize
  5132. the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
  5133. - It turns out sparc64 platforms crash on unaligned memory access
  5134. too -- so detect and avoid this.
  5135. - Handle truncated compressed data correctly (by detecting it and
  5136. giving an error).
  5137. - Fix possible-but-unlikely free(NULL) in control.c.
  5138. - When we were closing connections, there was a rare case that
  5139. stomped on memory, triggering seg faults and asserts.
  5140. - Avoid potential infinite recursion when building a descriptor. (We
  5141. don't know that it ever happened, but better to fix it anyway.)
  5142. - We were neglecting to unlink marked circuits from soon-to-close OR
  5143. connections, which caused some rare scribbling on freed memory.
  5144. - Fix a memory stomping race bug when closing the joining point of two
  5145. rendezvous circuits.
  5146. - Fix an assert in time parsing found by Steven Murdoch.
  5147. o Other bugfixes on 0.1.0.x:
  5148. - When we're doing reachability testing, provide more useful log
  5149. messages so the operator knows what to expect.
  5150. - Do not check whether DirPort is reachable when we are suppressing
  5151. advertising it because of hibernation.
  5152. - When building with -static or on Solaris, we sometimes needed -ldl.
  5153. - One of the dirservers (tor26) changed its IP address.
  5154. - When we're deciding whether a stream has enough circuits around
  5155. that can handle it, count the freshly dirty ones and not the ones
  5156. that are so dirty they won't be able to handle it.
  5157. - When we're expiring old circuits, we had a logic error that caused
  5158. us to close new rendezvous circuits rather than old ones.
  5159. - Give a more helpful log message when you try to change ORPort via
  5160. the controller: you should upgrade Tor if you want that to work.
  5161. - We were failing to parse Tor versions that start with "Tor ".
  5162. - Tolerate faulty streams better: when a stream fails for reason
  5163. exitpolicy, stop assuming that the router is lying about his exit
  5164. policy. When a stream fails for reason misc, allow it to retry just
  5165. as if it was resolvefailed. When a stream has failed three times,
  5166. reset its failure count so we can try again and get all three tries.
  5167. Changes in version 0.1.0.15 - 2005-09-23
  5168. o Bugfixes on 0.1.0.x:
  5169. - Reject ports 465 and 587 (spam targets) in default exit policy.
  5170. - Don't crash when we don't have any spare file descriptors and we
  5171. try to spawn a dns or cpu worker.
  5172. - Get rid of IgnoreVersion undocumented config option, and make us
  5173. only warn, never exit, when we're running an obsolete version.
  5174. - Don't try to print a null string when your server finds itself to
  5175. be unreachable and the Address config option is empty.
  5176. - Make the numbers in read-history and write-history into uint64s,
  5177. so they don't overflow and publish negatives in the descriptor.
  5178. - Fix a minor memory leak in smartlist_string_remove().
  5179. - We were only allowing ourselves to upload a server descriptor at
  5180. most every 20 minutes, even if it changed earlier than that.
  5181. - Clean up log entries that pointed to old URLs.
  5182. Changes in version 0.1.0.14 - 2005-08-08
  5183. o Bugfixes on 0.1.0.x:
  5184. - Fix the other half of the bug with crypto handshakes
  5185. (CVE-2005-2643).
  5186. - Fix an assert trigger if you send a 'signal term' via the
  5187. controller when it's listening for 'event info' messages.
  5188. Changes in version 0.1.0.13 - 2005-08-04
  5189. o Bugfixes on 0.1.0.x:
  5190. - Fix a critical bug in the security of our crypto handshakes.
  5191. - Fix a size_t underflow in smartlist_join_strings2() that made
  5192. it do bad things when you hand it an empty smartlist.
  5193. - Fix Windows installer to ship Tor license (thanks to Aphex for
  5194. pointing out this oversight) and put a link to the doc directory
  5195. in the start menu.
  5196. - Explicitly set no-unaligned-access for sparc: it turns out the
  5197. new gcc's let you compile broken code, but that doesn't make it
  5198. not-broken.
  5199. Changes in version 0.1.0.12 - 2005-07-18
  5200. o New directory servers:
  5201. - tor26 has changed IP address.
  5202. o Bugfixes on 0.1.0.x:
  5203. - Fix a possible double-free in tor_gzip_uncompress().
  5204. - When --disable-threads is set, do not search for or link against
  5205. pthreads libraries.
  5206. - Don't trigger an assert if an authoritative directory server
  5207. claims its dirport is 0.
  5208. - Fix bug with removing Tor as an NT service: some people were
  5209. getting "The service did not return an error." Thanks to Matt
  5210. Edman for the fix.
  5211. Changes in version 0.1.0.11 - 2005-06-30
  5212. o Bugfixes on 0.1.0.x:
  5213. - Fix major security bug: servers were disregarding their
  5214. exit policies if clients behaved unexpectedly.
  5215. - Make OS X init script check for missing argument, so we don't
  5216. confuse users who invoke it incorrectly.
  5217. - Fix a seg fault in "tor --hash-password foo".
  5218. - The MAPADDRESS control command was broken.
  5219. Changes in version 0.1.0.10 - 2005-06-14
  5220. o Fixes on Win32:
  5221. - Make NT services work and start on startup on Win32 (based on
  5222. patch by Matt Edman). See the FAQ entry for details.
  5223. - Make 'platform' string in descriptor more accurate for Win32
  5224. servers, so it's not just "unknown platform".
  5225. - REUSEADDR on normal platforms means you can rebind to the port
  5226. right after somebody else has let it go. But REUSEADDR on Win32
  5227. means you can bind to the port _even when somebody else already
  5228. has it bound_! So, don't do that on Win32.
  5229. - Clean up the log messages when starting on Win32 with no config
  5230. file.
  5231. - Allow seeding the RNG on Win32 even when you're not running as
  5232. Administrator. If seeding the RNG on Win32 fails, quit.
  5233. o Assert / crash bugs:
  5234. - Refuse relay cells that claim to have a length larger than the
  5235. maximum allowed. This prevents a potential attack that could read
  5236. arbitrary memory (e.g. keys) from an exit server's process
  5237. (CVE-2005-2050).
  5238. - If unofficial Tor clients connect and send weird TLS certs, our
  5239. Tor server triggers an assert. Stop asserting, and start handling
  5240. TLS errors better in other situations too.
  5241. - Fix a race condition that can trigger an assert when we have a
  5242. pending create cell and an OR connection attempt fails.
  5243. o Resource leaks:
  5244. - Use pthreads for worker processes rather than forking. This was
  5245. forced because when we forked, we ended up wasting a lot of
  5246. duplicate ram over time.
  5247. - Also switch to foo_r versions of some library calls to allow
  5248. reentry and threadsafeness.
  5249. - Implement --disable-threads configure option. Disable threads on
  5250. netbsd and openbsd by default, because they have no reentrant
  5251. resolver functions (!), and on solaris since it has other
  5252. threading issues.
  5253. - Fix possible bug on threading platforms (e.g. win32) which was
  5254. leaking a file descriptor whenever a cpuworker or dnsworker died.
  5255. - Fix a minor memory leak when somebody establishes an introduction
  5256. point at your Tor server.
  5257. - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
  5258. Adam Langley.)
  5259. - Add ./configure --with-dmalloc option, to track memory leaks.
  5260. - And try to free all memory on closing, so we can detect what
  5261. we're leaking.
  5262. o Protocol correctness:
  5263. - When we've connected to an OR and handshaked but didn't like
  5264. the result, we were closing the conn without sending destroy
  5265. cells back for pending circuits. Now send those destroys.
  5266. - Start sending 'truncated' cells back rather than destroy cells
  5267. if the circuit closes in front of you. This means we won't have
  5268. to abandon partially built circuits.
  5269. - Handle changed router status correctly when dirserver reloads
  5270. fingerprint file. We used to be dropping all unverified descriptors
  5271. right then. The bug was hidden because we would immediately
  5272. fetch a directory from another dirserver, which would include the
  5273. descriptors we just dropped.
  5274. - Revise tor-spec to add more/better stream end reasons.
  5275. - Revise all calls to connection_edge_end to avoid sending 'misc',
  5276. and to take errno into account where possible.
  5277. - Client now retries when streams end early for 'hibernating' or
  5278. 'resource limit' reasons, rather than failing them.
  5279. - Try to be more zealous about calling connection_edge_end when
  5280. things go bad with edge conns in connection.c.
  5281. o Robustness improvements:
  5282. - Better handling for heterogeneous / unreliable nodes:
  5283. - Annotate circuits with whether they aim to contain high uptime
  5284. nodes and/or high capacity nodes. When building circuits, choose
  5285. appropriate nodes.
  5286. - This means that every single node in an intro rend circuit,
  5287. not just the last one, will have a minimum uptime.
  5288. - New config option LongLivedPorts to indicate application streams
  5289. that will want high uptime circuits.
  5290. - Servers reset uptime when a dir fetch entirely fails. This
  5291. hopefully reflects stability of the server's network connectivity.
  5292. - If somebody starts his tor server in Jan 2004 and then fixes his
  5293. clock, don't make his published uptime be a year.
  5294. - Reset published uptime when we wake up from hibernation.
  5295. - Introduce a notion of 'internal' circs, which are chosen without
  5296. regard to the exit policy of the last hop. Intro and rendezvous
  5297. circs must be internal circs, to avoid leaking information. Resolve
  5298. and connect streams can use internal circs if they want.
  5299. - New circuit pooling algorithm: keep track of what destination ports
  5300. we've used recently (start out assuming we'll want to use 80), and
  5301. make sure to have enough circs around to satisfy these ports. Also
  5302. make sure to have 2 internal circs around if we've required internal
  5303. circs lately (and with high uptime if we've seen that lately too).
  5304. - Turn addr_policy_compare from a tristate to a quadstate; this should
  5305. help address our "Ah, you allow 1.2.3.4:80. You are a good choice
  5306. for google.com" problem.
  5307. - When a client asks us for a dir mirror and we don't have one,
  5308. launch an attempt to get a fresh one.
  5309. - First cut at support for "create-fast" cells. Clients can use
  5310. these when extending to their first hop, since the TLS already
  5311. provides forward secrecy and authentication. Not enabled on
  5312. clients yet.
  5313. o Reachability testing.
  5314. - Your Tor server will automatically try to see if its ORPort and
  5315. DirPort are reachable from the outside, and it won't upload its
  5316. descriptor until it decides at least ORPort is reachable (when
  5317. DirPort is not yet found reachable, publish it as zero).
  5318. - When building testing circs for ORPort testing, use only
  5319. high-bandwidth nodes, so fewer circuits fail.
  5320. - Notice when our IP changes, and reset stats/uptime/reachability.
  5321. - Authdirservers don't do ORPort reachability detection, since
  5322. they're in clique mode, so it will be rare to find a server not
  5323. already connected to them.
  5324. - Authdirservers now automatically approve nodes running 0.1.0.2-rc
  5325. or later.
  5326. o Dirserver fixes:
  5327. - Now we allow two unverified servers with the same nickname
  5328. but different keys. But if a nickname is verified, only that
  5329. nickname+key are allowed.
  5330. - If you're an authdirserver connecting to an address:port,
  5331. and it's not the OR you were expecting, forget about that
  5332. descriptor. If he *was* the one you were expecting, then forget
  5333. about all other descriptors for that address:port.
  5334. - Allow servers to publish descriptors from 12 hours in the future.
  5335. Corollary: only whine about clock skew from the dirserver if
  5336. he's a trusted dirserver (since now even verified servers could
  5337. have quite wrong clocks).
  5338. - Require servers that use the default dirservers to have public IP
  5339. addresses. We have too many servers that are configured with private
  5340. IPs and their admins never notice the log entries complaining that
  5341. their descriptors are being rejected.
  5342. o Efficiency improvements:
  5343. - Use libevent. Now we can use faster async cores (like epoll, kpoll,
  5344. and /dev/poll), and hopefully work better on Windows too.
  5345. - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
  5346. kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
  5347. - Find libevent even if it's hiding in /usr/local/ and your
  5348. CFLAGS and LDFLAGS don't tell you to look there.
  5349. - Be able to link with libevent as a shared library (the default
  5350. after 1.0d), even if it's hiding in /usr/local/lib and even
  5351. if you haven't added /usr/local/lib to your /etc/ld.so.conf,
  5352. assuming you're running gcc. Otherwise fail and give a useful
  5353. error message.
  5354. - Switch to a new buffer management algorithm, which tries to avoid
  5355. reallocing and copying quite as much. In first tests it looks like
  5356. it uses *more* memory on average, but less cpu.
  5357. - Switch our internal buffers implementation to use a ring buffer,
  5358. to hopefully improve performance for fast servers a lot.
  5359. - Reenable the part of the code that tries to flush as soon as an
  5360. OR outbuf has a full TLS record available. Perhaps this will make
  5361. OR outbufs not grow as huge except in rare cases, thus saving lots
  5362. of CPU time plus memory.
  5363. - Improve performance for dirservers: stop re-parsing the whole
  5364. directory every time you regenerate it.
  5365. - Keep a big splay tree of (circid,orconn)->circuit mappings to make
  5366. it much faster to look up a circuit for each relay cell.
  5367. - Remove most calls to assert_all_pending_dns_resolves_ok(),
  5368. since they're eating our cpu on exit nodes.
  5369. - Stop wasting time doing a case insensitive comparison for every
  5370. dns name every time we do any lookup. Canonicalize the names to
  5371. lowercase when you first see them.
  5372. o Hidden services:
  5373. - Handle unavailable hidden services better. Handle slow or busy
  5374. hidden services better.
  5375. - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
  5376. circ as necessary, if there are any completed ones lying around
  5377. when we try to launch one.
  5378. - Make hidden services try to establish a rendezvous for 30 seconds
  5379. after fetching the descriptor, rather than for n (where n=3)
  5380. attempts to build a circuit.
  5381. - Adjust maximum skew and age for rendezvous descriptors: let skew
  5382. be 48 hours rather than 90 minutes.
  5383. - Reject malformed .onion addresses rather then passing them on as
  5384. normal web requests.
  5385. o Controller:
  5386. - More Tor controller support. See
  5387. http://tor.eff.org/doc/control-spec.txt for all the new features,
  5388. including signals to emulate unix signals from any platform;
  5389. redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
  5390. closestream; closecircuit; etc.
  5391. - Encode hashed controller passwords in hex instead of base64,
  5392. to make it easier to write controllers.
  5393. - Revise control spec and implementation to allow all log messages to
  5394. be sent to controller with their severities intact (suggested by
  5395. Matt Edman). Disable debug-level logs while delivering a debug-level
  5396. log to the controller, to prevent loop. Update TorControl to handle
  5397. new log event types.
  5398. o New config options/defaults:
  5399. - Begin scrubbing sensitive strings from logs by default. Turn off
  5400. the config option SafeLogging if you need to do debugging.
  5401. - New exit policy: accept most low-numbered ports, rather than
  5402. rejecting most low-numbered ports.
  5403. - Put a note in the torrc about abuse potential with the default
  5404. exit policy.
  5405. - Add support for CONNECTing through https proxies, with "HttpsProxy"
  5406. config option.
  5407. - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
  5408. based on patch from Adam Langley (basic auth only).
  5409. - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
  5410. the fast servers that have been joining lately. (Clients are now
  5411. willing to load balance over up to 2 MB of advertised bandwidth
  5412. capacity too.)
  5413. - New config option MaxAdvertisedBandwidth which lets you advertise
  5414. a low bandwidthrate (to not attract as many circuits) while still
  5415. allowing a higher bandwidthrate in reality.
  5416. - Require BandwidthRate to be at least 20kB/s for servers.
  5417. - Add a NoPublish config option, so you can be a server (e.g. for
  5418. testing running Tor servers in other Tor networks) without
  5419. publishing your descriptor to the primary dirservers.
  5420. - Add a new AddressMap config directive to rewrite incoming socks
  5421. addresses. This lets you, for example, declare an implicit
  5422. required exit node for certain sites.
  5423. - Add a new TrackHostExits config directive to trigger addressmaps
  5424. for certain incoming socks addresses -- for sites that break when
  5425. your exit keeps changing (based on patch from Mike Perry).
  5426. - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
  5427. which describes how often we retry making new circuits if current
  5428. ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
  5429. how long we're willing to make use of an already-dirty circuit.
  5430. - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
  5431. a config option "ShutdownWaitLength" (when using kill -INT on
  5432. servers).
  5433. - Fix an edge case in parsing config options: if they say "--"
  5434. on the commandline, it's not a config option (thanks weasel).
  5435. - New config option DirAllowPrivateAddresses for authdirservers.
  5436. Now by default they refuse router descriptors that have non-IP or
  5437. private-IP addresses.
  5438. - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
  5439. smart" default value: low for servers and high for clients.
  5440. - Some people were putting "Address " in their torrc, and they had
  5441. a buggy resolver that resolved " " to 0.0.0.0. Oops.
  5442. - If DataDir is ~/.tor, and that expands to /.tor, then default to
  5443. LOCALSTATEDIR/tor instead.
  5444. - Implement --verify-config command-line option to check if your torrc
  5445. is valid without actually launching Tor.
  5446. o Logging improvements:
  5447. - When dirservers refuse a server descriptor, we now log its
  5448. contactinfo, platform, and the poster's IP address.
  5449. - Only warn once per nickname from add_nickname_list_to_smartlist()
  5450. per failure, so an entrynode or exitnode choice that's down won't
  5451. yell so much.
  5452. - When we're connecting to an OR and he's got a different nickname/key
  5453. than we were expecting, only complain loudly if we're an OP or a
  5454. dirserver. Complaining loudly to the OR admins just confuses them.
  5455. - Whine at you if you're a server and you don't set your contactinfo.
  5456. - Warn when exit policy implicitly allows local addresses.
  5457. - Give a better warning when some other server advertises an
  5458. ORPort that is actually an apache running ssl.
  5459. - If we get an incredibly skewed timestamp from a dirserver mirror
  5460. that isn't a verified OR, don't warn -- it's probably him that's
  5461. wrong.
  5462. - When a dirserver causes you to give a warn, mention which dirserver
  5463. it was.
  5464. - Initialize libevent later in the startup process, so the logs are
  5465. already established by the time we start logging libevent warns.
  5466. - Use correct errno on win32 if libevent fails.
  5467. - Check and warn about known-bad/slow libevent versions.
  5468. - Stop warning about sigpipes in the logs. We're going to
  5469. pretend that getting these occassionally is normal and fine.
  5470. o New contrib scripts:
  5471. - New experimental script tor/contrib/exitlist: a simple python
  5472. script to parse directories and find Tor nodes that exit to listed
  5473. addresses/ports.
  5474. - New experimental script tor/contrib/ExerciseServer.py (needs more
  5475. work) that uses the controller interface to build circuits and
  5476. fetch pages over them. This will help us bootstrap servers that
  5477. have lots of capacity but haven't noticed it yet.
  5478. - New experimental script tor/contrib/PathDemo.py (needs more work)
  5479. that uses the controller interface to let you choose whole paths
  5480. via addresses like
  5481. "<hostname>.<path,separated by dots>.<length of path>.path"
  5482. - New contributed script "privoxy-tor-toggle" to toggle whether
  5483. Privoxy uses Tor. Seems to be configured for Debian by default.
  5484. - Have torctl.in/tor.sh.in check for location of su binary (needed
  5485. on FreeBSD)
  5486. o Misc bugfixes:
  5487. - chdir() to your datadirectory at the *end* of the daemonize process,
  5488. not the beginning. This was a problem because the first time you
  5489. run tor, if your datadir isn't there, and you have runasdaemon set
  5490. to 1, it will try to chdir to it before it tries to create it. Oops.
  5491. - Fix several double-mark-for-close bugs, e.g. where we were finding
  5492. a conn for a cell even if that conn is already marked for close.
  5493. - Stop most cases of hanging up on a socks connection without sending
  5494. the socks reject.
  5495. - Fix a bug in the RPM package: set home directory for _tor to
  5496. something more reasonable when first installing.
  5497. - Stop putting nodename in the Platform string in server descriptors.
  5498. It doesn't actually help, and it is confusing/upsetting some people.
  5499. - When using preferred entry or exit nodes, ignore whether the
  5500. circuit wants uptime or capacity. They asked for the nodes, they
  5501. get the nodes.
  5502. - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
  5503. artificially capped at 500kB.
  5504. - Cache local dns resolves correctly even when they're .exit
  5505. addresses.
  5506. - If we're hibernating and we get a SIGINT, exit immediately.
  5507. - tor-resolve requests were ignoring .exit if there was a working circuit
  5508. they could use instead.
  5509. - Pay more attention to the ClientOnly config option.
  5510. - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
  5511. installer screens; and don't put stuff into StartupItems unless
  5512. the user asks you to.
  5513. o Misc features:
  5514. - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
  5515. rather than just rejecting it.
  5516. - If our clock jumps forward by 100 seconds or more, assume something
  5517. has gone wrong with our network and abandon all not-yet-used circs.
  5518. - When an application is using socks5, give him the whole variety of
  5519. potential socks5 responses (connect refused, host unreachable, etc),
  5520. rather than just "success" or "failure".
  5521. - A more sane version numbering system. See
  5522. http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
  5523. - Change version parsing logic: a version is "obsolete" if it is not
  5524. recommended and (1) there is a newer recommended version in the
  5525. same series, or (2) there are no recommended versions in the same
  5526. series, but there are some recommended versions in a newer series.
  5527. A version is "new" if it is newer than any recommended version in
  5528. the same series.
  5529. - Report HTTP reasons to client when getting a response from directory
  5530. servers -- so you can actually know what went wrong.
  5531. - Reject odd-looking addresses at the client (e.g. addresses that
  5532. contain a colon), rather than having the server drop them because
  5533. they're malformed.
  5534. - Stop publishing socksport in the directory, since it's not
  5535. actually meant to be public. For compatibility, publish a 0 there
  5536. for now.
  5537. - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
  5538. cookies to disk and doesn't log each web request to disk. (Thanks
  5539. to Brett Carrington for pointing this out.)
  5540. - Add OSX uninstall instructions. An actual uninstall script will
  5541. come later.
  5542. - Add "opt hibernating 1" to server descriptor to make it clearer
  5543. whether the server is hibernating.
  5544. Changes in version 0.0.9.10 - 2005-06-16
  5545. o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
  5546. - Refuse relay cells that claim to have a length larger than the
  5547. maximum allowed. This prevents a potential attack that could read
  5548. arbitrary memory (e.g. keys) from an exit server's process
  5549. (CVE-2005-2050).
  5550. Changes in version 0.0.9.9 - 2005-04-23
  5551. o Bugfixes on 0.0.9.x:
  5552. - If unofficial Tor clients connect and send weird TLS certs, our
  5553. Tor server triggers an assert. This release contains a minimal
  5554. backport from the broader fix that we put into 0.1.0.4-rc.
  5555. Changes in version 0.0.9.8 - 2005-04-07
  5556. o Bugfixes on 0.0.9.x:
  5557. - We have a bug that I haven't found yet. Sometimes, very rarely,
  5558. cpuworkers get stuck in the 'busy' state, even though the cpuworker
  5559. thinks of itself as idle. This meant that no new circuits ever got
  5560. established. Here's a workaround to kill any cpuworker that's been
  5561. busy for more than 100 seconds.
  5562. Changes in version 0.0.9.7 - 2005-04-01
  5563. o Bugfixes on 0.0.9.x:
  5564. - Fix another race crash bug (thanks to Glenn Fink for reporting).
  5565. - Compare identity to identity, not to nickname, when extending to
  5566. a router not already in the directory. This was preventing us from
  5567. extending to unknown routers. Oops.
  5568. - Make sure to create OS X Tor user in <500 range, so we aren't
  5569. creating actual system users.
  5570. - Note where connection-that-hasn't-sent-end was marked, and fix
  5571. a few really loud instances of this harmless bug (it's fixed more
  5572. in 0.1.0.x).
  5573. Changes in version 0.0.9.6 - 2005-03-24
  5574. o Bugfixes on 0.0.9.x (crashes and asserts):
  5575. - Add new end stream reasons to maintainance branch. Fix bug where
  5576. reason (8) could trigger an assert. Prevent bug from recurring.
  5577. - Apparently win32 stat wants paths to not end with a slash.
  5578. - Fix assert triggers in assert_cpath_layer_ok(), where we were
  5579. blowing away the circuit that conn->cpath_layer points to, then
  5580. checking to see if the circ is well-formed. Backport check to make
  5581. sure we dont use the cpath on a closed connection.
  5582. - Prevent circuit_resume_edge_reading_helper() from trying to package
  5583. inbufs for marked-for-close streams.
  5584. - Don't crash on hup if your options->address has become unresolvable.
  5585. - Some systems (like OS X) sometimes accept() a connection and tell
  5586. you the remote host is 0.0.0.0:0. If this happens, due to some
  5587. other mis-features, we get confused; so refuse the conn for now.
  5588. o Bugfixes on 0.0.9.x (other):
  5589. - Fix harmless but scary "Unrecognized content encoding" warn message.
  5590. - Add new stream error reason: TORPROTOCOL reason means "you are not
  5591. speaking a version of Tor I understand; say bye-bye to your stream."
  5592. - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
  5593. into the future, now that we are more tolerant of skew. This
  5594. resolves a bug where a Tor server would refuse to cache a directory
  5595. because all the directories it gets are too far in the future;
  5596. yet the Tor server never logs any complaints about clock skew.
  5597. - Mac packaging magic: make man pages useable, and do not overwrite
  5598. existing torrc files.
  5599. - Make OS X log happily to /var/log/tor/tor.log
  5600. Changes in version 0.0.9.5 - 2005-02-22
  5601. o Bugfixes on 0.0.9.x:
  5602. - Fix an assert race at exit nodes when resolve requests fail.
  5603. - Stop picking unverified dir mirrors--it only leads to misery.
  5604. - Patch from Matt Edman to make NT services work better. Service
  5605. support is still not compiled into the executable by default.
  5606. - Patch from Dmitri Bely so the Tor service runs better under
  5607. the win32 SYSTEM account.
  5608. - Make tor-resolve actually work (?) on Win32.
  5609. - Fix a sign bug when getrlimit claims to have 4+ billion
  5610. file descriptors available.
  5611. - Stop refusing to start when bandwidthburst == bandwidthrate.
  5612. - When create cells have been on the onion queue more than five
  5613. seconds, just send back a destroy and take them off the list.
  5614. Changes in version 0.0.9.4 - 2005-02-03
  5615. o Bugfixes on 0.0.9:
  5616. - Fix an assert bug that took down most of our servers: when
  5617. a server claims to have 1 GB of bandwidthburst, don't
  5618. freak out.
  5619. - Don't crash as badly if we have spawned the max allowed number
  5620. of dnsworkers, or we're out of file descriptors.
  5621. - Block more file-sharing ports in the default exit policy.
  5622. - MaxConn is now automatically set to the hard limit of max
  5623. file descriptors we're allowed (ulimit -n), minus a few for
  5624. logs, etc.
  5625. - Give a clearer message when servers need to raise their
  5626. ulimit -n when they start running out of file descriptors.
  5627. - SGI Compatibility patches from Jan Schaumann.
  5628. - Tolerate a corrupt cached directory better.
  5629. - When a dirserver hasn't approved your server, list which one.
  5630. - Go into soft hibernation after 95% of the bandwidth is used,
  5631. not 99%. This is especially important for daily hibernators who
  5632. have a small accounting max. Hopefully it will result in fewer
  5633. cut connections when the hard hibernation starts.
  5634. - Load-balance better when using servers that claim more than
  5635. 800kB/s of capacity.
  5636. - Make NT services work (experimental, only used if compiled in).
  5637. Changes in version 0.0.9.3 - 2005-01-21
  5638. o Bugfixes on 0.0.9:
  5639. - Backport the cpu use fixes from main branch, so busy servers won't
  5640. need as much processor time.
  5641. - Work better when we go offline and then come back, or when we
  5642. run Tor at boot before the network is up. We do this by
  5643. optimistically trying to fetch a new directory whenever an
  5644. application request comes in and we think we're offline -- the
  5645. human is hopefully a good measure of when the network is back.
  5646. - Backport some minimal hidserv bugfixes: keep rend circuits open as
  5647. long as you keep using them; actually publish hidserv descriptors
  5648. shortly after they change, rather than waiting 20-40 minutes.
  5649. - Enable Mac startup script by default.
  5650. - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
  5651. - When you update AllowUnverifiedNodes or FirewallPorts via the
  5652. controller's setconf feature, we were always appending, never
  5653. resetting.
  5654. - When you update HiddenServiceDir via setconf, it was screwing up
  5655. the order of reading the lines, making it fail.
  5656. - Do not rewrite a cached directory back to the cache; otherwise we
  5657. will think it is recent and not fetch a newer one on startup.
  5658. - Workaround for webservers that lie about Content-Encoding: Tor
  5659. now tries to autodetect compressed directories and compression
  5660. itself. This lets us Proxypass dir fetches through apache.
  5661. Changes in version 0.0.9.2 - 2005-01-04
  5662. o Bugfixes on 0.0.9 (crashes and asserts):
  5663. - Fix an assert on startup when the disk is full and you're logging
  5664. to a file.
  5665. - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
  5666. style address, then we'd crash.
  5667. - Fix an assert trigger when the running-routers string we get from
  5668. a dirserver is broken.
  5669. - Make worker threads start and run on win32. Now win32 servers
  5670. may work better.
  5671. - Bandaid (not actually fix, but now it doesn't crash) an assert
  5672. where the dns worker dies mysteriously and the main Tor process
  5673. doesn't remember anything about the address it was resolving.
  5674. o Bugfixes on 0.0.9 (Win32):
  5675. - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
  5676. name out of the warning/assert messages.
  5677. - Fix a superficial "unhandled error on read" bug on win32.
  5678. - The win32 installer no longer requires a click-through for our
  5679. license, since our Free Software license grants rights but does not
  5680. take any away.
  5681. - Win32: When connecting to a dirserver fails, try another one
  5682. immediately. (This was already working for non-win32 Tors.)
  5683. - Stop trying to parse $HOME on win32 when hunting for default
  5684. DataDirectory.
  5685. - Make tor-resolve.c work on win32 by calling network_init().
  5686. o Bugfixes on 0.0.9 (other):
  5687. - Make 0.0.9.x build on Solaris again.
  5688. - Due to a fencepost error, we were blowing away the \n when reporting
  5689. confvalue items in the controller. So asking for multiple config
  5690. values at once couldn't work.
  5691. - When listing circuits that are pending on an opening OR connection,
  5692. if we're an OR we were listing circuits that *end* at us as
  5693. being pending on every listener, dns/cpu worker, etc. Stop that.
  5694. - Dirservers were failing to create 'running-routers' or 'directory'
  5695. strings if we had more than some threshold of routers. Fix them so
  5696. they can handle any number of routers.
  5697. - Fix a superficial "Duplicate mark for close" bug.
  5698. - Stop checking for clock skew for OR connections, even for servers.
  5699. - Fix a fencepost error that was chopping off the last letter of any
  5700. nickname that is the maximum allowed nickname length.
  5701. - Update URLs in log messages so they point to the new website.
  5702. - Fix a potential problem in mangling server private keys while
  5703. writing to disk (not triggered yet, as far as we know).
  5704. - Include the licenses for other free software we include in Tor,
  5705. now that we're shipping binary distributions more regularly.
  5706. Changes in version 0.0.9.1 - 2004-12-15
  5707. o Bugfixes on 0.0.9:
  5708. - Make hibernation actually work.
  5709. - Make HashedControlPassword config option work.
  5710. - When we're reporting event circuit status to a controller,
  5711. don't use the stream status code.
  5712. Changes in version 0.0.9 - 2004-12-12
  5713. o Bugfixes on 0.0.8.1 (Crashes and asserts):
  5714. - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
  5715. write() call will fail and we handle it there.
  5716. - When we run out of disk space, or other log writing error, don't
  5717. crash. Just stop logging to that log and continue.
  5718. - Fix isspace() and friends so they still make Solaris happy
  5719. but also so they don't trigger asserts on win32.
  5720. - Fix assert failure on malformed socks4a requests.
  5721. - Fix an assert bug where a hidden service provider would fail if
  5722. the first hop of his rendezvous circuit was down.
  5723. - Better handling of size_t vs int, so we're more robust on 64
  5724. bit platforms.
  5725. o Bugfixes on 0.0.8.1 (Win32):
  5726. - Make windows sockets actually non-blocking (oops), and handle
  5727. win32 socket errors better.
  5728. - Fix parse_iso_time on platforms without strptime (eg win32).
  5729. - win32: when being multithreaded, leave parent fdarray open.
  5730. - Better handling of winsock includes on non-MSV win32 compilers.
  5731. - Change our file IO stuff (especially wrt OpenSSL) so win32 is
  5732. happier.
  5733. - Make unit tests work on win32.
  5734. o Bugfixes on 0.0.8.1 (Path selection and streams):
  5735. - Calculate timeout for waiting for a connected cell from the time
  5736. we sent the begin cell, not from the time the stream started. If
  5737. it took a long time to establish the circuit, we would time out
  5738. right after sending the begin cell.
  5739. - Fix router_compare_addr_to_addr_policy: it was not treating a port
  5740. of * as always matching, so we were picking reject *:* nodes as
  5741. exit nodes too. Oops.
  5742. - When read() failed on a stream, we would close it without sending
  5743. back an end. So 'connection refused' would simply be ignored and
  5744. the user would get no response.
  5745. - Stop a sigpipe: when an 'end' cell races with eof from the app,
  5746. we shouldn't hold-open-until-flush if the eof arrived first.
  5747. - Let resolve conns retry/expire also, rather than sticking around
  5748. forever.
  5749. - Fix more dns related bugs: send back resolve_failed and end cells
  5750. more reliably when the resolve fails, rather than closing the
  5751. circuit and then trying to send the cell. Also attach dummy resolve
  5752. connections to a circuit *before* calling dns_resolve(), to fix
  5753. a bug where cached answers would never be sent in RESOLVED cells.
  5754. o Bugfixes on 0.0.8.1 (Circuits):
  5755. - Finally fix a bug that's been plaguing us for a year:
  5756. With high load, circuit package window was reaching 0. Whenever
  5757. we got a circuit-level sendme, we were reading a lot on each
  5758. socket, but only writing out a bit. So we would eventually reach
  5759. eof. This would be noticed and acted on even when there were still
  5760. bytes sitting in the inbuf.
  5761. - Use identity comparison, not nickname comparison, to choose which
  5762. half of circuit-ID-space each side gets to use. This is needed
  5763. because sometimes we think of a router as a nickname, and sometimes
  5764. as a hex ID, and we can't predict what the other side will do.
  5765. o Bugfixes on 0.0.8.1 (Other):
  5766. - Fix a whole slew of memory leaks.
  5767. - Disallow NDEBUG. We don't ever want anybody to turn off debug.
  5768. - If we are using select, make sure we stay within FD_SETSIZE.
  5769. - When poll() is interrupted, we shouldn't believe the revents values.
  5770. - Add a FAST_SMARTLIST define to optionally inline smartlist_get
  5771. and smartlist_len, which are two major profiling offenders.
  5772. - If do_hup fails, actually notice.
  5773. - Flush the log file descriptor after we print "Tor opening log file",
  5774. so we don't see those messages days later.
  5775. - Hidden service operators now correctly handle version 1 style
  5776. INTRODUCE1 cells (nobody generates them still, so not a critical
  5777. bug).
  5778. - Handle more errnos from accept() without closing the listener.
  5779. Some OpenBSD machines were closing their listeners because
  5780. they ran out of file descriptors.
  5781. - Some people had wrapped their tor client/server in a script
  5782. that would restart it whenever it died. This did not play well
  5783. with our "shut down if your version is obsolete" code. Now people
  5784. don't fetch a new directory if their local cached version is
  5785. recent enough.
  5786. - Make our autogen.sh work on ksh as well as bash.
  5787. - Better torrc example lines for dirbindaddress and orbindaddress.
  5788. - Improved bounds checking on parsed ints (e.g. config options and
  5789. the ones we find in directories.)
  5790. - Stop using separate defaults for no-config-file and
  5791. empty-config-file. Now you have to explicitly turn off SocksPort,
  5792. if you don't want it open.
  5793. - We were starting to daemonize before we opened our logs, so if
  5794. there were any problems opening logs, we would complain to stderr,
  5795. which wouldn't work, and then mysteriously exit.
  5796. - If a verified OR connects to us before he's uploaded his descriptor,
  5797. or we verify him and hup but he still has the original TLS
  5798. connection, then conn->nickname is still set like he's unverified.
  5799. o Code security improvements, inspired by Ilja:
  5800. - tor_snprintf wrapper over snprintf with consistent (though not C99)
  5801. overflow behavior.
  5802. - Replace sprintf with tor_snprintf. (I think they were all safe, but
  5803. hey.)
  5804. - Replace strcpy/strncpy with strlcpy in more places.
  5805. - Avoid strcat; use tor_snprintf or strlcat instead.
  5806. o Features (circuits and streams):
  5807. - New circuit building strategy: keep a list of ports that we've
  5808. used in the past 6 hours, and always try to have 2 circuits open
  5809. or on the way that will handle each such port. Seed us with port
  5810. 80 so web users won't complain that Tor is "slow to start up".
  5811. - Make kill -USR1 dump more useful stats about circuits.
  5812. - When warning about retrying or giving up, print the address, so
  5813. the user knows which one it's talking about.
  5814. - If you haven't used a clean circuit in an hour, throw it away,
  5815. just to be on the safe side. (This means after 6 hours a totally
  5816. unused Tor client will have no circuits open.)
  5817. - Support "foo.nickname.exit" addresses, to let Alice request the
  5818. address "foo" as viewed by exit node "nickname". Based on a patch
  5819. from Geoff Goodell.
  5820. - If your requested entry or exit node has advertised bandwidth 0,
  5821. pick it anyway.
  5822. - Be more greedy about filling up relay cells -- we try reading again
  5823. once we've processed the stuff we read, in case enough has arrived
  5824. to fill the last cell completely.
  5825. - Refuse application socks connections to port 0.
  5826. - Use only 0.0.9pre1 and later servers for resolve cells.
  5827. o Features (bandwidth):
  5828. - Hibernation: New config option "AccountingMax" lets you
  5829. set how many bytes per month (in each direction) you want to
  5830. allow your server to consume. Rather than spreading those
  5831. bytes out evenly over the month, we instead hibernate for some
  5832. of the month and pop up at a deterministic time, work until
  5833. the bytes are consumed, then hibernate again. Config option
  5834. "MonthlyAccountingStart" lets you specify which day of the month
  5835. your billing cycle starts on.
  5836. - Implement weekly/monthly/daily accounting: now you specify your
  5837. hibernation properties by
  5838. AccountingMax N bytes|KB|MB|GB|TB
  5839. AccountingStart day|week|month [day] HH:MM
  5840. Defaults to "month 1 0:00".
  5841. - Let bandwidth and interval config options be specified as 5 bytes,
  5842. kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
  5843. o Features (directories):
  5844. - New "router-status" line in directory, to better bind each verified
  5845. nickname to its identity key.
  5846. - Clients can ask dirservers for /dir.z to get a compressed version
  5847. of the directory. Only works for servers running 0.0.9, of course.
  5848. - Make clients cache directories and use them to seed their router
  5849. lists at startup. This means clients have a datadir again.
  5850. - Respond to content-encoding headers by trying to uncompress as
  5851. appropriate.
  5852. - Clients and servers now fetch running-routers; cache
  5853. running-routers; compress running-routers; serve compressed
  5854. running-routers.z
  5855. - Make moria2 advertise a dirport of 80, so people behind firewalls
  5856. will be able to get a directory.
  5857. - Http proxy support
  5858. - Dirservers translate requests for http://%s:%d/x to /x
  5859. - You can specify "HttpProxy %s[:%d]" and all dir fetches will
  5860. be routed through this host.
  5861. - Clients ask for /tor/x rather than /x for new enough dirservers.
  5862. This way we can one day coexist peacefully with apache.
  5863. - Clients specify a "Host: %s%d" http header, to be compatible
  5864. with more proxies, and so running squid on an exit node can work.
  5865. - Protect dirservers from overzealous descriptor uploading -- wait
  5866. 10 seconds after directory gets dirty, before regenerating.
  5867. o Features (packages and install):
  5868. - Add NSI installer contributed by J Doe.
  5869. - Apply NT service patch from Osamu Fujino. Still needs more work.
  5870. - Commit VC6 and VC7 workspace/project files.
  5871. - Commit a tor.spec for making RPM files, with help from jbash.
  5872. - Add contrib/torctl.in contributed by Glenn Fink.
  5873. - Make expand_filename handle ~ and ~username.
  5874. - Use autoconf to enable largefile support where necessary. Use
  5875. ftello where available, since ftell can fail at 2GB.
  5876. - Ship src/win32/ in the tarball, so people can use it to build.
  5877. - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
  5878. is broken.
  5879. o Features (ui controller):
  5880. - Control interface: a separate program can now talk to your
  5881. client/server over a socket, and get/set config options, receive
  5882. notifications of circuits and streams starting/finishing/dying,
  5883. bandwidth used, etc. The next step is to get some GUIs working.
  5884. Let us know if you want to help out. See doc/control-spec.txt .
  5885. - Ship a contrib/tor-control.py as an example script to interact
  5886. with the control port.
  5887. - "tor --hash-password zzyxz" will output a salted password for
  5888. use in authenticating to the control interface.
  5889. - Implement the control-spec's SAVECONF command, to write your
  5890. configuration to torrc.
  5891. - Get cookie authentication for the controller closer to working.
  5892. - When set_conf changes our server descriptor, upload a new copy.
  5893. But don't upload it too often if there are frequent changes.
  5894. o Features (config and command-line):
  5895. - Deprecate unofficial config option abbreviations, and abbreviations
  5896. not on the command line.
  5897. - Configuration infrastructure support for warning on obsolete
  5898. options.
  5899. - Give a slightly more useful output for "tor -h".
  5900. - Break DirFetchPostPeriod into:
  5901. - DirFetchPeriod for fetching full directory,
  5902. - StatusFetchPeriod for fetching running-routers,
  5903. - DirPostPeriod for posting server descriptor,
  5904. - RendPostPeriod for posting hidden service descriptors.
  5905. - New log format in config:
  5906. "Log minsev[-maxsev] stdout|stderr|syslog" or
  5907. "Log minsev[-maxsev] file /var/foo"
  5908. - DirPolicy config option, to let people reject incoming addresses
  5909. from their dirserver.
  5910. - "tor --list-fingerprint" will list your identity key fingerprint
  5911. and then exit.
  5912. - Make tor --version --version dump the cvs Id of every file.
  5913. - New 'MyFamily nick1,...' config option for a server to
  5914. specify other servers that shouldn't be used in the same circuit
  5915. with it. Only believed if nick1 also specifies us.
  5916. - New 'NodeFamily nick1,nick2,...' config option for a client to
  5917. specify nodes that it doesn't want to use in the same circuit.
  5918. - New 'Redirectexit pattern address:port' config option for a
  5919. server to redirect exit connections, e.g. to a local squid.
  5920. - Add "pass" target for RedirectExit, to make it easier to break
  5921. out of a sequence of RedirectExit rules.
  5922. - Make the dirservers file obsolete.
  5923. - Include a dir-signing-key token in directories to tell the
  5924. parsing entity which key is being used to sign.
  5925. - Remove the built-in bulky default dirservers string.
  5926. - New config option "Dirserver %s:%d [fingerprint]", which can be
  5927. repeated as many times as needed. If no dirservers specified,
  5928. default to moria1,moria2,tor26.
  5929. - Make 'Routerfile' config option obsolete.
  5930. - Discourage people from setting their dirfetchpostperiod more often
  5931. than once per minute.
  5932. o Features (other):
  5933. - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
  5934. get back to normal.)
  5935. - Accept *:706 (silc) in default exit policy.
  5936. - Implement new versioning format for post 0.1.
  5937. - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
  5938. log more informatively.
  5939. - Check clock skew for verified servers, but allow unverified
  5940. servers and clients to have any clock skew.
  5941. - Make sure the hidden service descriptors are at a random offset
  5942. from each other, to hinder linkability.
  5943. - Clients now generate a TLS cert too, in preparation for having
  5944. them act more like real nodes.
  5945. - Add a pure-C tor-resolve implementation.
  5946. - Use getrlimit and friends to ensure we can reach MaxConn (currently
  5947. 1024) file descriptors.
  5948. - Raise the max dns workers from 50 to 100.
  5949. Changes in version 0.0.8.1 - 2004-10-13
  5950. o Bugfixes:
  5951. - Fix a seg fault that can be triggered remotely for Tor
  5952. clients/servers with an open dirport.
  5953. - Fix a rare assert trigger, where routerinfos for entries in
  5954. our cpath would expire while we're building the path.
  5955. - Fix a bug in OutboundBindAddress so it (hopefully) works.
  5956. - Fix a rare seg fault for people running hidden services on
  5957. intermittent connections.
  5958. - Fix a bug in parsing opt keywords with objects.
  5959. - Fix a stale pointer assert bug when a stream detaches and
  5960. reattaches.
  5961. - Fix a string format vulnerability (probably not exploitable)
  5962. in reporting stats locally.
  5963. - Fix an assert trigger: sometimes launching circuits can fail
  5964. immediately, e.g. because too many circuits have failed recently.
  5965. - Fix a compile warning on 64 bit platforms.
  5966. Changes in version 0.0.8 - 2004-08-25
  5967. o Bugfixes:
  5968. - Made our unit tests compile again on OpenBSD 3.5, and tor
  5969. itself compile again on OpenBSD on a sparc64.
  5970. - We were neglecting milliseconds when logging on win32, so
  5971. everything appeared to happen at the beginning of each second.
  5972. - Check directory signature _before_ you decide whether you're
  5973. you're running an obsolete version and should exit.
  5974. - Check directory signature _before_ you parse the running-routers
  5975. list to decide who's running.
  5976. - Check return value of fclose while writing to disk, so we don't
  5977. end up with broken files when servers run out of disk space.
  5978. - Port it to SunOS 5.9 / Athena
  5979. - Fix two bugs in saving onion keys to disk when rotating, so
  5980. hopefully we'll get fewer people using old onion keys.
  5981. - Remove our mostly unused -- and broken -- hex_encode()
  5982. function. Use base16_encode() instead. (Thanks to Timo Lindfors
  5983. for pointing out this bug.)
  5984. - Only pick and establish intro points after we've gotten a
  5985. directory.
  5986. - Fix assert triggers: if the other side returns an address 0.0.0.0,
  5987. don't put it into the client dns cache.
  5988. - If a begin failed due to exit policy, but we believe the IP
  5989. address should have been allowed, switch that router to exitpolicy
  5990. reject *:* until we get our next directory.
  5991. o Protocol changes:
  5992. - 'Extend' relay cell payloads now include the digest of the
  5993. intended next hop's identity key. Now we can verify that we're
  5994. extending to the right router, and also extend to routers we
  5995. hadn't heard of before.
  5996. o Features:
  5997. - Tor nodes can now act as relays (with an advertised ORPort)
  5998. without being manually verified by the dirserver operators.
  5999. - Uploaded descriptors of unverified routers are now accepted
  6000. by the dirservers, and included in the directory.
  6001. - Verified routers are listed by nickname in the running-routers
  6002. list; unverified routers are listed as "$<fingerprint>".
  6003. - We now use hash-of-identity-key in most places rather than
  6004. nickname or addr:port, for improved security/flexibility.
  6005. - AllowUnverifiedNodes config option to let circuits choose no-name
  6006. routers in entry,middle,exit,introduction,rendezvous positions.
  6007. Allow middle and rendezvous positions by default.
  6008. - When picking unverified routers, skip those with low uptime and/or
  6009. low bandwidth, depending on what properties you care about.
  6010. - ClientOnly option for nodes that never want to become servers.
  6011. - Directory caching.
  6012. - "AuthoritativeDir 1" option for the official dirservers.
  6013. - Now other nodes (clients and servers) will cache the latest
  6014. directory they've pulled down.
  6015. - They can enable their DirPort to serve it to others.
  6016. - Clients will pull down a directory from any node with an open
  6017. DirPort, and check the signature/timestamp correctly.
  6018. - Authoritative dirservers now fetch directories from other
  6019. authdirservers, to stay better synced.
  6020. - Running-routers list tells who's down also, along with noting
  6021. if they're verified (listed by nickname) or unverified (listed
  6022. by hash-of-key).
  6023. - Allow dirservers to serve running-router list separately.
  6024. This isn't used yet.
  6025. - You can now fetch $DIRURL/running-routers to get just the
  6026. running-routers line, not the whole descriptor list. (But
  6027. clients don't use this yet.)
  6028. - Clients choose nodes proportional to advertised bandwidth.
  6029. - Clients avoid using nodes with low uptime as introduction points.
  6030. - Handle servers with dynamic IP addresses: don't just replace
  6031. options->Address with the resolved one at startup, and
  6032. detect our address right before we make a routerinfo each time.
  6033. - 'FascistFirewall' option to pick dirservers and ORs on specific
  6034. ports; plus 'FirewallPorts' config option to tell FascistFirewall
  6035. which ports are open. (Defaults to 80,443)
  6036. - Try other dirservers immediately if the one you try is down. This
  6037. should tolerate down dirservers better now.
  6038. - ORs connect-on-demand to other ORs
  6039. - If you get an extend cell to an OR you're not connected to,
  6040. connect, handshake, and forward the create cell.
  6041. - The authoritative dirservers stay connected to everybody,
  6042. and everybody stays connected to 0.0.7 servers, but otherwise
  6043. clients/servers expire unused connections after 5 minutes.
  6044. - When servers get a sigint, they delay 30 seconds (refusing new
  6045. connections) then exit. A second sigint causes immediate exit.
  6046. - File and name management:
  6047. - Look for .torrc if no CONFDIR "torrc" is found.
  6048. - If no datadir is defined, then choose, make, and secure ~/.tor
  6049. as datadir.
  6050. - If torrc not found, exitpolicy reject *:*.
  6051. - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
  6052. - If no nickname is defined, derive default from hostname.
  6053. - Rename secret key files, e.g. identity.key -> secret_id_key,
  6054. to discourage people from mailing their identity key to tor-ops.
  6055. - Refuse to build a circuit before the directory has arrived --
  6056. it won't work anyway, since you won't know the right onion keys
  6057. to use.
  6058. - Parse tor version numbers so we can do an is-newer-than check
  6059. rather than an is-in-the-list check.
  6060. - New socks command 'resolve', to let us shim gethostbyname()
  6061. locally.
  6062. - A 'tor_resolve' script to access the socks resolve functionality.
  6063. - A new socks-extensions.txt doc file to describe our
  6064. interpretation and extensions to the socks protocols.
  6065. - Add a ContactInfo option, which gets published in descriptor.
  6066. - Write tor version at the top of each log file
  6067. - New docs in the tarball:
  6068. - tor-doc.html.
  6069. - Document that you should proxy your SSL traffic too.
  6070. - Log a warning if the user uses an unsafe socks variant, so people
  6071. are more likely to learn about privoxy or socat.
  6072. - Log a warning if you're running an unverified server, to let you
  6073. know you might want to get it verified.
  6074. - Change the default exit policy to reject the default edonkey,
  6075. kazaa, gnutella ports.
  6076. - Add replace_file() to util.[ch] to handle win32's rename().
  6077. - Publish OR uptime in descriptor (and thus in directory) too.
  6078. - Remember used bandwidth (both in and out), and publish 15-minute
  6079. snapshots for the past day into our descriptor.
  6080. - Be more aggressive about trying to make circuits when the network
  6081. has changed (e.g. when you unsuspend your laptop).
  6082. - Check for time skew on http headers; report date in response to
  6083. "GET /".
  6084. - If the entrynode config line has only one node, don't pick it as
  6085. an exitnode.
  6086. - Add strict{entry|exit}nodes config options. If set to 1, then
  6087. we refuse to build circuits that don't include the specified entry
  6088. or exit nodes.
  6089. - OutboundBindAddress config option, to bind to a specific
  6090. IP address for outgoing connect()s.
  6091. - End truncated log entries (e.g. directories) with "[truncated]".
  6092. Changes in version 0.0.7.3 - 2004-08-12
  6093. o Stop dnsworkers from triggering an assert failure when you
  6094. ask them to resolve the host "".
  6095. Changes in version 0.0.7.2 - 2004-07-07
  6096. o A better fix for the 0.0.0.0 problem, that will hopefully
  6097. eliminate the remaining related assertion failures.
  6098. Changes in version 0.0.7.1 - 2004-07-04
  6099. o When an address resolves to 0.0.0.0, treat it as a failed resolve,
  6100. since internally we use 0.0.0.0 to signify "not yet resolved".
  6101. Changes in version 0.0.7 - 2004-06-07
  6102. o Fixes for crashes and other obnoxious bugs:
  6103. - Fix an epipe bug: sometimes when directory connections failed
  6104. to connect, we would give them a chance to flush before closing
  6105. them.
  6106. - When we detached from a circuit because of resolvefailed, we
  6107. would immediately try the same circuit twice more, and then
  6108. give up on the resolve thinking we'd tried three different
  6109. exit nodes.
  6110. - Limit the number of intro circuits we'll attempt to build for a
  6111. hidden service per 15-minute period.
  6112. - Check recommended-software string *early*, before actually parsing
  6113. the directory. Thus we can detect an obsolete version and exit,
  6114. even if the new directory format doesn't parse.
  6115. o Fixes for security bugs:
  6116. - Remember which nodes are dirservers when you startup, and if a
  6117. random OR enables his dirport, don't automatically assume he's
  6118. a trusted dirserver.
  6119. o Other bugfixes:
  6120. - Directory connections were asking the wrong poll socket to
  6121. start writing, and not asking themselves to start writing.
  6122. - When we detached from a circuit because we sent a begin but
  6123. didn't get a connected, we would use it again the first time;
  6124. but after that we would correctly switch to a different one.
  6125. - Stop warning when the first onion decrypt attempt fails; they
  6126. will sometimes legitimately fail now that we rotate keys.
  6127. - Override unaligned-access-ok check when $host_cpu is ia64 or
  6128. arm. Apparently they allow it but the kernel whines.
  6129. - Dirservers try to reconnect periodically too, in case connections
  6130. have failed.
  6131. - Fix some memory leaks in directory servers.
  6132. - Allow backslash in Win32 filenames.
  6133. - Made Tor build complain-free on FreeBSD, hopefully without
  6134. breaking other BSD builds. We'll see.
  6135. - Check directory signatures based on name of signer, not on whom
  6136. we got the directory from. This will let us cache directories more
  6137. easily.
  6138. - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
  6139. settings too.
  6140. o Features:
  6141. - Doxygen markup on all functions and global variables.
  6142. - Make directory functions update routerlist, not replace it. So
  6143. now directory disagreements are not so critical a problem.
  6144. - Remove the upper limit on number of descriptors in a dirserver's
  6145. directory (not that we were anywhere close).
  6146. - Allow multiple logfiles at different severity ranges.
  6147. - Allow *BindAddress to specify ":port" rather than setting *Port
  6148. separately. Allow multiple instances of each BindAddress config
  6149. option, so you can bind to multiple interfaces if you want.
  6150. - Allow multiple exit policy lines, which are processed in order.
  6151. Now we don't need that huge line with all the commas in it.
  6152. - Enable accept/reject policies on SOCKS connections, so you can bind
  6153. to 0.0.0.0 but still control who can use your OP.
  6154. - Updated the man page to reflect these features.
  6155. Changes in version 0.0.6.2 - 2004-05-16
  6156. o Our integrity-checking digest was checking only the most recent cell,
  6157. not the previous cells like we'd thought.
  6158. Thanks to Stefan Mark for finding the flaw!
  6159. Changes in version 0.0.6.1 - 2004-05-06
  6160. o Fix two bugs in our AES counter-mode implementation (this affected
  6161. onion-level stream encryption, but not TLS-level). It turns
  6162. out we were doing something much more akin to a 16-character
  6163. polyalphabetic cipher. Oops.
  6164. Thanks to Stefan Mark for finding the flaw!
  6165. o Retire moria3 as a directory server, and add tor26 as a directory
  6166. server.
  6167. Changes in version 0.0.6 - 2004-05-02
  6168. o Features:
  6169. - Hidden services and rendezvous points are implemented. Go to
  6170. http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
  6171. hidden services. (This only works via a socks4a proxy such as
  6172. Privoxy, and currently it's quite slow.)
  6173. - We now rotate link (tls context) keys and onion keys.
  6174. - CREATE cells now include oaep padding, so you can tell
  6175. if you decrypted them correctly.
  6176. - Retry stream correctly when we fail to connect because of
  6177. exit-policy-reject (should try another) or can't-resolve-address.
  6178. - When we hup a dirserver and we've *removed* a server from the
  6179. approved-routers list, now we remove that server from the
  6180. in-memory directories too.
  6181. - Add bandwidthburst to server descriptor.
  6182. - Directories now say which dirserver signed them.
  6183. - Use a tor_assert macro that logs failed assertions too.
  6184. - Since we don't support truncateds much, don't bother sending them;
  6185. just close the circ.
  6186. - Fetch randomness from /dev/urandom better (not via fopen/fread)
  6187. - Better debugging for tls errors
  6188. - Set Content-Type on the directory and hidserv descriptor.
  6189. - Remove IVs from cipher code, since AES-ctr has none.
  6190. o Bugfixes:
  6191. - Fix an assert trigger for exit nodes that's been plaguing us since
  6192. the days of 0.0.2prexx (thanks weasel!)
  6193. - Fix a bug where we were closing tls connections intermittently.
  6194. It turns out openssl keeps its errors around -- so if an error
  6195. happens, and you don't ask about it, and then another openssl
  6196. operation happens and succeeds, and you ask if there was an error,
  6197. it tells you about the first error.
  6198. - Fix a bug that's been lurking since 27 may 03 (!)
  6199. When passing back a destroy cell, we would use the wrong circ id.
  6200. - Don't crash if a conn that sent a begin has suddenly lost its circuit.
  6201. - Some versions of openssl have an SSL_pending function that erroneously
  6202. returns bytes when there is a non-application record pending.
  6203. - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
  6204. o We were using an array of length zero in a few places.
  6205. o Win32's gethostbyname can't resolve an IP to an IP.
  6206. o Win32's close can't close a socket.
  6207. o Handle windows socket errors correctly.
  6208. o Portability:
  6209. - check for <sys/limits.h> so we build on FreeBSD again, and
  6210. <machine/limits.h> for NetBSD.
  6211. Changes in version 0.0.5 - 2004-03-30
  6212. o Install torrc as torrc.sample -- we no longer clobber your
  6213. torrc. (Woo!)
  6214. o Fix mangled-state bug in directory fetching (was causing sigpipes).
  6215. o Only build circuits after we've fetched the directory: clients were
  6216. using only the directory servers before they'd fetched a directory.
  6217. This also means longer startup time; so it goes.
  6218. o Fix an assert trigger where an OP would fail to handshake, and we'd
  6219. expect it to have a nickname.
  6220. o Work around a tsocks bug: do a socks reject when AP connection dies
  6221. early, else tsocks goes into an infinite loop.
  6222. o Hold socks connection open until reply is flushed (if possible)
  6223. o Make exit nodes resolve IPs to IPs immediately, rather than asking
  6224. the dns farm to do it.
  6225. o Fix c99 aliasing warnings in rephist.c
  6226. o Don't include server descriptors that are older than 24 hours in the
  6227. directory.
  6228. o Give socks 'reject' replies their whole 15s to attempt to flush,
  6229. rather than seeing the 60s timeout and assuming the flush had failed.
  6230. o Clean automake droppings from the cvs repository
  6231. o Add in a 'notice' log level for things the operator should hear
  6232. but that aren't warnings
  6233. Changes in version 0.0.4 - 2004-03-26
  6234. o When connecting to a dirserver or OR and the network is down,
  6235. we would crash.
  6236. Changes in version 0.0.3 - 2004-03-26
  6237. o Warn and fail if server chose a nickname with illegal characters
  6238. o Port to Solaris and Sparc:
  6239. - include missing header fcntl.h
  6240. - have autoconf find -lsocket -lnsl automatically
  6241. - deal with hardware word alignment
  6242. - make uname() work (solaris has a different return convention)
  6243. - switch from using signal() to sigaction()
  6244. o Preliminary work on reputation system:
  6245. - Keep statistics on success/fail of connect attempts; they're published
  6246. by kill -USR1 currently.
  6247. - Add a RunTesting option to try to learn link state by creating test
  6248. circuits, even when SocksPort is off.
  6249. - Remove unused open circuits when there are too many.
  6250. Changes in version 0.0.2 - 2004-03-19
  6251. - Include strlcpy and strlcat for safer string ops
  6252. - define INADDR_NONE so we compile (but still not run) on solaris
  6253. Changes in version 0.0.2pre27 - 2004-03-14
  6254. o Bugfixes:
  6255. - Allow internal tor networks (we were rejecting internal IPs,
  6256. now we allow them if they're set explicitly).
  6257. - And fix a few endian issues.
  6258. Changes in version 0.0.2pre26 - 2004-03-14
  6259. o New features:
  6260. - If a stream times out after 15s without a connected cell, don't
  6261. try that circuit again: try a new one.
  6262. - Retry streams at most 4 times. Then give up.
  6263. - When a dirserver gets a descriptor from an unknown router, it
  6264. logs its fingerprint (so the dirserver operator can choose to
  6265. accept it even without mail from the server operator).
  6266. - Inform unapproved servers when we reject their descriptors.
  6267. - Make tor build on Windows again. It works as a client, who knows
  6268. about as a server.
  6269. - Clearer instructions in the torrc for how to set up a server.
  6270. - Be more efficient about reading fd's when our global token bucket
  6271. (used for rate limiting) becomes empty.
  6272. o Bugfixes:
  6273. - Stop asserting that computers always go forward in time. It's
  6274. simply not true.
  6275. - When we sent a cell (e.g. destroy) and then marked an OR connection
  6276. expired, we might close it before finishing a flush if the other
  6277. side isn't reading right then.
  6278. - Don't allow dirservers to start if they haven't defined
  6279. RecommendedVersions
  6280. - We were caching transient dns failures. Oops.
  6281. - Prevent servers from publishing an internal IP as their address.
  6282. - Address a strcat vulnerability in circuit.c
  6283. Changes in version 0.0.2pre25 - 2004-03-04
  6284. o New features:
  6285. - Put the OR's IP in its router descriptor, not its fqdn. That way
  6286. we'll stop being stalled by gethostbyname for nodes with flaky dns,
  6287. e.g. poblano.
  6288. o Bugfixes:
  6289. - If the user typed in an address that didn't resolve, the server
  6290. crashed.
  6291. Changes in version 0.0.2pre24 - 2004-03-03
  6292. o Bugfixes:
  6293. - Fix an assertion failure in dns.c, where we were trying to dequeue
  6294. a pending dns resolve even if it wasn't pending
  6295. - Fix a spurious socks5 warning about still trying to write after the
  6296. connection is finished.
  6297. - Hold certain marked_for_close connections open until they're finished
  6298. flushing, rather than losing bytes by closing them too early.
  6299. - Correctly report the reason for ending a stream
  6300. - Remove some duplicate calls to connection_mark_for_close
  6301. - Put switch_id and start_daemon earlier in the boot sequence, so it
  6302. will actually try to chdir() to options.DataDirectory
  6303. - Make 'make test' exit(1) if a test fails; fix some unit tests
  6304. - Make tor fail when you use a config option it doesn't know about,
  6305. rather than warn and continue.
  6306. - Make --version work
  6307. - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
  6308. Changes in version 0.0.2pre23 - 2004-02-29
  6309. o New features:
  6310. - Print a statement when the first circ is finished, so the user
  6311. knows it's working.
  6312. - If a relay cell is unrecognized at the end of the circuit,
  6313. send back a destroy. (So attacks to mutate cells are more
  6314. clearly thwarted.)
  6315. - New config option 'excludenodes' to avoid certain nodes for circuits.
  6316. - When it daemonizes, it chdir's to the DataDirectory rather than "/",
  6317. so you can collect coredumps there.
  6318. o Bugfixes:
  6319. - Fix a bug in tls flushing where sometimes data got wedged and
  6320. didn't flush until more data got sent. Hopefully this bug was
  6321. a big factor in the random delays we were seeing.
  6322. - Make 'connected' cells include the resolved IP, so the client
  6323. dns cache actually gets populated.
  6324. - Disallow changing from ORPort=0 to ORPort>0 on hup.
  6325. - When we time-out on a stream and detach from the circuit, send an
  6326. end cell down it first.
  6327. - Only warn about an unknown router (in exitnodes, entrynodes,
  6328. excludenodes) after we've fetched a directory.
  6329. Changes in version 0.0.2pre22 - 2004-02-26
  6330. o New features:
  6331. - Servers publish less revealing uname information in descriptors.
  6332. - More memory tracking and assertions, to crash more usefully when
  6333. errors happen.
  6334. - If the default torrc isn't there, just use some default defaults.
  6335. Plus provide an internal dirservers file if they don't have one.
  6336. - When the user tries to use Tor as an http proxy, give them an http
  6337. 501 failure explaining that we're a socks proxy.
  6338. - Dump a new router.desc on hup, to help confused people who change
  6339. their exit policies and then wonder why router.desc doesn't reflect
  6340. it.
  6341. - Clean up the generic tor.sh init script that we ship with.
  6342. o Bugfixes:
  6343. - If the exit stream is pending on the resolve, and a destroy arrives,
  6344. then the stream wasn't getting removed from the pending list. I
  6345. think this was the one causing recent server crashes.
  6346. - Use a more robust poll on OSX 10.3, since their poll is flaky.
  6347. - When it couldn't resolve any dirservers, it was useless from then on.
  6348. Now it reloads the RouterFile (or default dirservers) if it has no
  6349. dirservers.
  6350. - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
  6351. many users don't even *have* a /usr/local/sbin/.
  6352. Changes in version 0.0.2pre21 - 2004-02-18
  6353. o New features:
  6354. - There's a ChangeLog file that actually reflects the changelog.
  6355. - There's a 'torify' wrapper script, with an accompanying
  6356. tor-tsocks.conf, that simplifies the process of using tsocks for
  6357. tor. It even has a man page.
  6358. - The tor binary gets installed to sbin rather than bin now.
  6359. - Retry streams where the connected cell hasn't arrived in 15 seconds
  6360. - Clean up exit policy handling -- get the default out of the torrc,
  6361. so we can update it without forcing each server operator to fix
  6362. his/her torrc.
  6363. - Allow imaps and pop3s in default exit policy
  6364. o Bugfixes:
  6365. - Prevent picking middleman nodes as the last node in the circuit
  6366. Changes in version 0.0.2pre20 - 2004-01-30
  6367. o New features:
  6368. - We now have a deb package, and it's in debian unstable. Go to
  6369. it, apt-getters. :)
  6370. - I've split the TotalBandwidth option into BandwidthRate (how many
  6371. bytes per second you want to allow, long-term) and
  6372. BandwidthBurst (how many bytes you will allow at once before the cap
  6373. kicks in). This better token bucket approach lets you, say, set
  6374. BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
  6375. performance while not exceeding your monthly bandwidth quota.
  6376. - Push out a tls record's worth of data once you've got it, rather
  6377. than waiting until you've read everything waiting to be read. This
  6378. may improve performance by pipelining better. We'll see.
  6379. - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
  6380. from failed circuits (if they haven't been connected yet) and attach
  6381. to new ones.
  6382. - Expire old streams that haven't managed to connect. Some day we'll
  6383. have them reattach to new circuits instead.
  6384. o Bugfixes:
  6385. - Fix several memory leaks that were causing servers to become bloated
  6386. after a while.
  6387. - Fix a few very rare assert triggers. A few more remain.
  6388. - Setuid to User _before_ complaining about running as root.
  6389. Changes in version 0.0.2pre19 - 2004-01-07
  6390. o Bugfixes:
  6391. - Fix deadlock condition in dns farm. We were telling a child to die by
  6392. closing the parent's file descriptor to him. But newer children were
  6393. inheriting the open file descriptor from the parent, and since they
  6394. weren't closing it, the socket never closed, so the child never read
  6395. eof, so he never knew to exit. Similarly, dns workers were holding
  6396. open other sockets, leading to all sorts of chaos.
  6397. - New cleaner daemon() code for forking and backgrounding.
  6398. - If you log to a file, it now prints an entry at the top of the
  6399. logfile so you know it's working.
  6400. - The onionskin challenge length was 30 bytes longer than necessary.
  6401. - Started to patch up the spec so it's not quite so out of date.
  6402. Changes in version 0.0.2pre18 - 2004-01-02
  6403. o Bugfixes:
  6404. - Fix endian issues with the 'integrity' field in the relay header.
  6405. - Fix a potential bug where connections in state
  6406. AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
  6407. Changes in version 0.0.2pre17 - 2003-12-30
  6408. o Bugfixes:
  6409. - Made --debuglogfile (or any second log file, actually) work.
  6410. - Resolved an edge case in get_unique_circ_id_by_conn where a smart
  6411. adversary could force us into an infinite loop.
  6412. o Features:
  6413. - Each onionskin handshake now includes a hash of the computed key,
  6414. to prove the server's identity and help perfect forward secrecy.
  6415. - Changed cell size from 256 to 512 bytes (working toward compatibility
  6416. with MorphMix).
  6417. - Changed cell length to 2 bytes, and moved it to the relay header.
  6418. - Implemented end-to-end integrity checking for the payloads of
  6419. relay cells.
  6420. - Separated streamid from 'recognized' (otherwise circuits will get
  6421. messed up when we try to have streams exit from the middle). We
  6422. use the integrity-checking to confirm that a cell is addressed to
  6423. this hop.
  6424. - Randomize the initial circid and streamid values, so an adversary who
  6425. breaks into a node can't learn how many circuits or streams have
  6426. been made so far.
  6427. Changes in version 0.0.2pre16 - 2003-12-14
  6428. o Bugfixes:
  6429. - Fixed a bug that made HUP trigger an assert
  6430. - Fixed a bug where a circuit that immediately failed wasn't being
  6431. counted as a failed circuit in counting retries.
  6432. o Features:
  6433. - Now we close the circuit when we get a truncated cell: otherwise we're
  6434. open to an anonymity attack where a bad node in the path truncates
  6435. the circuit and then we open streams at him.
  6436. - Add port ranges to exit policies
  6437. - Add a conservative default exit policy
  6438. - Warn if you're running tor as root
  6439. - on HUP, retry OR connections and close/rebind listeners
  6440. - options.EntryNodes: try these nodes first when picking the first node
  6441. - options.ExitNodes: if your best choices happen to include any of
  6442. your preferred exit nodes, you choose among just those preferred
  6443. exit nodes.
  6444. - options.ExcludedNodes: nodes that are never picked in path building
  6445. Changes in version 0.0.2pre15 - 2003-12-03
  6446. o Robustness and bugfixes:
  6447. - Sometimes clients would cache incorrect DNS resolves, which would
  6448. really screw things up.
  6449. - An OP that goes offline would slowly leak all its sockets and stop
  6450. working.
  6451. - A wide variety of bugfixes in exit node selection, exit policy
  6452. handling, and processing pending streams when a new circuit is
  6453. established.
  6454. - Pick nodes for a path only from those the directory says are up
  6455. - Choose randomly from all running dirservers, not always the first one
  6456. - Increase allowed http header size for directory fetch.
  6457. - Stop writing to stderr (if we're daemonized it will be closed).
  6458. - Enable -g always, so cores will be more useful to me.
  6459. - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
  6460. o Documentation:
  6461. - Wrote a man page. It lists commonly used options.
  6462. o Configuration:
  6463. - Change default loglevel to warn.
  6464. - Make PidFile default to null rather than littering in your CWD.
  6465. - OnionRouter config option is now obsolete. Instead it just checks
  6466. ORPort>0.
  6467. - Moved to a single unified torrc file for both clients and servers.
  6468. Changes in version 0.0.2pre14 - 2003-11-29
  6469. o Robustness and bugfixes:
  6470. - Force the admin to make the DataDirectory himself
  6471. - to get ownership/permissions right
  6472. - so clients no longer make a DataDirectory and then never use it
  6473. - fix bug where a client who was offline for 45 minutes would never
  6474. pull down a directory again
  6475. - fix (or at least hide really well) the dns assert bug that was
  6476. causing server crashes
  6477. - warnings and improved robustness wrt clockskew for certs
  6478. - use the native daemon(3) to daemonize, when available
  6479. - exit if bind() fails
  6480. - exit if neither socksport nor orport is defined
  6481. - include our own tor_timegm (Win32 doesn't have its own)
  6482. - bugfix for win32 with lots of connections
  6483. - fix minor bias in PRNG
  6484. - make dirserver more robust to corrupt cached directory
  6485. o Documentation:
  6486. - Wrote the design document (woo)
  6487. o Circuit building and exit policies:
  6488. - Circuits no longer try to use nodes that the directory has told them
  6489. are down.
  6490. - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
  6491. bitcounts (18.0.0.0/8).
  6492. - Make AP connections standby for a circuit if no suitable circuit
  6493. exists, rather than failing
  6494. - Circuits choose exit node based on addr/port, exit policies, and
  6495. which AP connections are standing by
  6496. - Bump min pathlen from 2 to 3
  6497. - Relay end cells have a payload to describe why the stream ended.
  6498. - If the stream failed because of exit policy, try again with a new
  6499. circuit.
  6500. - Clients have a dns cache to remember resolved addresses.
  6501. - Notice more quickly when we have no working circuits
  6502. o Configuration:
  6503. - APPort is now called SocksPort
  6504. - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
  6505. where to bind
  6506. - RecommendedVersions is now a config variable rather than
  6507. hardcoded (for dirservers)
  6508. - Reloads config on HUP
  6509. - Usage info on -h or --help
  6510. - If you set User and Group config vars, it'll setu/gid to them.
  6511. Changes in version 0.0.2pre13 - 2003-10-19
  6512. o General stability:
  6513. - SSL_write no longer fails when it returns WANTWRITE and the number
  6514. of bytes in the buf has changed by the next SSL_write call.
  6515. - Fix segfault fetching directory when network is down
  6516. - Fix a variety of minor memory leaks
  6517. - Dirservers reload the fingerprints file on HUP, so I don't have
  6518. to take down the network when I approve a new router
  6519. - Default server config file has explicit Address line to specify fqdn
  6520. o Buffers:
  6521. - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
  6522. - Make listener connections not ever alloc bufs
  6523. o Autoconf improvements:
  6524. - don't clobber an external CFLAGS in ./configure
  6525. - Make install now works
  6526. - create var/lib/tor on make install
  6527. - autocreate a tor.sh initscript to help distribs
  6528. - autocreate the torrc and sample-server-torrc with correct paths
  6529. o Log files and Daemonizing now work:
  6530. - If --DebugLogFile is specified, log to it at -l debug
  6531. - If --LogFile is specified, use it instead of commandline
  6532. - If --RunAsDaemon is set, tor forks and backgrounds on startup