Potential GPL Violation

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1938870438==
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigDE20F4B5E8A179BB08ADA522"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigDE20F4B5E8A179BB08ADA522
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I found a project that appears to use various GPL components. I saw some
interesting strings on the binaries, but they explain it in their own
site (and on a file):

http://www.kmplayer.com/forums/showthread.php?t=3D141

It does include a verbatim copies of the GPL and LGPL, but there's no
way to obtain the source code, and I got no response from it's authors.

This is a big issue. There's an article talking about this in the site,
but it's in korean so I can't read it...

When replying to a mailing-list please CC me.


--------------enigDE20F4B5E8A179BB08ADA522
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkrAdrAACgkQ/mxY0+yOXJrq0gCgmGvvyUjNldlyKEPDSrmpZl7R
VRMAnRhLwPubktUfQjw/ZVgGVLmB1VgO
=3rdI
-----END PGP SIGNATURE-----

--------------enigDE20F4B5E8A179BB08ADA522--

--===============1938870438==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MPlayer-dev-eng mailing list
[email protected]
https://lists.mplayerhq.hu/mailman/listinfo/mplayer-dev-eng
--===============1938870438==--