Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-15T23:38:04Zhttps://gitlab.torproject.org/legacy/trac/-/issues/20209Torbrowser 6.5a3 packages now signed with sha1, not sha5122020-06-15T23:38:04ZRoger DingledineTorbrowser 6.5a3 packages now signed with sha1, not sha512```
$ gpg -v torbrowser-install-6.0.5_en-US.exe.asc
gpg: assuming signed data in `torbrowser-install-6.0.5_en-US.exe'
gpg: Signature made Fri 16 Sep 2016 07:53:01 AM EDT
gpg: using RSA key 2E1AC68ED40814E0
gpg: using subke...```
$ gpg -v torbrowser-install-6.0.5_en-US.exe.asc
gpg: assuming signed data in `torbrowser-install-6.0.5_en-US.exe'
gpg: Signature made Fri 16 Sep 2016 07:53:01 AM EDT
gpg: using RSA key 2E1AC68ED40814E0
gpg: using subkey 2E1AC68ED40814E0 instead of primary key 4E2C6E8793298290
gpg: using PGP trust model
gpg: Good signature from "Tor Browser Developers (signing key) <torbrowser@torproject.org>"
gpg: binary signature, digest algorithm SHA512
```
compared to
```
$ gpg -v torbrowser-install-6.5a3_en-US.exe.asc
gpg: armor header: Version: GnuPG v1
gpg: assuming signed data in `torbrowser-install-6.5a3_en-US.exe'
gpg: Signature made Tue 20 Sep 2016 11:10:10 AM EDT
gpg: using RSA key D1483FA6C3C07136
gpg: using subkey D1483FA6C3C07136 instead of primary key 4E2C6E8793298290
gpg: using PGP trust model
gpg: Good signature from "Tor Browser Developers (signing key) <torbrowser@torproject.org>"
gpg: binary signature, digest algorithm SHA1
```
What made us switch to SHA1 for the latest alpha build? Is this some bug in our release process?https://gitlab.torproject.org/legacy/trac/-/issues/20057inconsistent Torbutton behavior when control port config is missing2020-06-16T01:28:01ZMark Smithinconsistent Torbutton behavior when control port config is missingTorbutton is inconsistent in how it handles missing control port configuration. Some code disables features if one or more pieces of information needed to access the control port are missing (e.g., New Identity is disabled if there is no...Torbutton is inconsistent in how it handles missing control port configuration. Some code disables features if one or more pieces of information needed to access the control port are missing (e.g., New Identity is disabled if there is no control port socket or TCP port). In other cases, defaults are used (e.g., the circuit display uses a default port of 9151). We should decide what behavior we want and modify the code to be consistent with it.https://gitlab.torproject.org/legacy/trac/-/issues/18860Reply button text and text editing Dingbats in Trac are not visible on Gnu+Li...2020-06-15T23:34:39ZGeorg KoppenReply button text and text editing Dingbats in Trac are not visible on Gnu+Linux TBBStrangely, the text on the reply button in our bug tracker is not visible with Tor Browser based on ESR45. I have no such issues with 6.0a4. The security slider setting does not matter. This is on a Linux box.Strangely, the text on the reply button in our bug tracker is not visible with Tor Browser based on ESR45. I have no such issues with 6.0a4. The security slider setting does not matter. This is on a Linux box.https://gitlab.torproject.org/legacy/trac/-/issues/16757Verify that new DOM properties are really disabled2020-06-13T17:40:40ZMike PerryVerify that new DOM properties are really disabledIn https://lists.torproject.org/pipermail/tor-qa/2015-August/000667.html, boklm notes:
```
We have the following DOM objects that were not present in esr31:
onlanguagechange, mozRequestOverfill, back, forward, home, openDialog,
control...In https://lists.torproject.org/pipermail/tor-qa/2015-August/000667.html, boklm notes:
```
We have the following DOM objects that were not present in esr31:
onlanguagechange, mozRequestOverfill, back, forward, home, openDialog,
controllers, realFrameElement, MozSelfSupport, _content, Symbol,
WeakSet, HTMLPictureElement, AnimationEffect, PerformanceMeasure,
PluginCrashedEvent, MenuBoxObject, ScrollViewChangeEvent,
SelectionStateChangedEvent, DOMMatrixReadOnly, DOMMatrix,
PopupBoxObject, AnimationTimeline, PerformanceMark, DOMApplication,
IDBMutableFile, StereoPannerNode, CameraDetectedFace,
CameraStateChangeEvent, CSSCounterStyleRule, CameraRecorderVideoProfile,
CameraRecorderProfile, CameraRecorderProfiles, AnonymousContent,
NamedNodeMap, DOMApplicationsManager, ContentProcessMessageManager,
CameraConfigurationEvent, HTMLAllCollection, PromiseDebugging,
SubtleCrypto, Animation, CameraRecorderAudioProfile, RadioNodeList,
WindowRoot, CameraClosedEvent, CryptoKey, CameraFacesDetectedEvent,
MozSettingsTransactionEvent, IDBFileRequest, BroadcastChannel,
MessageChannel, AnimationPlayer
```
Some of those should have been disabled by various prefs we have set (in particular PerformanceMeasure, PerformanceMark, and the IDB objects). We should look into that. Hopefully they are just empty placeholders. Also, the camera stuff should have been compiled out and also disabled via the peerconnection prefs, I thought.https://gitlab.torproject.org/legacy/trac/-/issues/14271Make Torbutton work with Unix Domain Socket option2020-06-15T23:23:17ZGeorg KoppenMake Torbutton work with Unix Domain Socket optionEven if it is only for *NIX systems first, we should modify Torbutton to work with the Unix Domain Socket option.Even if it is only for *NIX systems first, we should modify Torbutton to work with the Unix Domain Socket option.Kathleen BradeKathleen Brade