Christian Fischer comments

Results 39 comments of


                                            Christian Fischer

Authoritative Evidence from Vendor

> hey do not intend to fix this at this time This could be reviewed again now that https://github.com/openssh/openssh-portable/pull/194 has been merged in https://github.com/openssh/openssh-portable/commit/197e29f1cca190d767c4b2b63a662f9a9e5da0b3

CSV Hosts filtered report contains wrong data when Overrides are applied

@greenbone/gvm-dev Please move / transfer this issue to https://github.com/greenbone/gvmd as this isn't an issue in GSA. But not even sure if this is an issue at all or if only...

CSV Hosts filtered report contains wrong data when Overrides are applied

@bitmind : > gsa: 8.0.0 > gvm: 8.0.0 > openvas-scanner: 6.0.0 Looks like outdated components as well: https://community.greenbone.net/t/gvm-10-old-old-stable-initial-release-2019-04-05/208 Please update to more recent versions and try again to make sure...

[20.8.0] failure during pg_upgrade from PostgreSQL 12 to 13 because of removed sql_next_time & valid_db_resource_type functions

I don't think this is the issue. I have noticed something similar while upgrading vom PostgreSQL 12 to 13 and it was caused by having the postgresql-12 development files still...

[20.8.0] failure during pg_upgrade from PostgreSQL 12 to 13 because of removed sql_next_time & valid_db_resource_type functions

Could be a different issue then the one i had faced. But note that the problem on my side was also seen while running pg_upgrade, and this only happened during...

[20.8.0] failure during pg_upgrade from PostgreSQL 12 to 13 because of removed sql_next_time & valid_db_resource_type functions

Any chances that you're building from the 20.08.0 tag? I guess it might be possible that this was already fixed in the (not released yet 20.08.1) with https://github.com/greenbone/gvmd/pull/1251 At least...

[20.8.0] failure during pg_upgrade from PostgreSQL 12 to 13 because of removed sql_next_time & valid_db_resource_type functions

Unfortunately i'm not familiar with that stuff but maybe @timopollmeier or @mattmundell can say something about that. Also cc @bjoernricks for the patch releases as i don't have any insights...

[20.8.0] failure during pg_upgrade from PostgreSQL 12 to 13 because of removed sql_next_time & valid_db_resource_type functions

Just for the records, the issue i had faced / described in https://github.com/greenbone/gvmd/issues/1339#issuecomment-718718098 was indeed something different. Just had upgraded a second installation giving the following below which is caused...

libgvm util g_message end up in stdout

> with the following gvm_log.conf: Is this a typo or have you really tried to configure this in a `gvm_log.conf`? Because there is no such file in GVM, only the...

Feed sync

Note that the deprecated / old `greenbone-nvt-sync` has been now removed completely in the scanner with / since greenbone/openvas-scanner#1589 so some adjustments to this PR might be required.