Still no support from Eziriz :(
ColinA
still haven't heard a single thing about the FIPS mode issue I
outlined here:
http://groups.google.com/group/net-reactor-support/browse_thread/thread/bfc520e03f4d2dbe
In my first email to Eziriz I even suggested a possible code solution
(obviously guessing on the internals of .NET Reactor, based on the
error message I get in FIPS mode). If .NET Reactor won't use a FIPS-
compliant encryption algorithm (a FIPS-compliant AES module does ship
with the .NET Framework), then I am unable to use it at all.
Denis has posted here a few times, so...
...Denis, Eziriz, please - I'd really appreciate some support with
this problem
Thanks,
Colin
ColinA
*nothing* from Eziriz :(
On May 27, 10:22 pm, ColinA <colin.ander...@akersolutions.com> wrote:
> Despite sending emails to Eziriz going back to the 19th of May, I
> still haven't heard a single thing about the FIPS mode issue I
> outlined here:
>
Andrew McKay
Andrew
--
You received this message because you are subscribed to the Google Groups ".Net Reactor Support" group.
To post to this group, send email to net-react...@googlegroups.com.
To unsubscribe from this group, send email to net-reactor-sup...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/net-reactor-support?hl=en.
Munawar Bijani
months or so. Last I heard from them, they were caught up with "life" at the
moment. This was back in March I believe. My license expired in March so I'm
not able to upgrade to the newest version, and this is one of the reasons
I'm not upgrading. Reactor 4.1.30 works fine for me and based on all the
bugs and stuff I've been seeing on this list, I don't think 4.4 is a good
buy. It does everything I need it to anyway.
I hope you do get a response from Eziriz soon--if not, and you have just
recently purchased Reactor, you may be entitled to a refund. Check your
receipt Email sent from Eziriz's processing company and there will be a link
there to open up an issue. I did this and Eziriz did eventually respond to
me. My issue had to do with LicenseGen.dll not running on Mono under Linux
like Eziriz claimed. They did send me quick dll update and it worked, so I
really hope you can get your problem solved soon. I know how frustrating it
is when you depend on a company for your lock and intellectual property
rights' protection and that company doesn't respond to support requests.
Munawar A. Bijani
BPCPrograms, LLC
http://www.bpcprograms.com
muna...@gmail.com
-----Original Message-----
From: ColinA
Sent: Wednesday, June 01, 2011 5:08 AM
To: .Net Reactor Support
Subject: Re: Still no support from Eziriz :(
--
ColinA
sent...
...still zero support of any kind from Eziriz :-/
I like the software, but I'm coming to the conclusion that this guy is
a swindler...
On Jun 1, 10:08 am, ColinA <colin.ander...@> wrote:
> Just a quick update - 13 days and 5 emails later, and I've still heard
> *nothing* from Eziriz :(
>
Ivan Borges
ColinA
On Jun 13, 5:11 pm, Ivan Borges <iva...@gmail.com> wrote:
> Have you tried calling him?
>
> Phone (+49)01520/9461592
> Normal Office Hours: 8:30am-6:00pm Germany (GMT + 01:00)
>
> On Mon, Jun 13, 2011 at 12:41 PM, ColinA
Glen Harvy
ColinA
more inclined to believe it if I'd ever had so much as a _single
response_ to the support queries I've raised. I reckon he's quite
happy to wheel out new versions every now and then, but has little or
no intention of providing support - he should say so, rather than
giving the impression that customers are purchasing a supported
product.
As an aside, I've been trialling another product, Babel, as it looks
increasingly likely that I'll need to write off my investment in
Reactor. It looks like Eziriz doesn't care about his customers, and
really can't be bothered to even respond, let alone fix problems.
Anyway, it turned out that Babel had the same problem as Reactor has,
whereby it doesn't work in FIPS mode. I contacted the author, and
included the code required to fix it (as I did with Eziriz). I had a
response within the hour, and he sent me a beta version that included
the fix within 12 hours! _That's_ good service.
Munawar Bijani
I'm glad you found a different product. This is how Eziriz USED TO be until
about six months ago. As I've said before it's also what stopped me from
upgrading to Reactor what is it, 4.4? It's buggy, and Eziriz isn't really
doing anything about it--4.1 works fine.
Munawar A. Bijani
BPCPrograms, LLC
http://www.bpcprograms.com
muna...@gmail.com
-----Original Message-----
From: ColinA
Sent: Tuesday, June 14, 2011 2:52 AM
To: .Net Reactor Support
Subject: Re: Still no support from Eziriz :(
--
SdB
singing "Dennis Moore Dennis Moore ...." rather than Eziriz is
responding to support request.
I did not upgrade to the latest version and now and then comment on my
Eziriz support experiences.
Stefan de Buhr
ColinA
sent...
...and I've still heard _nothing_ from Eziriz :-/
I think I'll keep this thread going, posting updates every now and
then... will be interesting to see it I'm still saying I haven't got
any support in 2012 ;)
Up to Eziriz I suppose...
Glen Harvy
You should be aware that Denis rarely visits this forum and he has no
obligation to either. Posting an update every month or so will perhaps
serve some purpose but won't result in your getting any support any quicker.
If you have a specific problem, you should post your question in the
hope that someone can help you fix the problem.
As far as getting Denis to answer your support requests, I suggest you
send him regular follow up emails as that will have more chance of success.
Regards,
Glen Harvy.
ColinA
does. I would have thought however that he certainly does have an
obligation to provide customer support through the official channels
(email and telephone).
Customers and prospective customers do however visit this group -
perhaps I can shame Eziriz into providing support, and if not I
suppose this thread should at least serve as a warning for others.
My specific problem is posted here:
http://groups.google.com/group/net-reactor-support/browse_thread/thread/bfc520e03f4d2dbe
I don't believe anyone but Eziriz can help - this is something that
needs to be fixed in .NET Reactor by using the FIPS-compliant
cryptography algorithms that ship with the .NET framework, rather that
the non-FIPS compliant ones.
Since May I have sent Eziriz 10 emails on this specific subject, with
each being ignored. I'll continue to send emails and will report here
periodically.
As an aside, just after I initially purchased .NET Reactor I had a
query regarding 64-bit assemblies - I sent Eziriz several mails on the
subject, as well as trying him on the phone, and eventually gave up.
As I've said before, I like the software - but I guess I feel somewhat
cheated on the support side of things, and feel I should be more
persistent this time around (especially since this FIPS issue is a
complete show stopper for me).
Glen Harvy
do are not necessarily the same. I see no reason why the US Government
should have any more rights than the Australian Government when it comes
to reading encrypted data and I'm sure many countries/citizens feel the
same. Eziriz is after all German.
I have just had a quick look at the Eziriz web site and I cannot see
anywhere where FIPS is claimed to be supported however I could be wrong.
I have no idea how important this is to you, nor at what point you
discovered this but generally speaking, under Australian law, you may be
entitled to a full cash refund. I suggest to you that you pursue that
alternative and possibly keep us up-to-date on your progress on that
front rather than wait and hope that they add FIPS as (hopefully) yet
another option for me to make sure is not selected.
With regard to lack of support - I agree. But Eziriz is not alone in
this lack of support area. InstallAware for example sells it's product
for thousands of dollars and NO support is included in the base price.
So you pay a couple of thousand dollars and need to use a free bulletin
broad system for support! Perhaps Denis should advertise his support
'policy' more openly.
With regard to the 64bit issue, I have used .Net Reactor without any
difficulty with x64 and suggest you start a separate thread on that item.
Best of luck ....
ColinA
government that wants FIPS support - customers elsewhere in the world
are actually running with FIPS mode enabled too.
I also didn't claim that Eziriz said anything about supporting FIPS
mode. .NET Reactor worked great for my previous requirements, and I
was quite happy with the product (though not the support). FIPS is a
new requirement for me (I didn't need this when I initially
purchased), and my request to Eziriz was to ask if there was any way
to get it to work with FIPS mode (maybe there's a switch to enable use
of FIPS-compliant algorithms), or to add support for FIPS mode if not.
As I say, I even gave implementation clues as to how this could be
done - testing aside (and I realise that of course takes much longer),
it would take him 10 minutes. In any case it would take him 2 minutes
to bother responding to my emails.
I don't think it's 'good enough' to say "ah well, he's not the only
one that can't be bothered supporting customers" - I hardly think that
crap support should form any kind of benchmark. We certainly agree on
one thing though - if he's not going to bother supporting customers,
he should say so.
My x64 issues were 'resolved' long ago - with zero support from
Eziriz, and from memory I ended up building for 'Any CPU', rather than
producing x64 assemblies, which .NET Reactor couldn't do at the time
(it may support it in later versions, I don't know).
As I already mentioned in this thread, I've started using Babel to
obfuscate my assemblies that use FIPS algorithms. Fantastic support,
and very well priced BTW :) I do however prefer .NET Reactor's
Necrobit, why is why I haven't given up my seemingly futile quest to
get some form of response from the ever elusive Eziriz :)
