I found a picture online: https://beta.techcrunch.com/wp-content/uploads/2010/07/q6uvf.jpg
and had an idea: I wanted to play around with DRM on .wmv and .wma files
I don't want to decrypt DRM content or strip DRM out of a file (because I don't have any files with that)
I want to encrypt a file create a license server, and then decrypt that using Windows Media Player (like that picture describes but with my own files and server)
I read on Wikipedia: https://en.wikipedia.org/wiki/Windows_Media_DRM
that I need Windows Media Rights Manager SDK to package content and create licenses
I found that some documentation on how to use that here: https://blogs.msdn.microsoft.com/mediasdkstuff/2008/09/26/wmrm-sdk-10-1-2-best-practice-sample-code/
but the page is disabled and IA doesn't have any snapshot of it
So does anyone have that SDK with some sample code (the language the sample code is in does not matter but C# would be nice)
Thanks for Anwsering and Best Regards
Related
I work with angular 7
I'm looking for a viewer which open the most extension files like : pdf,image,word,powerpoint...
and the most important thing this viewer contain the signature feature.
I try to use pdftron viewer but it has a problem with signature feature ( can not be saved ) ad has problem with word document
I try also with pspdfkit but it open only pdf document.
can someone help me to find a viewer which open more than
one extension and has a signature feature
I’m part of the PSPDFKit for Web team. Our solution supports signatures and we have an online demo available to try at https://web-examples.pspdfkit.com/signatures. We are actively working on and will be supporting server side conversion of MS Office files to PDF this year, so you would be able to handle those files as well when launched.
We will be happy to answer any question you have at https://support.pspdfkit.com/hc/en-us/requests/new
In our application, I am trying to play a stream through the TPasLibVlcPlayer component (http://prog.olsztyn.pl/paslibvlc/). I succeeded in doing this, but only when VLC is installed.
The goal is to deploy the needed dll's with our application so we can use our application on a (Windows) pc that doesn't have VLC installed.
Question is: what do I need to do to make this work? So far I tried to put
libvlc.dll
libvlccore.dll
in a separate folder and deinstall VLC, then set the path to these dll's
PasLibVlcPlayer1.VLC.Path := 'C:\Tools';
However when trying to play the stream, nothing happens. I debugged and saw that the libvlc.dll is loaded (a handle is returned) and the needed procedures could be executed (GetProcAddress returns an assigned addres for all supported procedures), however when libvlc_new is called (inside TPasLibVlc.GetHandle), this returns nil.
Should there be other dll's in that directory or what do I need to do to make this work?
VLC is not a monolithic program.
VLC is a complex framework of different classes plugins and the database of those plugins, and the dispatcher to build the interconnected network of those plugins for every particular task like converting or playing a given source.
VLC is in the same league like GStreamer or Direct X ( the DirectShow/DirectMedia subpart of it ). Can you use Direct X framework without installing Direct X ? Hardly so.
Even the AceStreamer project that aims to turn BitTorrent into p2p online video streaming platform and is being coding it for few years already they still did not "copied few libraries" from VLC but rather modified its soures and made their own build of VLC player to use with their P2P-to-streaming proxy daemon. After all the years and with all the experience they had and gained.
Granted, VLC being Linux-originating is not dependent upon Windows means of installing, so if that is okay for your goal, you can install VLC in VLC terms but avoid installing it in Windows terms. To do it you would have to
take the zip (not exe) distro of the VLC (win32 or win64 - should be the same as your program platform).
create a folder where you would unpack the whole VLC to
after unpacking you would have to run vlc-plugins-cache-generator so it would enumerate all the plugins and create the database of its classes and implementations
then you would have to ensure all those files can be read and executed by mere user. Your installation would almost surely run under UAC-elevated Administrator permissions. That means by default all the unpacked VLC file including plugins DB would not be reachable by non-elevated or non-admin users of the computer. You would have to fix it explicitly giving users the rights to read/execute those files.
Then you would be able to call VLC functions from DLLs in that folder.
But personally I think the candles are not worth the game here and you better give your users the freedom to use VLC as they see fit and to upgrade it when new versions would be issued. Otherwise your program would most probably turn into a source of security problems for them.
Above points were made from a purely technical point of view. But there is another issue - legal.
Are you even going to DISTRIBUTE your program outside your office? As soon as you would pass any rights to your program from the original rights holder to a licensee - you would have to respect VLC team rights.
http://www.videolan.org/legal.html - note that little "most" word, when VLC team describe status of smaller software projects they integrate into VLC.
As long as you redistribute the non-modified VLC installation bundle - you are clean and safe. VLC team gave you explicit permission to do so. If anyone would consider VLC bundle having some pirated or otherwise illegal code - you are somewhat protected by "I did not know, I merely trusted them they do play fair" defence line. You are acting like a consumer when taking VLC installer for granted. Like a person who purchased a car in a shop. If later it would be revealed the shop was illegal and was selling hijacked cars - you would loose that car, but at least you would not go to jail yourself.
However as soon as you would make your own VLC packages containing selected parts of VLC you become VLC co-developer. You gain those "four freedoms" of FLOSS, but any freedom comes with responsibility. Now if "intellectual property" vultures would come to you, you would no more say "VLC did it", no. From this point it is YOU who did it.
And if some FLOSS project would claim VLC pirated their code (chances are very tiny, but hypothetically that is possible too, complex FLOSS project are assembled from hordes different small works (from libraries to snippets and bugfix patches) with different initial licenses, and it is responsibility of maintainer (that means now - of YOU) to check or negotiate re-licensing compatibility), you would be co-responsible for it after you abandon standard ready-made bundle.
And then there come that very "virus nature" of strict GPL license. When you use standard installer package you do not mix your code with VLC code. You just put several different installers into one media and you only use APIs explicitly published to be consumed by other software. But if you would rehash VLC into your own streamlined set of files - from that point on you are a co-developer not a consumer any more. So chances are one day you would be asked to disclose the sources of your application because you use LGPL/GPL sources of VLC and your program now should be distributed under the same terms, otherwise your distribution of VLC maybe become piracy, maybe not, you are free to stand for your point of view in public trial.
Would you like it ?
Those concerns do not apply to you in two cases:
You do not DISTRIBUTE your program, you only use it in-house. Then GPL/LGPL responsibilities are not affecting you, and for "intellectual properties" vultures you are mostly under radars.
You use standard unmodified VLC bundle as it is made by VLC team. Then you are not bound by GPL/LGPL either and any vultures would have to fight with the VLC team first before they may come to you claiming VLC is illegal software.
If those cases do not suit you then you want to become a co-developer of VLC and thus you do accept all the responsibilities of it. Just for small space gain. Are you ready for it? Are the candles worth the game?
When I was learning Portable Executable (PE) file format for windows, tools like PE-Explorer and PEView helped me in learning things quickly and nicely. Now, I need to learn and understand the apple quick time file format. Are there any
Tools with which I can browse the quick time format?
Export sections of the file?
Any additional resources other than the specifications?
PS: I'm on windows and I don't have mac/macOS
Tools with which I can browse the quick time format?
On Windows you can use MP4 Explorer, and since it is open source you can also learn from it. Since MP4 uses a similar structure to QuickTime you can use it for both.
There is also the old Dumpster tool from Apple. There is an old version of this tool for Windows, but I could not find it in the Apple developer site. This forum post has a copy that you can try. This is very old though, I'm not sure if it'll work with recent QT files.
If you can obtain access to a Mac running OS X, then you can use Dumpster or Atom Explorer.
Export sections of the file?
I don't know of any public tool for this. Your best bet is to extend MP4 Explorer to do this, or write your own parser. Parsing the atoms is actually pretty simple, things start to get complicated when you need to interpret the content of the atoms and cross-reference them to, for example, locate where the frame data is.
Any additional resources other than the specifications?
The QuickTime file format specification is the best resource for Apple generated QuickTime files, but you may need to do some reverse engineering, as the spec is not very complete in some areas, like the handling of MPEG-2 and MPEG-4 video. If you have access to ISO specs, then ISO/IEC 14496-12 is a standardized version of the QuickTime format (or better said, of a subset of it). The ISO/IEC 14496-15 specification builds on top of 14496-12 and defines a specific implementation of this format for the H.264 format. This is the so called MP4 format.
With the above three documents you should be pretty good in terms of documentation.
The MPEG4 (.MP4) file format is based on the QuickTime file format. You should be able to use the MPEG4IP tools to examine .MOV files. You can find windows binaries here.
Media Box Viewer does exactly this and much more. In addition to Quicktime, it can also open mp4, 3gp, etc. It runs on all platforms, Windows, Mac, Linux, etc.
It can be downloaded from www.jdxsoftware.org.
I need to add a PDF reader that reads a PDF document from a URL to my Blackberry Playbook app. Is it possible?
The PlayBook will come with Adobe Reader, so you shouldn't have to add anything else.
In principle, using QNXApplication.qnxApplication.openFile('myfile.pdf') should be sufficient to open that file in Reader.
None of this has been documented yet by RIM so you will have to wait at least until the release of the 1.0 SDK (expected prior to the tablet shipping, but maybe not by much) to learn more.
Creating a ruby on rails site that uses RMagick to create thumbnails for many types of images. RMagick cannot read dwg files however.
I've tried a few things, looked into the Java library JDWGLib, which would probably allow me to write a converter, but it would be a total from the ground up solution, where I just need a thumbnail.
Also considered using a viewer program to open the file in a remote X session and do a screen capture, however I'm not sure how I could ever guarantee that the viewer had completed opening when I took the screenshot.
I'm not concerned with being able to manipulate the file other than to create the thumbnail. It is going to be used for commercial purposes, so any libraries used need to be compatible.
cad2svg is a simple Linux command-line utility that automatically converts AutoCAD files (both dwg and dxf) to SVG.
the link
I could not find any command-line-able tool for making thumbnails, on either windows or linux.
I guess you could download the DWGdirect lib (C++) wich allows the exportation of a DWG to a bitmap... but this requires purchasing a membership license on the """Open""" Design Aliance.
I would recommend adding an additional file input on your form that says "thumbnail". And let the users provide the screenshots.