View Issue Details

IDProjectCategoryView StatusLast Update
0001812Kali LinuxGeneral Bugpublic2018-01-29 13:40
Reporterjukkapach1Assigned Tog0tmi1k  
PriorityhighSeveritymajorReproducibilityunable to reproduce
Status closedResolutionsuspended 
Product Version1.0.9 
Summary0001812: Can't login to OpenVAS after upgrade
Description

After upgrading today (apt-get update, apt-get upgrade) it seems that OpenVAS has been upgraded to version 7. Unfortunately I can not login to the Web GUI anymore receiving "Login failed."

Additional Information

Versions:
OpenVAS Scanner 4.0.2
OpenVAS Manager 5.0.2
Greenbone Security Assistant 5.0.1

It seems the user accounts have been migrated to the database.

I tried "openvasmd --migrate" and "openvasmd --rebuild" without any effort. Even changing users passwords from the console did not solve the issue.

Relationships

duplicate of 0001757 closedg0tmi1k Can't login to OpenVAS after upgrade 

Activities

pepelegal

pepelegal

2014-10-19 18:41

reporter   ~0002660

Last edited: 2014-11-03 18:25

Same issue here.
Running Kali 32 bits on a VMWare.
Unable to use Nexpose because it works only for 64 bit OS.

pepelegal

pepelegal

2014-11-02 12:51

reporter   ~0002677

Possible solution: https://forums.kali.org/showthread.php?23394-OpenVas-Solution

CygnusTM

CygnusTM

2014-11-03 20:57

reporter   ~0002684

The problem seems to be that some OpenVAS packages in the repo require libopenvas7, but there remain two, gsd and openvas-administrator, that still require libopenvas6. The update process removes libopenvas6 in favor of libopenvas7 and removes gsd and openvas-administrator along with it, breaking OpenVAS.

rhertzog

rhertzog

2014-11-03 22:15

administrator   ~0002685

Both gsd and openvas-administrator are obsolete components. The new openvas metapackage conflicts with "gsd" so it should be dropped on upgrade. And it should probably be dropped from the repository alltogether.

openvas-administrator has been merged in openvas-manager and the new openvas-manager conflicts and replaces the old package which should also be dropped on upgrade too.

But I doubt that this has anything to do with the problem reported here. It looks more like some bad database migration when switching from v6 to v7.

g0tmi1k

g0tmi1k

2015-06-19 10:40

administrator   ~0003421

Duplicate: https://bugs.kali.org/view.php?id=1757

g0tmi1k

g0tmi1k

2018-01-29 13:40

administrator   ~0008315

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling 2016.x), these legacy versions are no longer supported.
We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux - https://www.kali.org/downloads/)?

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing,and also give information about your setup?
For more information, please read: https://kali.training/topic/filing-a-good-bug-report/

Issue History

Date Modified Username Field Change
2014-10-14 11:11 jukkapach1 New Issue
2014-10-14 11:11 jukkapach1 Issue generated from: 0001757
2014-10-19 18:41 pepelegal Note Added: 0002660
2014-11-02 12:51 pepelegal Note Added: 0002677
2014-11-03 18:25 pepelegal Note Edited: 0002660
2014-11-03 20:57 CygnusTM Note Added: 0002684
2014-11-03 22:15 rhertzog Note Added: 0002685
2014-11-21 20:03 haider Issue cloned: 0001896
2015-06-19 10:40 g0tmi1k Note Added: 0003421
2018-01-26 12:05 g0tmi1k Relationship added duplicate of 0001757
2018-01-29 13:40 g0tmi1k Assigned To => g0tmi1k
2018-01-29 13:40 g0tmi1k Status new => closed
2018-01-29 13:40 g0tmi1k Resolution open => suspended
2018-01-29 13:40 g0tmi1k Note Added: 0008315