Browse Source
			
			
			
			
				
		We also need to validate the note sizes on key-rotation. If we do not validate them before we store them, that could lead to a partial or total loss of the password vault. Validating these restrictions before actually processing them to store/replace the existing ciphers should prevent this. There was also a small bug when using web-sockets. The client which is triggering the password/key-rotation change should not be forced to logout via a web-socket request. That is something the client will handle it self. Refactored the logout notification to either send the device uuid or not on specific actions. Fixes #3152pull/3164/head
							committed by
							
								 Daniel García
								Daniel García
							
						
					
				
				 3 changed files with 30 additions and 8 deletions
			
			
		
					Loading…
					
					
				
		Reference in new issue