Thank you for your kind explanation
I hope there's only good things in your future.
James
2020년 4월 1일 (수) 오전 6:42, Jaeger, Michael C. 님이
작성:
> Hello,
>
>
>
> thanks for reaching out to us. To your questions:
>
>
>
> *) is source code leaking out from a fossology server? Answer:
>
>
>
>1.
On Tue, 2020-03-31 at 21:42 +, Michael C. Jaeger wrote:
Hello,
thanks for reaching out to us. To your questions:
*) is source code leaking out from a fossology server? Answer:
1. Usually not , the fossology solution is entire self contained. You can
run fossology entirely without acc
Hi,
I’m not opening an issue because I suspect this is to do with my
install, not a general issue.
Still, this is a big failure for me, and I would love it if
someone could help me out.
I’m on:
Version: [3.7.0], Branch: [HEAD], Commit: [#193515] 2019/12/12
07:29 UTC built @ 2019/12/12 08:48 U
Hi Matija,
I don't know for certain if this is the problem you're seeing, but I see
some files in your log with .eot and .otf extensions.
There is a known problem with Fossology in that it fails to correctly
unpack or handle .eot and .otf files. See:
https://github.com/fossology/fossology/issues/
Hi,
I am not sure how the creation of a self signed certificate as part of the
installation of the FOSSology software improves the situation.
From a technical point of view, of course, we could even add a self signed
certificate creation step in the post install operations. But, for most cases,
On Wed, 2020-04-01 at 18:25 +, Jaeger, Michael C. wrote:
Hi,
I am not sure how the creation of a self signed certificate as part of the
installation of the FOSSology software improves the situation.
Well, in Debian, the self-signed "snake oil" cert can get you up and running
with https quic
Hi,
Please go ahead, sound good in general, just allow me to understand the cases
here
* either we add a 127.0.0.1 / snakeoil certificate and then there will be an
error message in the browser that hostname does not match the cert when
accessing the fossology over the network (server setup)
*
Hello,
right, now I remember too, frankly I did not see it at first sight.
And if I remember correctly, the problem with this one is that we do not have a
good lib for parsing / understanding true type / open type font files.
I think currently, the workaround is to remove these files from your
On Wed, 2020-04-01 at 18:52 +, Michael C. Jaeger wrote:
Hi,
Please go ahead, sound good in general, just allow me to understand the cases
here
* either we add a 127.0.0.1 / snakeoil certificate and then there will be an
error message in the browser that hostname does not match the cert when
Hi,
for all contributions:
* it would be good have an issue, I have created one:
https://github.com/fossology/fossology/issues/1676
* consider open a PR here, you can do this from your fork:
https://github.com/fossology/fossology/pulls
* a help with contributing guidelines is here:
https://git
Hello,
we have a new solution for hosting a test instance, infrastructure cost was
a unresolved for a long time, even a very small instance in the Internet costs
some money.
Now, thanks to the Linux Foundation and the OSU Open Source Lab (OSU: Oregon
State University, https://osuosl.org) th
11 matches
Mail list logo
