SpiderOakONE 歷史版本列表 Page1

更新時間：2019-09-04
更新細節：

更新時間：2019-09-04
更新細節：

What's new in this version:

SpiderOakONE 7.5.1 (64-bit)
- Change log not available for this version


SpiderOakONE 7.4.0 (64-bit)
- Change log not available for this version


SpiderOakONE 7.3.0 (64-bit)
- Disable LAN sync by default
- Limit length for email on signup
- Only show currently backed up folders when setting up Sync
- Remove preview generator
- Improve settings UX by making preferences show in a more consistent way
- Force TLSv1.2 method for TLS connections in Windows


SpiderOakONE 7.2.0 (64-bit)

Changes:
- Add notice for data storage
- Normalize naming conventions
- Calculate space usage in a more efficient way

Bug Fixes:
- Fix sync bug where the client reports that it can’t find a journal
- (Groups only) Fix icons in dashboard for policy enforcement


SpiderOakONE 7.1.0 (64-bit)

Changes:
- Command line help improved/updated
- Manpage improved/updated
- Backup file/directory deselection behavior improved
- Update Hive icon branding
- Restart no longer required when changing size/age file restrictions.

Bug Fixes:
- Prevent unicode related sync issues
- Prevent preferences from freezing under certain conditions


SpiderOakONE 7.0.1 (64-bit)
- Updated SSL certificate pins based on CA changes in spideroak.com


SpiderOakONE 7.0.0 (64-bit)

Features:
- Redesign of the UI

Bug Fixes:
- Fix support links
- Fix for edge case where files can become 0 bytes in syncs
- --purge-historical-versions improvements
- Removable media detection improvements
- Fix an issue that was causing the client to get stuck at “Calculations pending” state


SpiderOakONE 6.4.0 (64-bit)
Bug fixes:
- Language improvements
- Made CDM on Windows more robust
- Implemented secure unsharing
- Added High Sierra support


SpiderOakONE 6.3.0 (64-bit)
Our team recently investigated and resolved three bugs reported by security researchers at Aarhus University (Denmark) in April 2017. The following bugs were fixed:
1. bcrypt login scheme memory leak - This leak happened only at setup and was a bug in the third-party library SpiderOak uses; this bug leaked memory to the server. We didn't validate the parameters set by the server, which allowed the SpiderOak server to weaken the strength of the password hashing. We patched the third-party library and validated the parameters to address this issue.
2. escrow/challenge - This bug only applied to end-users of the SpiderOak Groups product. It was discovered that an end-user could be unintentionally tricked by the client into revealing their password to the server. The design could also result in the client transmitting the user's password unencrypted. A lot of the problem here was confusion caused by poor wording on SpiderOak's end around Fingerprints, which could have caused a user to unintentionally reveal their password to SpiderOak. To address this bug, we now validate the keys and updated the confusing text in the application.
3. Remote Procedure Call (RPC) - The client exposed two unsafe RPC methods, which could've been used to extract a user's password. The client had an option to enable remote diagnostics through which an additional unsafe remote procedure could have been exposed. This is a feature that was never implemented on SpiderOak's server so we've removed the offending code from the client.

更新時間：2019-08-11
更新細節：

更新時間：2019-07-22
更新細節：

更新時間：2019-04-02
更新細節：

What's new in this version:

