octoleo/syncthing
1
0
Fork 0
mirror of https://github.com/octoleo/syncthing.git synced 2024-12-23 11:28:59 +00:00
Code Issues Packages Projects Releases Wiki Activity
a7f7058636
syncthing/test/h2/config.xml

106 lines
5.3 KiB
XML
Raw Normal View History

gui: Hide "Failed Items" unless there is an actual failure (fixes #3647) Since delta indexes it's perfectly normal for us to need files that are currently unavailable due to devices being disconnected. This doesn't imply a failure, so we should not show the "Failed Items" line and corresponding eternal spinner (since it would never be filled in, since there is no failure). We still show state "Out of Sync" (correct) and the list of files we need (correct).
2016-10-17 11:35:30 +00:00
<configuration version="16">
test: Update test configs to latest format
2016-05-31 08:36:33 +00:00
<folder id="default" label="" path="s2/" type="readwrite" rescanIntervalS="15" ignorePerms="false" autoNormalize="true">
Rename Repository -> Folder, Node -> Device (fixes #739)
2014-09-28 11:00:38 +00:00
<device id="I6KAH76-66SLLLB-5PFXSOA-UFJCDZC-YAOMLEK-CP2GB32-BV5RQST-3PSROAU"></device>
Generate ECDSA keys instead of RSA This replaces the current 3072 bit RSA certificates with 384 bit ECDSA certificates. The advantage is these certificates are smaller and essentially instantaneous to generate. According to RFC4492 (ECC Cipher Suites for TLS), Table 1: Comparable Key Sizes, ECC has comparable strength to 3072 bit RSA at 283 bits - so we exceed that. There is no compatibility issue with existing Syncthing code - this is verified by the integration test ("h2" instance has the new certificate). There are browsers out there that don't understand ECC certificates yet, although I think they're dying out. In the meantime, I've retained the RSA code for the HTTPS certificate, but pulled it down to 2048 bits. I don't think a higher security level there is motivated, is this matches current industry standard for HTTPS certificates.
2015-11-27 08:09:39 +00:00
<device id="MRIW7OK-NETT3M4-N6SBWME-N25O76W-YJKVXPH-FUMQJ3S-P57B74J-GBITBAC"></device>
Rename Repository -> Folder, Node -> Device (fixes #739)
2014-09-28 11:00:38 +00:00
<device id="373HSRP-QLPNLIE-JYKZVQF-P4PKZ63-R2ZE6K3-YD442U2-JHBGBQG-WWXAHAU"></device>
Update test configs to v11
2015-08-14 12:19:43 +00:00
<minDiskFreePct>1</minDiskFreePct>
Don't start model until services have been added (fixes #1969)
2015-06-20 18:04:47 +00:00
<versioning type="trashcan">
<param key="cleanoutDays" val="1"></param>
Move index to index-v0.11.0.db (new format) and centralize location config
2015-03-29 10:55:27 +00:00
</versioning>
Data race: ProgressEmitter (debug output only)
2014-11-29 21:51:13 +00:00
<copiers>1</copiers>
<pullers>16</pullers>
Add renames to integration tests
2014-12-20 23:12:12 +00:00
<hashers>0</hashers>
Don't start model until services have been added (fixes #1969)
2015-06-20 18:04:47 +00:00
<order>random</order>
Update test configs to v11
2015-08-14 12:19:43 +00:00
<ignoreDelete>false</ignoreDelete>
Update test configs to modern v0.12 defaults
2015-10-22 06:06:17 +00:00
<scanProgressIntervalS>0</scanProgressIntervalS>
<pullerSleepS>0</pullerSleepS>
<pullerPauseS>0</pullerPauseS>
Include maxConflicts -1 in test configs
2015-10-19 13:09:54 +00:00
<maxConflicts>-1</maxConflicts>
Generate ECDSA keys instead of RSA This replaces the current 3072 bit RSA certificates with 384 bit ECDSA certificates. The advantage is these certificates are smaller and essentially instantaneous to generate. According to RFC4492 (ECC Cipher Suites for TLS), Table 1: Comparable Key Sizes, ECC has comparable strength to 3072 bit RSA at 283 bits - so we exceed that. There is no compatibility issue with existing Syncthing code - this is verified by the integration test ("h2" instance has the new certificate). There are browsers out there that don't understand ECC certificates yet, although I think they're dying out. In the meantime, I've retained the RSA code for the HTTPS certificate, but pulled it down to 2048 bits. I don't think a higher security level there is motivated, is this matches current industry standard for HTTPS certificates.
2015-11-27 08:09:39 +00:00
<disableSparseFiles>false</disableSparseFiles>
test: Update test configs to latest format
2016-05-31 08:36:33 +00:00
<disableTempIndexes>false</disableTempIndexes>
Rename Repository -> Folder, Node -> Device (fixes #739)
2014-09-28 11:00:38 +00:00
</folder>
test: Update test configs to latest format
2016-05-31 08:36:33 +00:00
<folder id="¯\_(ツ)_/¯ Räksmörgås 动作 Адрес" label="" path="s12-2/" type="readwrite" rescanIntervalS="15" ignorePerms="false" autoNormalize="true">
Rename Repository -> Folder, Node -> Device (fixes #739)
2014-09-28 11:00:38 +00:00
<device id="I6KAH76-66SLLLB-5PFXSOA-UFJCDZC-YAOMLEK-CP2GB32-BV5RQST-3PSROAU"></device>
Generate ECDSA keys instead of RSA This replaces the current 3072 bit RSA certificates with 384 bit ECDSA certificates. The advantage is these certificates are smaller and essentially instantaneous to generate. According to RFC4492 (ECC Cipher Suites for TLS), Table 1: Comparable Key Sizes, ECC has comparable strength to 3072 bit RSA at 283 bits - so we exceed that. There is no compatibility issue with existing Syncthing code - this is verified by the integration test ("h2" instance has the new certificate). There are browsers out there that don't understand ECC certificates yet, although I think they're dying out. In the meantime, I've retained the RSA code for the HTTPS certificate, but pulled it down to 2048 bits. I don't think a higher security level there is motivated, is this matches current industry standard for HTTPS certificates.
2015-11-27 08:09:39 +00:00
<device id="MRIW7OK-NETT3M4-N6SBWME-N25O76W-YJKVXPH-FUMQJ3S-P57B74J-GBITBAC"></device>
Update test configs to v11
2015-08-14 12:19:43 +00:00
<minDiskFreePct>1</minDiskFreePct>
Integration tests with API key
2014-06-05 09:48:22 +00:00
<versioning></versioning>
Data race: ProgressEmitter (debug output only)
2014-11-29 21:51:13 +00:00
<copiers>1</copiers>
<pullers>16</pullers>
Add renames to integration tests
2014-12-20 23:12:12 +00:00
<hashers>0</hashers>
Don't start model until services have been added (fixes #1969)
2015-06-20 18:04:47 +00:00
<order>random</order>
Update test configs to v11
2015-08-14 12:19:43 +00:00
<ignoreDelete>false</ignoreDelete>
Update test configs to modern v0.12 defaults
2015-10-22 06:06:17 +00:00
<scanProgressIntervalS>0</scanProgressIntervalS>
<pullerSleepS>0</pullerSleepS>
<pullerPauseS>0</pullerPauseS>
Include maxConflicts -1 in test configs
2015-10-19 13:09:54 +00:00
<maxConflicts>-1</maxConflicts>
Generate ECDSA keys instead of RSA This replaces the current 3072 bit RSA certificates with 384 bit ECDSA certificates. The advantage is these certificates are smaller and essentially instantaneous to generate. According to RFC4492 (ECC Cipher Suites for TLS), Table 1: Comparable Key Sizes, ECC has comparable strength to 3072 bit RSA at 283 bits - so we exceed that. There is no compatibility issue with existing Syncthing code - this is verified by the integration test ("h2" instance has the new certificate). There are browsers out there that don't understand ECC certificates yet, although I think they're dying out. In the meantime, I've retained the RSA code for the HTTPS certificate, but pulled it down to 2048 bits. I don't think a higher security level there is motivated, is this matches current industry standard for HTTPS certificates.
2015-11-27 08:09:39 +00:00
<disableSparseFiles>false</disableSparseFiles>
test: Update test configs to latest format
2016-05-31 08:36:33 +00:00
<disableTempIndexes>false</disableTempIndexes>
Rename Repository -> Folder, Node -> Device (fixes #739)
2014-09-28 11:00:38 +00:00
</folder>
test: Update test configs to latest format
2016-05-31 08:36:33 +00:00
<folder id="s23" label="" path="s23-2/" type="readwrite" rescanIntervalS="15" ignorePerms="false" autoNormalize="true">
Generate ECDSA keys instead of RSA This replaces the current 3072 bit RSA certificates with 384 bit ECDSA certificates. The advantage is these certificates are smaller and essentially instantaneous to generate. According to RFC4492 (ECC Cipher Suites for TLS), Table 1: Comparable Key Sizes, ECC has comparable strength to 3072 bit RSA at 283 bits - so we exceed that. There is no compatibility issue with existing Syncthing code - this is verified by the integration test ("h2" instance has the new certificate). There are browsers out there that don't understand ECC certificates yet, although I think they're dying out. In the meantime, I've retained the RSA code for the HTTPS certificate, but pulled it down to 2048 bits. I don't think a higher security level there is motivated, is this matches current industry standard for HTTPS certificates.
2015-11-27 08:09:39 +00:00
<device id="MRIW7OK-NETT3M4-N6SBWME-N25O76W-YJKVXPH-FUMQJ3S-P57B74J-GBITBAC"></device>
Rename Repository -> Folder, Node -> Device (fixes #739)
2014-09-28 11:00:38 +00:00
<device id="373HSRP-QLPNLIE-JYKZVQF-P4PKZ63-R2ZE6K3-YD442U2-JHBGBQG-WWXAHAU"></device>
Update test configs to v11
2015-08-14 12:19:43 +00:00
<minDiskFreePct>1</minDiskFreePct>
Integration tests with API key
2014-06-05 09:48:22 +00:00
<versioning></versioning>
Data race: ProgressEmitter (debug output only)
2014-11-29 21:51:13 +00:00
<copiers>1</copiers>
<pullers>16</pullers>
Add renames to integration tests
2014-12-20 23:12:12 +00:00
<hashers>0</hashers>
Don't start model until services have been added (fixes #1969)
2015-06-20 18:04:47 +00:00
<order>random</order>
Update test configs to v11
2015-08-14 12:19:43 +00:00
<ignoreDelete>false</ignoreDelete>
Update test configs to modern v0.12 defaults
2015-10-22 06:06:17 +00:00
<scanProgressIntervalS>0</scanProgressIntervalS>
<pullerSleepS>0</pullerSleepS>
<pullerPauseS>0</pullerPauseS>
Include maxConflicts -1 in test configs
2015-10-19 13:09:54 +00:00
<maxConflicts>-1</maxConflicts>
Generate ECDSA keys instead of RSA This replaces the current 3072 bit RSA certificates with 384 bit ECDSA certificates. The advantage is these certificates are smaller and essentially instantaneous to generate. According to RFC4492 (ECC Cipher Suites for TLS), Table 1: Comparable Key Sizes, ECC has comparable strength to 3072 bit RSA at 283 bits - so we exceed that. There is no compatibility issue with existing Syncthing code - this is verified by the integration test ("h2" instance has the new certificate). There are browsers out there that don't understand ECC certificates yet, although I think they're dying out. In the meantime, I've retained the RSA code for the HTTPS certificate, but pulled it down to 2048 bits. I don't think a higher security level there is motivated, is this matches current industry standard for HTTPS certificates.
2015-11-27 08:09:39 +00:00
<disableSparseFiles>false</disableSparseFiles>
test: Update test configs to latest format
2016-05-31 08:36:33 +00:00
<disableTempIndexes>false</disableTempIndexes>
Rename Repository -> Folder, Node -> Device (fixes #739)
2014-09-28 11:00:38 +00:00
</folder>
Update integration test configs to v10
2015-03-21 14:40:00 +00:00
<device id="I6KAH76-66SLLLB-5PFXSOA-UFJCDZC-YAOMLEK-CP2GB32-BV5RQST-3PSROAU" name="s1" compression="metadata" introducer="false">
Update test configs to v12
2015-08-20 07:38:47 +00:00
<address>tcp://127.0.0.1:22001</address>
Rename Repository -> Folder, Node -> Device (fixes #739)
2014-09-28 11:00:38 +00:00
</device>
Generate ECDSA keys instead of RSA This replaces the current 3072 bit RSA certificates with 384 bit ECDSA certificates. The advantage is these certificates are smaller and essentially instantaneous to generate. According to RFC4492 (ECC Cipher Suites for TLS), Table 1: Comparable Key Sizes, ECC has comparable strength to 3072 bit RSA at 283 bits - so we exceed that. There is no compatibility issue with existing Syncthing code - this is verified by the integration test ("h2" instance has the new certificate). There are browsers out there that don't understand ECC certificates yet, although I think they're dying out. In the meantime, I've retained the RSA code for the HTTPS certificate, but pulled it down to 2048 bits. I don't think a higher security level there is motivated, is this matches current industry standard for HTTPS certificates.
2015-11-27 08:09:39 +00:00
<device id="MRIW7OK-NETT3M4-N6SBWME-N25O76W-YJKVXPH-FUMQJ3S-P57B74J-GBITBAC" name="s2" compression="metadata" introducer="false">
Update test configs to v12
2015-08-20 07:38:47 +00:00
<address>tcp://127.0.0.1:22002</address>
Rename Repository -> Folder, Node -> Device (fixes #739)
2014-09-28 11:00:38 +00:00
</device>
Update integration test configs to v10
2015-03-21 14:40:00 +00:00
<device id="373HSRP-QLPNLIE-JYKZVQF-P4PKZ63-R2ZE6K3-YD442U2-JHBGBQG-WWXAHAU" name="s3" compression="metadata" introducer="false">
Update test configs to v12
2015-08-20 07:38:47 +00:00
<address>tcp://127.0.0.1:22003</address>
Rename Repository -> Folder, Node -> Device (fixes #739)
2014-09-28 11:00:38 +00:00
</device>
cmd/syncthing, lib/config: Enable HTTP CPU/heap profile collection for users This adds a config to enable debug functions on the API server, which is by default disabled. When enabled, the /rest/debug things become available and become available without requiring a CSRF token (although authentication is required if configured). We also add a new endpoint /rest/debug/cpuprof?duration=15s (with the duration being configurable, defaulting to 30s). This runs a CPU profile for the duration and returns it as a file. It sets headers so that a browser will save the file with an informative name. The same is done for heap profiles, /rest/debug/heapprof, which does not take any parameters. The purpose of this is that any user can enable debugging under advanced, then point their browser to the endpoint above and get a file that contains a CPU or heap profile we can use, with the filename telling us what version and architecture the profile is from. On the command line, this becomes curl -O -J http://localhost:8082/rest/debug/cpuprof?duration=5s curl: Saved to filename 'syncthing-cpu-darwin-amd64-v0.14.3+4-g935bcc0-110307.pprof' GitHub-Pull-Request: https://github.com/syncthing/syncthing/pull/3467
2016-08-02 11:06:45 +00:00
<gui enabled="true" tls="false" debugging="true">
Integration tests with API key
2014-06-05 09:48:22 +00:00
<address>127.0.0.1:8082</address>
<apikey>abc123</apikey>
test: Update test configs to latest format
2016-05-31 08:36:33 +00:00
<theme>default</theme>
Integration tests with API key
2014-06-05 09:48:22 +00:00
</gui>
Fix integration test
2014-03-14 09:39:37 +00:00
<options>
test: Update test configs to latest format
2016-05-31 08:36:33 +00:00
<listenAddress>dynamic+https://relays.syncthing.net/endpoint</listenAddress>
Update test configs to v12
2015-08-20 07:38:47 +00:00
<listenAddress>tcp://127.0.0.1:22002</listenAddress>
New global discovery protocol over HTTPS (fixes #628, fixes #1907)
2015-09-20 13:30:25 +00:00
<globalAnnounceServer>default</globalAnnounceServer>
Update test configs to modern v0.12 defaults
2015-10-22 06:06:17 +00:00
<globalAnnounceEnabled>false</globalAnnounceEnabled>
Fix local announce (IPv6 multicast, include all listen addresses)
2014-03-18 16:51:55 +00:00
<localAnnounceEnabled>true</localAnnounceEnabled>
Update test configs to modern v0.12 defaults
2015-10-22 06:06:17 +00:00
<localAnnouncePort>21027</localAnnouncePort>
Change default IPv6 multicast address (fixes #2090)
2015-08-23 12:59:38 +00:00
<localAnnounceMCAddr>[ff12::8384]:21027</localAnnounceMCAddr>
test: Fix test config
2016-11-09 01:00:22 +00:00
<maxSendKbps>0</maxSendKbps>
Upgrade integration test configs
2014-09-16 21:03:18 +00:00
<maxRecvKbps>0</maxRecvKbps>
Fix integration test
2014-03-14 09:39:37 +00:00
<reconnectionIntervalS>5</reconnectionIntervalS>
Update test configs to v12
2015-08-20 07:38:47 +00:00
<relaysEnabled>true</relaysEnabled>
<relayReconnectIntervalM>10</relayReconnectIntervalM>
Fix integration test
2014-03-14 09:39:37 +00:00
<startBrowser>false</startBrowser>
test: Update test configs to latest format
2016-05-31 08:36:33 +00:00
<natEnabled>true</natEnabled>
<natLeaseMinutes>0</natLeaseMinutes>
<natRenewalMinutes>1</natRenewalMinutes>
<natTimeoutSeconds>10</natTimeoutSeconds>
Update test configs to modern v0.12 defaults
2015-10-22 06:06:17 +00:00
<urAccepted>-1</urAccepted>
<urUniqueID></urUniqueID>
<urURL>https://data.syncthing.net/newdata</urURL>
<urPostInsecurely>false</urPostInsecurely>
<urInitialDelayS>1800</urInitialDelayS>
Upgrade integration test configs
2014-09-16 21:03:18 +00:00
<restartOnWakeup>true</restartOnWakeup>
Upgrade test configs to v6
2014-10-18 18:37:15 +00:00
<autoUpgradeIntervalH>12</autoUpgradeIntervalH>
<keepTemporariesH>24</keepTemporariesH>
test: Update test configs to latest format
2016-05-31 08:36:33 +00:00
<cacheIgnoredFiles>false</cacheIgnoredFiles>
Data race: ProgressEmitter (debug output only)
2014-11-29 21:51:13 +00:00
<progressUpdateIntervalS>5</progressUpdateIntervalS>
Update test configs to v7
2014-12-02 21:05:15 +00:00
<symlinksEnabled>true</symlinksEnabled>
test: Fix test config
2016-11-09 01:00:22 +00:00
<limitBandwidthInLan>false</limitBandwidthInLan>
Update test configs to v11
2015-08-14 12:19:43 +00:00
<minHomeDiskFreePct>1</minHomeDiskFreePct>
test: Update test configs to latest format
2016-05-31 08:36:33 +00:00
<releasesURL>https://upgrades.syncthing.net/meta.json</releasesURL>
<overwriteRemoteDeviceNamesOnConnect>false</overwriteRemoteDeviceNamesOnConnect>
<tempIndexMinBlocks>10</tempIndexMinBlocks>
Fix integration test
2014-03-14 09:39:37 +00:00
</options>
</configuration>
Reference in New Issue Copy Permalink