From f57a9a5bb8f7c8bf28f91a44c227b1ba34c055b5 Mon Sep 17 00:00:00 2001
From: Jan Vykopal <98724@mail.muni.cz>
Date: Wed, 13 Nov 2019 09:34:15 +0000
Subject: [PATCH] Known issues updated

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index f26aae4..7a1ffa9 100644
--- a/README.md
+++ b/README.md
@@ -87,9 +87,9 @@ The name of the correct network interface can be different for every box. The su
 - other VirtualBox attributes
 - more complex routing
 
-### Known [issues](https://gitlab.ics.muni.cz/cs4eu/sandbox-creator/issues?label_name%5B%5D=known_issue):
+### Known [issues](https://gitlab.ics.muni.cz/cs4eu/sandbox-creator/issues?scope=all&utf8=âś“&state=all&label_name[]=known_issue):
 - After running on Windows the output may contain invalid multibyte chars.
-- Vagrant can somtimes get stuck on "SSH auth method: private key". This is probably an issue of VirtualBox. This was observed using the box generic/debian10 on some computers. In this case try to create the machine again.
+- Vagrant up can somtimes get stuck on "SSH auth method: private key" in case of "generic/debian10" box or on "SSH auth method: password" in case of "kalilinux/rolling-light" box. This is probably an issue of VirtualBox. In this case try to create the machine again. In case of "kalilinux/rolling-light" remove the line `device.ssh.password = "vagrant"` from the generated Vagrantfile and try to bring it up again.
 - On some machines ansible local (flag -l) can get stuck while connecting to the created virtual machine.
 
 ### Notes
-- 
GitLab