Resolved Issues:
- Type.IsSubclassOf Performance Regression
- unhandled-exception-2.exe crashes crash reporting
- BinaryReaderTest.ReadBytesException and BinaryReaderTest.ReadCharsException fail on FullAOT+LLVM after hybrid suspend change
- recent string loading changes break big endian with mojibake
- Process.GetProcessesByName Memory Leak, Not Disposing Filtered Process Objects
- Generic with “unmanaged” constraint crashes runtime
- ProductHeaderValue parser throws exception for empty values
- opt and llc missing from mono 2018-08 pkg
- [wasm] Make test.js use generated driver and bindings.
- Latest mono on macOS broke Xamarin Studio 5 compatibility: Marshal.SizeOf reports type 0x01 not handled
- Mono issuing SIGSEGV running C# Semantic Tests
- Native crash when debugging with exception watchpoint
- FullAOT LLVM Linux x64 one flaky failure.
- [ WASM ]Build fail host error
- [iOS] CalendarTest.Hijri and CalendarTest.UmAlQura fail
- mono_thread_info_exit ignores exit_code and just passes 0 on.
- iOS cannot save Entity models with Nullable Guid (Guid?) property types (among others) using EF Core 2.1.2.
- HttpWebRequest throws an uncatchable task exception when processing requests simultaneously with timeout specified
- Update CI build scripts to not hardcode -j4
- Wrong characters in decimal number representation on s390x
- Many scary “Your mono runtime and class libraries are out of sync” mono warnings when building for device
- [wasm] Stop using mmap for loading assemblies
- [wasm] Rename sdks WebAssembly framework libraries
- [wasm] Build fails - ninja can not be found.
- mono64[80780:1186894] error: * Assertion: should not be reached at debugger-agent.c:6619
- mono_jit_init on macOS 10.14 has graphics corruption due to mprotect invocation
- Error loading generic override of in parameter
- Possible GC hang while building msbuild with mono/2018-08 and mono/master
- Type.IsSubclassOf throws TypeLoadException
- Hybrid suspend: mono_add_internal_call is broken
- Unhandled exception at the end of MonoDevelop.UnitTesting.Tests test run
- Mac installer does not always clear out old files
- SDK ‘Microsoft.NET.Sdk.Razor’ not found
- ParameterInfo.[Raw]DefaultValue returns Missing.Value for non-null default values of DateTime? and decimal? parameters
- Unexpected behaviour of DateTime.ToString with Korean language on iOS/Android
- [WASM AOT] Method returning a ValueType is not returning its value as a value
- HttpClient requests not cancelled in Dispose()
- [XA] [2018-10] Failure in PropertyInfoTests.GetValue_Invalid
- Loading assembly generated using tlbimp.exe give error in mono runtime
- IronPython 2.7.9 strange issue on mono 5.16
- AOT crash: error: * Assertion: should not be reached at ../../../../../mono/mini/mini-arm64-gsharedvt.c:119
- watchOS: mini test failure in release mode: JitTests.Aot : System.Reflection.TargetInvocationException
- os-event-unix.c:82 assert(event) failure
- [iOS/32bit/device] mscorlib test failures: DoubleFormatterTest.TestFormatStringsN# and DoubleTest.LongLongValueRoundtrip
- MethodInfo.ReturnParameter.IsDefined(type) throws IndexOutOfRangeException
- [watchOS] MT3001: Could not AOT the assembly mscorlib.dll
- Crash while profiling roslyn compiler server
- FastCopy may silently fail to do anything
- Problem with DefaultValueAttribute and Color values
- Task calls SynchronizationContext.Post on cancelling
- ReflectionModelServices.IsExportFactoryImportDefinition should not throw
- xtro-sharpie.exe crashes with “Cannot transition thread 0x10c3ef5c0 from STATE_BLOCKING with DO_BLOCKING”
- System.Reflection.Emit.ParameterBuilder.SetCustomAttribute() throws undocumented ArgumentOutOfRangeException
- [iOS] Generic sharing with long float arguments list
- MonoDevelop SDB regressions
- Bug in TextRenderer.DrawText on Linux
- Calling TcpListener.Create(int port) on multiple threads can fail
- Mono mkbundle output executable throws: “Error mapping file: No error”
- struct with 3 bytes not marshaled correctly with LLVM on watchOS
- GetCustomAttributes on a type from an assembly in the LoadFile context fails
- Memory leak in HttpWebRequest / HttpWebResponse when using a WebProxy
- Starting process with empty ProcessStartInfo.Environment incorrectly inherits all variables
- Error when debugging
- Mono to SQL Server using integrated security no longer works on iOS
- WaitHandle.WaitAny returns invalid result
- SslStream.AuthenticateAsClient throws wrong exception types
- Mono.Unix.Native.Syscall.sys_strerror_r SEGFAULT on musl libc
- flaky runtime.finalizer-exception.exe (Assertion at unwind.c:640, condition `cfa_reg != -1’ not met)
- Update macOS minimal version
- Behaviour difference between Mono and CoreCLR
- iOS: 32-bit device unit test failure: [FAIL] FSharpTest.SprintfTest : Expected: True
- tests/src/baseservices/threading/readerwriterlockslim/upgrader.cs CoreCLR acceptance-test fails
- WASM: Use BrowserHttpMessageHandler when available
- System.Reflection.Assembly.LoadFile should throw ArgumentException for relative path name
- AOT images compiled with safepoints should be usable with MONO_THREADS_SUSPEND=preemptive
- cross build regressed wrt System.Native and “shm_open that works well enough with mmap”
- Update framework facades list used by loader
- SynchronizedCollection.Add throws an ArgumentOutOfRangeException

更新時間：2019-03-16
更新細節：

更新時間：2019-03-14
更新細節：

更新時間：2019-02-15
更新細節：

What's new in this version:

SpiderOakONE 7.5.0 (64-bit)
- Change log not available for this version


SpiderOakONE 7.4.0 (64-bit)
- Change log not available for this version


SpiderOakONE 7.3.0 (64-bit)
- Disable LAN sync by default
- Limit length for email on signup
- Only show currently backed up folders when setting up Sync
- Remove preview generator
- Improve settings UX by making preferences show in a more consistent way
- Force TLSv1.2 method for TLS connections in Windows


SpiderOakONE 7.2.0 (64-bit)

Changes:
- Add notice for data storage
- Normalize naming conventions
- Calculate space usage in a more efficient way

Bug Fixes:
- Fix sync bug where the client reports that it can’t find a journal
- (Groups only) Fix icons in dashboard for policy enforcement


SpiderOakONE 7.1.0 (64-bit)

Changes:
- Command line help improved/updated
- Manpage improved/updated
- Backup file/directory deselection behavior improved
- Update Hive icon branding
- Restart no longer required when changing size/age file restrictions.

Bug Fixes:
- Prevent unicode related sync issues
- Prevent preferences from freezing under certain conditions


SpiderOakONE 7.0.1 (64-bit)
- Updated SSL certificate pins based on CA changes in spideroak.com


SpiderOakONE 7.0.0 (64-bit)

Features:
- Redesign of the UI

Bug Fixes:
- Fix support links
- Fix for edge case where files can become 0 bytes in syncs
- --purge-historical-versions improvements
- Removable media detection improvements
- Fix an issue that was causing the client to get stuck at “Calculations pending” state


SpiderOakONE 6.4.0 (64-bit)
Bug fixes:
- Language improvements
- Made CDM on Windows more robust
- Implemented secure unsharing
- Added High Sierra support


SpiderOakONE 6.3.0 (64-bit)
Our team recently investigated and resolved three bugs reported by security researchers at Aarhus University (Denmark) in April 2017. The following bugs were fixed:
1. bcrypt login scheme memory leak - This leak happened only at setup and was a bug in the third-party library SpiderOak uses; this bug leaked memory to the server. We didn't validate the parameters set by the server, which allowed the SpiderOak server to weaken the strength of the password hashing. We patched the third-party library and validated the parameters to address this issue.
2. escrow/challenge - This bug only applied to end-users of the SpiderOak Groups product. It was discovered that an end-user could be unintentionally tricked by the client into revealing their password to the server. The design could also result in the client transmitting the user's password unencrypted. A lot of the problem here was confusion caused by poor wording on SpiderOak's end around Fingerprints, which could have caused a user to unintentionally reveal their password to SpiderOak. To address this bug, we now validate the keys and updated the confusing text in the application.
3. Remote Procedure Call (RPC) - The client exposed two unsafe RPC methods, which could've been used to extract a user's password. The client had an option to enable remote diagnostics through which an additional unsafe remote procedure could have been exposed. This is a feature that was never implemented on SpiderOak's server so we've removed the offending code from the client.

更新時間：2019-01-21
更新細節：

What's new in this version:

In Depth
- General: Due to limitations in the TLS stack on 10.7 we are updating the minimum macOS development target from 10.7 to 10.9. Mono will be supported only on 10.9 or newer versions starting with this release.

Runtime
- AOT: Few hard to track race conditions in trampolines unboxing for AOT backend targetting amd64 were fixed.
- Interpreter: The interpreter received the first set of low-level optimizations, improving the execution time of typeof call by the factor of 10. Further changes were made to avoid unnecessary allocations and support Xamarin native types (nint/nuint).
- Custom Marshalers: The logic handling custom marshalers, types implementing IICustomMarshaler has been mostly rewritten in managed code with additional caching mechanisms to match .NET Framework behaviour.
- Optimizations: The intrinsics built on top of SSE41 for Math.Round/Math.Floor/Math.Ceiling were added.
- Windows: Mono Windows cross-compiler is using the same LLVM release branch as Linux resolving issues in scenarios where llvm-config.exe can’t be run (none WSL/CygWin build target).

Class Libraries
- CoreFX convergence: In this release, more CoreFX code was imported in particular in System.Reflection namespace. Many common types in mscorlib System namespace are now fully CoreFX based including System.Math. The Registry implementation on Windows is now fully based on CoreFX implementation.
- Mono.Options: A new CommandSet.GetCompletions() method was introduced, which returns all possible commands which match a given completion prefix. This is intended for e.g. bash completion support.
- System.Runtime.InteropServices: It’s now possible to use RuntimeInformation API to detect ARM and ARM64 platforms.

Tools
- MSBuild: Reference assemblies for .NET 4.7.2 are included to allow targeting .NET Framework 4.7.2 using MSBuild on Mono.

更新時間：2018-12-03
更新細節：

What's new in this version:

SpiderOakONE 7.4.0 (64-bit)
- Change log not available for this version


SpiderOakONE 7.3.0 (64-bit)
- Disable LAN sync by default
- Limit length for email on signup
- Only show currently backed up folders when setting up Sync
- Remove preview generator
- Improve settings UX by making preferences show in a more consistent way
- Force TLSv1.2 method for TLS connections in Windows


SpiderOakONE 7.2.0 (64-bit)

Changes:
- Add notice for data storage
- Normalize naming conventions
- Calculate space usage in a more efficient way

Bug Fixes:
- Fix sync bug where the client reports that it can’t find a journal
- (Groups only) Fix icons in dashboard for policy enforcement


SpiderOakONE 7.1.0 (64-bit)

Changes:
- Command line help improved/updated
- Manpage improved/updated
- Backup file/directory deselection behavior improved
- Update Hive icon branding
- Restart no longer required when changing size/age file restrictions.

Bug Fixes:
- Prevent unicode related sync issues
- Prevent preferences from freezing under certain conditions


SpiderOakONE 7.0.1 (64-bit)
- Updated SSL certificate pins based on CA changes in spideroak.com


SpiderOakONE 7.0.0 (64-bit)

Features:
- Redesign of the UI

Bug Fixes:
- Fix support links
- Fix for edge case where files can become 0 bytes in syncs
- --purge-historical-versions improvements
- Removable media detection improvements
- Fix an issue that was causing the client to get stuck at “Calculations pending” state


SpiderOakONE 6.4.0 (64-bit)
Bug fixes:
- Language improvements
- Made CDM on Windows more robust
- Implemented secure unsharing
- Added High Sierra support


SpiderOakONE 6.3.0 (64-bit)
Our team recently investigated and resolved three bugs reported by security researchers at Aarhus University (Denmark) in April 2017. The following bugs were fixed:
1. bcrypt login scheme memory leak - This leak happened only at setup and was a bug in the third-party library SpiderOak uses; this bug leaked memory to the server. We didn't validate the parameters set by the server, which allowed the SpiderOak server to weaken the strength of the password hashing. We patched the third-party library and validated the parameters to address this issue.
2. escrow/challenge - This bug only applied to end-users of the SpiderOak Groups product. It was discovered that an end-user could be unintentionally tricked by the client into revealing their password to the server. The design could also result in the client transmitting the user's password unencrypted. A lot of the problem here was confusion caused by poor wording on SpiderOak's end around Fingerprints, which could have caused a user to unintentionally reveal their password to SpiderOak. To address this bug, we now validate the keys and updated the confusing text in the application.
3. Remote Procedure Call (RPC) - The client exposed two unsafe RPC methods, which could've been used to extract a user's password. The client had an option to enable remote diagnostics through which an additional unsafe remote procedure could have been exposed. This is a feature that was never implemented on SpiderOak's server so we've removed the offending code from the client.